Related
First time trying to root, I have an htc one. I got it unlocked and I've done everything correctly, but it still won't boot into recovery mode. I flashed the image file from twrp and i tried another one from cwm but neither is working, so my next idea is to clear my cache through adb but i'm not sure how to do that. can someone guide me?
aligator2727 said:
First time trying to root, I have an htc one. I got it unlocked and I've done everything correctly, but it still won't boot into recovery mode. I flashed the image file from twrp and i tried another one from cwm but neither is working, so my next idea is to clear my cache through adb but i'm not sure how to do that. can someone guide me?
Click to expand...
Click to collapse
Put the phone in fastboot mode and then run, on your computer:
fastboot erase cache
Sure you grabbed the correct twrp and flashed correct? Fastboot flash recovery blah.zip ?
When booted go to settings and power. Makes sure fastboot is not selected.
Sent from my HTC One using XDA Premium 4 mobile app
Are you picking recovery from your bootloader? If it is on fastboot you have to pick bootloader then recovery. Or if phone is booted adb reboot recovery.
Hello.
I was in the process of upgrading my HTC One from 4.2 and successfully unlocked the bootloader. But thereafter my phone just constantly reboots. It shows the HTC splash screen for about 10 seconds and the reboots again.
I am able to go into the fastboot screen (see screen shot). But when I select Recovery, the phone gors to the next screen - displays "Entering Recovery" - and nothing else happens thereafter.
Can anyone please help? Have looked at other such questions and tried but nothing has helped.
Thanks
sjgoel said:
Hello.
I was in the process of upgrading my HTC One from 4.2 and successfully unlocked the bootloader. But thereafter my phone just constantly reboots. It shows the HTC splash screen for about 10 seconds and the reboots again.
I am able to go into the fastboot screen (see screen shot). But when I select Recovery, the phone gors to the next screen - displays "Entering Recovery" - and nothing else happens thereafter.
Can anyone please help? Have looked at other such questions and tried but nothing has helped.
Thanks
Click to expand...
Click to collapse
I'm not sure you did ever flash a custom recovery!
1. Put your phone in fastboot from the bootloader meny. You already did this while rooting, so you got it already!
2. In your "SDK-tools" folder that you used while unlocking the device, put [nameofyourrecovery].img I recommend you to install TWRP 2.6.3.3, as it is the best one for flashing kitkat and lets you do this if you wish I cannot give you a link as I am a new member, but search google for TWRP 2.6.3.3 and you will find it. Make sure it is .img and not .zip!
3. While in fastboot, open a command prompt in the ADB folder.
4. To flash your custom recovery, type
fastboot flash recovery [nameofyourrecovery].img
Click to expand...
Click to collapse
Now give it another go
THeHopelessPainter said:
I'm not sure you did ever flash a custom recovery!
1. Put your phone in fastboot from the bootloader meny. You already did this while rooting, so you got it already!
2. In your "SDK-tools" folder that you used while unlocking the device, put [nameofyourrecovery].img I recommend you to install TWRP 2.6.3.3, as it is the best one for flashing kitkat and lets you do this if you wish I cannot give you a link as I am a new member, but search google for TWRP 2.6.3.3 and you will find it. Make sure it is .img and not .zip!
3. While in fastboot, open a command prompt in the ADB folder.
4. To flash your custom recovery, type
Now give it another go
Click to expand...
Click to collapse
Does not help. Used 2.6.3.3, the flash process went fine, then Recovery displays "Entering Recovery" - and then again bot loop.
sjgoel said:
Does not help. Used 2.6.3.3, the flash process went fine, then Recovery displays "Entering Recovery" - and then again bot loop.
Click to expand...
Click to collapse
You have an M7CDWG, twrp is for M7_U & M7_UL models, if i'm not mistaken. Start googling for M7CDWG, it's a completely different phone than the U / UL phones.
and you need to "fastboot erase cache" after flashing recovery
nkk71 said:
You have an M7CDWG, twrp is for M7_U & M7_UL models, if i'm not mistaken. Start googling for M7CDWG, it's a completely different phone than the U / UL phones.
and you need to "fastboot erase cache" after flashing recovery
Click to expand...
Click to collapse
Dear nkk71
Many thanks. I used your suggestion and rooted as per #9 in this post:
http://forum.xda-developers.com/showthread.php?p=45427332
I installed Chinese recovery followed by TWRP recovery. I was abe to Recover and reach TWRP manager 2.6.0.0.
Can you please suggest what next to instal?
If I reboot I still go into reboot loop, but can now reach TWRP manager.
Thanks
sjgoel said:
Dear nkk71
Many thanks. I used your suggestion and rooted as per #9 in this post:
http://forum.xda-developers.com/showthread.php?p=45427332
I installed Chinese recovery followed by TWRP recovery. I was abe to Recover and reach TWRP manager 2.6.0.0.
Can you please suggest what next to instal?
If I reboot I still go into reboot loop, but can now reach TWRP manager.
Thanks
Click to expand...
Click to collapse
Not really, don't know much about your model. You'll need to find a ROM compatible with your device; if it doesnt specifically say it's for your device, then most likely it isn't!!
I think there's a Maximus HD ROM for your version, but i have no idea where.
Did you..
Aside from flashing a recovery and rooting your phone, did you make any other modifications or flash any other partitions?
If no, then wipe Dalvek cache from TWRP. Boot into TWRP and select Wipe. Select advanced. Select Dalvek and Cache. Wipe power down. then power on and see if it will boot.
nkk71 said:
Not really, don't know much about your model. You'll need to find a ROM compatible with your device; if it doesnt specifically say it's for your device, then most likely it isn't!!
I think there's a Maximus HD ROM for your version, but i have no idea where.
Click to expand...
Click to collapse
Dear nkk71
Yes, Maximus has a ROM for dual SIM, Flashed, all went well, but the reboot loop still exists.
Thanks
Jcc1dls said:
Aside from flashing a recovery and rooting your phone, did you make any other modifications or flash any other partitions?
If no, then wipe Dalvek cache from TWRP. Boot into TWRP and select Wipe. Select advanced. Select Dalvek and Cache. Wipe power down. then power on and see if it will boot.
Click to expand...
Click to collapse
Dear Jcc1dls
Did as you mentioned - all went fine. But the reboot loop simply does not go away.
Thanks
sjgoel said:
Dear Jcc1dls
Did as you mentioned - all went fine. But the reboot loop simply does not go away.
Thanks
Click to expand...
Click to collapse
i had a similar problem last week with a One, a friend bricked his One by flashing "???" Dont know exactly whar he has done.
The phone had boot loops all the time.
my solution was:
- connecting the phone with the usb cable to my pc.
- started the phone into fastboot usb mode
- started cmd at my notebook
- change to the directory which contains adb and fastboot
- execute: fastboot erase cache
- restarted the phone
the phone starts normally into ARHD 40.3
perhaps it works ...
I unlocked the bootloader of My HTC One S with instructions from htcdev.com later I flashed it with latest touch CWM img file. The device is booting normally but when i am trying to go into recovery mode, it stuck in there showing 'Entering Recovery'. I cleared cache several times, tried to flash with twrp but same situation. If I just erase cache, it is still showing the same screen, tried stock recovery image also, still no luck. Please help. :crying:
Please try posting in the correct forum
http://forum.xda-developers.com/htc-one-s/help
Also make sure you flash a recovery from that forum, and not this one. Anything found here will break your device.
My phone has CM11 snapshot M8
Earlier tonight Google services on my phone crashed and couldn't restart, the error message just kept coming up, so I decided to reboot.
When it tried to turn back on, it was stuck on the boot animation for about an hour, so I decided to go into recovery and wipe the dalvik cache.
But before I can press the wipe button, the teamwin logo just shows for a couple seconds and the screen turns black. Then the phone tries to reboot into system again. Which of course leads me back to getting stuck on the boot animation.
I tried it multiple times, but it just keeps going through the loop. My computer doesn't recognize my phone in fastboot either. Damnit.
What should I do now?
alex93310 said:
My phone has CM11 snapshot M8
Earlier tonight Google services on my phone crashed and couldn't restart, the error message just kept coming up, so I decided to reboot.
When it tried to turn back on, it was stuck on the boot animation for about an hour, so I decided to go into recovery and wipe the dalvik cache.
But before I can press the wipe button, the teamwin logo just shows for a couple seconds and the screen turns black. Then the phone tries to reboot into system again. Which of course leads me back to getting stuck on the boot animation.
I tried it multiple times, but it just keeps going through the loop. My computer doesn't recognize my phone in fastboot either. Damnit.
What should I do now?
Click to expand...
Click to collapse
Hold down the power button and the volume down together, the lights on the bottom will flash 10 to 15 times, the phone will go off, at this point, release the power button but continue to hold the volume down, this will take you to the bootloader, post a screen shot of your bootloader please.
Seanie280672 said:
Hold down the power button and the volume down together, the lights on the bottom will flash 10 to 15 times, the phone will go off, at this point, release the power button but continue to hold the volume down, this will take you to the bootloader, post a screen shot of your bootloader please.
Click to expand...
Click to collapse
Here it is. What do you see?
alex93310 said:
Here it is. What do you see?
Click to expand...
Click to collapse
flash twrp again, clear cache and boot in recovery:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
use twrp 2.7.1.1 with cm11
and your fastboot issue is probably caused by your computer OS. Windows 8.1 isnt compatible with hboot 1.44.
418
alray said:
flash twrp again, clear cache and boot in recovery:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
use twrp 2.7.1.1 with cm11
and your fastboot issue is probably caused by your computer OS. Windows 8.1 isnt compatible with hboot 1.44.
Click to expand...
Click to collapse
Luckily fastboot decided to work this time.
First I used the recovery I originally had in my computer but it said "error: cannot load 'twrp.zip'"
Then I tried downloading it from the official website again but it showed the same error message.
I'm running Windows 7 btw.
alex93310 said:
Luckily fastboot decided to work this time.
First I used the recovery I originally had in my computer but it said "error: cannot load 'twrp.zip'"
Then I tried downloading it from the official website again but it showed the same error message.
I'm running Windows 7 btw.
Click to expand...
Click to collapse
its an img file not a zip file.
Code:
fastboot flash recovery (recovery_name)[B].img[/B]
fastboot erase cache
fastboot reboot-bootloader
alex93310 said:
First I used the recovery I originally had in my computer
Click to expand...
Click to collapse
you must use twrp 2.7.1.1 with CM11
from cyanogen team:
Recovery Update
Beginning with nightly 20140501 (or milestone 7, if you prefer the stable channel), several HTC devices are being transitioned to a new fstab layout. This will not affect your data. This change requires kernel support in recovery for CyanogenMod packages to install.
Affected devices include:
evita - HTC One XL
fireball - HTC Droid Incredible 4G LTE
jewel - HTC EVO 4G LTE
m4 - HTC One Mini
m7 - HTC One [GSM]
m7spr - HTC One [Sprint]
m7vzw - HTC One [Verizon]
ville - HTC One S
jewel and ville users: This is not the /data/media transition. That change is still being ruled out because there is simply no migration path that preserves data. With that said, if you are running an unofficial build of CyanogenMod that also incorporates this fstab change, TWRP recoveries are available from mdmower.cmphys.com. Look for jewel-dm and ville-dm in the filenames.
All of these recoveries are backwards compatible.
ClockworkMod recoveries with version greater than or equal to 6.0.4.8 support this fstab change. HTC One AT&T (m7att), HTC One T-Mobile (m7tmo), and HTC One non-US GSM (m7ul) can safely use the recovery for the generic "HTC One" (m7). Note: version 6.0.4.8 for m4 may have been built before by-name support was added to the kernel.
More recent builds of ClockworkMod recovery can be found at unstableapps.com
TWRP recoveries with version greater than or equal to 2.7.0.8 support this fstab change.* If you have a favorite recovery maintainer, encourage them to incorporate "block: by-name" support into their recovery kernels!
(*) Official 2.7.1.0 for m4, m7, m7spr/m7wls, and m7vzw/m7wlv mistakenly did not include the necessary fstab support, so 2.7.1.1 was released for these devices, addressing the issue.
More recent unofficial builds of TWRP can be found at mdmower.cmphys.com. You'll find source code for all these devices linked there as well.
Click to expand...
Click to collapse
ref: http://wiki.cyanogenmod.org/w/HTC_fstab_updates
and like said above, you are not entering the right command, recovery is a .img file
so try to flash twrp again, erase cache, reboot bootloader, boot in recovery and wipe cache/dalvik. if it doesnt work, reflash the rom after a full wipe/format
Seanie280672 said:
its an img file not a zip file.
Code:
fastboot flash recovery (recovery_name)[B].img[/B]
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
alray said:
you must use twrp 2.7.1.1 with CM11
from cyanogen team:
ref: http://wiki.cyanogenmod.org/w/HTC_fstab_updates
and like said above, you are not entering the right command, recovery is a .img file
so try to flash twrp again, erase cache, reboot bootloader, boot in recovery and wipe cache/dalvik. if it doesnt work, reflash the rom after a full wipe/format
Click to expand...
Click to collapse
LOL wow what a noob mistake :silly:
Yeah I had 2.7.1.1 all the time, both the original one on my computer and the newly downloaded one.
The .img file flashed successfully and erased the cache from fastboot, but the issue has not changed at all.
I went through the process twice and still no hope
I noticed something different though. I have a custom boot animation. Now whenever I try to boot it straight into system, it shows splash screen>CM original boot animation>splash screen>custom boot animation. This does not happen when it reboots itself when I try to go into recovery. It's just the normal splash screen>custom boot animation.
My phone keeps getting stuck on fastboot mode.
I'll flash the standard MIUI ROM using the MiFlash Tool, then I flash a custom recovery and a custom ROM(EvolutionX in this case), everything works and I can set up my phone, but as soon as I reboot I can no longer boot into android or recovery. i've tried flashing multiple recoveries using fastboot and straight up booting a recovery using "fastboot boot recovery.img" but it still always go to fastboot. The only solution is to start the process all over again, and obviously that's just not an option since I can never turn my phone off after that.
Any tips?
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Out of all that, the one instruction that solves it is the format data step. This is the magic step required. You always need to do this when flashing over MIUI.
Flashing vendor was totally irrelevant.
This will tell you what you need to do.
Simple Guide to flashing successfully
Here's a quick guide to some of the basics. Which recovery. ---------------------------- Use the latest from here. https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363/post79823568 Do not use Orange...
forum.xda-developers.com
Thanks a lot man! I'm having this issue and it is beyond annoying. I've lost so much time with this BS.
Edit: Does not help actually
I just had the same problem with my Lamentablet.
I was trying stuff up and restarted it in fastboot mode and got stuck there.
So, ways to deal with it:
adb reboot recovery
rebooted the tablet in recovery mode. All I had then was to press the power button to activate Reboot. Solved! From now on it boots normally.
Meanwhile I had discovered that by typing
fasboot continue
the tablet would resume, but at the next reboot cycle, power down + up cycle or reboot after a crash, the tablet would reboot into fastboot mode...
And I found this out when it crashed (it's not called a Lamentablet for nothing!).
Luckily I had a PC with Linux around. It didn't have the software installed but drivers were already in the Kernel and installing adb and fastboot was a matter of mere seconds. If I didn't have an easily ready PC at hand, this tablet would have become a brick until plugged in and rebooted...
OMG Thanks dude.... I'm literally working to installing custom rom on redmi 7a from stock rom but I don't know what reason that make my phone always stuck on fastboot when format data, before this was fine.
Osga21 said:
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Click to expand...
Click to collapse
thanks bro. flashing vendor after a format from twrp did the good