Related
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Thankyou!
Just wanted to say I'm the guy that messed up his phone and needed Jason's help. He got me into a Sense ROM and was able to then get clockwork running again and restore my Nand. Really save my bacon.
Also, I've followed your advice. I now have a rooted AND S-off hero running Gingerbread.
Thanks again!
jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
Really? Thanks for the Info... Helpful, and Good to Know!!
Sent from my Hero using XDA App
wow, this is valuable information. couldnt this be put into the wiki or something? i tend to go to the wiki often, but i dont know how to properly edit a wiki.
jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.
Houndog101 said:
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.
Click to expand...
Click to collapse
Which bootloader version do you have, and where did you get the fastboot binary?
jasonmaloney said:
Which bootloader version do you have, and where did you get the fastboot binary?
Click to expand...
Click to collapse
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..
hey Jason here's some background on his problem, I linked him this thread, hopefully you have more patience than me, but you know me, I don't really and I'm a dink http://forum.xda-developers.com/showthread.php?t=984688
Houndog101 said:
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..
Click to expand...
Click to collapse
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.
jasonmaloney said:
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.
Click to expand...
Click to collapse
Jason, Thanks a million times, That was a problem, I d/l your fast.boot and it got me to the Black with silver htc screen. I'll see what I can do from here. Just want to get it to where I can boot into recovery.. Thanks again for helping me.
I've followed all the instructions but with a slightly different problem. I can't get to bootloader at all, but if I plug my hero to my pc and turn it on then it will say "fastboot usb" in a red rectangle at the top left, but is still otherwise the white HTC screen. when I do "fastboot oem rebootRUU" the terminal says okay, but the phone reboots into the same state instead of the black and silver screen I am hoping to see. Is it a brick or is there another option?
I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.
beand1p said:
I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.
Click to expand...
Click to collapse
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Yea It's Me Again With the
Modified Hero
laie1472 said:
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Click to expand...
Click to collapse
I get the same error even with that zip. I am S-OFF also. I have HBOOT-1.47 with radio 2.42.01.04.27.
I've tried almost everything to unroot and get back to stock. I am about ready to throw in the towel.
Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]
dpeeps74 said:
Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]
Click to expand...
Click to collapse
All the stock RUU's I have tried always give me the RUU Error [140]: BOOTLOADER VERSION ERROR
EDIT
I was able to RUU after using this method: http://forum.xda-developers.com/showthread.php?t=843544
I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.
zbach said:
I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.
Click to expand...
Click to collapse
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.
jasonmaloney said:
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.
Click to expand...
Click to collapse
I have the zip file in the android file along with the fastboot.exe program. I still get a "Cannot load" error message
thank you x100000.
I couldnt flash the original ruu because of the weird bootloader issue, but this worked like a charm and i was able to flash with a .zip of the ruu.
Thanks again.
last night i flashed an update of clockwork mod through rom manager. i then went to do a back-up of my current rom. the phone re-booted to the fastboot mode and now says no boot or recovery img. when i scroll to recovery and click it, the phone reboots right back into the bootloader. i am trying to flash a new recovery through adb but i cant get anything to connect. when i do "adb devices" in the command prompt i get the daemon started and list of devices but there are no devices listed. "fastboot devices" does nothing either. i have the android sdk loaded onto c:\ and the drivers seem to be installed correctly. when i rooted the phone i used a different pc that i dont have access to now. i also used pdanet for the drivers so i have never had the google drivers set up correctly. i type fastboot flash recovery recovery.img and it says "cannot load recovery.img" i have downloaded the recovery-clockwork3.0.0.5-crespo.img to the "tools" folder and renamed it "recovery.img"
i have tried to explain everything i have done so far but i am sure there are some steps i have missed. i read some on odin and downloaded it but i am even more lost trying to figure that out. i really need some help here and i would appreciate anything i can get
when you're in bootloader, you're supposed to use "fastboot"
you cant flash a recovery using adb.
go into bootloader mode
fastboot devices
... if your device doesn't show up, then your drivers are not properly set up.. uninstall them and look for the sticky and reinstall your drivers using those set of instructions; assure your SDK is updated to support 2.3.X
when you get your device to appear in fastboot devices.
download clockwork recovery 3.0.2.5 (3.0.2.4 is buggy) or 3.0.0.5; 3.0.2.5 is found in dev forums; rename it to recovery.img
put it in /sdk/tools/
fastboot flash recovery recovery.img
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
tohg2 said:
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
Click to expand...
Click to collapse
if your device is unable to GET into bootloader mode... that wont get you anywhere.
when you plug your phone into the computer with the USB.. does that USB sound pop up? if it doesnt.. then its bricked.
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
when i plug the usb in i dont hear a sound. the phone will only boot into "fastboot mode".
when i do fast boot devices i see "38328e03afbf00ec fastboot"
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
bootloader mode is for fastboot. you wont be using ADB to recover your device.
you unzip the file. it should be like: clockwork-recovery-version..blah blah blah.img
rename it to "recovery.img" assure that your "fastboot" appears as "fastboot.exe" and not just "fastboot." if it is "fastboot" you need to go into folder options and show extensions otherwise you'll be trying to flash "recovery.img.img" and SDK wont recognize it
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
Make sure you are typing the full file path, for example on my setup its "fastboot flash recovery c:\android\tools\recovery.img"
Sent from my Nexus S using XDA App
file extensions are being shown and it is named recovery.img. still saying cannot load "recovery.img" i have tried several recovery downloads from different sources. as for file size of the img its 3,988kb sound right? i tried fastboot oem lock and unlock and everything worked fine. is there another recovery img i can try. maybe a stock recovery or somehting?
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
tohg2 said:
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
Click to expand...
Click to collapse
cd C:\program files (x86)\android-sdk\tools\
fastboot flash recovery recovery.img
is what you want to do.
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
tohg2 said:
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
Click to expand...
Click to collapse
Odin is last resort. If fastboot devices shows your phone you will be able to flash recovery. Reinstall phone drivers and get fastboot to work. Then get back to trying to flash recovery. I really think it is some small mistake. Did you exctract the zip of recovery and copy the .img file?
The error you were getting means the appropriate file was not found in the file path you specified, so its not a phone error.
Sent from my Nexus S using XDA App
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
tohg2 said:
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
Click to expand...
Click to collapse
Cool! Glad you got it, good job!
Sent from my Nexus S using XDA App
Please help, I'm having the exact the same problem
I know, I shouldn't have play around with my phone since I don't know much about rooting the device.
My phone booted into Andriod logo with an unlocked, I have successful downloaded
clockwork recovery 3.0.2.5 and rename it to recover.img
I ran following command
fastboot flash recovery recovery.img and it was successful..
I tired to reboot my phone after that as normal but I'm still getting the same screen which only showing the Android Logo with an unlocked lock.
I'm not sure what I am suppose to do after need to get my phone to work again, any help would be appreciated.
Thank you,
SOLVED!!
Hey guys, i've seemed to set myself up for a soft brick upon me not reading everything clearly and correctly.
I was trying to take an easy route and simply misread a few numbers.
I really need help here, I unlocked my bootloader then proceeded to use a 1 click root solution from here; http://android.modaco.com/topic/327000-08-aug-grj22-colour-revert-superboot-rooting-the-nexus-s/
I just went back to stock after wanting to start clean when I got this phone, anyway I didn't see that this was intended for 2.3 where as my phone was running 2.3.4 and thats where I think I went wrong.
I can access bootloader, after trying this method the phone just boots and hangs at the unlock screen and nothing else. I don't have recovery so I can't get into that, I tried locking and unlocking the bootloader to see if that would help but no luck.
Where do I go from here?
**at&t model
If you can access the bootloader, you're fine. Just install ADB on your computer and flash a custom recovery image. From there, you can flash a ROM.
deejaylobo said:
If you can access the bootloader, you're fine. Just install ADB on your computer and flash a custom recovery image. From there, you can flash a ROM.
Click to expand...
Click to collapse
im trying to push a recovery img from cmd and it's telling me "error: cannot load clockworkXXXXXXXX
I think you may not have entered the full file path when pushing the recovery image.
deejaylobo said:
I think you may not have entered the full file path when pushing the recovery image.
Click to expand...
Click to collapse
I was trying to follow this recent guide here; http://forum.xda-developers.com/showpost.php?p=18257219&postcount=1
the very last part about unlocking the bootloader
and it just keeps giving me that error
Okay, been awhile since I did the whole unlocking bootloader/flashing recovery thing. If I remember correctly, in the command prompt, you should navigate to fastboot which is located in <whatever you named your Android SDK folder>/platform-tools folder. Also, place your recovery image in the same folder. Then enter the command from the tutorial. "fastboot flash recovery <image recovery file name>"
sent you a PM
a huge thanks to deejaylobo for helping me out, a folder wasnt renamed so I had a hard time pushing recovery but he got me back on my feet!
thanks again!!
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).
irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.
irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.
Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.
by the way...if we can get this working, I'll post a picture of me holding the fixed phone!
My first post here so go easy on me
Anyway, I got an Evo Shift, I do not know its history, but its stuck in some sort of a boot loop, on the white screen with green HTC logo.
Things I know:
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT -0.99.0001
RADIO - 1.08.01.0111
Clockwork Recovery v5.0.2.0
I did not get an SD card with it, no recovery image.
RUU says version is 2.77.651.3
I know the S-on is a problem.
I have tried all 4 of the RUU versions - failed.
Tried RUU with Gold Card - failed.
Tried rom.zip from each RUU renamed to PG06IMG.zip - failed.
I have tried custom roms of all sorts, every methoud I found - failed.
Where do I go from here? Is there a way of manually flashing all the partitions from a ROM.zip file via fastboot? Is there a way of disabling a version check in RUU? Or is there a way of disabling MD5 sum in Clockwork so I can try flashing a restore image from another Shift?
I have spent 3 days on this phone, and I would hate to admit defeat, so I am reaching out to the genius minds here. Thanks in advance!
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
gzetski said:
Okay, I fixed it. Please delete the thread. Unless someone wants me to do a write up on how I did it in case someone else fubars their phone.
Click to expand...
Click to collapse
Did you unlock the bootloader with htcdev tool?
The bootloader was already unlocked when I got the phone.
Thanks for this. I will test it and add it to my guide.
VICODAN said:
Thanks for this. I will test it and add it to my guide.
Click to expand...
Click to collapse
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Place misc.img and PG06IMG.zip on sdcard using windows explorer or "adb push /sdcard/file.xxx" via usb
Click to expand...
Click to collapse
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
And BTW, I am now rooted, but with S-ON... Grrr. Superuser works, rom manager works, pretty much anything requiring root access works. I have rebooted the thing like 20 times to see if it goes away, and its sticking just fine, but I am afraid of trying to flash a custom rom with the S-ON.
All attempts to flash ENG bootloader fail, both by flashing via fastboot (all my MD5 sums match, the process is flawless from start to finish, when I reboot, still same bootloader with S-ON), or using ShiftRR.
Any ideas?
gzetski said:
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
Click to expand...
Click to collapse
shift-rootkit.rar
Read the prereqs.
Okay, got it.
Too many things floating through the intertubes with similar filenames.
gzetski said:
Okay, got it.
Too many things floating through the intertubes with similar filenames.
Click to expand...
Click to collapse
Yep, I've finally got the thread pinned, and I created 2 videos on how to do it the right way. They are uploading to youtube now.
S-off?
Did you ever figure out how to get S-Off? I seem to be right where you were a few days ago with the phone appearing to have root, but S-on still there. I'm also running HBOOT -0.99.0001 and unlocked via the HTC Dev tool. Is there anyway to downgrade to .93 or to turn S-Off. My ultimate goal is to get Cyanogenmod on this Shift.
Thanks in advance!
I have not messed with the phone for a few days. I am gonna try to go back to 2.3.4 then downgrade again. Most likely what I ended up having is a bunch of borked files, hopefully the latest RUU will fix that. This was really intended as a brick fix and not a legitimate 2.2 downgrade. When I mess with it, I will post the results for you though.
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
MTsol said:
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
Click to expand...
Click to collapse
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
drob311 said:
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Yes Sir . Been there done that. Had a HERO that somehow got " water damaged " after it was BRICKED .
signature verify fail
gzetski said:
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
Click to expand...
Click to collapse
First, I want to thank you for posting this even though it hasn't yet worked for me. I'm in essentially the same position you started in. Phone will not boot past the green-on-white HTC logo. I boot to recovery and can get to fastboot mode with USB detected. I flashed recovery.img and boot.img with no problems, but trying to flash dzdata onwards gives me the same error every time: "(bootloader) signature checking... FAILED (remote: signature verify fail)" and will not flash the other components from ROM.ZIP.
Any thoughts on how to proceed? This thing is rapidly approaching permanent brick status.
You need to unlock your bootloader and then flash the rom. zip files through fastboot
The "failed" message means that your bootloader is locked
to get S-off the easiest method is to downgrade your device from 2.3.4 to 2.2 and then FOLLOW THE SAME INSTRUCTIONS AS OBTAINING S-OFF ON 2.3.4. i had the same issue when i first unlocked my Shift bootloader.