Database Info

Can't flash recovery/ROMs/achieve root?

I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?

New Jer-Z said:
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
Click to expand...
Click to collapse
You skipped right over the "can't seem to able to flash a recovery."
Please explain in detail the instructions you followed AFTER unlocking via HTCdev.com. This includes files you downloaded, where you put them, how you attempted to flash, etc.
These details will be very helpful. Don't worry, sounds like you're not in any serious trouble at all. Just don't go flashing anything you see.
Also, please post this to the Q&A forum or General next time. This development forum is intended for development posts ONLY (ie. ROMs, Kernels, Radio's, etc). Just a heads up. Welcome to the forums

Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?

Moved To Q&A​
Please post all questions in the Q&A section​

New Jer-Z said:
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Click to expand...
Click to collapse
Ahhh, not to stir up the pot here, but you're getting vague again with what's going on. You say "when I try to reboot into recovery, I don't get very far". What do you mean by this? Details are extremely important in helping you. Sounds like you're saying that recovery was successfully pushed, but then I didn't get any details as to what's going on when you attempt to load recovery. Also, which recovery file did you use? Use this one
I'm not trying to get on to your case here, but you've got to be really specific when you say stuff doesn't work, because that doesn't help us diagnose your issue. When your recovery is done flashing, you should be able to access the bootloader by holding Pwr + Vol-Down for like 5 secs, then choose recovery (that or fastboot>recovery....I cant recall if recovery is a main menu item). What happens after you choose that? Mine shows the htc splash screen, with a development message in red, and then it boots Clockworkmod.

No, no, lol I totally understand, I guess I am being vague.
I was going to go into details, but I was at work. Interestingly enough, my phone died, and when I plugged it and let it charge for a little bit, the phone booted right into CWM touch - so odd! So I was like, ok, i've achieved root - well, no, cuz I opened ROM Manager and it says SU couldn't be found.
BEFORE, when I would do what you said I should do, it would take me to the HTC splash screen where it was in red text, some disclaimer about some proprietary information crap, then it would skip recovery and just boot into Android -___-
Let's see if I can replicate booting into recovery now. (What method are you using to flash your recoveries?)
EDIT: Well it looks like I can't get back into recovery. Same thing as mentioned above. I can get to the fastboot screen, but if I click recovery, it takes me to that HTC disclaimer screen, the little loading bar loads then - poof - screen goes blank and Android boots up.

I have the same problem -_-! Can someone help please
The recovery image was flashed succesfully from Hasoon2000's toolkit. But when i go to the bootloader and select Recovery, I get the red warning for from HTC about how this is for development purpose only... then the phone's screen goes black, then it boots into the stock ROM.

Cant flash recovery
Hello everyone.
I have a similar problem. I successfully proceeded with the bootloader, but now I can't install the recovery. It simply wont flash.
I was following the xda tutorial that's in this very forum, but i got stuck: In my desktop i downloaded the needed files (or so I believe), and so i have in my desktop a folder called "carpeta" (random name) with these files within: adb.exe, adbwinapi.dll, fastboot and 3 different recovery images i have tried to flash.
I use mac, so i open the command prompt for mac (terminal) and go to the "carpeta" folder and after that, I type "cd fastboot flash recovery xxxxx.img" (the xxx are the names of the recovery images that i have in the folder, one at a time) but it simply wont flash anything. I attach a screenshot to ilustrate what happens...
Please help me
http :// img710.imageshack.us/img710/6026/capturadepantalla201205.png

Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps

I'll give it a shot later tonight on my lunch break.

batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...

alexjuanes said:
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
Click to expand...
Click to collapse
Make sure that you navigate to the proper folder using the "cd" command.(for example" cd C:\Fastboot ", if your adb and recovery are in that location)
Make sure that the Clockwork Mod recovery file is in the same folder as the adb and make sure that you type the file name correctly
I used these file and put the recovery image inside the folder after unzipping
http://www.mediafire.com/?50baad8rykng2j0
Here is the recovery I used :
http://loadbalancing.modaco.com/download.php?file=r2-modaco-recovery-clockwork-touch-ville.img
But your running Mac so I don't know if the method I used will work for you because I'm on Windows

Doesnt work...
I have the bootloader (when i start in bootloader mode my phone says ***tampered*** and also ***unlocked***.
BUT
I've been 2 days trying to flash my recovery on my htc one s from my macbook, and after i use the command prompt to get to the folder where i have adb, fastboot, my recovery .img file,etc... this is what happens:
-----
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$ fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
-bash: fastboot: command not found
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$
-----
ive already updated all that i could in the sdk manager, or whatever its name is...
please some help?

batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
This actually worked for me. I am rooted, and am now running a custom ROM.
Thanks so much for all your help!

Hey everyone
i seem to have made a very tiny bit of progress here since now i can type the commands and make it start, but only that... starting.
my command box is stuck in a "waiting for device" message that will start nothing, and my phone is just there, untouched.
i never thought flashing a recovery would give me this much of a long headache...
help anyone? how do i make my pc stop "waiting for device"?

Have you tried a different USB cable/port? I had a similar problem but moving to a different port worked.
Sent from my HTC VLE_U

I have the same problem i did everything as in the guide posted here http://forum.xda-developers.com/showthread.php?t=1583427
But when i flash recovery through fastboot ( fastboot flash recovery recoveryname.img) everything goes ok but when i want to boot into recovery i get stuck on the HTC screen.
Than i wanted to go to recovery trough fastboot ( fastboot boot recovery ) i get message cannot load recovery.
If you need more info for help i can provide you guys with the screenshots.
Thanks in advance Nikola.

[Q] Nexus s 4g locked up

Okay, first of all I know, I'm a total noob. I have followed these forums a long time and have successfully rooted a few phones. One of which was my nexus s 4g. I was trying to unroot the phone so I could get ics. This is when I ran into problems and right now I just want to be able to get my phone working again. Right now I am stuck on the Miui boot up screen and no matter how long I wait it stays on that screen. If I do a battery pull and hold down power and vol up I can get into the bootloader screen with the information as follows: fastboot mode, product name-Herring, HW Version Rev 34, Bootloader version-D720SPAKE1, Baseband version-D720SPAKE1, Carrier info, SPR, serial number-37308B81276A00EC, Lock State-locked. Then the different options I can choose are reboot bootloader, reboot, recovery, power off. If I choose reboot, it takes me back to the mius screen and stays there. If I choose recovery, I get the triangle with the exclamation point. I then hold power and up volume again and I get a screen that says Android system recovery <3e> with reboot system now, apply update from sd card wipe data/factory reset and wipe cache partition. I have tried all of these as well with no luck. When I go to apply update from sd card I get matrix-cfs_v15.5 zip, root.zip, update.zip and then what looks like apps such as Alarms/, Android/,MIUI?, etc. If I try to select any of the first ones such as matrix-cfs_v15.5 zip, I get Install /sdcard... , finding update package..., opening update package..., verifying update package..., E.signature verification failed, Installation aborted. Then it gives me the system recovery options again. Any help would be appreciated.

Did you try ADB fastboot method?

Not sure how to try that

I tried doing the adb, followed all directions and installed and when I go to the command prompt and type in anything, such as, adb reboot bootloader I get, adb is not recognized as an internal or external command, operable program or batch file.

ok I got that working now but when I type adb devices and press enter I get a message saying List of devices attached and then it doesn't show anything and I get the command prompt again saying:c:\android\android-sdk\platform-tools>

also since the phone is stuck in either the miui screen or bootloader I can't get into it to put it in usb debugging mode. I am trying on my own to get this going and am stuck any and all help would be very much appreciated.

TerryUK98 said:
Lock State-locked.
Click to expand...
Click to collapse
I think that means you have a locked bootloader.
And from what you're telling, I believe you have stock recovery.
Also, when you're in fastboot mode, I don't think adb commands apply. Use fastboot commands instead (i.e. fastboot devices).
Search for guides showing you how to install and use fastboot.

I did fastboot as well and the problem I think I am having is it's not recognizing my phone because usb debugging wasn't turned on before it locked up. How would I get it to recognize my phone or download an img to my phone if it is not being recognized. Sorry if this is a stupid question.

You don't need usb debugging in fastboot mode.
You either:
1. Don't have drivers installed.
2. Don't have fastboot installed correctly.
You really need to read a guide or two, through and thoroughly.
Bc it sounds like you have no clues.

Yeah dude. Take a step back and go over what you have installed and where you installed it.Yes, fastboot commands start with fastboot instead of adb. And you're on stock recovery.

Thanks for the answer that I don't need usb debugging in fastboot mode, I wasn't sure of that. I have downloaded and installed my drivers multiple times and when I use the device manager to update drivers it says I have the latest drivers installed already. Whenever I do fastboot commands I will type in fastboot devices and shouldn't my device serial number come up? It just gives me the line c:\android\android-sdk\platform-tools>
And is waiting on me to type a command in. And yes I have been looking at guides all night. I appreciate any help you guys might have and remember we were all noobs at one time.

The zip in this tutorial should help.
It has adb, fastboot, and the drivers needed.
And unlock the bootloader because it is locked.

Finally got it, I had everything downloaded that I needed already, but looking at different forums, etc, it seemed like everyone named it something different. So I just used the one link you gave me and did it exactly the same way and it worked. Thanks so much! and again thanks for your patience.

[Q] Issues flashing custom recovery

I just got this phone, and was told to unlock the bootloader and flash custom recovery as the first step, so I'm following this guide: forums.oneplus.net/threads/full-guide-setting-drivers-up-unlocking-bootloader-flashing-recovery-roms-kernels-rooting.291274/
I've been following it to a T and everything was working well. Once I got up to #3 and type in cmd "fastboot reboot" and it boots back to normal mode (so I can disable Cyanogen Recovery), typing "adb reboot bootloader" in cmd returns "error: device not found." If I'm in fastboot mode and enter "fastboot oem device-info" it returns true for tampered and unlocked so I know I have the bootloader unlocked. If I'm in normal mode, the phone shows up in device manager under portable devices. If I uninstall it, it disappears from the list. Once I unplug it and plug it back in, it pops back up in the same place, saying device installed correctly. If I try to update the drivers, most of the options from the Manufacturer list (see in the gifs from the guide) are gone, including the google ones.
How do I move from here? should I just wipe the whole thing and try again? What's the best way to do that? If I use the the USBDeview thing and remove the A0001 driver, will that allow me to put the android ADB Interface on the phone (Basically starting over)?
Thanks friends. Really excited to get going on Android!

threemor said:
I just got this phone, and was told to unlock the bootloader and flash custom recovery as the first step, so I'm following this guide: forums.oneplus.net/threads/full-guide-setting-drivers-up-unlocking-bootloader-flashing-recovery-roms-kernels-rooting.291274/
I've been following it to a T and everything was working well. Once I got up to #3 and type in cmd "fastboot reboot" and it boots back to normal mode (so I can disable Cyanogen Recovery), typing "adb reboot bootloader" in cmd returns "error: device not found." If I'm in fastboot mode and enter "fastboot oem device-info" it returns true for tampered and unlocked so I know I have the bootloader unlocked. If I'm in normal mode, the phone shows up in device manager under portable devices. If I uninstall it, it disappears from the list. Once I unplug it and plug it back in, it pops back up in the same place, saying device installed correctly. If I try to update the drivers, most of the options from the Manufacturer list (see in the gifs from the guide) are gone, including the google ones.
How do I move from here? should I just wipe the whole thing and try again? What's the best way to do that? If I use the the USBDeview thing and remove the A0001 driver, will that allow me to put the android ADB Interface on the phone (Basically starting over)?
Thanks friends. Really excited to get going on Android!
Click to expand...
Click to collapse
You probably don't have ADB enabled on your OPO, but you don't even need it for this. "adb reboot bootloader" is just a handy way of rebooting to fastboot without shutting down and holding the up volume button while turning it on. Once you get into fastboot by doing that, continue on as the guide says! (i.e. "fastboot flash recovery xxxx.img")

Z3 Won't start or enter recovery

Guys,
I need help. I'm struggling for the last 3 days trying to revive my phone with no sucess. :crying::crying::crying:
I managed to put a custom rom sucessfully, but i had to make a restore on recovery mode.
During the restore process some error ocurred, something like "something not mounted", i did'nt have the ROM to flash anymore. For no reason i decied do reboot the phone.
Now i can't enter recovery anymore and the phone is froze on the "Sony Xperia" on the begginig.
Since start i'm having difficulty with the Z3 driver for Windows 10. To enter recovery mode i tryed to adb reboot recover but my adb doesn't work.
It's strange..
if i type fastboot devices it's show.
if i type adb devices it's show's "no emulators/xxx found".
I need help, don't know what to do anymore.
TLDR:
- Frozen at "Sony Xperia"
- Recovery don't enter pressing Volume Down/UP
- adb devices doesnt' work.
- fastboot devices work
Thank you!

pedroveber said:
Guys,
I need help. I'm struggling for the last 3 days trying to revive my phone with no sucess. :crying::crying::crying:
I managed to put a custom rom sucessfully, but i had to make a restore on recovery mode.
During the restore process some error ocurred, something like "something not mounted", i did'nt have the ROM to flash anymore. For no reason i decied do reboot the phone.
Now i can't enter recovery anymore and the phone is froze on the "Sony Xperia" on the begginig.
Since start i'm having difficulty with the Z3 driver for Windows 10. To enter recovery mode i tryed to adb reboot recover but my adb doesn't work.
It's strange..
if i type fastboot devices it's show.
if i type adb devices it's show's "no emulators/xxx found".
I need help, don't know what to do anymore.
TLDR:
- Frozen at "Sony Xperia"
- Recovery don't enter pressing Volume Down/UP
- adb devices doesnt' work.
- fastboot devices work
Thank you!
Click to expand...
Click to collapse
You have some choices to restor stock rom:
1) Try Xperia compagnon fron Sony ==> Software repair (not shure about the label in english version)
2) Use flashtool (google for it) and a rom (*.ftf) of your choice.
When you are back to stock, then you can install a custom rom again
HTH
Norbert

Hey,
Sounds like a corrupted system, not too sure what happened with the recovery though.
Try this out:
1. You need the phone driver and the fastboot & ADB driver. You can get the Sony phone drivers from the Xperia PC Companion. You can get fastboot & adb drivers almost anywhere, just google for them or scroll a bit through xda.
2. Unlock your bootloader if you haven't done so already here.
3. boot into fastboot mode by completely powering off the phone then holding "power+volume up" and waiting until a blue LED appears in the top left.
4. Find a custom recovery, rename it to recovery.img, navigate to the folder that contains it in CMD (i.e. cd C:\Users\USERNAME\Downloads\Android) and type "Fastboot flash recovery recovery.img"
5.You should now be able to boot into recovery again. All that's left is find a ROM of your liking, push it to the phone in ADB and install it.
Hope this helps!
Samyam25

Phone wont go into bootloader. How to root + flash new recovery?

Hello. I can't get my phone rooted in any way.
I want to Root so I can use TWRP app to flash TWRP recovery .img, and after that I can boot into TWRP recovery and flash new ROM. Correct????
What I've tried so far. OppoTools 1.6.5 = One key root gets hard stuck on Oppo logo at start-up and then I have to flash Coloros ROM again from recovery. Also KingRoot says app not installed. On windows version of KingRoot it gets to some percentage and then it Fails.
I have downloaded "unlocked bootloader" Coloros from this forum that was mentioned before ( Dropbox link )
I have also tried two different ColorOs versions.
I have installed 15sec ADB installer.
I plug my phone into PC and run CMD.
I type adb devices into command prompt and it detects my R7 plus.
then I try to command " adb reboot bootloader "
Phone restarts normally and doesnt go to bootloader. Tell me if im stupid, but isn't Bootloader different than Recovery? Because I can get to recovery command "adb reboot recovery"
I tried some weird button combination Vol+ Vol- + Power and phone semibricked for awhile and PC didnt even react USB driver correctly and almost waved the white flag on this case.
I've enabled USB-debuggin and OEM unlock from devices dev-options.
When I to type command "fastboot oem unlock" on command prompt is says Waiting for device. Nothing pops-up on device and nothing happens.
So now Im stuck on situation that my phone doesnt launch into bootloader where presumably "fastboot oem unlock" would work?

If you have flashed the version of Color OS that has bootloader enabled, you should simply need to go into the settings, enable USB debugging and OEM unlocking, then shutdown the phone before holding the power and volume+ buttons and waiting the ADB bootloader screen. After that, just plug it into the computer and follow the guide on flashing twrp with ADB.