Database Users

Bootloop with any custom ROM

I will try to cover any info you might need. I am using windows 7, my phone had 1.5 originally 1.47 hboot. I got the 2.1 official ota.
On monday, I rooted using the pb00img.zip, loaded amon-ra 1.6.2, did factory/data wipe, dalvik wipe, flashed kaos v20, boot looped, tried v.19 with full and dalvik wipe, same.
I have tried all version of kaos from 19-23, evileris 3, celb, cyanogenmod 6. All have the same boot loop, I have done the following:
Reloaded the pb file
Reloaded amon-ra
Have tried manually wiping data and dalvik using adb shell
I have formatted my sd card through windows
I have partitioned my card through amon-ra
Here is a pastebin of my bootup.
http://pastebin.com/SMhKDYZq
The phone starts up with the 3 skateboarding droids, sits there for a bit, screen goes black, i get a little vibrate, then the 3 skaters come back, rinse and repeat.
I have dont have apps2sd, or setcpu. Any help would be greatly appreciated,

cdjadex said:
I will try to cover any info you might need. I am using windows 7, my phone had 1.5 originally 1.47 hboot. I got the 2.1 official ota.
On monday, I rooted using the pb00img.zip, loaded amon-ra 1.6.2, did factory/data wipe, dalvik wipe, flashed kaos v20, boot looped, tried v.19 with full and dalvik wipe, same.
I have tried all version of kaos from 19-23, evileris 3, celb, cyanogenmod 6. All have the same boot loop, I have done the following:
Reloaded the pb file
Reloaded amon-ra
Have tried manually wiping data and dalvik using adb shell
I have formatted my sd card through windows
I have partitioned my card through amon-ra
Here is a pastebin of my bootup.
http://pastebin.com/SMhKDYZq
The phone starts up with the 3 skateboarding droids, sits there for a bit, screen goes black, i get a little vibrate, then the 3 skaters come back, rinse and repeat.
I have dont have apps2sd, or setcpu. Any help would be greatly appreciated,
Click to expand...
Click to collapse
Did you ever create a nand backup? If so, go back to it first and verify you don't have a hardware issue.
If you don't have a backup, search this forum for the Eris RUU and I'd go back to that and root using the newest method...basically start over from a working phone.

I do have a nand backup, I have been restoring when i leave work because my phone has to be working. It works fine with the OTA 2.1 that i had just rooted...

have you tried doing full data wipe/dalvik wipe after flashing a rom when i first installed roms i didn't wipe anything for 2 or 3 roms but they all seemed to flash over eachother. but then i couldn't flash anything and i thought somehow i broke something. but then i just did a full wipe after a flash and started up like it should have. took a while the first boot but ever since then i haven't run into any issues

Sjflowerhorn said:
have you tried doing full data wipe/dalvik wipe after flashing a rom when i first installed roms i didn't wipe anything for 2 or 3 roms but they all seemed to flash over eachother. but then i couldn't flash anything and i thought somehow i broke something. but then i just did a full wipe after a flash and started up like it should have. took a while the first boot but ever since then i haven't run into any issues
Click to expand...
Click to collapse
I had this same issue last night, though I kept repeating the Nexus-style boot screen (the "X" thing) over and over. I did a full data/dalvik wipe and everything came up just fine. I had this experience with two different CyanogenMod ports.

Boot loop - rooted Iconia a500 in taboonay 2.1 HC3.2

After playing a youtube video, suddenly my tab reboot by itself, and it stuck in a boot loop.
I tried to wipe factory setting and cache, still the same problem occured. I even tried to reinstall the same rom, it still give the same problem.
When i tried to install other rom (My-Rom 1.0) it stucks on installing kernel.
i try to find any hint on the xda, brought me to this post
http://forum.xda-developers.com/showthread.php?t=1128565
it still unable to solve my problem. Hope anyone can help.

Try installing a different ROM, besides the two you installed, I had the same problem when I flashed HoneyVillain to Taboonay then to Lightspeed, I was stuck on a bootloop, couldn't flash back Taboonay, but was able to get HoneyVillain.

Still has the problem
I tried as you said, Installed honeyvillain 1.2 rom, and still has the same problem.
2 things which i realized is that,
1. there is sudden blink of loop screen that is different from boot loop that i have seen before.
2. there is error when i tried to do factory wipe
error moving data/data/com.estrong.android.pop/lib/libes_dropbox.so
hopefully anyone can help me

have you tried using acer recovery app to reinstal CWM, then use it to download just a basic 3.2 rom if possible and see how that goes

I am having the exact same problem error removing data/bluestacks, bootloops with little flashes in boot animation. tried every option in recovery and like 4 different back up restoration and the boot animation changes to that of the new restore but same thing.Help!!
thor's 13 then updated to 14 and this started

If you want, go to www.tegraowners.com . Thor's site. He made the recovery. If you go to his forums, Rom section, you will see he posted some steps to completely wipe internal memory. More than what the usual steps we take.
I suppose, there is some residual data left, which is why some errors are happening.
Also, any files named "update.zip", should be removed from SD.
Then you should be able to flash a new rom.
Here are the steps....
go to in recovery enter Backup and Restore and click on Toggle backup and restore of internal storage (/data/media)
should say enabled....
then go into Mounts and Storage and format /data
this will REALLY format data and you will loose all you have in the in the internal memory
then reinstall the rom and everything should work as expected....

im currently having this issue as of right now , idk wat the problem is
EDIT: and i cannot access CWM either

[Q] Stuck @ google logo

hi,
last day i flashed cyanogen 7.1 stable mod for defy.
it was working nicely
later on i wiped the system and and installed the backup of stock 2.2.2 using clockworkmod recovery, it also worked without any problems
again i wiped the system cache and installed cyanogen again ,but this time i got stuck at the cyanogen logo which comes in loop, so i flashed again but no positive
after that i entered into recovery mod and cleared the system cache and data
after this i got stuck at google logo,(still able to enter into default recovery mod, but i cannot enter into clockworkmod recovery)
plz help urgently
thanks

when this happened to me i had to flash a whole sbf to get things right.

exorz said:
when this happened to me i had to flash a whole sbf to get things right.
Click to expand...
Click to collapse
thanks
i will try it

i flashed stock froyo got from xda, back to normal
thanks thanks a lot
a million thanks

you're welcome. glad i could help out

Hi,
I am having the same problem.. I have followed the tutorial: http://wiki.cyanogenmod.com/wiki/Motorola_Defy:_Full_Update_Guide
With the only exception of this part:
On the computer, open terminal and run the following commands:
Code:
adb shell
su
cp -R /sdcard/bootmenu /data/bootmenu
For some reason the bootmenu directory was not present in the sdcard directory, so I created the directory myself and pushed the files for the bootloader 1 at a time (individually).
Everything goes well, until, after the installation, I reboot the phone. It stays on the Google logo. I have tried with and without the Google-Apps pack, but the result is still the same.
To get the phone back on track, I use the sbf file presented in this tutorial:
http://forum.xda-developers.com/showthread.php?t=1216982
Any idea on what is happening?
I have tried clearing the cache and factory settings, but to no avail as well.
I have also tried a nightly build, but this time it gets stuck on the Motorola logo... tired clearing cache and factory settings... no use.

A500 recovery stuck "loading recovery kernel image"

Hi awesome XDA dudes
I've searched the forums, and even posted in the basic QA section to no avail. I may have just missed it somewhere, but here is the issue.
Tablet will work fine in Lightspeed 4.8 ROM. No issue there. But, when I try to get into the recovery (power and volume down) I get "booting recovery kernel image," forever.
I recently changed from the Clockwork to TWRP recovery and that is when the recovery function would no longer load.
How can I get back to Clockwork or smililar so that I can put a different ROM on my tab?
Thanks in advance!
Tom

Fixed this problem, only to find another.
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:

SOLVED !!
tfbielawski said:
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:
Click to expand...
Click to collapse
Ok, so I had a working ROM but my recovery was fried. So, using Acer Recovery Installer I was able to get a working recovery going.
Then the next problem was that I could not get CM10 to install. When I realized I needed to flash the bootloader (and yes fellow noobs this is different than the recovery) I was unsuccessful.
I tried the automated route using the Blackthund3r app, but the process would just hang at Entering bootloader.
I tried the manual NVFlash route provided by Dibbs and it would get past this point and then hang.
So Dibbs (thanks dude) helped me out via email and suggested I download babsector.rar
After I extracted the rar file, I saw the A501 A.bat file and flashed it. This provided me with hope as it flashed the tablet and the screen atcually read "PASS." But, I wasn't done yet as I still could not install CM10. So, back to APX mode and back into the babsector rar folder. I flashed the Tab with A501 B.bat and followed that immediately with flashing the v8.bat file. In the V8.bet file I chose the Thor 1.7.3 recovery (as suggested by Dibbs and others) and WOOHOOO.....PASS on the tablet again.
Feeling ever more confident, I booted into recovery and flashed the CM10 Rom....SUCCESS!!!!!!!!!!!!!!!
If you are having trouble....don't give up. Thanks again for the help to Dibbs and OKAstro!!

[Q] Boot hangs at Android sign.

Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.

I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija

uglyjohny said:
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
Click to expand...
Click to collapse
I don't have access to a micro sd card reader if the file must be placed on the micro SD card. I already have flashed the stock rom supposedly via TWRP, so I shouldn't have to flash it again, I wouldn't think. If I do, I guess I'll have to get a reader.

Yes. Micro sd. Rename it. You have guodes gere on xda. Im hoping it will help you.
poslato sa elmag radija

It didn't work. Still in same state as before.

I also have access to fastboot if that would help.

m27frogy said:
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
Click to expand...
Click to collapse
Babsector should still work - you would need t do a search for it

It seems to have worked properly, sort of. Flashing FLEXReaper results in an "Encryption failed." prompt at boot, which the button, of course, does not work. Wiping everything works except that the prompt notes "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4" Trying to reflash V8 with TWRP with the V8.bat file fails at format. More help?

My tablet is still displaying "Encryption failed", the button still doesn't work, and I still love my a500. Help?
Anyone?

I guess I'm screwed, then.

In the end, I think my data partition failed. Formatting or wiping data fails and when installing FlexReaper, it reports /data size as -1. Unless anyone knows how to fix flash memory, I think I'm stuck.