General :: Allwinner A13 Tablet Stuck On Boot Screen?
Apr 20, 2014
I received a generic Chinese table. it worked well for about two-and-a-half months. Then, just recently, I discovered rooting and the wonderful things it allowed you to do. I decided to download a system-tweak app, which included a CPU control. I was a little wary of overclocking my CPU, having heard it may decrease its life expectancy, but finally I thought "What the heck?" and in a brilliant stroke of genius cranked my 1Ghz processor up to 1.5Ghz, and it promptly froze, forcing me to power it down. When I turned it back on, I discovered that it had been factory reset. I re-installed my apps, including the system-tweak app, and decided not to touch the CPU controls for a while. Soon after, while at my sister's talent show, I discovered I had about 30% battery life, and I was still supposed to record her. So I figured I'd underclock it to save the battery.
Unfortunately, as my finger touched the slider, my brother bumped my arm and caused me to lower the CPU frequency to its lowest setting. It became extremely sluggish, almost to the point of being unresponsive, and finally I had to shut it down. When I restarted it, it started to boot but then got stuck on the shimmering Android logo, and now that's all it does. I can't even boot into recovery mode, and unfortunately I had just turned off USB debugging that same day.
i have a allwinner a13 tablet that has gotten stuck in the process of opening. i had installed clockmodrecovery and uberizer. and was looking for a way to correct root 'permission" that kept coming up when trying to install programs that needed root access. then i messed up.
i was trying to restore factory when it froze. i cannot use buttons to enter recovery mode. i made a back up in uberizer but am unable to find .how to use. also since this is happened i cannot load any driver to recognize the tablet into windoes 7device manager.
Recently I have rooted my android tablet and I was exploring what I could do. One guy was telling me about an app that can work with performance in game(ChainFire 3D). He said it lowers the pixels in the game to run better. I tapped the install button and it said rebooting now. It then started to reboot but then proceeded to get stuck at the boot screen. I tried doing a hard reset but it is still stuck. I have also tried flashing the stock rom, but I get installation aborted when I try and install it.
i just bought a tuvva powerplay tablet..aka the game mid....it contains a rockchip 3066 cpu and 4 core gpu 400 ok iv been trying to flash custom roms on this for awhile..i never could..i got it rooted though..well then i heard of this thing called chainfire 3d thats supposed to improve fps...well i installed that tablet turned off...then it booted up with the logo..thats it..nothing more..i can enter the stock recovry..and my computers makes a bumpuda sound like its conntect..all i want to do is delete the dang chainfire thing..but i dont know how..iv tried using adp..
I want to get a custum recovery because I can't access to my recovery mode it shows a foto of a droid, I tried rebooting from rom manager app, and from the power and Vol+ .. but nothing works you can check the foto in the attachments.
Is CWM available for the Eken T01? I have posted this question several times on other boards and never got an answer either way. I just got this tablet and I have rooted it. However I would really like to make backups with CWM like I do with my phone because it has saved my butt more than once
- bought a Thomson QM734-8G tablet (Allwinner A13b clone), running Jellybean 4.2.2; - PC interface worked fine in MTP and large storage modes; - setup Android SDK & Java JDK on PC and communicate with tablet via ADB;
All OK so far..After a couple of days, I decided to replace stock recovery with ClockworkMod Recovery, so I could start messing about with the tablet.
I found the CWM 184.108.40.206 mod supposed to work with these tablets and, following instructions, determined it was indeed running on sun5i hardware and had 10 partitions (nandj) and downloaded the appropriate version.
I used ADB sideload to install CWM and everything appeared to work OK ... until I rebooted and found myself stuck in a never-ending cycle of CWM-based recovery bootloop.All I get is the CWM recovery console, with a few lines of error & the tablet will go no further.
E:can't mount /cache/recovery/command E:cant mount /cache/recovery/log E:cant open /cache/recovery/log E:cant mount /cache/recovery/last_log E:cant open /cache/recovery/last_log
CWM functions work properly and nothing will mount through the 'Mounts and Storage' section, although sideload mode still seems to work.Attempts to use ADB sideload to install a different CWM or other recovery image have all failed, and LiveSuit and PhoenixSuit both have issues detecting the tablet (despite trying various versions of each & following instructions precisely), so I can't flash a replacement ROM to fix things.
At the moment, I just want to rip CWM out and go back to factory recovery mode and have a working tablet again! I think the Bootloader is locked and the tablet is unrooted. Superuser or SuperSU don't want to install properly. However, using ADB, it looks like I can get root access in shell (#).
I have a generic Allwinner A13 7" tablet essentially identical to this one. The internal memory is set so that part of it is seen as internal, and part as a fake SD card mounted on /mnt/sdcard. Actual SD cards get mounted to /mnt/extsd.
I find this very annoying for a number of reasons, and would like all the internal memory to be seen as internal with no fake SD cards, and SD cards to be mounted to /mnt/sdcard. If this were one of those tablets capable of running Linux I'd run gparted and do the job from there, but it isn't.
Is there any way to merge the two internal memory partitions into just one?
I'm aware I can edit vold.fstab and invert the two mount points, and I'll keep it as a fallback solution, but I hate the idea of wasting a gig of useful internal space like that.
Tablet hangs in Bootloop after installed cm9_nightly_20120721 + protab2xxl_compatibility_1.2.0 startet from cwm 220.127.116.11. Noticed that the "/data" partition only has 15MB of Space with 0B Byte free. I wiped the cache after installation with cwm, i am not able to boot to cwm again because key combinations not work on this device.
Got a T15A Generic tablet which has the same Hardware than protab 2 xxl, Goclever A103, Coby 1042 etc..how to get CM9 or CM10 running?
I am trying to use my cheap virtually unbrickable tablet to learn more about kernel development and eventually ROM building.
I have extracted the manufacturers (WoPad) LiveSuit image and used split_bootimg.pl to break up the boot image.
I extracted the config file from the kernel image using extract-ikconfig and it created a config file. I didn't see the config in /proc.
So, I have the factory ramdisk and the factory kernel config.
I have downloaded several kernel sources (lichee-3.0.8, ChritianTroy's 3.0.36, and another one from linux-sunxi 3.0.72). I can successfully compile all of them without errors and they all generate zImages, uImages, etc using the factory config as well as the sun4i_crane configs they come with.
When I repack the boot.img with the newly created kernel and install it on nandc it wont' boot past the android icon (u-boot). When I compare my boot.img to the factory one, they both have the same offset where the kernel starts (0x00000800). I have also ensured I'm replacing the kernel modules when I'm changing kernel versions.
I own a Allwinner A13 7 inch tablet, on which I installed the Cyanogen 10 mod (Due to restrictions I cannot place the link to the mod)
The problem is I probably installed the wrong touchscreen driver, so the tablet boots perfectly into the Mod but I can't do anything. Normally it would be no problem to just put back my backup, but I can't get it to boot into CWM.
In the first place I rebooted into CWM to instal the mod by adding the following command through the "terminal app" before rebooting,
My Galaxy gio is rooted and is with a clockworkmod recovery. Yesterday, I tried to flash a custom kernel. After flashing successfully (through cwm recovery), i reboot my phone and then it stuck at boot screen.I did many searches but cannot understand any.I can go into recovery and download mode which is i think so required by odin.I wonder if I can flash any stock rom again easily. Need zip file with which i can put in sd card and install zip through cwm recovery by which i can unbrick my phone. I tried wipe data and factory reset but nothing worked.
I restarted my phone because it was freezing and it turned on on the boot screen where it gives me options to Recover, Reboot, etc. The volume button broke a long time ago. It sometimes works to move the option but pushing the power button doesn't do anything. Is there anything I can do to restart my phone avoiding this screen? It goes there every time. Could one of the volume buttons be stuck?
! i was trying to install a new custom ROM ( C.A.M.P ) i had Cyanogenmod 10... i came to where i flash the new rom on my computer then when i wanted to fastboot reboot to install zip on phone, my computer shuts off, now when i turn my phone on it lights up black and stays like this and i cant do anything(no CWM no nothing) so i remove battery to turn off....
My device is rooted, i was installing an app that tweaks performance which needed drivers to be downloaded / installed. As soon as i clicked that driver download / install button the device immediatly shut down. Now i'm stuck on its boot logo (Its a Chinese tablet powered by a RK3066 Chip / android 4.1.1) I tried (Holding power + volume down) = Dead android logo with red exc. mark on top / (Holding power + volume up) = Nothing / (Holding power + both volume up and down) = Dead android logo with red exc. mark on top / (Leaving dead android logo for a couple of minutes) = resets and logo is still stuck.
I have no custom anything . I did not do anything with the root except download apps.
I also do not have linux.
When the tablet is plugged into the PC when the dead android is displaying , it detects, but that is it, i cannot browse it what so ever.
All recovery methods in the tablet are (dead android logo)
Well rooted the i10 tonight fine went to install the play store and got force close on alot of stuff hit the reset button as the tablet forze and it boots but wont go past the impression screen then huts of
I have an android tablet (I'm not really sure what brand it is, but on the back it says m706b) that does not boot anymore.... it just sits at the "loading..." screen. Can I factory reset the device somehow?
I just installed the Android Revolution ROM for my phone, and I am now unable to get past the boot screen. I've been sitting here waiting for it to boot for 1/2 hour, before I took the battery out and tried booting again. Waited 1/2 hour again. Still no progress.
I had just made my phone S-OFF with SuperCID, and had flashed a new radio.img to my phone as recommended in the thread. After doing that, I went and used SuperWipe, and then I installed Android Revolution. Installation encountered no errors, so i was surprised when I was unable to boot.
I can still access 4ext recovery luckily.
EDIT: Wanted to point out that I was able to boot into my old rom after S-OFF, SuperCID and radio.img, but not after installing revolution rom.
Today my Huawei Ascend P1 got stuck on boot screen by itself, left it on the table and when I picked it up there was only a black screen with Huawei logo, and nothing else. I tried to turn it off - didn't work, tried pressing down button and power button, tried connecting it to the computer, but nothing seems to work, it's just stuck there and I didn't even do anything.
OK, one day I was able to open a Genymotion device, but later that day I wasn't. Reason?
When I opened a terminal (using CrunchBang Waldorf) and ran Genymotion, it would work fine, but then when I booted a Samsung Galaxy S4 4.3 , it would bring up the device fine, but it would get stuck on that "Android" screen, with the light going across.
I waited for a few hours, only to come back to the same message. I would open up the .Genymobile/genymotion-player.log using cat in terminal. The results?
I have an unlocked HTC Sensation and when i updated it when it was rebooting it got stuck at the htc screen for ages soo i took the battery out and now it gets stuck at the boot screen with the htc on it I Really am unclear
I was installing some custom ROMs on my brothers OT-955. Everything worked fine, I got CWM on there and installed a ROM called PAC [URL] ......
It worked pretty well, but the phone froze a couple of times a day so I decided to try some others yesterday. When I installed a CM-based ROM, I got a 'status 7' error in CWM and after I rebooted the phone was stuck in a boot loop.
After a while, it showed up when I ran `fastboot devices` and I was able to get it into recovery and install a different ROM. When that ROM had some trouble I ran into the same 'status 7' error with another one.
I miss-clicked and rebooted instead of installing a working ROM. Once again, I was able to reboot to recovery using fastboot and everything worked out.
Fast forward 30 minutes, the last ROM had some trouble too and I decided to move back to stock. CWM reported that stock was installed successfully so I rebooted.
Since then, the phone won't move past the boot screen. Fastboot doesn't recognize it, `adb` used to recognize it as offline until I replugged it.
I already:Reinstalled the device driver Cycled the power (empty, full) Tried a different host machine What to try next.
I just replaced my LCD and digitizer on my Nexus 4 after i dropped it and the screen cracked. It was still in working condition after the damage, but the touch screen was unresponsive. The installation went pretty smoothly but when I went to boot it up after it gets stuck at the bootup screen with the 4 bubbles. I tried some of the solutions people found for a similar problem a few months back when Google released Kit Kat 4.4 for the Nexus 4 but none of them have worked for me. There doesn't seem to be any hardware functionality issues, just some software glitch that I can't figure out.