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

Help me save my TF101

Well I dont think I totally screwed it up because I am able to get to the recovery but here is the scoop.
I decided I was going to root and install jellybean. So I used the 1 click method to root from [TOOL]"1-Click Transformer Root"-Root/Unroot/cwm/stock rec-TF101(G)/201/300T(G)/SL101 - xda-developers
I did the 1.1 verison. All went well tablet was rooted my stock rom still worked fine.
Then I went to flash jellybean rom which i did this one here v6.0 [ROM][JB][4.1.1] AOSP build #6.0.0 - xda-developers
Before i flashed i made a nand back up. and wiped all cache.
After install of RaymanFX's jellybean rom it got stuck after the splash animation.
I then tried to reflash it. Only to see the same result.
So I cleared all the cache again and ran the nand backup i made now i am stuck at asus splash screen.
Someone please tell me what i am missing.
Thank you in advance for any help.

Copy this ROM to your SDcard or MicroSD card, whichever one you used to hold the ROM the first time
http://downloads.timduru.org/android/tf101/eos4/EOS4.2.2-tf101-20130408_previewB190.zip
Copy these Gapps to the same place
http://goo.im/devs/teameos/roms/eos4/gapps/gapps_4.2.2_TF101_20130323b.zip
Copy this Kernel to the same place
http://downloads.timduru.org/android/tf101/K.A.T/kernel/Tim_KatKernel_102_JB4.2_Lidpatch.zip
Boot into Recovery, Wipe System, Cache and Dalvik Cache
Flash the ROM
Wipe Cache and Dalvik Cache only
Flash the Kernel
Wipe Cache and Dalvik Cache only
Flash Gapps
Wipe Cache and Dalvik Cache only
Reboot
All being well, you will boot into EOS4 (Jellybean 4.2.2)
Also, this tool is the best way to root / flash custom recovery and to unbrick
http://forum.xda-developers.com/showthread.php?t=1688012

[Q] CM11 - cannot get past the boot screen

Hi,
First, I followed the instructions in this guide: http://forum.xda-developers.com/showthread.php?t=2507905
I installed the CWM recovery and then flashed the CM11-20131228 nightly and then the recommended Google Apps that are linked at their wiki: http://wiki.cyanogenmod.org/w/Gapps#Downloads (I took the 20131208 ones)
Now my phone is stuck in the boot screen with the circle spinning around the cyanogenmod logo (I can boot the bootloader and recovery but when I try to boot CM11 it’s stuck) and I dont know how to get to a working cm11 rom. The guide said that the first boot with a new rom takes longer than usual because the phone rebuilds caches and so on but I think it should not take more than half an hour...
What I already tried is:
- Wiping the chaches with the CWM recovery an then booting cm11 -> still just the arrow spinning around the logo
- Wiping the caches with recovery and then re-flashing the same zip without flashing the google apps afterwards -> did not work
- Wiping and then pushing the newer cm11 nightly via adb so that I could try this one -> recovery did not find the pushed zip on my scdard
- Wiping, then tried to install the new nightly via adb sideload -> cmd prompt said it was send properly and as far as I can say the phone installed it but I was still stuck on that bootscreen ...
- I even restored to the stock 4.4.2 factory image and then flashed the cwm recovery, than wiped caches and then installed the latest cm11 nightly an then the google apps but I still can not get past the boot animation
What am I doing wrong and how can I get past the boot screen?

You talk about wiping caches but are you wiping data too?

Oh, yes. I just didnt mention it. I always did the three steps from the guide:
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache

BopItXtremeII said:
Oh, yes. I just didnt mention it. I always did the three steps from the guide:
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Click to expand...
Click to collapse
So you get the bootloop only when trying to install CM and when you flashed the factory image, it booted up fine?
Sent from my Nexus 5

Exactly.
I install the factory image with method 1 from this guide: http://forum.xda-developers.com/showthread.php?t=2513701 and then flash CWM recovery to install CM (factory reset + wipe cache + wipe dalvik cache + install cm-zip + install gapps-zip) and then there is the bootloop.

BopItXtremeII said:
Exactly.
I install the factory image with method 1 from this guide: http://forum.xda-developers.com/showthread.php?t=2513701 and then flash CWM recovery to install CM (factory reset + wipe cache + wipe dalvik cache + install cm-zip + install gapps-zip) and then there is the bootloop.
Click to expand...
Click to collapse
Did you check the md5 of the cm download?

BopItXtremeII said:
Exactly.
I install the factory image with method 1 from this guide: http://forum.xda-developers.com/showthread.php?t=2513701 and then flash CWM recovery to install CM (factory reset + wipe cache + wipe dalvik cache + install cm-zip + install gapps-zip) and then there is the bootloop.
Click to expand...
Click to collapse
Sometimes formatting all of the partitions (except the sd card) works.
Sent from my Nexus 5

jd1639 said:
Did you check the md5 of the cm download?
Click to expand...
Click to collapse
The md5 sum is the same as on the download page.
PhilipTD said:
Sometimes formatting all of the partitions (except the sd card) works.
Sent from my Nexus 5
Click to expand...
Click to collapse
Which partitions? boot, cache, recovery and system? Sorry, I'm new to android... And what do I have to install on these partitions after erasing them?

BopItXtremeII said:
The md5 sum is the same as on the download page.
Which partitions? boot, cache, recovery and system? Sorry, I'm new to android... And what do I have to install on these partitions after erasing them?
Click to expand...
Click to collapse
Flash the boot.img and reboot
Then see
Sent from my LT26i using xda premium

BopItXtremeII said:
The md5 sum is the same as on the download page.
Which partitions? boot, cache, recovery and system? Sorry, I'm new to android... And what do I have to install on these partitions after erasing them?
Click to expand...
Click to collapse
Wipe system, data, dalvik, and cache

jd1639 said:
Wipe system, data, dalvik, and cache
Click to expand...
Click to collapse
^^^^^^Precisely^^^^^^
Sent from my Nexus 5

I got another problem now ... The last thing I did was flashing the stock rom. Now I want to flash the latest CM nightly (20131229) but fastboot does not let me install cwm recovery and says
Code:
FAILED <remote: partition table doesn't exist>
I flashed the whole stock rom again but the error still occurs... I have to wipe the partitions after I installed CM, right?

BopItXtremeII said:
I got another problem now ... The last thing I did was flashing the stock rom. Now I want to flash the latest CM nightly (20131229) but fastboot does not let me install cwm recovery and says
Code:
FAILED <remote: partition table doesn't exist>
I flashed the whole stock rom again but the error still occurs... I have to wipe the partitions after I installed CM, right?
Click to expand...
Click to collapse
Are you using
fastboot flash recovery recovery.img
Where recovery.img is the cwm image file

jd1639 said:
Are you using
fastboot flash recovery recovery.img
Where recovery.img is the cwm image file
Click to expand...
Click to collapse
I use this command. But I missed a c in recovery so fastboot did not find the partition named "reovery" >_< Ok, CWM is installed. Now I have to install CM11 an then wipe the 4 partitions you mentioned with cwm? Wheres the option to wipe system, I just find the other 3.

BopItXtremeII said:
I use this command. But I missed a c in recovery so fastboot did not find the partition named "reovery" >_< Ok, CWM is installed. Now I have to install CM11 an then wipe the 4 partitions you mentioned with cwm? Wheres the option to wipe system, I just find the other 3.
Click to expand...
Click to collapse
I'm cwm just do the other 3

So I installed CM + Gapps and then wiped data, cache and dalvik cache with CWM. Now Im waiting for 8 minutes for the bootscreen to go away, but think it didnt work. By the way, if I wipe the system partition, I delete CM, dont I? I dont understand how that will help booting into CM.

BopItXtremeII said:
So I installed CM + Gapps and then wiped data, cache and dalvik cache with CWM. Now Im waiting for 8 minutes for the bootscreen to go away, but think it didnt work. By the way, if I wipe the system partition, I delete CM, dont I? I dont understand how that will help booting into CM.
Click to expand...
Click to collapse
Wipe before the install.
So,
1 Put rom zip on phone internal storage
2 Wipe partitions except internal storage
3 Flash rom
4 Flash GApps
5 Reboot
Sent from my Nexus 5

BopItXtremeII said:
So I installed CM + Gapps and then wiped data, cache and dalvik cache with CWM. Now Im waiting for 8 minutes for the bootscreen to go away, but think it didnt work. By the way, if I wipe the system partition, I delete CM, dont I? I dont understand how that will help booting into CM.
Click to expand...
Click to collapse
8 minutes is too long. You have some other problem. Do any other roms work? Wiping system in twrp does not wipe the internal sd card. That's why you didn't find it in cwm.

PhilipTD said:
Wipe before the install.
So,
1 Put rom zip on phone internal storage
2 Wipe partitions except internal storage
3 Flash rom
4 Flash GApps
5 Reboot
Sent from my Nexus 5
Click to expand...
Click to collapse
Thats what I did.
jd1639 said:
8 minutes is too long. You have some other problem. Do any other roms work? Wiping system in twrp does not wipe the internal sd card. That's why you didn't find it in cwm.
Click to expand...
Click to collapse
I will try the AOKP nightly and post the results. Is it okay to just wipe data, cache and dalvik cache before installing the aokp zip or is it better to flash the stock rom before flashing aokp?

No need to flash stock, just do the wipes

[Q] boot loop every rom

So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...

Me too bro....
Jur13n said:
So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...
Click to expand...
Click to collapse
Yeah Bro I have this exact problem, except i made a backup and my wifi is working fine now. One thing tho i cannot connect to google servers and when i boot up it says inconsistent UID's device may not work properly format your data partition(formatted it and yah nothing)

cated resionit
Jur13n said:
So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...
Click to expand...
Click to collapse
For no-wifi problem try to flash the rom from page 9 in repack thread. Work for me.

Update/dirty flashing Euphoria OS freezes at the Google boot screen

So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?

stynatu46 said:
So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?
Click to expand...
Click to collapse
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.

One more thing. I always make sure to have the latest TWRP installed before I attempt any dirty flash.
Latest version as of this post is TWRP 2.8.5.2

joegestes said:
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.
Click to expand...
Click to collapse
I usually do both of those things. I will say that I used ROM Installer to update it, but then dirty flashed with twrp and it still didn't work. Maybe next week I should just straight out flash with TWRP first?

Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?

I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Are you undervolting?
Ignore. Wrong thread.

Bump

stynatu46 said:
Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?
Click to expand...
Click to collapse
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.

joegestes said:
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.
Click to expand...
Click to collapse
I've tried this several times yesterday, I think I waited 20 minutes and rebooted again to do the same thing. I also don't have that many apps, I only have 4 rows filled in my app drawer

Okay everyone, I found the problem! All I had to do was uninstall the driver/app for CF.lumen before flashing because it tampered with the /system partition making it unable to boot. I then installed it again after the flash was done.