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

HTC One X Evita Issue

I have S-On. I'm running the latest AOKP build for my phone. All was well but I wanted to flash MIUI Rom. I flashed the boot.img and then tried to flash the rom. I use TWRP. I wiped the cache and dalvik as usual. I have been flashing roms for awhile now but not the MIUI one. When I did the phone rebooted in to fastboot mode. I tried to go to recovery but my recovery wasn't there. I was able to reboot my phone and the AOKP rom was in tact and appeared to be running even though I tried to flash the MIUI. I navigated to ES file explorer and is says the SD card isn't mounted. Everytime I try to boot to recovery my screen goes blank and I have to use the power button depressed to get it to restart. I then used fastboot flasher 2.4 to try to flash the TWRP recovery again. It appeared to take and I got the words fastboot USB. I thought for sure problem was solved. After my phone rebooted again the SD card wasn't mounted and still isn't. I am able to use the phone and AOKP seems to be running as intended but the SD card won't mount. After I flashed TWRP again it still doesn't boot into recovery. I get an EACCES permission failed when I try to move anything to the card or try to access it. I tried team Nocturnal's method for the SD Fix but it didn't work. Am I going to have to flash an RUU file? If so, where can I get that from? Any help????

It looks like your sd is corrupt. Did you factory reset in bootloader? You didn't mention doing a full wipe when you flashed the ROM, you only mentioned cache and dalvik cache, you should always wipe cache/dalvik cache/factory reset in recovery when flashing a ROM. Also, which MIUI did you flash?
Sent from my Evita

I dont believe I did. Using trwp promts me and i follow that. Now i cant get to recovery or flash it. Any other options?
Sent from my One X using xda app-developers app

You might need to RUU but I'm not even sure if that's going to help with your sd problem. It's worth a try though. Run the RUU, flash TWRP, format your sd card. Make sure you have s-off before you run any RUU though or you'll brick.
Sent from my Evita

I cant seem to get s off. Not sure i want to go that route. Any other way to get it working?
Sent from my One X using xda app-developers app

What exactly is the problem with getting s-off?
Sent from my Evita

My P6800 kitkat 4.4.2 problem! can not boot.

I flashed omni-4.4.2-20140124-p6800-HOMEMADE.zip last night, but it can't work , when I boot system . it stay on OMNI logo screen. And I can not enter twrp 2.6.3.1 too. Is it brick? but I can enter odin mode . any one can help???? thanks

I wanna ask daniel_hk but I just a junior and I can't post at " Android Development" . help!!!!!!

Either flash full official firmware package with Odin or try re-flash recovery and (if successful) wipe, and then restore your Nandroid.

linvas said:
I flashed omni-4.4.2-20140124-p6800-HOMEMADE.zip last night, but it can't work , when I boot system . it stay on OMNI logo screen. And I can not enter twrp 2.6.3.1 too. Is it brick? but I can enter odin mode . any one can help???? thanks
Click to expand...
Click to collapse
Full wipe by CWM before upgrade to 4.4.

1) Reboot to cwm recovery
2) Do full wipe data, cache and davik cache
3) Reboot to cwm recovery again
4) Install KK442
5) Install Gapps
6) Install supersu (optional)
7) Reboot to system

69444091 said:
Full wipe by CWM before upgrade to 4.4.
Click to expand...
Click to collapse
HAPPYFATHER said:
1) Reboot to cwm recovery
2) Do full wipe data, cache and davik cache
3) Reboot to cwm recovery again
4) Install KK442
5) Install Gapps
6) Install supersu (optional)
7) Reboot to system
Click to expand...
Click to collapse
OP says cannot boot into recovery.......
That's why I suggested to flash firmware package or recovery with Odin.
Without a working recovery, it's the only option. From there, he can move on.
Sent from my GT-I9500 using XDA Premium 4 mobile app

[GTab 2 7.0] Can't install custom 4.4.4 ROMs

I can't install custom ROMs on p3113
Steps Taken
Starting with stock firmware/recovery
using chainfire autoroot
reboot
use root checker to confirm root
Use Odin to flash a custom recovery. (I tried Andi's CWM, TWRP, and also Philz touch 6.40)
Custom recovery flashes no issues and I can boot into custom recovery
I do factory wipe, then also dalvik, and cache again for good measure
Go to install a custom ROM via recovery
Go to reboot and the recovery prompts me that I need root and to asks gives me an option to install su
When I do that and reboot it bootloops.
I've tried 3 different recoveries. The ROMs I've attempted to flash are Dhollmen 4..4.4, and Andi's Omnirom 4.4..4.
It appears I can install 5.x ROMs without issue.
Any idea what I can do to fix this problem?
edit: in the process of trying twrp 2.8.0.5
edit2: no luck with 2..8.0.5 which I found on Dhollmen's thread. Going go browse through the forum looking for older recoveries.

Have you tried clearing /system

Yes

Try updating your SU binary before the flash, also try plain jane CWM, Andis CWM acts weird sometimes.
If SU binary won't update delete and install a different one, then update.
Pp.

Wipe cache
Wipe dalvic
Format /data
Format /system
Reboot recovery once
Flash rom.zip (don't flash anything else!)
Reboot into system, don't use "fix root"!
If it boots (Lollipop takes some time) your are good to go to flash gapps etc.
Send from OnePlus One using Tapatalk

Android-Andi said:
Wipe cache
Wipe dalvic
Format /data
Format /system
Reboot recovery once
Flash rom.zip (don't flash anything else!)
Reboot into system, don't use "fix root"!
If it boots (Lollipop takes some time) your are good to go to flash gapps etc.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
The only thing I wasn't doing was rebooting after wiping. Wiping then rebooting let me install the 4.4.4 ROMs no problem. I never would have figured this out thanks a lot. What causes the need to reboot after wiping?

@HappyRoot good to hear.
Seems like one of the partition wasn't unmount by the updater-script or recovery after wipe and caused that issue.
Send from OnePlus One using Tapatalk

Android-Andi said:
@HappyRoot good to hear.
Seems like one of the partition wasn't unmount by the updater-script or recovery after wipe and caused that issue.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
It only worked with installing SlimKat/Dhollmen I'm still unable to install Omni 4.4.4. I've done a complete wipe Odin'd twrp 2.8.4.1 and flash the zip via adb sideload. I keep getting an updater binary error.
update: twrp would crash at 37% and give me a binary error. when i odin'd updated cwm from you android file list i was able to get to 100% but then i would get a status 6 error.

Then you are doing something wrong...
Recovery log?
Send from OnePlus One using Tapatalk