[Q] Help flashing new Radio - Desire HD Q&A, Help & Troubleshooting

I seem to have an annoying problem. When the phone is connected via USB and is properly on i.e. in the sense launcher and everything, typing 'adb devices' on cmd works fine and I find the device. However when I power down
1. it goes into recovery
2. If I do manage to get into bootloader the PC tries to reinstall the drivers which it fails to do hence 'adb devices' doesn't come up with any results.
Any help would really be appreciated.

Android SDK?

Few quick questions, you have installed ADB drivers(i guess you have else no "devices" would show)? You are running in USB Debugging? I have only known fastboot to work in recovery mode, which guide are you following to flash the radio?
As far as i remember it is all fastboot commands once you have ADB reboot recovery then it's something like fastboot copy radio.img etc,
Check this post http://forum.xda-developers.com/showthread.php?t=896597

@Xtrema - I have the android sdk and in tools i put the three ADB files in there.
@wbbigdave - I'm pretty sure I have the ADB drivers because I can find it when the phone is fully on and I have HTC sync installed which has the Desire HD come up. I'm using this guide to flash the radio and method 2 since it seems like the method that the Android Rev maker said to use.
http://forum.xda-developers.com/showthread.php?p=11557769
My main problem is that it won't find my device when I'm in the bootloader :S but finds it when the phone is fully on.
Shall I try Method 1?

Method 1 is the one i use.
Download the radio flash.zip and extract to desktop, extract the radio.img file into the extracted folder. Then double click the 'start here' file. This will then open a command window into which you type the commands.
Phone should be in recovery when you do this.

Thanks alot, I was getting confused. Method 1 seems a lot easier but I was already in fastboot when I wasn't suppose to be
So far it seems to have gone through. How do I make sure I have the correct radio. In the bootloader will it not show the first half the the radio file name?

Settings, About phone, Software information, Baseband version.

Related

[Q] Can't flash img-files. Need tips!

I want to update radio and clockwork mod recovery but I can't flash image files. I tried two ways the below one being the first:
"1. Extract the contents of the radio zip package. You should have radio.img file in it.
2. Copy/move the radio.img file to “Tools” directory of the Android SDK setup. Fastboot.exe will also be located in the same folder.
3. Connect the Phone to computer via USB cable.
5. Open the command prompt and run the following command:
adb reboot bootloader
fastboot flash radio radio.img
6. Wait for the radio flash to complete.
After flashing is completed, reboot your Android phone. It should boot with the new Radio ROM! That’s it. You have successfully installed Radio.img on your Android Phone."
I couldn't run the fastboot command. After reboot to bootloader I couldn't connect to the desire. All I got was an error message saying "device not found". What's up with that? I do have the right drivers (at least i think so). Before the reboot the device was found all right. I rebooted via the command prompt and it worked just fine. USB debugging was activated all the time.
The second method I tried was using android terminal (trying to flash the new recovery) like this:
su
flash_image recovery /sdcard/recovery.img
The super user command worked fine but the next one didn't. Another error message "flash_image not found"
This has nothing to do with the recovery image not being in the right place or me misspelling. Tried it many times belive me. What seems to be the case is that I don't have flash_image on my phone.
Am I missing something here. I'm new to rooting and installing ROMs so I figure I might
Background:
I just recently rooted my Desire. I wanted more space for apps and to get rid of many apps included in the stock ROM.
I searched all over the place and figured Redux to be the ROM for me. I used the unrevoked method too root and Alpharev 1.8 to S-off. I use the Oxygen HBOOT flashed via the zip-file from Alpharev. I don't think I've ever used adb to flash images since I never had to.
Any ideas?
1. Install the HBOOT drivers form unrevoked site (From here.)
2. Download android SDK from their site and install it + platform tools, revision 3 (from SDK MANAGER).
3. Reboot the phone into fastboot (POWER + BACK key). Should say FASTBOOT USB.
4. Run CMD.EXE and navigate to your folder where is fastboot.exe is located (android-sdk-\tools) on your hard drive.
5. run command (e.g. fastboot flash radio xyz.img)
6. run command reboot-bootloader
Sorry, for the noobish instructions, but this should work, I just did it yesterday.
Don't worry, I'm a noob
I have already done 1 and 2. All drivers are up to date. I do get to FASTBOOT USB when doing 3 but then I can't execute any adb commands due to my device not being found.
Weirdly I can see Android Phone 1 on my laptop where you unmount en externel drive.
I might just do steps 1 and 2 over again.
For now I managed flashing the new Clockwork Mod Recovery using a guide suggesting to download a flash_image file extracted from one of the cyanogenmod ROMs and pushing it to the system/bin directory on the phone. adb commands works fine when the phone is completely rebooted so I could do that. Then I just used Terminal Emulator to flash the recovery image.
Thanks for your instructions!

[SOLVED]What happen if I flash ROM using the not recommended recovery?

Hi there.
As the above title says, what happen if I do so?
I do not have recovery version 2.5.1.3 in my ROM Manager anymore(I have no idea know why). Also do not have 3.0.2.5.
The only recovery I have is 2.5.1.4, 3.0.0.5, 3.0.0.6 and 3.0.2.4. Plus I am unable to flash 2.5.1.4 version(it pops up an error)
Some have no issues, but some have experienced issues when trying to restore cwm backups.
Have a look in the LeeDrOiD 2.2.3 thread a few days ago. I have posted methods to manually flash it via a tool or adb commands. I have also provided dl links as well.
Sent from my Desire HD using XDA App
Hi Upintheair
Thanks for the reply. Erm.. do you remember the exact date you post that in LeeDroid's thread? The thread is overloading. I cannot find them. =(
From Index of /cm/recoveries Download recovery-clockwork-2.5.1.3-ace.img
Try one of these 2 tools, instructions are on the threads;
1. Thread: [TOOL][All devices & OS] Fastboot Commander [v.1.1]
Download: Fastboot Commander v1.1
2. Thread: Android Flasher
Download: [UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.7.4]
OR
Manually through ADB:
1. Place the image in where fastboot.exe is located.
2. Connect phone to PC with Bootloader FASTBOOT USB
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
Click to expand...
Click to collapse
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
kgulruh said:
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
Click to expand...
Click to collapse
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Edit: I would advise flashing through a battery only powered notebook, don't want a power surge or cut 1/2 way through a flash . Also ensure notebook & phone batteries have near full charge.
Fastboot Commander v1.1 is compatabe with Linux, there is instruction how to install the tool in the Dev's thread. It has everything you need in the zip, and no need for the adb / fastboot commands in CMD.
...............The first result Mr. Google gave me with the search string "download fastboot.exe" Choice of platforms; Windoes, Mac, Linux
Once extracted, just copy the files into your SDK folder where adb.exe is located (maybe tools or platform-tools........)
To make sure fastboot is working ok, boot phone into FASTBOOT, connect to PC & it will change to FASTBOOT USB. Open up CMD and navigate (cd\......) to the folder where adb & fastboot.exe is now located. Now type "fastboot devices", if connected & communicating correctly using Fastboot commands -> HTxxxxxxxxx, giving the device serial number.
If you want to use CMD:
Place image inside SDK folder where fastboot & adb.exe are located.
Rename it to radio.img (unless you like to type the whole name again)
CMD type: " fastboot flash radio radio.img", then
"fastboot reboot"
I am not too sure about Linux PCs, always been Windows until Android.
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
SERGI.3210 said:
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
Click to expand...
Click to collapse
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Thanks UpInTheAir
I'll try it later tonight. Guess I will try to manually flash them.
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
I just recalled I read it somewhere last time when I was learning how to flash new radio. x)
superstick1 said:
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
Click to expand...
Click to collapse
If you are referring to the "tool" as in the CMD (Command Prompt)?
If this is what you mean, the answer is Yes & Yes.
Most of the tools, some examples & links I've given, just save you time, not having to use the adb or fastboot commands, cd\ (navigate) to the location of adb.exe or fastboot.exe in the SDK folder etc. These tools can also do a lot more, particularly Fastboot Commander which can be run on Windows or Linux.
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
superstick1 said:
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
Click to expand...
Click to collapse
Ensure Fastboot is OFF & USB debugging ON in phone settings
When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
Did you test Fastboot communication by command "fastboot devices"?
Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Edit: I see your signature is ENG S-off?, double check in HBOOT Bootloader. If the above still doesn't work, try the Fastboot Commander Tool, maybe your making a typo somewhere........
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
superstick1 said:
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
Click to expand...
Click to collapse
1. Mine works fine with usb debugging on & fastboot off.
2. Power off phone. HOLD volume down (don't release) & press power button once. Phone will boot into HBOOT, you will see FASTBOOT. Connect to pc with usb cable. Wait a few seconds and HBOOT will change to FASTBOOT USB.
3. Use Cmd (command prompt) in Windows. Pc to navigate to the sdk tools or platform tools folder (where fastboot.exe is located). Now type "fastboot devices", if you are communicating in fastboot, you will get HTxxxxxx (device serial number), and can now proceed with "fastboot flash recovery recovery.img"
If it doesn't work, you have not setup properly, or typo, I would suggest using fastboot commander tool.
Sent from my Desire HD using XDA App
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
UpInTheAir said:
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Click to expand...
Click to collapse
i know, and I understand you, only I say that there are CWM's versions you very validate for flash apart from the recommended ones that work perfectly, I am flashing with the current one (leedroid, coredroid, hd rev ..) and it me works to the perfection and the nandroid also.
Certainly .... which is the meaning of "koush"???
superstick1 said:
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
Click to expand...
Click to collapse
Here are two zip files: Recovery 3.0.2.8 & 2.5.1.3.
3.0.2.8 doesn't show in ROM Manager, but version shows when boot into CWM Recovery, so no worries.
Reference Thread: [RELEASE][25/04/2011] ClockworkMod Recovery 3.0.2.8
I downloaded 3.0.2.8 from the above thread, extracted replaced the 3.0.2.8 image with 2.5.1.3 image (renamed recovery.img), and zipped again to upload.
View attachment Recovery_Ace_v2.5.1.3.zip
View attachment Recovery_Ace_v3.0.2.8.zip
Installation:
1. Power off your DHD
2. Put it in bootloader mode; Power+Vol down and select Fastboot from menu.
3. Plug-in the USB cable. (FASTBOOT USB)
4. Extract xxxx.zip
5. Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
6. Done! The device will be automatically rebooted.
7. If the version doesn't show in ROM Manager, reboot into recovery to check version actually installed.
I tested the windows commands and worked perfect Linux should too!!
I do recommend you read up a bit yourself on adb & fastboot commands, and if you aren't able to do that, use the flashing tools provided by the various Devs, thanks to them, life is much easier.
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
UpInTheAir said:
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Click to expand...
Click to collapse
Thanks a lot man, used the one in cwm 3.0.2.8 update tool "fastboot-linux" and it works perfectly just need to rename it for consistency.
For me typing in linux is better then knowing nothing in windows
superstick1 said:
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
Click to expand...
Click to collapse
I always boot into CWM Recovery menu to flash, and not through ROM Manager (wherever possible).
Try that way.

[answer] [how to] [CDMA/LTE] How To Re-Flash Factory-Image/Recover from Soft-Brick

How To Re-Flash Stock Image
Assuming you have ADB and everything setup already....
1. I just did this for practice. I did not need to do it –but I wanted to do it successfully before I “needed” to do it. I thought I would expand a little on the process and make it a little more noob friendly.
2. Getting started.
a. Read through the entire set of instructions first.
b. I am not responsible if you BORK your phone. I BORKED mine using someone else’s instructions and tried to write a very detailed step-by-step to help others out– but it is completely possible I have also made some small error in the instructions.
3. This will completely wipe your phone – including the SD partition – so transfer any files you need before you do this.
4. This will not re-lock your bootloader. It will remain unlocked.
5. Syntax (spelling, spaces, periods, dashes, CAPITOL, or lower case) matters. There were some spelling errors and file extensions left off the commands – and that will not work.
6.I used the file…
mysid-icl53f-factory-65895fa8.tgz
…which is 4.0.2 for the cdma/lte galaxy nexus [code name = toro/mysid]. The file is located here...
http://www.google.co...NiI9yTxKdUyW1tA
7. Unzip the file (I used 7.zip to do this).
Then you will have a .tar file…
mysid-icl53f-factory-65895fa8.tar
8. Unzip that file and you should end up with a folder…
mysid-icl53f
Inside that folder you will have five files…
i. bootloader-toro-primekk15.img
ii. flash-all.sh
iii. radio-cdma-toro-i515.ek05.img
iv. radio-toro-i515.ek02.img
v. image-mysid-icl53f.zip
Do not unzip “image-mysid-icl53f.zip”
9. Go ahead and copy and paste all these files to your directory…
/android/platform-tools
(or whatever directory you work from. You do not need the “flash-all.sh” so you do not have to copy it).
10. Open the Command Prompt in the directory where you have placed the necessary files by navigating to the directory, pressing shift, and then right mouse click (normally “C: /android/tools” or C: /android/platform-tools). This will bring up the dialogue box and you can select “open a command window here”.
11. Then enter the command…
adb devices
[…this should return your serial number…]
12. enter the command…
adb reboot-bootloader
[wait for bootloader – you should here 2 alert sounds – not just 1]
13. enter the command…
fastboot flash bootloader bootloader-toro-primekk15.img
14. enter the command…
fastboot reboot-bootloader
[wait]
15. enter the command…
fastboot flash radio radio-toro-i515.ek02.img
16. enter the command…
fastboot reboot-bootloader
[wait]
17. enter the command…
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
18. enter the command…
fastboot reboot-bootloader
19. enter the command…
fastboot -w update image-mysid-icl53f.zip
20. So you know, steps 17 (flashing the cdma radio) and step 19 (flashing the update image) took longer than the rest so don't freak out - just be patient. If you did the steps in the proper order after entering the last command your phone should reboot on its own and be completely “fresh”. If you made mistakes (like I did the first time) and flashed the radios out of order (like I did) or did not wait long enough for an “Okay” dialogue (like I did) then when you reboot you will have no signal and no phone number and you will have to go through the process again and do it right (like I did).
Hope this helps someone.
Credit goes to JW at that other site for the fastboot commands. I just added detail for the write up.
Great guide, but what if the serial number doesn't show up?
Thank you for the excellent walkthrough. I am following it, but when I enter "adb devices" at the command prompt I receive "list of devices attached" but no serial number. Also, my Nexus displays: "Fastboot Command Read Error -2147483647". I did a battery pull after getting stuck in a bootloop, and am trying to recover. I can unlock and relock the bootloader, but that is the only command that is working.
Ominous39061 said:
Thank you for the excellent walkthrough. I am following it, but when I enter "adb devices" at the command prompt I receive "list of devices attached" but no serial number. Also, my Nexus displays: "Fastboot Command Read Error -2147483647". I did a battery pull after getting stuck in a bootloop, and am trying to recover. I can unlock and relock the bootloader, but that is the only command that is working.
Click to expand...
Click to collapse
if it does not return a serial number than the phone is not being recognized. I believe that there are 2 different sets of drivers that are needed. Let me look for the link and info.
the fact that it returns "list of devices attached" but no number means that it is not finding your device which means it is probably a driver issue. let me see what I can come up with. But I am no expert at any of this.
Ok - so I just did some testing of my own. I ran into the same problem as you. And I know that I have the drivers installed. So what I did was try and "shut down" any thing that could interfere with with ADB/Fastboot.
Any tethering apps that you may have - PDA NET, Easy Tether, etc, could possibly do this. Also - when you plug your phone in - and the Auto Play options pop up for FTP (File Transfer Protocol) - X out of that.
I initially plugged in my phone. Opened the command prompt in my platform-tools folder. typed in...
adb devices
...and I got the same message as you. I then "turned off" everything that could be causing problems with the process. I unplugged the phone and replugged it in (and closed the dialog box again) and then re-opened the command prompt and entered...
adb devices
...and then I got the proper return message.
thepolishguy said:
Ok - so I just did some testing of my own. I ran into the same problem as you. And I know that I have the drivers installed. So what I did was try and "shut down" any thing that could interfere with with ADB/Fastboot.
Any tethering apps that you may have - PDA NET, Easy Tether, etc, could possibly do this. Also - when you plug your phone in - and the Auto Play options pop up for FTP (File Transfer Protocol) - X out of that.
I initially plugged in my phone. Opened the command prompt in my platform-tools folder. typed in...
adb devices
...and I got the same message as you. I then "turned off" everything that could be causing problems with the process. I unplugged the phone and replugged it in (and closed the dialog box again) and then re-opened the command prompt and entered...
adb devices
...and then I got the proper return message.
Click to expand...
Click to collapse
I got the same problem with mine i dont have anything like pda net installed but nothing i have tried is able to get adb to list my phone
Getting the same issue myself...help!
Thank you so much I'm a total noob with this stuff but your guide was very helpful!
Noev said:
I got the same problem with mine i dont have anything like pda net installed but nothing i have tried is able to get adb to list my phone
Click to expand...
Click to collapse
ChuckTu said:
Getting the same issue myself...help!
Click to expand...
Click to collapse
Ok - so another member posted this...
ADB/Naked Drivers
...and I have heard some people say that it was very helpful. So hopefully this will help you guys to get your devices recognized.
Then there is also this thread and the OP said this...
Code:
On your windows PC. Use the root guide by bman
( [url]http://rootzwiki.com...nlock-and-root/[/url] )
and download the third option for drivers. Extract all
of these tho wherever you have your fast boot
( for me it was c:/users/thatmayh3mguy/) then run
fastboot in the cmd. The adbapi.DLL file will be there
and will make the fast boot work. I didn't have the sdk
installed ( fresh install of win 7 ultimate last week and
don't have it all set up yet) and it worked
thread...
adb help/getting your drivers installed correctly
OK - here is also another method that I found. I have PDA Net installed and I did not have any issues with fastboot. Here are some instructions that say the drivers that PDA Net use are the same drivers that you need for fastboot. So here is a link to the thread and hopefully one of these methods is going to work for you.
Installing PDA Net to solve your fastboot problems
ah ha - just read something else that I should have thought of...
If your phone is already in bootloader - the command...
adb devices
...will not work. so if you are in bootloader you should try the command...
fastboot devices
...instead and see if that returns anything for you.
just wanted to jump back in hear and say i was able to get mine working again. adb was allowing me to lock/unlock the bootloader i toggled that on and off then when i went to boot my phone it took a long time to boot but finally did. Thanks for all the help was in a real jam there for a minute. I used the naked adb drivers posted above not sure if that did anything but it worked for me. Thanks again!
Noev said:
just wanted to jump back in hear and say i was able to get mine working again. adb was allowing me to lock/unlock the bootloader i toggled that on and off then when i went to boot my phone it took a long time to boot but finally did. Thanks for all the help was in a real jam there for a minute. I used the naked adb drivers posted above not sure if that did anything but it worked for me. Thanks again!
Click to expand...
Click to collapse
cool. glad to hear it.
trying this with a Linux OS
So I have a Samsung Galaxy Nexus on Verizon and I put 4.0.4 (IMM30B) using the Galaxy Nexus ToolKit on Windows. Since then I've had a few issues with performance so I want to go back to stock (ICF53F) then maybe goto latest IMM76K (I think). I've retrieved the zip file from steps above and untar'd the file, but when I try to flash the boot file it just sits there waiting for device. I'm not sure what it's waiting for. I'm in fastboot mode and then plugged in the phone to the usb cord but nothing happens.
Any ideas?
UPDATE:
I figured out the issue. On a linux machine using fastboot requires super user privileges. Maybe an update to the instructions may be in order?
CMD keeps telling me waiting for device.
How long will it takes first time?
this after entering: fastboot flash bootloader bootloader-toro-primekk15.img
ladyminnie said:
CMD keeps telling me waiting for device.
How long will it takes first time?
this after entering: fastboot flash bootloader bootloader-toro-primekk15.img
Click to expand...
Click to collapse
Does "fastboot devices" return your device?
If not, you may have a driver issue.
Sent from my Galaxy Nexus using Tapatalk 2
A mistake I made a while ago, if you are sure that you have already installed ADB drivers, and your device still isn't being recognized by ADB..
Be sure USB Debugging is checked on.
Sent from my Galaxy Nexus using Tapatalk 2
adb devices returns my number from the phone
adb reboot-bootloader does bring my phone into bootloader
than it stops with the next command. I waited for 45 minutes/
---------- Post added at 07:03 PM ---------- Previous post was at 06:57 PM ----------
usb debugging was/is still on
The white small led is lightning up every 10 seconds orso
problem solved with:
http://forum.xda-developers.com/showthread.php?t=1766475

[Q] Image Unzipping Fail!!!

Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Freesoft64 said:
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Click to expand...
Click to collapse
Try to go into recovery mode. What exactly is the problem. If it is not booting in...go to recovery and select fix permissions... this will solve any problems. If not try to install a rom with full wipe and reboot. If you flash a PD98IMG.zip then once again you need to root, S OFF, etc etc....
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
JagDave said:
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
Click to expand...
Click to collapse
Well, actualy, i can`t get into Recovery, it reboots and the screen turns black, the only thing what the phone admits is PD98IMG.zip.
Thank you very much for responding!
Delete that file from your SD card, and check if you can get into recovery. If yes, download superWIPE for ARHD, and ARHD rom and install it ( it's different base i think, so you have to superWipe it )
PD98IMG.zip is the radio, if that's what you need they can all be found here:
http://forum.xda-developers.com/showthread.php?t=996630
Might be worth flashing the latest and seeing if your phone behaves enough afterwards to let you get into recovery.
I take it you are trying from bootloader?
Also does your computer recognize the phone on usb?
Sent from The App that Time Forgot.
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
JagDave said:
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
Click to expand...
Click to collapse
I am trying all this and i think it will work, the problem is my phone is "SHIP S-OFF"
But i don`t know hot to change from Ship to ENG...
Thank you very much for the answer, from now in one week i think my DHD will work again
If memory serves, you only need Eng to change the radio.
But don't quote me on that
Sent from The App that Time Forgot.
I have tried this http://forum.xda-developers.com/showthread.php?t=1396253
The PD98IMG.zip worked, so i am glad my desire is not bricked yet.
I still not having access to recovery, my phone is SHIP S-OFF not ENG S-OFF and i can`t change the Recovery, i can`t install the SDK drivers for bootloader.
I tried too with Android Flasher, and there doesn`t work because my phone is not ENG S-OFF.
My questions are this: how i can change now to ENG S-OFF?
What else i can do for revive the Desire HD?
Thank a lot for responding this post, i don`t know what i`ll do without all of you!
Personally I see no reason to Eng soff. You can still flash radios and recoveries with just regular soff. Just its done in a different way.
In that thread you posted their is a link for cwr in a pd98img. Just follow the directions I wrote.(its the first section)
But if you are set on getting Eng soff in the dev section you can use jkoljo tool.
Your second question confuses me. You said your phone is now working so what do you mean by reviving your phone?
Well, i tried ADB, the problem now is when i installed the drivers, in the command prompt i cant find my phone.
I was trying with this:
C:\adb devices
List of devices attached
In Device Manager it appairs like: Android Phone>Android ADB Interface
What i can do now?
I know I'm a little annoying, but I will really appreciate your help if we make it work!
Anyone can help with ADB with desire hd?
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
earthbrother said:
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
Click to expand...
Click to collapse
I did that, it doesn`t work because it says "error: device not found" i tried reinstalling many times the ADB drivers and another few with the path file, no results. With "adb devices" it says "list of devices attached" then, nothing.
I am really gratefull with all your answers, i hope we can made it work
I have a question more, it`s posible to put it in "debugging mode" from HBOOT?
Thanks a lot!
So, nobody can help me? that who help me will be rewarded!
You said only the recovery pd98 works. Reflash it. After it reboot and hangs take out battery and SD card. Reinsert battery and enter boot. Wait for it to scan, then reinsert sdcard and enter recovery. Wipe and reflash a rom or backup
Edit - still confused, from your pm you suggested that your dhd doesn't work? I need a simple yes it boots or doesn't, before we can go anywhere
Sent from my Desire HD using XDA App

[Q] Trouble with flashing new recovery

Hey everyone,
Alright so I have been trying to root my phone for the past 4 hours. I have unlocked it and flashed a custom recovery using adb. Or at least I thought I did. I tried flashing the clockworks recovery and when I would reboot it into the recovery, I would get an icon of a phone and an exclimation point. I assumed a bricked the phone and freaked out. A minute later the phone rebooted out of recovery and works fine afterwards. So I assume that the problem is the recovery. Something went wrong and I am not sure what.
Here are the steps I followed:
I was fine up until step four when I was trying to flash superuser.
No idea what to do from here.
HTC Unlocked = Bootloader is unlocked?
Not to take away from the OP, but i created a guide for a guy here at work and thought others might benefit from it.
Unlock Bootloader and Root
Unlocking your bootloader will wipe all data from your phone. Meaning you will loose everything make a backup.
Step 1: ADB Installation Instructions. NOTE:You must have ADB installed on your PC even if you use method 2b to unlock the bootloader. You will need adb to install recovery in Step 4.
1. Go to http://developer.android.com/sdk/index.html and download the sdk.
2. Follow installation instructions found here. Note: This is not a forum for this device DO NOT do anything but the adb installation on your system.
Step 2a: Download software from HTC to allow your bootloader to be unlocked.
1. Go to http://www.htcdev.com/
2. Login to the website. NOTE: Register for an account if you haven’t already. You must provide a valid email address.
3. Select “All Other Supported Models” from the drop down list and click “Begin Unlock Bootloader”
4. Follow online instructions.
1. SuperUser http://androidfiles.org/securekey.ph.../superuser.zip - Copy this file you phone. Special thanks to jmztaylor his link.
2. Recovery of your choice TWRP Recovery http://forum.xda-developers.com/show....php?t=2161702 or CWM Recovery http://forum.xda-developers.com/show....php?t=2161706. Put this file in the ADB Tools folder. NOTE: You must type the name of this file perfectly when using adb to flash it in step 4.
Step 4: Using ADB to install recovery
1. Open command prompt ( shift + right click, then choose “Open command window here”) and type “ADB devices” you should see you phone listed, if you do not start over at Step 1. NOTE: Phone must be plugged in and USB Debugging must be checked in settings.
2. Type “ADB flash recovery recovery.img” without the quotes. NOTE: the red is actually the title of the recovery file that you copied in step 3. If it’s different substitute your files name instead.
3. Once complete type “ABD reboot recovery”.
4. You should at this point backup your device
5. Once you create a backup, Choose install and navigate to the SuperUser file you put on your phone in Step 3.
6. If all goes well you are now rooted. Select reboot system to restart phone.
There is some very good information here but its spread out pretty thin. Guides IMHO are very usefull to fill the gap between devs/powerusers and the newbs.Most people that come here have a hard time with the things we take for granted such as adb commands, or adb its self (most will be setting it up for the first time). I tried my best to put it in a knowledge base that everyone can understand if for some reason you do not understand what i was trying to say please ask. I don't own this phone, just helped a friend root his, but if you need to get ahold of me pm me. I'll get back to you as soon as possible.
Any help? Just trying to get rid of the bloatware -_-
Did you copy superuser to your phone? And are you sure you are using the correct file location for adb in the command prompt? You must make sure you are and that all files you want to flash are also in the same folder as adb. Please respond if you have superuser on your phone and if you are positive you are using the correct adb folder location for the command prompt. I'm not the best at this however, I read up a lot on it just to root my phone. Took me 4 hours about as well, but that was before the recoverys came out. I suggest trying to flash twrp recovery, it's a bit buggy (for me) but I find it easier to use.
Sent from my HTC One VX using xda app-developers app
Code:
ADB flash recovery recovery.img
that is your problem to start with its not "ADB flash"
boot your phone into bootloader with usb connected to PC, Phone should read "fastboot"
Go the your adb directory in command prompt.
ex.
Code:
C:\PcUser\Master\Androidsdk\adb\
Make sure all drivers are installed, from CMD prompt window type "fastboot devices" to check your phone is showing.
if you see your device then you can type
fastboot flash recovery [drag your recovery image into cmd window] and hit enter and it should flash
once recovery is flashed you can either "fastboot Reboot" or on the phone use the Vol rockers to navigate to menu and hit bootloader then from there choose recovery
Hi,
I have the same issue about 2 days, I install TWRP Recovery and all it's ok, and flash in fastboot mode with adb like ilostchild tolds You.
It seems that I met the same problem.
My issue is the phone only boot into CMW mode, although I tried to restart it many times. When connect to usb cable, lappy did not recognize the phone so I can use adb command.
Please help me.
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
zeratos said:
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
Click to expand...
Click to collapse
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
spooky_ghosty said:
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
Click to expand...
Click to collapse
I already tried all those things you mentioned, I have been looking for 3 days for a solution for this problem on google without any luck, the device doesn't recognize any command either and I already set up a virtual machine and tried on that machine as well. u_u
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Johann12911 said:
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Click to expand...
Click to collapse
Already tried uninstalling HTC Sync, after that I deleted every trace of it. USB Debugging WAS ON before the phone crashed but I can't activate it now because the phone keeps looping between reboots.
Try to flash it via htc sync. Download the update and rewrite everything!
Sent from my HTC One VX using xda app-developers app

Categories

Resources