I kept getting the "set metadata error" on the latest Android Revolution HD rom so installed the latest version of CWM recovery but I kept getting the same error upon installing the rom. However, this time my phone is really screwed up. I cannot get back into CWM to restore my last backup, when I get the little "entering recovery" text on the top of my phone the screen goes black and then flashes something on the screen and that's it. I plugged the phone into my pc and followed the instructions for flashing TWRP recovery but again...when I try to enter recovery this time the TWRP log flashes and then it disappears. For some reason it also appears I am S-ON now as well! I can connect the phone and go to FASTBOOT USB and type "fastboot devices" and my phone shows up but no matter what I do I cannot get into TWRP to restore. What the heck do I do?!
type fastboot clear cache and try again
Related
ok soi as trying to flash new battery icons and when i rebooted the phone it dosnt start it just forcecloses my home screen and other ****...basically i cant get into my phone at all.
I went into adb typed recovery and it brought me to the stock recovery and not clockworks so i couldnt restore my backup so i wiped the phone with the stock recovery and it still boots up the same with the forcecloses. My phone is no longer read by my computer and when i type "adb devices" it no longer shows up.
I cant get into recovery mode manually because it just reboots.
I really need help.
Hello, im coming from Defy to Atrix, mine is Brazilian 2.3.6 Retail, and just unlocked the bootloader using Bell SBF. After installing RomRacer CWM (recovery-atrix5.img) using the fastboot method, my phone went in a continuous bootloop. Fastboot mode shows me an error something like FAILED TO EXECUTE COMMAND %e (a0cccx) that repeats and scrolls down the screen in red lines. I have to pull battery to stop this. RSD mode reboots the phone. Android Recovery shows me "Entering Android Recovery Mode" and after that phone hangs. To have the things worse, battery drained down.
After charging the battery using an universal charger, phone started, but when Android loaded, it hanged everything. I had to pull the battery. After that, phone went in bootloop again. I got into fastboot, wiped everything. After that i was able to get into Android Recovery, wiped everything again and tried to start the system, no luck. It went in bootloop again and the message in fastboot mode came on again.
One more point is, when the battery in on the phone, the phone is getting really hot.
I was using the phone for about 5 hours before messing the whole thing up, if i have it working again, i will stick with original firmware. No more customizing on this Atrix as long as its really easy to hardbrick. Im afraid that i did this to mine.
Defy is almost impossible to hardbrick. And its bootloader is locked. I see no goodness on having a phone that is that easy to kill... Please help me................
look into flashing an sbf on your atrix. puts it back to stock firmware.
if youre only soft bricked this will fix it. or try going to android recovery ( if it still has the original) and do a factory data wipe.
hope i helped!
I recommend you to download again RomRacer CWM
enter fastboot mode and flash again CWM (in case your download is corrupt)
type "fastboot devices" Press Enter.
type "fastboot erase recovery" Press Enter.
type "fastboot flash recovery recovery-atrix5.img"
if this didnt fix it
perform a full fastboot wipe
http://forum.xda-developers.com/showthread.php?t=1421261
and then try to reflash the recovery. if u cant fix it this way flash a sfb!
I recently tried a factory reset on my phone after finding that one of my apps was sending out spam texts to random people and racking up my text plan. Upon the first boot, it showed a green android man with a blue orb thing spinning in its stomach and kept going for hours.
My phone was previously running an unofficial build of CM12 and was unlocked and rooted.
Now, I just figured that I could just flash a new recovery to the phone and flash a new ROM to get it back up and running, but I also keep having troubles getting it to flash. Using 'flashboot devices', I see my phone's serial, but when I try to use 'flashboot erase recovery' or 'flashboot flash recovery recovery.img' seems to hang up. I finally got it to write clockwork recovery to the phone somehow, but the device still boots to the green android man w/ blue instead of clockwork. I thought it was an issue, so I have been trying to flash TWRP, and it just hangs, and doesn't even give the <waiting for device> text, so I know it sees it.
Can anyone help me figure out a way to get my recovery flashed correctly? From that point, I should be good to go, as long as it loads into recovery.
Tampered
I have tried everything I can think of, and it still stalls while it is supposed to flash the new recovery, then fails with the error "too many links".
Also, now the **TAMPERED** flag pops up at the top of the bootloader. It still lets me into the FASTBOOT portion, so I don't believe that it is effecting anything, so I will probably just have to worry about that later, if I really feel like going through the whole rumrunner/revone process.
TWRP
Not sure if it is a good sign or not, but I replaced the USB cable and was able to get TWRP to install and actually load once. There were errors after it booted, and I choose to do a full factory wipe to hopefully start over fresh, and the phone rebooted itself. Now TWRP seems to endlessly load while it the splash screen flashes on and off, almost as if it is in a bootloop. I tried reflashing with a slightly older TWRP for my phone, and no luck.
Also, another strange thing is that when I flash a new recovery file, it shows that it only takes a total time of 2.607s. If feel like this is quite short and I remember it taking a bit longer in the past. I just feel like it is not writing the entire recovery, hense the blinking teamwin logo that seems to be stuck in a bootloop.
Bootloops, Partition Table(s), and "35 RU_PARTITION_NOT_SUPPORT {partitionName}"
Hey Guys,
I had no idea how best to word the title for this because I'm having a hard time narrowing down the actual issue. I have attempted an RUU, both by 0PJAIMG.zip method and .exe method. The .exe method fails because it times out trying to reboot to the bootloader, and the .zip method fails because I get stuck in a bootloop (black background with dark HTC logo, described below).
Background -- On the Sprint variant of the M9. Earlier this week installed MM via RUU. Phone is S-ON and Unlocked (successfully ran RUU against it in this state earlier this week, strangely). Phone turned itself off while doing a WhatsApp backup, and this was the resulting situation.
Symptoms:
1. Turning on the phone results in HTC screen with white background and red text, where it hangs forever
2. "fastboot oem lock" doesn't work -- phone remains "Unlocked"
3. TWRP 3.0.2-0 is not able to mount any of my partitions (/cache, /system, /data, /devlog, /carrier, /cota, /preload) All say "Failed to mount '/{partitionName}' (Invalid argument)"
4. If I turn on the phone while holding power down key, I get what looks like the first step of Download Mode (dark HTC logo, black background), but it shows that screen vibrates, goes black, vibrates, shows that screen again...etc - forever
5. Attempting to flash any firmware-related items results in "35 RU_PARTITION_NOT_SUPPORT {partitionName}", where partitionName = whatever I was trying to flash (aboot, hosd, radio...etc)
6. In TWRP, when looking at the "Select Storage" dialog in Mount screen, "Internal Storage" shows "(0MB)"
7. Flashing Stock Recovery img results in still seeing TWRP when booting
8. The only way I am able to reach the bootloader is by holding all three buttons together. I can connect via fastboot in the bootloader, but I can't flash anything there because I'm S-ON.
9. When running RUU.exe, everything functions until it tries to reboot the phone into the bootloader the first time, where it would begin the flash process. It boots the HTC logo, white background, with red text and hangs
a. I tried to reach the bootloader for it by using the steps in #8, but while I can see the device in fastboot devices in the bootloader, the RUU never sees it and eventually times out
10. Restoring "System Image" from TWRP from before I had done anything at all to it doesn't change anything
11. Restoring "Recovery" backup from TWRP, from before I flashed TWRP also results in no change (TWRP still boots when I choose to reboot into recovery)
My guess, at this point, is a corrupt partition table or EMMC. Is it possible to try rebuilding this?
Does anyone think this is recoverable? Thoughts on next steps?
Any/all help is greatly appreciated!
Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
silkt said:
Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
Click to expand...
Click to collapse
I ended up eventually un-bricking my phone by booting into safe mode and re-connecting the ADB. I then successfully ran 'flash-all.'