Hi There! How can I get access to all commands in FastBoot? I need command fastboot oem writeimei.
Device info(S-OFF):
HBOOT:1.25.0003
RADIO: 1.15.40.04
Do you have a patched bootloader on a Desire X? ENG instead of SHIP?
Normally fastboot is a DOS-command (phone should be in FASTBOOT mode).
RuudM said:
Do you have a patched bootloader on a Desire X? ENG instead of SHIP?
Normally fastboot is a DOS-command (phone should be in FASTBOOT mode).
Click to expand...
Click to collapse
I enter command(on my screenshot): fastboot oem ?. I use modificated HBoot. How can I patch my bootloader?
Actually it was a question about the patched HBoot, it seems to be an engineering HBoot (Google) which is rarely seen. Most phones (Desire X) are S-On so you can use the fastboot.exe command. The 'engineering HBoot' is different. I don't know how that command is executed. It looks like you don't need the fastboot command itself on that Hboot.
I assume you tried already al sorts of writeimei commands inside the box, with or without bootloader. Sorry, can't help you any further!
Iinformation of somebody else:
eng= engineering. In the bootloader screen,it will say "eng" where it currently says "ship"
Eng bootloaders were initially prepaired for testers of pre-release and developmental devices to make specific changes. they were never really intended to be in the public's hands as i mentioned,i dont think ive ever seen one for the one s. im sure one exists,but no one has leaked it,or accidentally found a device with it,if it does.
once,i completely randomly stumbled upon an eng hboot for the htc merge,while helping a user in puerto rico(his friends device had one)
patched= modified stock
it is simply a stock hboot that is "patched" or modified to provide some(but not all) of the extra fastboot commands,and elimiate the restrictions of the stock version(example,being able to "fastboot flash" ALL partitions)
patched hboots are not signed with an official htc signiture,and therefore,can ONLY be installed on s off phones. sneeking one onto an s on device(or turning a device s on with one present) will result in a potentially unrecoverable hard brick.
an example of a patched hboot is the hboots installed when one runs the "revolutionary" tool on older phones that that particular tool works on.
come to think of it,ive not seen any patched hboots for the one s,either,but then,im not in the xda one s forums daily
OK. What affects the commands of FastBoot? Version of HBoot? How can I get ENG Hboot?
Related
I did the HTC Dev Bootloader Unlock;I installed custom recovery; and I installed a rom via fastboot that had everything....... including the hacked 1.05 hboot now i keep getting boot loop and forsome reason even though the bootloader says ***UNLOCKED***" at the top; it still says S-on.... any help?
Sorry I don't know the answer but maybe you'd get a quicker and better response in the Rooting thread in the Dev section.
Did you downgrade the software if it was @ the most current OTA version?
http://forum.xda-developers.com/showthread.php?t=1401959
Sent from my HTC ThunderBolt using XDA Premium App
yeah from .9 to .5 then unlocked bootloader
smtom said:
Did you downgrade the software if it was @ the most current OTA version?
http://forum.xda-developers.com/showthread.php?t=1401959
Sent from my HTC ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
You install (flash) the super user app?
Sent from my HTC ThunderBolt using XDA Premium App
You downgraded and then you unlocked the bootloader? Had never heard of doing any phone in that order
FWIK and from my personal experience with HTCDEV unlock is that you will never have S-Off, not without an Eng-HBoot. Hacked HBoot's and other exploits can help gain it but "S-On" is in reference to a security feature in relation to the kernel and recovery partition, it was a safety measure to (in theory) keep you from bricking your phone by flashing an unstable kernel on it through recovery mode and possibly being unable to restore your previous nand by effing your recovery up. That is a simplified explanation and not all the reasons but you get the idea. I hope you can get it fixed. Best way to try to fix it is to go back and start from the beginning with just getting an Eng-HBoot or a hacked one that will allow writing to the secure kernel partition through recovery (one that will allow you to copy the NAND part of your device and it's kernel, htcdev unlock only allows nand no matter what the recovery's log says), if you can't do that then try using fastboot in a cmd window to boot a saved recovery image from the fastboot directory on your computer, that may allow you to fix your issues, good luck, hope it helps
if i get the eng hboot how am i going to flash it if its not letting me run pc'img's?
loveableterrorepic4g said:
You downgraded and then you unlocked the bootloader? Had never heard of doing any phone in that order
FWIK and from my personal experience with HTCDEV unlock is that you will never have S-Off, not without an Eng-HBoot. Hacked HBoot's and other exploits can help gain it but "S-On" is in reference to a security feature in relation to the kernel and recovery partition, it was a safety measure to (in theory) keep you from bricking your phone by flashing an unstable kernel on it through recovery mode and possibly being unable to restore your previous nand by effing your recovery up. That is a simplified explanation and not all the reasons but you get the idea. I hope you can get it fixed. Best way to try to fix it is to go back and start from the beginning with just getting an Eng-HBoot or a hacked one that will allow writing to the secure kernel partition through recovery (one that will allow you to copy the NAND part of your device and it's kernel, htcdev unlock only allows nand no matter what the recovery's log says), if you can't do that then try using fastboot in a cmd window to boot a saved recovery image from the fastboot directory on your computer, that may allow you to fix your issues, good luck, hope it helps
Click to expand...
Click to collapse
Have you tried using fastboot as a way to reboot the bootloader? I mean, my big thing is if you can get the pg img for the eng-hboot then you should be able to put it on your SD and then reboot the bootloader to let it try to boot the Pg, I know that I had a panic moment on the original EVO before they figured out a downgrade fix that I nearly bricked it, it wouldn't run the PG img check on first boot of the bootloader until I used fastboot to actually reflash the partitions on the phone (i may hate heimdall when I am working with samsungs but fastboot damn near broke me ha) the best thing to do it get a more intimate knowledge of the process and of fastboot and adb, they are great things to know how to use. Like I said I don't have a Thunderbolt but in dealing with HTC and HTCDEVs unlock tool I am pretty knowledgeable after working with it multiple times, I do know I had to downgrade my EVO (original) by manual partition flashing after I used the HTCDEV unlock tool, it unlocked the bootloader to allow me to boot what I flashed, but the kernel partition was still secure (S-On) this is what the tool, it seems that it was an attempt to cover their ass to ensure that those who don't know what their doing couldn't fully eff things up without more knowledge of the system and could reverse anything that may be unstable.
Hello
I'm trying to revert back to complete stock (stock rom, no root, S-ON) and following this guide/post:
http://forum.xda-developers.com/showthread.php?p=33770807
For that i need to do check the CID and then write back the original CID (Though i can skip this because i didn't use HTC Dev method at all, just original root and revolutionary S-OFF)
Then i need to do "fastboot oem lock" before running the RUU.. but here in lies my problem.
For some reason i can't get fastboot to work.
ADB works fine and i can push and pull files when in android or recovery, but as soon as i enter hboot and try to use fastboot commands, i just get "< Waiting for device >" and have to close the CMD window. (Before you ask, yes it does say "FASTBOOT USB" on the screen)
I have tried both using my standard adb and fastboot files, and i have also tried downloading the latest android SDK and using those files, but neither to any luck.
Anyone have any idea? It might be something simple, as i haven't had to use fastboot before now.
I'm guessing it can't be a driver problem as i can connect fine with ADB and it shows my device when doing "adb devices" (Though it does not show my device when i do "fastboot devices", it just skips the line entirely and prompts me to enter something new).
- Moon
Moonbloom said:
I'm guessing it can't be a driver problem as i can connect fine with ADB and it shows my device when doing "adb devices" (Though it does not show my device when i do "fastboot devices", it just skips the line entirely and prompts me to enter something new).
Click to expand...
Click to collapse
If "fastboot devices" doesn't show the serial number of your phone, none of the other fastboot commands are going to work.
Have you tried disconnecting the phone, rebooting your PC and then connecting the phone again? If that doesn't work, try uninstalling the drivers, rebooting the PC, then reinstalling the drivers.
ramjet73
ramjet73 said:
If "fastboot devices" doesn't show the serial number of your phone, none of the other fastboot commands are going to work.
Have you tried disconnecting the phone, rebooting your PC and then connecting the phone again? If that doesn't work, try uninstalling the drivers, rebooting the PC, then reinstalling the drivers.
ramjet73
Click to expand...
Click to collapse
Tried to reboot the computer, no change.
Decided to try using my laptop before going through the trouble of reinstalling drivers, and it worked
My laptop can see my device fine using "fastboot devices" and i'm able to get my CID (cid: 0202)
Thanks for trying to help me out anyways I might be back with more questions
EDIT: I just google'd a bit and found another command to get the CID "fastboot oem readcid" and it shows HTC_Y13 (which i find more believable tbh).
Is your hboot unlocked?
I am s-off, but couldn't use fastboot commands untill i unlocked my bootloader again..
klect said:
Is your hboot unlocked?
I am s-off, but couldn't use fastboot commands untill i unlocked my bootloader again..
Click to expand...
Click to collapse
There's no need to unlock the bootloader if you are S-OFF.
If you want to run fastboot commands like "flash" or "erase" just install a custom bootloader like ENG, JBear or Revoutionary from the current bootloader. It's better to keep the bootloader locked since that's the stock status and it makes it much easier to return the phone to 100% stock.
AFAIK, the "*** RELOCKED ***" heading you get when locking an unlocked bootloader which flags to HTC/Sprint that you modified the phone can only be undone with the JuopunutBear wire trick.
ramjet73
For me IT was the only way to get fastboot working though...
Sent from my Evo 3D GSM using xda app-developers app
klect said:
For me IT was the only way to get fastboot working though...
Click to expand...
Click to collapse
Did you try one of the JuopunutBear bootloaders (GB or ICS) for the GSM version of the Evo 3D? That should allow the fastboot commands without unlocking.
ramjet73
Yeah, after i s-offed i flashed the ICS jb hboot, but no luck...
So i decided to flash the 1.49.0007 hboot and unlock it the htcdev way.
But if you want to lock it again, you can simply redo the wiretrick right?
klect said:
Yeah, after i s-offed i flashed the ICS jb hboot, but no luck...
So i decided to flash the 1.49.0007 hboot and unlock it the htcdev way.
But if you want to lock it again, you can simply redo the wiretrick right?
Click to expand...
Click to collapse
That's correct.
ramjet73
For all those who were directed here...
This solved my problem when everybody else's advice failed, and it was the easiest.
http://forums.androidcentral.com/ve...how-install-device-drivers-android-1-0-a.html
Hey everyone, I'm having a lot of trouble updating my firmware. Last time I rooted was sometime last year and now when I use the regular system update, it does not complete the update.
I've downloaded the RUU and it does not work as well, I'm stuck on the black background HTC logo.
My HBOOT is 1.50 S-ON. Unlocked.
Any help would be grateful.
You must relock your hboot before flashing RUU. To do this use command:
fastboot oem lock
After that you can use RUU. Good luck!
nyczwillz said:
Hey everyone, I'm having a lot of trouble updating my firmware. Last time I rooted was sometime last year and now when I use the regular system update, it does not complete the update.
I've downloaded the RUU and it does not work as well, I'm stuck on the black background HTC logo.
My HBOOT is 1.50 S-ON. Unlocked.
Any help would be grateful.
Click to expand...
Click to collapse
You have to relock your bootloader before you can flash an RUU since you are S-ON.
Start your bootloader by removing/replacing the battery then hold VolumeDown+Power until the bootloader appears. Press the power button again to select fastboot, then connect it to a PC and the "fastboot" should change to "fastboot usb". Then issue the following commands from the directory with ADB and fastboot:
fastboot devices (make sure this command shows the serial # of your phone)
fastboot oem lock
The start the RUU.exe again from Windows and it should run this time.
ramjet73
Thanks guys. Now I'm guessing the phone is no rooted anymore? How do I root it once again? Its been a while
Follow ramjets quick and easy guide to gaining root. http://forum.xda-developers.com/showthread.php?t=1889438 of course you can always stop at after you unlock your boot loader if you don't feel like gaining s-off with the wire trick. Same method as before though. HTC dev unlock method. However its more beneficial to gain s-off if you want to run ROMs like aosp ICS or jb that require you to downgrade your hboot. Having s-off will make that a snap.
I usually just root it to tether and I rarely use other ROMs. Which method do you think is best? THANKS
Then HTC dev unlock method is the solution sir.
Thanks, I will be trying this when I get off work.
Guys before 8 months i Bricked my HTC EVO 3D GSM
it had HBOOT 1.53.000.7 and it was on The official ICS rom
then i flashed the Caynogen mod 10 and it stucked in the bootloop so i removerd the battrey and boom i got my self in qhsubs_dlload mode
so i talked to SOME GUY who can do J-TAG REPAIR
so he got my phone and he worked on it and he told me it is DEAD
so now (after 8 months) i connected my device i was bored and i was sad about the device
so what i got was i found out that fastboot started to work
only the fastboot commands FROM CMD NOT THE BOOTLOADER
i can,t access anything and i still have the qhsubs_dlload however i have fastboot working using fastboot devices
and no i can,t flash anything using it because it says remote not allowed
and i can,t flash ruu and i basically can,t do anything
and fastboot getvar all shows that my hboot is 1.53.000.7 but the radio is N/A and then i get TOO MANY LINKS
and so on
so what can i do with a device with only fastboot commands and nothing to flash
And yeah i forgot to say it was S-OFF
Well you cant do much with fastboot unless you are using the eng hboot. My first suggestion would be to try and flash it. You are on GSM correct? I would link you but all I have are CDMA files.
Just rename to PG86IMG.zip and place on the root of your sdcard. It should try and flashing it automatically when it goes into your bootloader. If it correctly remove the file from your sdcard and then go into usb-fastboot and you will be able to use fastboot commands.
Good luck and hope you get it going.
jlmancuso said:
Well you cant do much with fastboot unless you are using the eng hboot. My first suggestion would be to try and flash it. You are on GSM correct? I would link you but all I have are CDMA files.
Just rename to PG86IMG.zip and place on the root of your sdcard. It should try and flashing it automatically when it goes into your bootloader. If it correctly remove the file from your sdcard and then go into usb-fastboot and you will be able to use fastboot commands.
Good luck and hope you get it going.
Click to expand...
Click to collapse
That would be awsome if i could get into fastboot or bootloader
My only access here is fastboot commands for 10 seconds only
oo yeah did i mention that before the brick i had s-off
but how come my computer i identify this as an HTC device and with bootloader of 1.53.000.7????
and yeah i tried the fastboot oem writesecureflag 3
to brick it to get into emmc mode but nope same state
Well I don't know if this will help or not but it is worth a shot.
http://forum.xda-developers.com/showthread.php?p=28001007
I was browsing the EVO 4g LTE section and they have a fix for this issue on the LTE. Most of them are helpful and they might be able to help you with this issue. Just hit them up and see what they say.
Hello,
This is an odd request, but I'm in need of some help with this HTC Rezound. A bit of background first. It's not mine. I'm a G2 user (rooted and I know my way around Android hacking). This phone belongs to a friend and despite having it rooted he knows nothing about how he got there or how to fix a problem. Currently it's stuck in a bootloop. He mailed the phone to me (we live 750 miles apart) and he's hoping I might be able to assist. I can get into recovery (I'm assuming it's a custom recovery - looks like ClockworkMod) and my hope was to flash a new ROM but he stupidly neglected to send the phone to me with an SD Card. I'm wondering if there's a way to get a ROM/gapps onto the phone (internal storage) and flash from there. I see there's an option for USB-MS toggle and I've tried playing around in the internal_sd area, and I can get a G: drive to appear when choosing this and connected via USB to my computer, but when I put the ROM/gapps on there I cannot seem to access it for flashing purposes.
Sorry for the long-winded description. But is this a simple solution? Do I just need to get a hold of an SD card and put the files needed on there for flashing? Or is there a way to flash the ROM directly from internal storage?
Thanks in advance for any help you might provide.
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Sorry for my noobness, but I have no idea how to do that with this phone. I know nothing about HTC devices - never owned one before.
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Thanks for the reply. My time messing with the phone is done for the night, but I'll give that a try tomorrow.
Okay sounds good
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Uzephi said:
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Click to expand...
Click to collapse
Yep, pretty much, what I was trying to get him through first was actually pushing a ROM to the phone, also the fastboot getvar all gives almost all info. But true with that, that's probably the MOST important part of rooting and ROMing HTC lol. Although he never stated what rom he has. Trying to get him through some basics of HTC too.
Sent from my Rezound running Sense 5. S-OFF
Yeah, just wanted to put that out there in case he found it how to flash a ROM without us, he will see that post to fix his boot loop (if s-on)
Sent from my Rezound
Thanks again for the replies everyone. Very helpful. As stated before, this is an odd situation because I know nothing about rooting/ROMs for HTC and this isn't my phone.
Anyway, a bit of where I'm at and some better info regarding the phone's situation. The phone, upon attempting to boot, would just bootloop. I don't remember exactly which ROM was on there as I've since done a factory reset, but needless to say it wasn't working. Also, I happened to track down an SD card from an old phone of mine and I used the USB-MS feature in recovery to put a ROM on there for flashing. Wiped everything as I would any other phone, flashed the ROM (which stated was successful) and upon a reboot the phone just hangs on the white HTC screen. Did a bit of digging and decided to try returning to stock (he doesn't care if this phone is still rooted, just wants it working). Found this link http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ and followed the instructions exactly. Update seemed to take just fine, but again a reboot just got me stuck on the white HTC screen.
I've yet to hook this up to try the fastboot getvar thing as the computer I'm using didn't have ADB installed and I didn't have the time to do so. In the meantime any additional suggestions?
I'm attaching a pic of the phone in hboot so you can see some info that might be helpful.
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Rodeojones said:
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Click to expand...
Click to collapse
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Uzephi said:
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Click to expand...
Click to collapse
Again, thank you. Going to give this a go after my son's t-ball game. I feel like more of a noob than when I rooted my OG Droid years ago.
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Rodeojones said:
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Click to expand...
Click to collapse
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
pball52998 said:
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
Click to expand...
Click to collapse
Flashing them in recovery would be great, if there's a link to download the files. But just to be clear, despite this phone finally booking up there's more I need to do to make it 100% usable?
It is 100% usable, but you will experience less overheats and better battery life with the new firmware. I know the hboot ph98img zip is somewhere in this forum for the updated hboot and radio (for that zip you would just put in root of external SD card and in hboot it will automatically flash)
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Hello, I have been preparing to RUU back to 4.03.605.2 and want to be sure of process. I read REV3NT3CH's post on downgrading, so I downloaded the latest 2 PH89IMGs via his instructions and here's where I stand:
S Off
Hboot 2.28
Radio 2.23.10.0123r/1.23.10.0124r
also running CleanRom 4.5
Can I just place PH89IMG on sdcard to RUU or am I missing a step? Thank you in advance
Just place it in the root of SD card and reboot to your boot loader
Sent from my Rezound