Related
I unlocked the bootloader then went to flash recovery and it shows it flashed but won't reboot into recovery. What am I doing wrong? Thank you
Sent from my Nexus One using XDA App
are u rooted? and just download rom manager from the market and flash through the app.
Sent from my LG-V909 using Tapatalk
I'm not rooted. How would I root without flashing recovery?
Sent from my Nexus One using XDA App
Make sure you have a recovery for the nexus one.
Go into fastboot. Flash the recovery. Then enter the command fastboot reboot recovery. Do that with out booting into the os.
Read the Wiki, Recovery section, and follow the guide for unlocked bootloader.
I did all that and it won't go into recovery. I have read the wiki quite a few times
Sent from my Nexus One using XDA App
fastboot boot name-of-recovery.img
If you reboot your phone, the stock recovery will be reinstalled...
Exactly. I guess you're not following the guide properly.
The guide says:
"fastboot flash recovery recovery.img"
"fastboot reboot recovery"
Did you execute those as above? Or did you do it in some other way?
I did the commands just like that. One of u guys says its "fastboot boot recovery " and the other says reboot. Which is it? When I do the recovery.kimgom command it says its sending and writing it
Sent from my Nexus One using XDA App
"fastboot boot recovery.img" sends the image to boot from your HD, and doesn't check the image that is already in recovery partition.
"fastboot reboot recovery" uses the boot image from recovery partition - the one you just wrote.
What happens when you execute "fastboot reboot recovery"?
Nothing on the phone. On the command window the recovery shows
Sent from my Nexus One using XDA App
Do I have to put the recovery image on the SD card to?
Sent from my Nexus One using XDA App
The recovery can't show on command window.
Again, what happens when you execute "fastboot reboot recovery"?
Print the screen, because it looks like you can't explain what's going on.
No, you just need to follow the guide correctly.
Does OP need to run these before he reboots and right after flashing new recovery--
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
If he doesn't even boot into OS - then no, he doesn't need it and can't do it from bootloader anyway.
gotcha--thanks Jack
When I execute the command nothing happens.
Sent from my Nexus One using XDA App
Are you sure you got the drivers installed?
Are you sure the bootloader is unlocked.
The commands have to work. Boot into fastboot and issue this command. Fastboot devices. Your devices serial number should show up in the command prompt.
What makes you think the recovery flashed
Did you put recovery in your SDK tools folder and go to that path in terminal before fastbooting the .img
I also read somewhere a long time ago, some phones like mine don't accept reboot command thru fastboot
You could run your commands and then adb kill-server, disconnect phone and reboot using phone buttons
When I turn in the phone it shows the unlocked padlock. I put the image in my tools folder and I pit the command fastboot devices and get my serial #
Sent from my Nexus One using XDA App
I was on CleanROM 1.5 for AT&T, but decided to switch to ARHD for continued updates. Flashed the ROM and the problem began. I've since tried to go back to cleanrob via pushing the rom with adb, no go. I've wiped the phone countless times. I've erased the fastboot cache. I've switched TWRP/CWM neither changed anything. Fixed permission, flashed the boot images associated with each rom. Let it hang on the HTC screen for 30 minutes. I've exhausted the extent of google. Can anyone help?
Hi
Greetings,
Try againg this step
1. Boot into recovery
2. Wipe everything except sd card
3. Wipe cache and dalvik cache
4. Use abd sideload to install new downloaded(download again even if you have) ARHD rom(check md5 sum of the newly Downloaded Rom before instaltion)
5. Reboot into bootloader
6. Flash ARHD boot.img( you will have extract that from ARHD rom)
7. Wipe cache " fastboot erase cache"
8. Reboot
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
Try againg this step
1. Boot into recovery
2. Wipe everything except sd card
3. Wipe cache and dalvik cache
4. Use abd sideload to install new downloaded(download again even if you have) ARHD rom(check md5 sum of the newly Downloaded Rom before instaltion)
5. Reboot into bootloader
6. Flash ARHD boot.img( you will have extract that from ARHD rom)
7. Wipe cache " fastboot erase cache"
8. Reboot
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Re-downloading, will check MD5 and follow these steps without deviation. Will post when done.
shrex said:
Hi
Greetings,
Try againg this step
1. Boot into recovery
2. Wipe everything except sd card
3. Wipe cache and dalvik cache
4. Use abd sideload to install new downloaded(download again even if you have) ARHD rom(check md5 sum of the newly Downloaded Rom before instaltion)
5. Reboot into bootloader
6. Flash ARHD boot.img( you will have extract that from ARHD rom)
7. Wipe cache " fastboot erase cache"
8. Reboot
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
All steps complete, stuck on HTC logo screen. =( I didn't get any errors during any of the steps it went smoothly. Just doesn't work..... am I the only person with an unruly HTC One?
Hi
Greetings,
Hi the HTC logo means
1.White screen with green HTC logo and quietly brilliant.
2. Or the screen when beats audio comes and ONE is written that screen
If its 2nd screen that means it is Rom problem
If it doesnot pass the HTC logo I thing its kernel issue ( at least I have been using this in my sensation)
Have you flashed the kernel
Your option is to try stock Rom search it in development sector
Can u access the sdcard memory when you connect .possibility is rare as the phone has not booted
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
Hi the HTC logo means
1.White screen with green HTC logo and quietly brilliant.
2. Or the screen when beats audio comes and ONE is written that screen
If its 2nd screen that means it is Rom problem
If it doesnot pass the HTC logo I thing its kernel issue ( at least I have been using this in my sensation)
Have you flashed the kernel
Your option is to try stock Rom search it in development sector
Can u access the sdcard memory when you connect .possibility is rare as the phone has not booted
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
First option and yes I am able to sideload to the device and push things to it through ADB.
Hi
Greetings,
M out of idea
Matt95 might help you wait for his response
Sent from my HTC Sensation Z710e using xda premium
do you get any error when you boot into recovery? which one do you have now?
matt95 said:
do you get any error when you boot into recovery? which one do you have now?
Click to expand...
Click to collapse
No error booting into recovery, I'm using the newest version of CWM (non touch). Sometimes in recovery the cache doesn't mount properly, restarting seems to fix this.
ok, we will start fresh just to make sure that everything is allright... re-install the CWM recovery by typing
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase cache
and then reboot into recovery
matt95 said:
ok, we will start fresh just to make sure that everything is allright... re-install the CWM recovery by typing
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase cache
and then reboot into recovery
Click to expand...
Click to collapse
Done. I couldn't erase recovery I got the error "c:\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s"
ryan9316 said:
Done. I couldn't erase recovery I got the error "c:\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s"
Click to expand...
Click to collapse
is your bootloader unlocked right?
matt95 said:
is your bootloader unlocked right?
Click to expand...
Click to collapse
Yes S-On Unlocked/Tampered
ok, did you get that error also when you flash the recovery.img?
matt95 said:
ok, did you get that error also when you flash the recovery.img?
Click to expand...
Click to collapse
No it flashed fine. I'm sitting in recovery now.
ok, if it gives no error then proceed with the installation of the rom
first flash its boot.img and then flash the rom in recovery...do not install any mod or anything that could compromise the correct installation
matt95 said:
ok, if it gives no error then proceed with the installation of the rom
first flash its boot.img and then flash the rom in recovery...do not install any mod or anything that could compromise the correct installation
Click to expand...
Click to collapse
Flashed boot.img from " AT&T Stock Root 1.26.502.10 -| Flashes boot.img | System RW capable! |-". http://forum.xda-developers.com/showthread.php?t=2252959
Rebooted to recover. Entered ADB Sideload mode. Flashed above rom.
Install successful.....Sitting in recovery awaiting your command sir.
ryan9316 said:
Flashed boot.img from " AT&T Stock Root 1.26.502.10 -| Flashes boot.img | System RW capable! |-". http://forum.xda-developers.com/showthread.php?t=2252959
Rebooted to recover. Entered ADB Sideload mode. Flashed above rom.
Install successful.....Sitting in recovery awaiting your command sir.
Click to expand...
Click to collapse
did you flash the boot.img from fastboot directly?
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
now it should boot up the rom...
matt95 said:
did you flash the boot.img from fastboot directly?
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
now it should boot up the rom...
Click to expand...
Click to collapse
Rebooted into bootloader. Flashed boot.img, rebooted
Now sitting on the "HTC Quietly brilliant" screen. Not moving.
While on that screen it still shows up under ADB devices. Should I try relocking/unlocking the bootloader?
ryan9316 said:
Rebooted into bootloader. Flashed boot.img, rebooted
Now sitting on the "HTC Quietly brilliant" screen. Not moving.
While on that screen it still shows up under ADB devices. Should I try relocking/unlocking the bootloader?
Click to expand...
Click to collapse
don't think it will solve the problem but it's worth a try
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?
bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."
I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?
If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."
OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.
SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!
SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!
Thanks for posting back. Edit your title to [SOLVED]! and enjoy!
Hi,
I'm in desperate need of some help and am not sure what to do. My HTC One m7 got stuck in Cyanogenmod Simple Recovery after the latest update. It will keep rebooting back into Simple Recovery. Is there any way to get my phone back either to stock or to Cyanogenmod?
I always just left it on Cyanogenmod so I'm not very familiar with flashing or other programs. If anyone has any advice, could you please point me to the correct tutorials and downloads?
I am at a complete loss with how to get my phone to its original state.
Perez92 said:
Hi,
I'm in desperate need of some help and am not sure what to do. My HTC One m7 got stuck in Cyanogenmod Simple Recovery after the latest update. It will keep rebooting back into Simple Recovery. Is there any way to get my phone back either to stock or to Cyanogenmod?
I always just left it on Cyanogenmod so I'm not very familiar with flashing or other programs. If anyone has any advice, could you please point me to the correct tutorials and downloads?
I am at a complete loss with how to get my phone to its original state.
Click to expand...
Click to collapse
Follow this nkk71's Return to 100% Stock Guide!
majmoz said:
Follow this nkk71's Return to 100% Stock Guide!
Click to expand...
Click to collapse
Thank you for the response, however my biggest issue is getting out of simple recovery. How do I install a new recovery, such as TWRP or CWM at the simple recovery screen and how do I flash the latest cyanogenmod rom?
Perez92 said:
Thank you for the response, however my biggest issue is getting out of simple recovery. How do I install a new recovery, such as TWRP or CWM at the simple recovery screen and how do I flash the latest cyanogenmod rom?
Click to expand...
Click to collapse
You will have to flash CWM recovery in bootloader/FASTBOOT USB. You can get the recovery from http://www.clockworkmod.com/rommanager find your phone then download the recovery.
In bootloader/FASTBOOT USB, flash CWM recovery (either rename the file CWM.img or type the whole name in place of CWM):
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
majmoz said:
You will have to flash CWM recovery in bootloader/FASTBOOT USB. You can get the recovery from http://www.clockworkmod.com/rommanager find your phone then download the recovery.
In bootloader/FASTBOOT USB, flash CWM recovery (either rename the file CWM.img or type the whole name in place of CWM):
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thank you for replying.
So from what I'm understanding is that I will need to use ADB to sideload the recovery onto my phone, correct?
I'm not sure what the bootloader/FASTBOOT USB you refer to, I feel like I need it to be ELI5. My brain is melting when trying to read this.
P.S. I am STUCK in Cyanogenmod Simple Recovery. I am not able to power down the device or get to any other screen.
Perez92 said:
Thank you for replying.
So from what I'm understanding is that I will need to use ADB to sideload the recovery onto my phone, correct?
I'm not sure what the bootloader/FASTBOOT USB you refer to, I feel like I need it to be ELI5. My brain is melting when trying to read this.
Click to expand...
Click to collapse
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
majmoz said:
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
Click to expand...
Click to collapse
So I was able to get my device past the first prompt. I now see the white bootloader screen and it does say "FASTBOOT USB". I downloaded the latest TWRP and placed it in the same folder as ADB and Fastboot. I did the second command to flash it, however I keep getting the error "error: cannot open 'TWRP.img'. Any idea as to what I could be doing wrong?
majmoz said:
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
Click to expand...
Click to collapse
Got it to work. Used adb to get into fastboot. Then opened up the CM installer and let it redownload cyanogenmod onto my phone.
Thanks for the help!
Hi everyone
I stuck with root procedure (first link when you type "htc mini 2 root" in google)
I did unlock bootloader with htcdev, I am able to run adb and fastboot - meaning I can restart my phone into fastboot loader but I cannot run TWRP recovery, I dont know why. I downloaded few versions of this .img file, I run command fastboot boot recovery xxxx.img, with some files there is no reaction at all, with file recovery-twrp-2.8.5.0 phone is restarting but into normal function, there is no twrp screen. I have CWM-SuperSU-v1.30 on sd card in the phone
Does anyone have clue what can be wrong here?
Thank you
pudlll said:
Hi everyone
I stuck with root procedure (first link when you type "htc mini 2 root" in google)
I did unlock bootloader with htcdev, I am able to run adb and fastboot - meaning I can restart my phone into fastboot loader but I cannot run TWRP recovery, I dont know why. I downloaded few versions of this .img file, I run command fastboot boot recovery xxxx.img, with some files there is no reaction at all, with file recovery-twrp-2.8.5.0 phone is restarting but into normal function, there is no twrp screen. I have CWM-SuperSU-v1.30 on sd card in the phone
Does anyone have clue what can be wrong here?
Thank you
Click to expand...
Click to collapse
you using wrong command.
try:
fastboot flash recovery xxx.img
for root i recommend using TWRP and flash the SuperUser.
Make sure you using the correct recovery image...
All you need in here
kativiti said:
you using wrong command.
try:
fastboot flash recovery xxx.img
for root i recommend using TWRP and flash the SuperUser.
Make sure you using the correct recovery image...
All you need in here
Click to expand...
Click to collapse
It didnt worked, I download again twrp files and this time I guess I found newest version which worked with fastboot boot recovery.img
Thanx anyway