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] Moto G Stuck in CM12 Boot Loop

My Moto G, model XT1032 is stuck in a CM12 bootloop. I can boot into fastboot mode and ClockWorkMod Recovery.
So far I have tried re-flashing the CM12 ROM with no success, I have downloaded the original firmware and tried to flash that but I get a "Preflash Validation Failed" error, my phone won't show up on RSD, and I have tried wiping the phone to it's factory setting.
None of these worked and I am out of ideas. Are there any other options to try?
Thanks.

Did you ever have the GPE ROM on your phone? Does your data partition uses f2fs?
If you are getting the validation error when flashing motoboot.img, that is because your current bootloader is newer than the bootloader you are trying to flash.

Hi, I'm fairly certain I had the GPE ROM on it. It was what it came shipped with, that is all I know. As for the data partition I am unsure of the format of it, how would I go about finding this information?
Thanks.

If it has the GPE ROM, it would not use f2fs for data. Do you have twrp on it? If you do, boot into twrp, advanced wipe, and check partition info.

I do not have twrp, I have ClockWorkMod. How do I check the partition on this?

In CWM, go to wipe & format options, custom format options, toggle f2fs<->ext4 migration. Then wipe data, cache, Dalvik, and reboot.

I don't have those options on my CWM, All I have is Reboot, Install Zip, Wipe Data/Factory Reset, Wipe Cache Partition, Backup and Restore, Mounts and storage and advanced. I am using version 6.0.4.6 of CWM.

Install the latest version of Philz Touch for your phone.

Okay, I did that and now my device hangs at the Motorola Bootloader Unlocked Warning screen. Should I flash a new ROM such as CM or try again with the motoboot?

I would do a full wipe and re-install to see what happens.

It's just gone back into the CM boot loop where it hangs at the pulsing CM logo. Should I try a different version of CM that is more stable?

RyanVadera said:
It's just gone back into the CM boot loop where it hangs at the pulsing CM logo. Should I try a different version of CM that is more stable?
Click to expand...
Click to collapse
I'm running the latest CM12 on my xt1032 with no problem.
You may need to flash back to stock 4.4.4, re-install Philz, and them CM12.
The partition layout on the GPE ROM is different than the partition layout on the stock.

Do you know where I can find the stock 4.4.4 file? I can't seem to locate one?

Try here: http://motofirmware.center/files/category/26-falcon/

Thanks, I got 4.4.2 running fine. Any advice on how to avoid getting stuck in another bootloop when I try to re-flash CM12?

Install the latest Philz, create a backup, then flash a ROM of your choice. To be safe, do a full wipe, including system, but not internal storage, before and after the ROM was been flashed.

Okay, Thanks for all your help.

So it all worked? I hope it did.

I'm afraid to say it did not work, It just went back into the boot loop.

How about flashing stock 4.4.4 or ota to the latest stock before flashing cm.
Are you flashing the cm for your phone?

[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

after whiping data, phone is stuck and twrp does nothing

Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.

abati said:
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
Click to expand...
Click to collapse
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.

mikex8593 said:
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
Click to expand...
Click to collapse
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.

abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now

tabletalker7 said:
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
Click to expand...
Click to collapse
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.

abati said:
after whiping data, phone is stuck and twrp does nothing
Click to expand...
Click to collapse
After a whipping I wouldn't be inclined to do much either!

croques said:
After a whipping I wouldn't be inclined to do much either!
Click to expand...
Click to collapse
what do you mean, could you be more clear and specifiek ?

abati said:
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
Click to expand...
Click to collapse
Use a fastboot rom. That will wipe EVERYTHING - and guarantee that you have a usable phone afterwards

abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
You probably wiped system that's why you had nothing to boot into

yldlj said:
You probably wiped system that's why you had nothing to boot into
Click to expand...
Click to collapse
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw

abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Its the easy answer, say that you wiped system or such.
If you wiped Data with Magisk installed, without flashing the stock kernel, you won't be able to boot, since Magisk stores stuff necessary to boot on Data.
Usually, people is stuck on a infinite bucle on TWRP after this, you couldn't even enter TWRP? that's new. The issue you're telling sounds like you changed slot in TWRP somehow to an unused one or something like that, never heard of that.

abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Yeah I have wiped data in twrp with no issues. TBH it just sounds like there was no system to boot into. Wiping data is just that and shouldn't make the phone unbootable. Also you fixed the issue by flashing OOS which makes me believe this also. If you want to factory reset your phone the best way is to do it through settings.

Cant upgrade because of faulty TWRP, need help removing TWRP

Hi,
I accidently flashed TWRP, but i was already on emui9 so twrp doesent work there.
Now i can update the EMUI anymore because when the phone restarts during the install process it goes into recovery (twrp) which causes the update to fail
My question is: Can i remove twrp, maybe by flashing the orignal ramdisk image? pls help

You would have to reflash the recovery partition... Which we don't have, and since TWRP is kind of broken on EMUI 9.... well...
Can you just wipe caches and reboot to get the phone working? The update is stored in the cache partition, if you wipe cache it should boot normally.

acejavelin said:
You would have to reflash the recovery partition... Which we don't have, and since TWRP is kind of broken on EMUI 9.... well...
Can you just wipe caches and reboot to get the phone working? The update is stored in the cache partition, if you wipe cache it should boot normally.
Click to expand...
Click to collapse
so i cant really get rid of TWRP? :/
And how can i wipe the cache?

Pfollvosten said:
so i cant really get rid of TWRP? :/
And how can i wipe the cache?
Click to expand...
Click to collapse
Not if you are on EMUI 9... I don't believe so as we don't have the factory image for it, and to my knowledge we can't just dd it or make a backup of it right now. Although you might be able try the downgrade to 8.1 in another thread here, then upgrade via OTA again, but that's your choice.
I haven't installed TWRP on this devices, but basically go to the wipes menu, advanced wipes, and tick anything that says cache in it's name (often Dalvik cache and cache) and swipe to wipe them. This will not harm any of your data or applications, only the cache space. Then reboot.

acejavelin said:
Not if you are on EMUI 9... I don't believe so as we don't have the factory image for it, and to my knowledge we can't just dd it or make a backup of it right now. Although you might be able try the downgrade to 8.1 in another thread here, then upgrade via OTA again, but that's your choice.
I haven't installed TWRP on this devices, but basically go to the wipes menu, advanced wipes, and tick anything that says cache in it's name (often Dalvik cache and cache) and swipe to wipe them. This will not harm any of your data or applications, only the cache space. Then reboot.
Click to expand...
Click to collapse
The problem ist twrp doesent work.
It freezes when i enter recovery

Pfollvosten said:
Hi,
I accidently flashed TWRP, but i was already on emui9 so twrp doesent work there.
Now i can update the EMUI anymore because when the phone restarts during the install process it goes into recovery (twrp) which causes the update to fail
My question is: Can i remove twrp, maybe by flashing the orignal ramdisk image? pls help
Click to expand...
Click to collapse
Just flash your stock RECOVERY_RAMDIS.img*from your firmware. This will repair your recovery.
To extract images from*UPDATE.APP*in the zip, you have to use*Huawei Update Extractor.

oslo83 said:
Just flash your stock RECOVERY_RAMDIS.img*from your firmware. This will repair your recovery.
To extract images from*UPDATE.APP*in the zip, you have to use*Huawei Update Extractor.
Click to expand...
Click to collapse
Can you explain a bit further? Where do i get the RAMDIS.img from and how do i flash it?
and whats huawei update extractor?