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.
Related
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.
I get this problem in y htc evo 3d when i open recovery it shows yellow exclamation mark i proceed with pressing volume up+power buttons. Then in bottom of the commands it says Can't open /cache/recovery/command. After i press begin update from external storage it says invalid operation. Success rebooting by reason oem_00. Help me please I tried to install other rom. It is unlocked S-ON non-rooted hboot 1.53.007 latest android 4.0.3
Help please! Need to install Custom ROM!
twingle said:
I get this problem in y htc evo 3d when i open recovery it shows yellow exclamation mark i proceed with pressing volume up+power buttons. Then in bottom of the commands it says Can't open /cache/recovery/command. After i press begin update from external storage it says invalid operation. Success rebooting by reason oem_00. Help me please I tried to install other rom. It is unlocked S-ON non-rooted hboot 1.53.007 latest android 4.0.3
Help please! Need to install Custom ROM!
Click to expand...
Click to collapse
In other words, you haven't installed a custom Recovery yet. Don't worry, at least you haven't bricked it like I did with my Old Epic 4G.
Here's what you have to do.
Download SDK-Tools. http://goo.gl/zmFNr
Move it to your C:\ directory (assuming that's you're on Windows otherwise I can't help), afterwards... unzip there.
Then, download TWRP, (this is from my own personal stash please don't go around distributing it) http://goo.gl/oeA2b
And take the "recovery.img" and put in your now unzipped SDK-Tools folder.
From here on out you're going to be using the command prompt to control your phone. Pray that you have Android Debugging checked on your phone, otherwise this probably won't work.
Go to the Windows flag on the bottom left corner, and type in "cmd" and hit enter.
Command prompt open. Time to get into SDK-Tools. From here on out I'll be using code to explain, it there's an extra space between a line, that means you have to hit enter.
Code:
cd c:\sdk-tools
adb reboot bootloader
fastboot flash recovery recovery.img
And there you have it, you've now flashed your recovery. You now have two options, you can reboot into the System (GUI, ROM, whatever you want to call it.)
Code:
fastboot reboot
(if that doesn't work, try "adb reboot" but I believe the first is correct)
Or you can now go to the recovery...
Code:
fastboot boot recovery recovery.img
That's it! Enjoy!
And when you eventually get the courage to obtain S-Off, check my signature. Make sure to thank Globatron when you're done!
thebeastglasser said:
In other words, you haven't installed a custom Recovery yet. Don't worry, at least you haven't bricked it like I did with my Old Epic 4G.
Here's what you have to do.
Download SDK-Tools. http://goo.gl/zmFNr
Move it to your C:\ directory (assuming that's you're on Windows otherwise I can't help), afterwards... unzip there.
Then, download TWRP, (this is from my own personal stash please don't go around distributing it) http://goo.gl/oeA2b
And take the "recovery.img" and put in your now unzipped SDK-Tools folder.
From here on out you're going to be using the command prompt to control your phone. Pray that you have Android Debugging checked on your phone, otherwise this probably won't work.
Go to the Windows flag on the bottom left corner, and type in "cmd" and hit enter.
Command prompt open. Time to get into SDK-Tools. From here on out I'll be using code to explain, it there's an extra space between a line, that means you have to hit enter.
Code:
cd c:\sdk-tools
adb reboot bootloader
fastboot flash recovery recovery.img
And there you have it, you've now flashed your recovery. You now have two options, you can reboot into the System (GUI, ROM, whatever you want to call it.)
Code:
fastboot reboot
(if that doesn't work, try "adb reboot" but I believe the first is correct)
Or you can now go to the recovery...
Code:
fastboot boot recovery recovery.img
That's it! Enjoy!
And when you eventually get the courage to obtain S-Off, check my signature. Make sure to thank Globatron when you're done!
Click to expand...
Click to collapse
Thank you very much for your tutorial, everything was very clear and I made everything easily. Now there's another, even funnier problem. When I am trying to access Recovery, it just reboots my phone? How can be this?
twingle said:
When I am trying to access Recovery, it just reboots my phone...
Click to expand...
Click to collapse
My only guess would be the recovery I sent you. It's for the Evo V 4G... which is essentially the same phone (same hardware, different software).
Try this one. http://goo.gl/PyVdR
It's TWRP 1.1.1 for the 3D, the official one. Let's see how this works... :fingers-crossed:
EDIT: Or, while you're in fastboot and bootloader is highlighted... http://goo.gl/SEh0o
Press the power button, then hit the volume rockers until Recovery is highlighted. Press the power button and that could work as well.
No, this also doesnt load. I think something can be wrong with cmd. Theres an error.
Code:
C:\Users\aser>cd c:\Android
c:\Android>adb reboot bootloader
error: device not found
c:\Android>adb reboot bootloader
error: device not found
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)...
OKAY [ 1.328s]
writing 'recovery'...
OKAY [ 8.887s]
finished. total time: 10.223s
c:\Android>fastboot boot recovery recovery.img
cannot load 'recovery'
c:\Android>
Everything what I do: I connect my phone, open fastboot(in bootloader) than in pc open cmd type everything what I should, when it is installed I reboot bootloader than open recovery... And BAM! HTC is loading to boot my phone, gets black screen (turns off) after a sec turns on . Also after it I tried doing Bootloader Reboot mannualy, I pressed to reboot the bootloader. The same happened.Thats all
Do you have USB debugging enabled?
For the record, the same thing happens with my device, but I have S-Off. There's nothing wrong with command, I can tell you that. But if you can flash the recovery, clearly something's going right.
What I'd recommend from this point, is rooting your phone and getting something that can put you into recovery. Be it ROM Manager, Goomanager or Quickboot, clearly it doesn't want to manually work.
Before I get into that though... you do have HTC Sync installed... correct?
thebeastglasser said:
Do you have USB debugging enabled?
For the record, the same thing happens with my device, but I have S-Off. There's nothing wrong with command, I can tell you that. But if you can flash the recovery, clearly something's going right.
What I'd recommend from this point, is rooting your phone and getting something that can put you into recovery. Be it ROM Manager, Goomanager or Quickboot, clearly it doesn't want to manually work.
Before I get into that though... you do have HTC Sync installed... correct?
Click to expand...
Click to collapse
Sure, USB debugging is always enabled! Yes i have installed htc sync. You think i need to delete it?
twingle said:
You think i need to delete it?
Click to expand...
Click to collapse
No, you certainly need it for this.
Clearly the conventional tactics are not going to work. I'm afraid you're going to have to go all out. This will be easily achieved if your computer can boot from a Live CD. (and when I say easily, I mean more easily than UnknownForce's method)
Go for this, it's the last piece of help I can get you. It'll also save you a lot of work in the long run.
http://forum.xda-developers.com/showthread.php?t=1563342
There you go. Go for it. :highfive:
KEEP IN MIND THIS ONLY WORKS IF YOU HAVE AN EVO 3D NOT AN EVO V 4G, AND MUST BE CDMA.
thebeastglasser said:
No, you certainly need it for this.
Clearly the conventional tactics are not going to work. I'm afraid you're going to have to go all out. This will be easily achieved if your computer can boot from a Live CD. (and when I say easily, I mean more easily than UnknownForce's method)
Go for this, it's the last piece of help I can get you. It'll also save you a lot of work in the long run.
http://forum.xda-developers.com/showthread.php?t=1563342
There you go. Go for it. :highfive:
KEEP IN MIND THIS ONLY WORKS IF YOU HAVE AN EVO 3D NOT AN EVO V 4G, AND MUST BE CDMA.
Click to expand...
Click to collapse
Thanks for your help. Mine phone is GSM, so this won't go. I realy want to install custom rom, but I am doing that too much (about 8hours of trying) and I didn't do it just only unlocked from htcdev.com
That is awkward, that only you try to help me, theres so many people in xda (45000) online. I unlocked my evo 3d, people say that it is enough to install other rom. I don't want to do the S-OFF because I think it will be the same and we need to find solution now. Its because I won't do the S-OFF, because to make it unlocked was hard, and to make S-OFF is 10x harder! I know that you know more than me, please help me!
To be perfectly honest, I have the CDMA version, so I don't necessarily know anything more than you... nonetheless, I'll do what I can. It seems with the GSM version, you may need to flash the whole .zip versus just the recovery.
Skip to 10:17.
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-htc-evo-3d-gsm/
Also, before I continue, you're on HBOOT 1.5.X... so we're working with a totally different creature right now. I could be wrong, as I've heard the HBOOT 1.4.X. for the GSM can flash just about anything using 4ext (an app) or by flashing the kernel in fastboot. But I don't know how that applies to HBOOT 1.5.X.
If that's true, you may want to get S-Off so you can flash an older bootloader, otherwise I don't know whether or not you can flash custom ROMs.
And for the record, I know what it feels like. I've had a bunch of questions in the past and gotten 1 or no people responding. If you can't get the answer here, keep in mind there are more forums than just this. Something I did not initially know.
For example... androidcentral.com androidforums.com (aka phandroid.com ) and more...
Try posting there too if this doesn't work. That way you'll get the maximum amount of help. Good luck...
By the way, for the record, if you'd like to get S-Off, you can through this... afterwards everything's going to be easier. I know you'd rather not, but nonetheless I'd recommend it. To be honest I thought the same thing before I did it...
http://unlimited.io/jb_shooteru.htm
Either way, good luck in your endeavors.
You know what? It worked! I did it yesterday. I thought it will not work, that I will be with stock rom forever . I followed a bit of that video and the only things that I needed were to unlock bootloader from htcdev.com, download 4ext recovery updater from 4ext.com and downloaded latest final version of 4ext. Than download 4ext recovery.img put in computer and do the work with cmd (fastboot) which was explained before. And install the rom . And also the problem was that I needed to flash custom recovery (4ext). I gave thanks to every post you posted. Thanks a lot to you for your big help :highfive:
Hey, no problem come back any time. Happy flashing.
A friend has a Shift that no longer boots. She took it to Sprint and they told her they couldn't fix it. It is 3 months out of warranty. I can only select fastboot from the bootloader menu. All other options either send the phone in to an endless boot or gives a blank screen. I was able to UNLOCK the phone. I tried to load clockworkmod recovery using adb and fastboot and got an "ok" from the command prompt, but alas it just reboots constantly when choosing recovery from the bootloader.
***** UNLOCKED ******
SPEEDY XF SHIP S-ON
HBOOT-0. 99. 0001
RADIO-1.08.01.0111
eMMC-BOOT
Dec 29,2011.10:29:48
Any luck on fixing this or was the Sprint employee correct?
Have you tried trouble use an ruu on it? It basically reinstalls everything.
Sent from my cm_tenderloin using Tapatalk 2
Since I can only access fastboot, I assumed I needed a a PG06IMG.zip file placed on the SD card, but that didn't work. All the RUU files seemed to be exe files and required the phone to actually boot, correct? Or at least require S=OFF.
RandyMP said:
Since I can only access fastboot, I assumed I needed a a PG06IMG.zip file placed on the SD card, but that didn't work. All the RUU files seemed to be exe files and required the phone to actually boot, correct? Or at least require S=OFF.
Click to expand...
Click to collapse
When you're s-on you can flash everything except kernels (boot.img)
So extract the PG06IMG.zip, and move the boot.img to somewhere else
Now zip up the PG06IMG.zip (using "store" as your compression level)
Now put that on your sdcard and it should flash properly. Now to flash the kernel, put the phone into "fastboot" mode (select the "fastboot" option using the power button)
Now open a command prompt (you need the fastboot.exe and boot.img in the same folder) and change directory to where your fastboot.exe and boot.img are located
Then type this:
Code:
fastboot flash boot boot.img
And all should be good...if you need me to, i can upload the fastboot binary if you dont have it
Unfortunately, the PG06IMG.zip still doesn't work when I press power and vol down. Still says "no image".
RandyMP said:
Unfortunately, the PG06IMG.zip still doesn't work when I press power and vol down. Still says "no image".
Click to expand...
Click to collapse
Backup your sdcard and reformat to FAT32
Thanks for all the help, but that didn't do it either. I've thrown in the white flag!
RandyMP said:
Thanks for all the help, but that didn't do it either. I've thrown in the white flag!
Click to expand...
Click to collapse
Make sure the HTC Drivers are installed. Boot into Fastboot and run the .exe RUU from the desktop.
Unfortunately, when running the exe, it can't find the phone. Running fastboot commands, there is no problem finding the phone. I've returned the phone to my friend so I guess we can close this thread. Thanks for the help, though.
RandyMP said:
Unfortunately, when running the exe, it can't find the phone. Running fastboot commands, there is no problem finding the phone. I've returned the phone to my friend so I guess we can close this thread. Thanks for the help, though.
Click to expand...
Click to collapse
Sorry we couldn't get you sorted
TEAM MiK
MikROMs Since 3/13/11
RandyMP said:
Unfortunately, when running the exe, it can't find the phone. Running fastboot commands, there is no problem finding the phone. I've returned the phone to my friend so I guess we can close this thread. Thanks for the help, though.
Click to expand...
Click to collapse
You can flash ruu zipa through adb if you wanna give it another go
Sent from my EVO using xda app-developers app
A few days ago I tried getting my phone to s-off using the "[how to] manually achieve s-off,simunlock,supercid for Inspire 4g/DHD" guide on the Android forums. (Sorry, I can't post direct links.)
I got to the part where I was supposed to type in "fastboot flash boot boot.img" to the command line but I accidentally skipped that part and typed in "fastboot boot recovery recovery.img". I stopped everything and tried to start over but when I turned my phone back on I was stuck in a boot loop. Going to hboot and trying to choose Recovery or Factory Reset only results in more boot looping.
I've tried putting PD98IMG.zip on the SD card and booting it, but it only reads it and says "Parsing..." before doing nothing. Attempting to enter recovery mode after this makes it enter the boot loop again.
I've also tried using the HTC Sense and RUU from AT&T on my computer to fix the issue. My phone can connect to my PC after choosing fastboot from the hboot menu. The RUU can see the device and it starts recovering it, as my phone shows a black background with HTC on it. But the RUU stops after trying to update the signature saying "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again." I am 99% positive I am using the correct RUU.
I've searched high and low on the internet for a similar situation, but everyone else seems to have their problems solved using either of these steps. Thanks for any help.
Without knowing what you did (since you haven't given us a step-by-step and can't post links), we don't know how to help.
Sorry about that. I'll try to explain what I did the best I can.
Before using the guide, I managed to root my phone and used it for a few days, so everything was fine then. I later decided to s-off it so I could flash a custom ROM to it. Using the guide I mentioned above, I created a mini-adb directory in my C: drive with the ace-tools.zip that I downloaded. Using the command line I copied my stock boot image, though to where I do not know. (I feel like a fool for doing all this without being sure of what I was doing exactly. I deserve what came to me.) Then, using the command line I made my SD card a gold card. After that I changed the "misc version" (?) to allow installation of the downgrade firmware, and then relocked the boot loader and booted back into fastboot. Then I flashed the downgrade software and unlocked it again. It's here that my phone was supposed to be unable to boot, and I was supposed to flash the boot image but skipped that step.
Now I'm unsure of what I have to do, and I only want to get my device working again.
I wish I could post the link to the exact topic, but since I can't I guess you'd have to search the topic name to see exactly what the directions were trying to get me to do.
Thanks again.
Can you boot the phone into fastboot and flash the boot.img from fastboot?
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
SammichMonster said:
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
Click to expand...
Click to collapse
Wait. What? Not PD98IMG.zip from hboot. Extract the boot.img and flash from fastboot, not adb.
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
SammichMonster said:
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
Click to expand...
Click to collapse
No, the boot.img needs to be on your computer. Your phone needs to be in fastboot mode. From the folder where the boot.img is saved,
Code:
fastboot flash boot boot.img
I can't use the command prompt to connect with the device because it can't see it. I always get an "error: device not found" instead.
Is your phone in fastboot mode?
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
SammichMonster said:
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
Click to expand...
Click to collapse
So you're booting into hboot, navigating to fastboot with the volume buttons, and selecting it with the power button? What does fastboot devices say?
I'm assuming by "fastboot devices" you mean what it says in the command prompt.
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
I'm assuming I have to load the boot.img now?
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
SammichMonster said:
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
Click to expand...
Click to collapse
That's what i figured you were doing, so that's why I clarified.
SammichMonster said:
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
Click to expand...
Click to collapse
You're welcome. You could also have fastboot flashed any custom recovery image, flashed a ROM from recovery, and fastboot flashed that ROM's boot.img. So you weren't too badly off.
I am new to htc
i am flashing a custom rom for first time on htc
what do i have to know?
and what is needed?
and i am stuck on soft brick and cant mount internal storage
i am using
hboot 2.15
it shows tampered
and twrp 2.8
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Rapier said:
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Click to expand...
Click to collapse
Do i need to s off
and ive noticed that even after flashing rom system folder is empty except for bin and by the way my device is t mobile
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Rapier said:
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Click to expand...
Click to collapse
unlocked yes i did it but i cant flash the rom it wont be pushed into system at all
please my mind is not clear can you give me a link for kernal pleaseee
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
ive restored from ruu
Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
Why my device wont s-off its always telling me to f***off
eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
What RUU Worked?
eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
În order to properly s-off, you might need a certain ROM to be installed. Have you tried to get s-off having that stock ROM you got after RUU?
Sent from nowhere over the air...
Can s-off be achieved without an installed ROM?
bobby2x420 said:
Can s-off be achieved without an installed ROM?
Click to expand...
Click to collapse
Only by a j-tag device but I don't know how that works. The software methods presented here needs a ROM as far as I know
Sent from nowhere over the air...
bobby2x420 said:
What RUU Worked?
Click to expand...
Click to collapse
Ya it worked (not androidruu though) i had to search a lot i got tired of it