[Q] Trouble while flashing KitKat - Recovery gone - One (M7) Q&A, Help & Troubleshooting

Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?

wybren said:
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
Click to expand...
Click to collapse
try erasing the userdata using fastboot. I has a similar problem earlier this week and I remember using that command. Sometime when I enter recovery it just goes to normal boot (randomly), not sure if thats your problem but try entering recovery multiple times. If not...
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img

wybren said:
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
Click to expand...
Click to collapse
khhhhris said:
try erasing the userdata using fastboot. I has a similar problem earlier this week and I remember using that command. Sometime when I enter recovery it just goes to normal boot (randomly), not sure if thats your problem but try entering recovery multiple times. If not...
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
1- are you s-on or s-off, 4.4 is not compatible (at least for now) with S-On devices!
2- you need to "fastboot erase cache" after flashing recovery; personally i do it before and after, but the important part is after
3- why are you recommending "fastboot erase userdata", just wondering.

nkk71 said:
1- are you s-on or s-off, 4.4 is not compatible (at least for now) with S-On devices!
2- you need to "fastboot erase cache" after flashing recovery; personally i do it before and after, but the important part is after
3- why are you recommending "fastboot erase userdata", just wondering.
Click to expand...
Click to collapse
+1, s-off is required. I only recommend erasing userdata because I had a very similar issue, erasing userdata and a fresh recovery seemed to do the trick after no luck with simply flashing a new recovery and wiping cache Just going off past experience.

khhhhris said:
+1, s-off is required. I only recommend erasing userdata because I had a very similar issue, erasing userdata and a fresh recovery seemed to do the trick after no luck with simply flashing a new recovery and wiping cache Just going off past experience.
Click to expand...
Click to collapse
good to know, was "fastboot erase userdate" successfully? what kind of output did you get?

nkk71 said:
good to know, was "fastboot erase userdate" successfully? what kind of output did you get?
Click to expand...
Click to collapse
Thanks all for the response.
This did the trick:
erase cache
flash twrp recovery (first I tried cwm)
erase cache
Then I managed to enter twrp recovery and flash a new rom.
Don't know why, but I'm happy again
Thanks for the help.

Cool.. hit the users's thanks button!

Related

[Q] Problem Installing a Custom Recovery

I'm trying to install TWRP recovery via CMD but I'm having problems. As of now, I've done the following:
Downloaded TWRP 2.5.0.0
Placed the file in the same folder used to unlock the phone that also contains fastboot
With the phone connected, i run the following command
Code:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
In the prompt window, I received the following results "< waiting for device >" but i don't see anything progress thereafter on the phone or prompt window
I tried to reboot into recovery and now receive a red exclamation point within a triangle that's over a phone. See attached photo.
Thereafter, I have to force restart
Does anyone have any advice?
UPDATE
I was finally able to write the recovery on the phone. However, now when I try to boot into recovery, it fails to load recovery and boots as a normal restart.
UPDATE
I tried to reflash TWRP again. Following the reflash, I also deleted the cache using the following command
Code:
fastboot erase cache
I then reboot the bootloader using
Code:
fastboot reboot-bootloader
This time around, after making an attempt to boot into recovery, I would get the message "Entering Recovery...". However, after a few seconds, the phone would turn off.
Thereafter, I tried to flash the OEM recovery using the steps above and I'm still have the same problem. Is my recovery partition corrupt?
I read that it helps to erase the recovery partition prior to flashing over an existing recovery. I tired the command
Code:
fastboot erase recovery
But I receive the following results
Code:
c:\Android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
If erasing the recovery partition is good practice, how do I go about doing it?
I'm having the same problem.
I can successfully flash the TWRP 2.5.0.0 recovery ROM, but when I try to load into the recovery to flash a custom ROM, I see a flash of purple text on white background, then the screen goes black and boots normally.
Any help would be appreciated.
Ok... I had some issues when installing recovery so this is what I did...
Be advised that next steps are highly risky and that it might have worked for me but I take no responsibility if you break your device
After following almost all the instructions, I read that someone flashed the recovery to the boot partition. So I did that.
fastboot flash boot recovery.img
Now, after this, the device went to a constant bootloop and suddenly the recovery appeared.
Also, I erased the cache from fastboot with next command:
fastboot erase cache
I'm planning to post the procedure I've followed but I don't have much time lately.
Will try to do it as soon as possible.
Best regards.
---------- Post added at 12:22 AM ---------- Previous post was at 12:21 AM ----------
brianhill1980 said:
I'm having the same problem.
I can successfully flash the TWRP 2.5.0.0 recovery ROM, but when I try to load into the recovery to flash a custom ROM, I see a flash of purple text on white background, then the screen goes black and boots normally.
Any help would be appreciated.
Click to expand...
Click to collapse
For you mate, go into fastboot run:
fastboot erase cache
Then try again.
:No-Frost: said:
For you mate, go into fastboot run:
fastboot erase cache
Then try again.
Click to expand...
Click to collapse
You sir are my hero. Thank you!
I rebooted and went into Fastboot. Ran "fastboot erase cache". Then re-flashed the recovery image. Then ran the command "fastboot erase cache" again. Then restarted the bootloader, then went into the recovery and it worked.
brianhill1980 said:
You sir are my hero. Thank you!
I rebooted and went into Fastboot. Ran "fastboot erase cache". Then re-flashed the recovery image. Then ran the command "fastboot erase cache" again. Then restarted the bootloader, then went into the recovery and it worked.
Click to expand...
Click to collapse
Glad to help mate and glad to know you can go into recovery now
pwr2wh8 said:
UPDATE
I tried to reflash TWRP again. Following the reflash, I also deleted the cache using the following command
Code:
fastboot erase cache
I then reboot the bootloader using
Code:
fastboot reboot-bootloader
This time around, after making an attempt to boot into recovery, I would get the message "Entering Recovery...". However, after a few seconds, the phone would turn off.
Thereafter, I tried to flash the OEM recovery using the steps above and I'm still have the same problem. Is my recovery partition corrupt?
Click to expand...
Click to collapse
Do you have the Sprint version? I have Sprint and I was running into the same issue. After searching everywhere for this issue, I came across this post: http://forum.xda-developers.com/showpost.php?p=40828046&postcount=240
Here's the link to the file you need: http://techerrata.com/browse/twrp2/m7wls
I flashed this recovery img and it finally worked after all the other ones failed in the same way you described.
Hope it works for you!

Bricked phone, urgent help requested!

So earlier I was flashing TrickDroid, and Aroma froze and crashed the phone while it was installing... CWM showed a screen that said root may have been lost, and offered to fix root. I touched it, and this got the phone stuck in a continual boot loop. I've managed to get into the bootloader, but this is after clearing the cache with the terminal command "fastboot clear cache", and I have to type "fastboot reboot bootloader" when the phone boots up (at the HTC logo) in order to even get into the boot loader... otherwise, the phone will try to enter recovery (to no avail). I really hope I did not brick the phone... any help would be great. Can I fastboot a stock image?
NowhereOutThere said:
So earlier I was flashing TrickDroid, and Aroma froze and crashed the phone while it was installing... CWM showed a screen that said root may have been lost, and offered to fix root. I touched it, and this got the phone stuck in a continual boot loop. I've managed to get into the bootloader, but this is after clearing the cache with the terminal command "fastboot clear cache", and I have to type "fastboot reboot bootloader" when the phone boots up (at the HTC logo) in order to even get into the boot loader... otherwise, the phone will try to enter recovery (to no avail). I really hope I did not brick the phone... any help would be great. Can I fastboot a stock image?
Click to expand...
Click to collapse
Reboot into fastboot and try to fastboot erase cache then fastboot flash recovery again. If you can get into recovery, just try to reflash your ROM or do a NAND restore. Otherwise, use the All-in-One toolkit to help you adb sideload a ROM(this will bypass Aroma's epic failure rate, too, btw).
unremarked said:
Reboot into fastboot and try to fastboot erase cache then fastboot flash recovery again. If you can get into recovery, just try to reflash your ROM or do a NAND restore. Otherwise, use the All-in-One toolkit to help you adb sideload a ROM(this will bypass Aroma's epic failure rate, too, btw).
Click to expand...
Click to collapse
Great, worked like a charm. I flashed a different version of CWM this time, that might have been the problem? Oh well. Thanks!

[HELP] Soft Bricked Stuck at Boot

I tried to install ARHD ROM but then get stucked at 100% so I just turned it off and reboot but then I got stucked just rebooting...
Unable to enter Recovery too
Do an erase cache in fastboot and re-try to boot in recovery.
The command is:
Code:
fastboot erase cache[/hide]
Guich said:
Do an erase cache in fastboot and re-try to boot in recovery.
The command is:
Code:
fastboot erase cache[/hide][/QUOTE]
I've tried it, it says entering to Recovery then reboot again...maybe I flashed the wrong TWRP, perhaps you can help me find the right one. I have HTC ONE m7_ul
Click to expand...
Click to collapse
jirald said:
I've tried it, it says entering to Recovery then reboot again...maybe I flashed the wrong TWRP, perhaps you can help me find the right one. I have HTC ONE m7_ul
Click to expand...
Click to collapse
This is the recovery

Nexus 6 Stuck in Boot loop

Hey All.. my nexus 6 is stuck in a boot loop. I tried up dating to 5.0.1 and now it's boot looped. Anyone have any suggestions?
Try wiping cache in recovery.
eddies92 said:
Try wiping cache in recovery.
Click to expand...
Click to collapse
I can get to recovery, how do I wipe the cache?
To get to recovery hold the power button until it shuts off then press volume down and power at the same time to boot into bootloader. Then use the volume buttons to choose recovery mode and press power.
Sent from my Nexus 6
housry23 said:
To get to recovery hold the power button until it shuts off then press volume down and power at the same time to boot into bootloader. Then use the volume buttons to choose recovery mode and press power.
Sent from my Nexus 6
Click to expand...
Click to collapse
Hi! Same problem here. Happened when tried to update to 5.0.1 using this guide:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img (I used a decrypted boot.img for 5.0.1)
fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
I didn't get any error during the installation. I only did step 1 and 2, and when rebooted before step 3, I got the boot loop.
Recovery mode doesn't work, it shows a "dead" android with a red exclamation sign. I can still go to bootloader mode.
Can you please help me?
Solved it flashing "cache.img".
Hope it helps anyone.
mattogodoy said:
Solved it flashing "cache.img".
Hope it helps anyone.
Click to expand...
Click to collapse
my situation is the n6 will boot and then attempt to boot twrp but the boot splash screen of twrp loops so i guess the recvery segment is in a boot loop. if i co
low.humidity said:
my situation is the n6 will boot and then attempt to boot twrp but the boot splash screen of twrp loops so i guess the recvery segment is in a boot loop. if i co
Click to expand...
Click to collapse
Follow these steps:
Download Android 5.0.1 for Shamu (Nexus 6) from Google servers.
In the terminal:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img (I used a decrypted boot.img for 5.0.1)
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img (this one fixed my problem)
Hope that fixes it.
mattogodoy said:
Follow these steps:
Download Android 5.0.1 for Shamu (Nexus 6) from Google servers.
In the terminal:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img (I used a decrypted boot.img for 5.0.1)
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img (this one fixed my problem)
Hope that fixes it.
Click to expand...
Click to collapse
Why are you rebooting it twice while flashing? I've never rebooted it until it was done and I haven't had any issues. Maybe I'm just used to flashing older Nexus devices.
Pilz said:
Why are you rebooting it twice while flashing? I've never rebooted it until it was done and I haven't had any issues. Maybe I'm just used to flashing older Nexus devices.
Click to expand...
Click to collapse
I asked myself the same haha. For no special reason, I was just following a guide, but I've seen other guides where you don't reboot until the end of the process. It's fast and harmless anyway.
mattogodoy said:
I asked myself the same haha. For no special reason, I was just following a guide, but I've seen other guides where you don't reboot until the end of the process. It's fast and harmless anyway.
Click to expand...
Click to collapse
yeah, thanks for that info, it helped. i keep logs of the stuff i enter so it is not until i reread the logs that i really know wjhat i did , and some of those commands i did not do but you basically pointed me in the right direction. anyway, my device is working again thank god, i had moments of panic when i thought i had trashed a 700 buck phone but its all good now. again, thanks.
low.humidity said:
yeah, thanks for that info, it helped. i keep logs of the stuff i enter so it is not until i reread the logs that i really know wjhat i did , and some of those commands i did not do but you basically pointed me in the right direction. anyway, my device is working again thank god, i had moments of panic when i thought i had trashed a 700 buck phone but its all good now. again, thanks.
Click to expand...
Click to collapse
Haha, I'm very glad to know!
Same happened to me and scared the **** out of me. Luckily everything is fine now.
Enjoy your new nexus! It's AWESOME
i'm having trouble understanding..my n6 is stuck in bootloop, twrp keeps showing up after boot screen.. what programs are you guys using to slove this problem..please help..
---------- Post added at 06:37 PM ---------- Previous post was at 06:30 PM ----------
i'm having the same problem..what program are using to slove this problem..please help..
mattogodoy said:
Follow these steps:
Download Android 5.0.1 for Shamu (Nexus 6) from Google servers.
In the terminal:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img (I used a decrypted boot.img for 5.0.1)
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img (this one fixed my problem)
Hope that fixes it.
Click to expand...
Click to collapse
If I erase and flash cache… all my data and settings are gone?
Via my NeXus™ 7FHD on XDA Premium app
Nexus 6 Boot Loop
Im stuck in boot loop and im using the Nexus root toolkit to try to get me out of the of the loop. It downloaded the image and began to flash but gives me an error at the end saying boot.img was not found. Please help someone?
bitw_alex said:
Im stuck in boot loop and im using the Nexus root toolkit to try to get me out of the of the loop. It downloaded the image and began to flash but gives me an error at the end saying boot.img was not found. Please help someone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nex...sh-factory-images-nexus-6shamu-t2954008/page9
fastboot flash bootloader filename.img
fastboot flash radio filename.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img (in case you would like to wipe cache files)
fastboot flash userdata userdata.img (only in case you would like to wipe userdata)
fastboot reboot
Little different situation
Not sure what im doing wrong. my nexus was rooted for 2 to 3 weeks on android 5.1 . restarted today to only find myself stuck in a bootloop [ red green yellow blue ] nexus symbol continuously going, i booted into twrp and tried to restore my nexus to a backup i made after i rooted , but still stuck in bootloop , tried 1 more time to use my backup , but still in a bootloop , then tried to factory reset using twrp , and was still stuck in a bootloop , any tips would be awesome , thanks
EDIT: Think what put me in bootloop was making it where i need a password everytime i restart. just did it and seems some are having same problems .
EDIT 2: Well i got out of bootloop . appears i have also lost root . not sure what i did . after using twrp to install backups, format data , it finally restarted . im pretty positive the problem was caused by setting a restart passcode ! watch out guys ,
junior990 said:
i'm having trouble understanding..my n6 is stuck in bootloop, twrp keeps showing up after boot screen.. what programs are you guys using to slove this problem..please help..
---------- Post added at 06:37 PM ---------- Previous post was at 06:30 PM ----------
i'm having the same problem..what program are using to slove this problem..please help..
Click to expand...
Click to collapse
Same prob. Can't get into recovery
forcedairinduction said:
Same prob. Can't get into recovery
Click to expand...
Click to collapse
Can you get to bootloader? Stock or TWRP recovery?
Evolution_Tech said:
Can you get to bootloader? Stock or TWRP recovery?
Click to expand...
Click to collapse
Can get into bootloader, but if I try and go from there to recovery it goes back to team win splash repeatedly flashing
---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------
Evolution_Tech said:
Can you get to bootloader? Stock or TWRP recovery?
Click to expand...
Click to collapse
forcedairinduction said:
Can get into bootloader, but if I try and go from there to recovery it goes back to team win splash repeatedly flashing
Click to expand...
Click to collapse
PS, I'm very noon at this still. Been flashing since having my n4 but never got into this kinda trouble before. When things have gone wrong in the past I've always managed to go back into twrp & flash nandroid backup...... Scared stiff now

[Q] Mismatched partition size (recovery) when flashing stock 5.0.1 recovery

I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Evo_Shift said:
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Click to expand...
Click to collapse
I used fastboot -w to format the userdata/cache. And I also tried the three fastboot commands you listed. They all seem to work, but the reflashing of the recovery still throws the same error.
MD5 checksum of the whole zip is the same. I re-extracted the recovery.img file just to be sure and it still throws the same error.
Kramit said:
when I try to get back into recovery, the phone sits at the android with the red triangle and !.
Click to expand...
Click to collapse
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
yes, thats norml
cmh714 said:
yes, thats norml
Click to expand...
Click to collapse
Hmm. And if it doesn't work?
Kramit said:
I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Click to expand...
Click to collapse
I have the same problem here but maybe i have found a solution for it:
what i did was i left the 5.1 bootloader.img and took all the other stuff from a 5.0 factory image such as: radio.img, system.img..... fastbooted everything and i was with a 5.0 LP stock out of the box, then i have rooted it, installed twrp with f2fs support and voila i'm now good to go
hope this will help you out
Kramit said:
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
Click to expand...
Click to collapse
When you see the android with the red triangle and !, you need to hold the power button, and while you are holding it down, press volume up. Pushing them both together, or one after the other, or holding them down together or whatever else won't work.
Sent from my Nexus 6 using Tapatalk

Categories

Resources