Database Info

[Help] Xoom MZ601 stuck at bootanimation

Hey everyone, I need help for my Xoom 3G MZ601, I just rooted it and flashed EOS' rom and I'm stuck at bootanimation. I'm new to rooting and flashing custom roms for tablets, its different in phones.

When you say you are stuck, what have you tried to do? Have you tried to get back into your custom recovery? If you can, you could try to reflash your rom and gapps after wiping cache and dalvik cache. You would have your system wiped when you unlocked, but you could wipe again before reflashing...that might help.

Yes, I wiped everything, I did this 5 times and the same thing happens, stuck in bootanim.
okantomi said:
When you say you are stuck, what have you tried to do? Have you tried to get back into your custom recovery? If you can, you could try to reflash your rom and gapps after wiping cache and dalvik cache. You would have your system wiped when you unlocked, but you could wipe again before reflashing...that might help.
Click to expand...
Click to collapse

1. Do you have a backup of your stock rom? if you have a backup and recovery works you should be able to recover your stock system and everything will be allright.
2. If you don't have a backup enter this site motodev site (i can't post any links) download correct firmware for your device and flash every part of downloaded rom via fastboot.
I hope it will help you

It seems like your recovery img is the culprit, try downloading eos with goomanager..
try; adb reboot bootloader
fastboot flash recovery eos-recovery-r6.img http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6-softkeys.img or http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
adb reboot recovery

[Q] Flashing first ROM... is this normal?

I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.

dmccrack said:
I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.
Click to expand...
Click to collapse
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?

Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
SlimSnoopOS said:
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?
Click to expand...
Click to collapse

The ROM was downloaded via Goo.im app
dmccrack said:
Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
Click to expand...
Click to collapse

So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse

Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse
dmccrack said:
So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
Click to expand...
Click to collapse

dmccrack said:
Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
Click to expand...
Click to collapse
No problem. As for your issue, its fairly simple actually. What you need to do is a clean flash which is either of the two steps I listed earlier. You're trying to go from TW to AOSP but what you did was only wipe the cache then flashed the rom. Wiping cache and dalvik cache is regarded as a dirty flash, something you only do when flashing a newer version of the rom you're on. You never fully removed the TW rom before flashing Liquid which is why it did not boot. Basically, when you want to flash a new rom, by a different developer, you need to do 1 or 2 in order to have a successful flash.
For AOSP roms, you should also be flashing the recommended GApps (Google Apps) as well so that you have your Play Store and a few other Google Apps. The latest "generic" gapps zip is listed here at the top, its "20120301" which is March 1st. Liquid may have their own, that's for you to find out via their thread. Google apps are included in TW roms so this is not necessary.

Tried to inställning CM - stuck at boot (n8020)

Hi. Yesterday I succesdfully rooted my n8020 (galaxy note 10.1 LTE Swedish). Tho, when I tried to flash Sbiddens modded CM version, it failed. I wiped data/facto ry reset from CWM, wiped cache and Dalvik. Flashed CM and Gapps. Rebooted, only to get stuck at the blue-ring Cyanogenmod boot screen. Tried to redo all the steps in different orders, no succcess. Stillvstuck at boot.
Then came the puzzling part. I downloaded the original firmware from sammobile.com, and flashed it via Odin. It succeeded, bit whenbit booted in back to the standard rom, all my applications and all the data was intact! As I sevetal times wiped data/factory reset, I assumed thatevwrything would be gonw and that I'd have to install everythingnfrom scratch. Am I correct in assuming this, and may this be related to CM getting stuck at boot? Any hel greatly appreciated!

vargfloejt said:
Hi. Yesterday I succesdfully rooted my n8020 (galaxy note 10.1 LTE Swedish). Tho, when I tried to flash Sbiddens modded CM version, it failed. I wiped data/facto ry reset from CWM, wiped cache and Dalvik. Flashed CM and Gapps. Rebooted, only to get stuck at the blue-ring Cyanogenmod boot screen. Tried to redo all the steps in different orders, no succcess. Stillvstuck at boot.
Then came the puzzling part. I downloaded the original firmware from sammobile.com, and flashed it via Odin. It succeeded, bit whenbit booted in back to the standard rom, all my applications and all the data was intact! As I sevetal times wiped data/factory reset, I assumed thatevwrything would be gonw and that I'd have to install everythingnfrom scratch. Am I correct in assuming this, and may this be related to CM getting stuck at boot? Any hel greatly appreciated!
Click to expand...
Click to collapse
Bump

vargfloejt said:
Bump
Click to expand...
Click to collapse
I have seen something similar when I installed Cyanogenmod on a kindle fire, I had to do a factory reset after restoring back to stock firmware.
I would suggest that you try doing a factory reset after restoring factory firmware on your GNote.

Success with Philz recovery
Had the same problem loading onto my N8020.
In the end I used a different recovery and it worked first go.
Try using Phils recovery http://forum.xda-developers.com/showthread.php?t=2202714

[Completed] [Q] Stuck in recovery loop after using Rashr Flash Tool

Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
So I was in the process of manually installing CWM Touch via Rashr Flash Tool, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, whatever that app wrote into the androids system, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS. Even when I explicitly chose "reboot to bootloader" in CWM, it would still reboot to recovery. I've even went to a totally stock restore, and it still kept happening. Cleared cache, data, davik cache, same result. What can I do?
I currently have 2 restores. One of cyanogen, where i used Rashr's tool, and the other a V6 stock restore.

CartoonmanPDC said:
Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
So I was in the process of manually installing CWM Touch via Rashr Flash Tool, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, whatever that app wrote into the androids system, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS. Even when I explicitly chose "reboot to bootloader" in CWM, it would still reboot to recovery. I've even went to a totally stock restore, and it still kept happening. Cleared cache, data, davik cache, same result. What can I do?
I currently have 2 restores. One of cyanogen, where i used Rashr's tool, and the other a V6 stock restore.
Click to expand...
Click to collapse
Yes, restoring the last working nandroid backup would be an option.
Alternatively you may have to flash another recovery.
I found this guide to flash CWM recovery on a similar device: How to flash cwm recovery on the lg spectrum 2.
But I am not sure if it wil work for your device too.
So better ask in the General discussion > Questions and Answers forum.

Thread closed and thank you.

[Q] flashing from cm11 to 12 nightly then PA bootloop help needed

ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo

kanjo said:
ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo
Click to expand...
Click to collapse
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
EDIT: Exactly which thread are you getting these instructions from? Neither of the PA threads that I'm aware of contain those instructions.

Heisenberg said:
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
Click to expand...
Click to collapse
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.

kanjo said:
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.
Click to expand...
Click to collapse
Just to be clear, you've wiped system, data, cache, and dalvik cache directly before flashing PA? No CM flashes since wiping all of those partitions?
Also, which thread are you getting those install instructions from? Neither of the PA threads that I'm aware of contain those instructions.

ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
going to go back to twrp. wipe all data and flash PA again without gapps and without root. will report back in about 10 minutes. will flash by using TWRP and ADB sideload.
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom) at the moment i am trying to sideload PA rom after wiping data, system, cache and dalvik. is this why i am having the issue?
im dead tired so i admit i can be making mistakes though everything i have done seems to be what i am meant to do. flashed from cm11 to cm12, cleared all data, then flashed PA+gapps and root. = upgrading boot loop and errors mentioned above. tried flashing just PA and it booted with same errors, flashed gapps and errors.
all the files MD5s look good. not sure what is wrong.
--edit--
okay now i am at homescreen on PA.
when enabling/disabling adb in dev settings i get a reboot. is this normal now? does it need to reboot to mount the filesystem or something?
when it does boot after enabling adb i get "settings has stopped"
going to go to TWRP and flash GAPPS now and leave root not installed. will report back in a sec.

kanjo said:
ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
Click to expand...
Click to collapse
Please define wiped all data.
kanjo said:
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom)?
Click to expand...
Click to collapse
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.

Heisenberg said:
Please define wiped all data.
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.
Click to expand...
Click to collapse
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.

kanjo said:
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.
Click to expand...
Click to collapse
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.

Heisenberg said:
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.
Click to expand...
Click to collapse
balls, was hoping to us PA, haven't used it since my old s3 and figured it was the rom for me again. will have to check the rom comparison spreadsheet and look into others.
right now i have sideloaded PA alone. will copy PA and gapps to the internal storage to make things easier.
but it doesnt look like it is going to work for me.
going to try it once more like you said but locally rather than through sideload. though the internal storage is deciding when it does and doesnt want to show up.
TWRP
wipe system, cache, dalvik cache, and data.
and flash them both in tandem.
and for the fun of it when it asks if i want to install root i will let it go right ahead.
maybe this time it will work. if not then its a different rom for me. sadly.

okay so now **** got retarded. TWRP has been replaced by the stock cm11 recovery and i am too pissed off to think straight and cannot remember how to get this son of a ***** rooted again let alone to flash TWRP. i dont want to use any toolkits they all seem broken as hell.
can anyone point me in the right direction because ive just about lost my **** and this phone is going to meet my fist head on very shortly...
**edit**
done. after all this i am now on cm11 stock rooted ....seriously. hours upon hours, just to get back to where i started.
man i love when things go smoothly. anyway cheers for your help @Heisenberg . n