Okay, links first: PB31IMG.zip and PDM_4.08.605.15_release.zip
I was tooling around the intarwebs wondering if a 4.08.605.15 RUU had ever made itself available, and stumbled across this VZW Community thread. All the way at the last message I noticed a user linking to an RUU on dev-host.org.
So I'm thinking to myself, "Self, that's really unusual, especially for a message reportedly sent to the poster from HTC."
So I follow the link. It's going to what appears to be the 4.08.605.2 RUU. Slightly disappointing, but I decide to click on the username to see what else they might have publicly posted. There's a number of interesting files available, but inside the ROMs folder I notice a recently uploaded PB32IMG.zip of an appropriate size for our phones.
So I download it.
Inside most of the files are timestamped May 29, 2012, and the android-info.txt file contains the following:
Code:
modelid: PB3120000
cidnum: VZW__001
mainver: 4.08.605.15
hbootpreupdate:3
:good:
The included hboot appears to be 1.07.0000 (!!!). There's also a ramdisk.img and the radio.img matches the 2.15.10.12.20 radio I had (as opposed to 2.15.10.07.07 that came with 4.08.605.2). boot.img, recovery.img, and system.img are all different as well, but I don't have anything immediately handy at work to mount the images and diff their contents with.
Now, this might be a fake, but it's a lot of work to go through to build.
I kinda need my incredible since it's my phone and I'm not down with guinea-pigging my real device on stuff like this, but I thought some devs or more intrepid users might want to check it out and see if it's legit.
Should that link go down, I kept a copy.
Edit: Added second link to PDM_408.605.15_release.zip. This zip file contains both the PB31IMG.zip (SHA-1 identical to the first link) and the RUU Utility (amongst other things) digitally signed by HTC. I'm pretty sure this is legit. Got a copy of this too...
It does appear to be legit. But im not sure how to tell for sure other than finding someone who is s-on, and seeing if it flashes.
Im gonna flash it and see what happens, but im s-off.
Let me know what you find. Would there be a way back to s-off if one unlocks their bootloader?
ardax said:
Let me know what you find. Would there be a way back to s-off if one unlocks their bootloader?
Click to expand...
Click to collapse
It does flash 4.08.605.15, so I'm gonna say its the real deal. Great find.
What do you mean way back to s-off? As in can you get s-off by unlocking the bootloader, or if you unlock the bootloader will you lose s-off.
Sorry, that was rather obtuse. I was just thinking that if one was s-on and flashed the RUU, would they be able to regain s-off? I haven't had to research rooting an Inc in a looong time, though I suppose with an unlockable bootloader it wouldn't be as much of an issue. (Oh look, you have a thread about how to do it! How about that.)
I wonder what else is posted on that account that nobody else has seen before?
ardax said:
Sorry, that was rather obtuse. I was just thinking that if one was s-on and flashed the RUU, would they be able to regain s-off? I haven't had to research rooting an Inc in a looong time, though I suppose with an unlockable bootloader it wouldn't be as much of an issue. (Oh look, you have a thread about how to do it! How about that.)
I wonder what else is posted on that account that nobody else has seen before?
Click to expand...
Click to collapse
I looked at all the files, and this ruu seems to be the only file for the incredible.
Not just for the Incredible, but for other phones too. There's a lot of what appear to be RUU zip files for devices that have been recently uploaded. The Evo 4G, Evo 3D, Amaze, and Sensation at a glance.
Help
ardax and cmlusco,
Do you guys happened to keep a copy of the RUU for this version
(4.08.605.15)? - the RUU file in the 2nd link is no longer valid.
Here's my situation and hope it will help someone in this community:
I was new to this. I got an old Droid Incredible from someone. The device
was installed with various program and was reported 'space low'. I add
a 16GB SD and installed Maps.Me lite. Not long after that the thing crashed.
I was trapped in the boot loop.
I was able to unlock the bootloader. But I was not able to get to s-off, since
it seems that it requires the device to be able to boot up or enter into the
debug mode, which I did not do when the device was OK.
I played around and the flash of clockworkmod is of no effect. The flash
of system, boot, and recovery all failed to bring the the device out of the
boot loop. I tried some SD PB31IMG.zip and all failed. The only thing I
have been able to do is RUU with the 4.08.605.2, which downgraded from
4.08.605.19. Earlier version give me the HBoot version error.
Since the 4.08.605.2 is a small file about 8MB. It may not change the
system much to bring the device out of the boot loop and since the
only thing I have been successful is with RUU. If you guys still have
the RUU around, I think it may do the trick for me - I have been
look abound on the web but haven't find a copy of it.
Thanks.
Duncan
The RUU is still available at http://dinc.does-it.net/Stock_Images/4.08.605.15/
I think that's cmlusco's site.
ardax,
Thanks for quick reply.
Sorry for a newbie's question:
I thought RUU is a .exe file that can execute under the Windows?
For a zip file, all I know how to handle it is put in a FAT32 SD card
and boot the Incredible into HBoot - which I have tried for some
PB31IMG.zip file and haven't have any luck - I do not know the
reason why it is failed.
Is doing this way with zip file the same as RUU?
Thanks.
UPDATE: I just tried the zip file by putting it on a FAT32 SD card and
boot into fastboot. Still reporting No Imange or Wrong Image.
-- Not working. Still trapped in the Boot Loop.
Try flashing from fastboot then. I don't remember if this will work with an unlocked bootloader though.
The basic gist of it is this:
* Reboot into bootloader
* run "fastboot.exe oem rebootRUU"
* Once you're in RUU mode, "fastboot.exe flash zip PB31IMG.zip" (The zip file needs to be on your PC.)
* You'll most likely get an error pretty quickly telling you to try again (right after the hboot pre-update), so rerun the previous command
* With all good luck, watch the flash go for a few minutes
* When it's done run "fastboot.exe reboot"
You should be back to stock. Now you can re-unlock the bootloader if needed and/or try to gain S-OFF.
If you're not comfortable with this procedure, I'd recommend looking for more explicit step-by-step instructions.
Does anyone still have the links for this? Or can the re-up them?
ardax said:
Try flashing from fastboot then. I don't remember if this will work with an unlocked bootloader though.
The basic gist of it is this:
* Reboot into bootloader
* run "fastboot.exe oem rebootRUU"
* Once you're in RUU mode, "fastboot.exe flash zip PB31IMG.zip" (The zip file needs to be on your PC.)
* You'll most likely get an error pretty quickly telling you to try again (right after the hboot pre-update), so rerun the previous command
* With all good luck, watch the flash go for a few minutes
* When it's done run "fastboot.exe reboot"
You should be back to stock. Now you can re-unlock the bootloader if needed and/or try to gain S-OFF.
If you're not comfortable with this procedure, I'd recommend looking for more explicit step-by-step instructions.
Click to expand...
Click to collapse
Sorry, I don't have the files anymore, since my Droid Incredible is long since dead.
Related
Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks
pipefitter said:
Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks
Click to expand...
Click to collapse
Make sure PC36IMG.ZIP IS ALL CAPS look at my guide all the links needed to unroot
pipefitter said:
Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks
Click to expand...
Click to collapse
Make sure the PC36IMG.zip file doesn't have an additional suffix (exC36IMG.ZIP.zip) which is usually the case when the directions include renaming the original file to PC36IMG.zip. As for flashing it from within recovery, not unless it was designed to be flashed from recovery.
reaper24 said:
Make sure PC36IMG.ZIP IS ALL CAPS look at my guide all the links needed to unroot
Click to expand...
Click to collapse
Just to avoid any confusion for the OP, a quick correction. It's got to be PC36IMG.zip. We don't want the .zip in capitals. Only the PC36IMG is capitals. .zip remains lower case.
To the OP, as has been mentioned, be sure it's spelled correctly. Also, be sure it's on the main directory of your SD card, and not in any folders. If you're sure of both of those things, then double check that the file isn't corrupted. Can you open the zip file on your pc without getting an error?
As a rule of thumb, you don't ever want to flash PC36IMG.zip from recovery. If it won't flash from hboot, then there's something not right with the file (all of the above suggestions are good), but it's pretty much going to be a bad idea to flash that zip from recovery.
BAD PC36IMG.zip
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks
pipefitter said:
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks
Click to expand...
Click to collapse
Why are you unzipping the file? If I'm not mistaken, you rename PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip to PC36IMG.zip and flash from the bootloader.
k2buckley said:
Just to avoid any confusion for the OP, a quick correction. It's got to be PC36IMG.zip. We don't want the .zip in capitals. Only the PC36IMG is capitals. .zip remains lower case.
To the OP, as has been mentioned, be sure it's spelled correctly. Also, be sure it's on the main directory of your SD card, and not in any folders. If you're sure of both of those things, then double check that the file isn't corrupted. Can you open the zip file on your pc without getting an error?
Click to expand...
Click to collapse
dougjamal said:
Why are you unzipping the file? If I'm not mistaken, you rename PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip to PC36IMG.zip and flash from the bootloader.
Click to expand...
Click to collapse
Just trying to verify that it is a good download even though the md5 matches. Nobody seems to understand that I know what I'm doing. This is what is happening when i HBOOT:
SUPERSONIC EVT3 SHIP S-ON
MICROCHIO-041f
TOUCH PANEL-ATMELC03_16ac
HBOOT 2.10.0001
RADIO 2.15.00.11.11.19
HBOOT reads as follows
SD Checking...
Loading...[PC36DIAG.zip]
No Image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36IMG.nbh]
No image or wrong image!
So, I decided to try running RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe from my PC. It starts out fine and says it is rebooting to BOOTLOADER, then it reboots to the HTC screen and goes no farther. The RUU says waiting for BOOTLOADER for abut 45 seconds and then says a connection cannot be established.
pipefitter said:
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks
Click to expand...
Click to collapse
http://db.tt/gqTAPS1
Here's a link from my dropbox to the 3.70 software PC36IMG.
And by the way, I don't think that anyone assumed you didn't know what you are doing. There is truly know way of knowing someone's level of knowledge on any given subject, when we're all strangers on the internet. It's sometimes better to be sure that all bases have been covered, and that something simple wasn't overlooked. troubleshooting 101: start with the simplest stuff first. No matter what it is that you're troubleshooting. Anyways, hopefully the file from my dropbox will work for you.
have you tried running the RUU from fastboot mode? I see you had a connection error when you tried before. Boot into fastboot, from the bootloader. Or if you have adb setup type "adb reboot bootloader" and that should boot you to fastboot. Then connect your USB and try running the RUU again. It has a better chance of being recognized that way. Good luck.
pipefitter said:
Just trying to verify that it is a good download even though the md5 matches. Nobody seems to understand that I know what I'm doing....
Click to expand...
Click to collapse
Please don't be offended, my friend. Like my good friend, k2buckley stated, we have no idea of the level of knowledge that a person we are trying to help has and personally, every time I assume that a person knows a certain routine or technique, I quickly find that I am mistaken. In addition, I find that people will only post a small portion of what they have actually done and that makes it a tad difficult at times for those of us trying to help. teh roxxorz, k2buckley, HipKat, myself and many others spend a great deal of time in these forums trying to help when we can so please be patient with us.....
SOLVED!
k2buckley said:
http://db.tt/gqTAPS1
Here's a link from my dropbox to the 3.70 software PC36IMG.
And by the way, I don't think that anyone assumed you didn't know what you are doing. There is truly know way of knowing someone's level of knowledge on any given subject, when we're all strangers on the internet. It's sometimes better to be sure that all bases have been covered, and that something simple wasn't overlooked. troubleshooting 101: start with the simplest stuff first. No matter what it is that you're troubleshooting. Anyways, hopefully the file from my dropbox will work for you.
have you tried running the RUU from fastboot mode? I see you had a connection error when you tried before. Boot into fastboot, from the bootloader. Or if you have adb setup type "adb reboot bootloader" and that should boot you to fastboot. Then connect your USB and try running the RUU again. It has a better chance of being recognized that way. Good luck.
Click to expand...
Click to collapse
dougjamal said:
Please don't be offended, my friend. Like my good friend, k2buckley stated, we have no idea of the level of knowledge that a person we are trying to help has and personally, every time I assume that a person knows a certain routine or technique, I quickly find that I am mistaken. In addition, I find that people will only post a small portion of what they have actually done and that makes it a tad difficult at times for those of us trying to help. teh roxxorz, k2buckley, HipKat, myself and many others spend a great deal of time in these forums trying to help when we can so please be patient with us.....
Click to expand...
Click to collapse
Sorry guys, I was getting frustrated. I'm not used to failure. I'm no computer genius, but I pride myself in being able to follow and understand directions. I am officially unrooted!
This is what I did...
1)Uninstalled and reinstalled HTC drivers
2) Flashed a stock, rooted, odexed ROM. I was running Azrael 4.0. Don't know if this made any difference, but I tried the next steps before flashing the stock ROM and had no success.
3) Booted into FASTBOOT
4)Attached USB cable to computer and the phone immediately showed FASTBOOT USB
5) Ran RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe (this RUU matched my HBOOT and Radio)
6)Followed on-screen directions for RUU and 10 minutes later my phone was unrooted, completely stock.
Your success may vary. I had many people respond with the same mantra of "Do A, B, & C and your phone will be unrooted". By now, we should all know that each phone is different and sometimes they just won't cooperate. Don't get frustrated. Just keep at it and eventually you will solve your dilemma. I truly appreciate all the help from everyone on XDA!
Regards,
Mark
pipefitter said:
Sorry guys, I was getting frustrated. I'm not used to failure. I'm no computer genius, but I pride myself in being able to follow and understand directions. I am officially unrooted!
This is what I did...
1)Uninstalled and reinstalled HTC drivers
2) Flashed a stock, rooted, odexed ROM. I was running Azrael 4.0. Don't know if this made any difference, but I tried the next steps before flashing the stock ROM and had no success.
3) Booted into FASTBOOT
4)Attached USB cable to computer and the phone immediately showed FASTBOOT USB
5) Ran RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe (this RUU matched my HBOOT and Radio)
6)Followed on-screen directions for RUU and 10 minutes later my phone was unrooted, completely stock.
Your success may vary. I had many people respond with the same mantra of "Do A, B, & C and your phone will be unrooted". By now, we should all know that each phone is different and sometimes they just won't cooperate. Don't get frustrated. Just keep at it and eventually you will solve your dilemma. I truly appreciate all the help from everyone on XDA!
Regards,
Mark
Click to expand...
Click to collapse
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.
k2buckley said:
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.
Click to expand...
Click to collapse
+1...........Take care....
posting & replying via the XDA Premium app.
S-ON
k2buckley said:
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.
Click to expand...
Click to collapse
Yes, I flashed s-on with no problems. That's why I was getting so frustrated with the rest of the procedure.
Thanks everyone.
Okay, I'm literally at my wit's end. I have spent, and I kid you not, 3 hours trying to fix a friend's HTC Desire, UK T-Mobile.
I'm wanting to get it back to straight factory stock. No more ROMs, no partitioning this or that, nothing. He just wants his phone to be normal again.
I have tried different RUUs, tried command prompt, searched until my head was wanting to explode, I'm still having difficulties. There may be countless threads regarding this, some may say that I haven't searched right, but honestly, as of right now, I'm completely knackered and tearing my hair out after doing so much searching, reading the FAQ, reading other threads and Google search results. Now, all I want is just a simple answer or two, because having 15 tabs open in Firefox is making me dizzy.
Before heading to bed, this is the only info I have now:
HBOOT 6.93
Radio 5.11.05.27
We've gotten Error 110's before when trying RUUs, and he doesn't want to try anymore RUUs, since trying to find the right one was testing his patience (especially having a phone that would not get past that HTC splash screen with the four triangles). We've gotten other issues as well, and it's just been one problem after another, with no accomplishments in sight as of this writing.
Having the radio info, would this RUU be the correct one to use?
http://www.filefactory.com/file/b4a...9.00.32U_5.11.05.27_release_159811_signed.exe
Please tell me it is. I can't test on the phone because he has it with him, we were doing all of this via Skype.
Now, also, do I have to downgrade the HBOOT (from Alpharev) before I use that RUU to get the phone back to stock? I really hope not, because doing any sort of HBOOT change with the Alpharev stuff honestly gives me fits, it never goes right and ends up me being bald.
If I DO have to use the downgrader HBOOT off of Alpharev's site, would all I have to do is just rename it to "PB99IMG.img"? Yes, I'm sure this has been asked and answered countless times but I'm blitzed out. I just need a simple, straight-forward, dumbed down answer. And, I need it before my friend destroys his phone (literally).
I can give you a direct link to a Flashable Stock froyo 2.2 rom if you like.. Is it CDMA or GSM?
You have to flash downgrade... Reboot to fastboot flash stock then run RUU
If the phone is branded by cidnum you need to use goldcard to flash WWE RUU.
To flash hboot use fastboot and download proper IMG files from alpharev... Check md5 and flash...
PB99IMG.zip method is good way too
Sent from my HTC Desire using XDA Premium App
Belswick - GSM, the UK doesn't use CDMA.
kotag - I can't tell if it's branded by cidnum or not.
Is all I have to do is get the downgrader img file and rename it to PB99IMG.zip and flash it as such in FASTBOOT menu? I remember trying to do the whole reflash thing before and it never worked properly. Everyone else seems to always never have problems but when I try, something always fails.
to get cid:
fastboot oem gencheckpt
there will be a reboot to recovery but on the screen look for cid number
You can't mix 2 methods together... if you download img file flash it via fastboot, if zip use pb99img.zip method... check md5 all the time
Finally got it to work but with other methods not listed here.
That fastboot command prints phone info where you can find cidnum which will tell you if branded
Sent from my HTC Desire using XDA Premium App
So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
TH3_M0Nk said:
So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
Click to expand...
Click to collapse
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
glevitan said:
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
Click to expand...
Click to collapse
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
TH3_M0Nk said:
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
Click to expand...
Click to collapse
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
glevitan said:
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
Click to expand...
Click to collapse
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
TH3_M0Nk said:
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
Click to expand...
Click to collapse
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
glevitan said:
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
Click to expand...
Click to collapse
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
TH3_M0Nk said:
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
Click to expand...
Click to collapse
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
glevitan said:
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
Click to expand...
Click to collapse
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
TH3_M0Nk said:
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
Click to expand...
Click to collapse
Ok, just let me know when you are online and be arrange it.
glevitan said:
Ok, just let me know when you are online and be arrange it.
Click to expand...
Click to collapse
Yes I am online now. Let me know how to proceed.
TH3_M0Nk said:
Yes I am online now. Let me know how to proceed.
Click to expand...
Click to collapse
download the teamviewer: http://www.teamviewer.com
Get the ID and PASS and send them over a Private Message, NOT HERE
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Have you tried doing a factory reset using the stock recovery?
See if you can get a system.img to flash manually. If you can get an OS boot you should be able to fix your device.
tkoreaper said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
Using the adb shell command (recovery --wipe_data)? Yeah I've tried that, but I get a device not found error. adb isn't working right now, however I am still able to get fastboot commands, and the phone recognizing them at least. Otherwise, no I haven't what would I need to do?
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
5m4r7ph0n36uru said:
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
tw1tch175 said:
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
Click to expand...
Click to collapse
Yes. I just figured that out while searching haha. I did go through and use the UI, but I had no luck. I am looking for an img like you said but I am not having luck so far. Is there one of the Stock guide on my original post?
Ok so for ALL HTC the only proper way to s-on is to use fastboot/download and for oem writesecureflag 3, you should NEVER EVER EVER us echo/dd /hexeditor to go s-on.
For 2016+ phones, you should use sunshine or another tool to go from unlock/relocked to lock, do NOT use anything not designed for the phone in question, or attempt to do it manually. I can only vouch for SunShine's capability to safely change the bootloader status, I can't vouch for any other method or tool. I know SunShine does it right.
See http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264 for my PSA on the subject.
If the phone won't flash with a proper RUU, well you need to find someone with a EMMC write tool to rewrite all your firmware, this is probably going to run $100-200.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
bob3rt said:
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
Click to expand...
Click to collapse
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ah gotcha. That makes sense. Wouldn't have been the only thing that slipped my mind. I lost access to my Steam authenticator too. I was able to get the zip from the exe file like you said, after I put that on an SD card and boot to download mode do I just fastboot flash zip?
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
tkoreaper said:
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
Click to expand...
Click to collapse
That is in regards to wiping data, earlier versions of sunshien wiped data on all htc 10 going s-off, thats not the issue here. Issue here is he improperly set the phone lock/s-on. Gotta use sunshine to set it locked, and fastboot to set s-on.
Hey Everyone just wanted to give an update since yesterday evening.
Just wanted to give out some props to @5m4r7ph0n36uru . Following his advice of extracting the Rom.zip from RUU .exe I was able to run it in download mode and loaded up an OS on the phone. So Now I am unbricked! Yay. I had to find out how to do that using process monitor and everything, but it was a success. and I can breathe easy. Thankfully doing that was easier that doing the Database call handler stuff from today at work XD
Thankfully my lesson is learned and I'll flash correctly to full stock next time. Thank you all for your help in the matter.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
Hello,
Just to inform that if I try to run RUU.exe from PC when the phone is in bootloader menu, I get battery low error. However, if I "boot to download mode" in the bootloader menu, I can run the RUU.exe from the computer without any error.
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
drago10029 said:
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
Click to expand...
Click to collapse
Are you on MM firmware or N?
Also S-OFF is the way to go.
andybones said:
Are you on MM firmware or N?
Also S-OFF is the way to go.
Click to expand...
Click to collapse
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
If you wish to s-off first, please follow >> THIS GUIDE << by @jcase & return when your device is back up and running.
First boot will take approximately 15 minutes due to Art optimization
Click to expand...
Click to collapse
UPDATE: things have gotten worse.... I was attempting to relock the bootloader since RUU was failing with error 155, someone in a diff HTC thread said locked bootloader was needed for RUU. now phone flashes HTC logo then powers off. buttons pressed not going to recovery right now anyone wanna chime in? please...
@defcomg you know anything about HTC phones? I am currently stuck in the sunken place lol
drago10029 said:
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=1680928
andybones said:
https://forum.xda-developers.com/showthread.php?t=1680928
Click to expand...
Click to collapse
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
drago10029 said:
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
Click to expand...
Click to collapse
Keep in mind the date on that post is from a few years back (2012). You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
From my small amount of time, I think you may be confused about what the difference is between an unlocked bootloader and S-OFF, which I'd need to even go back and read that article, but thought it touched a little on it
The 10 has changed quite a bit too from past phones. Before you'd need to be S-OFF and unlocked bootloader. Now S-OFF unlocked and S-OFF locked are basically the same, but that can be found in threads if you'd like to find more info on that.
Most the info is there, you just need to search. If you need help finding articles, I can try and help with that. I've been surprised with the great info I've found after awhile of coming up empty.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
It seemed you were in a simple bootloop, but I'm not 100%. I think your issue was flashing MM ROM on N firmware. Can't do that.
Also, Verizon doesn't allow us to unlock bootloader on Htc-dev. So if we want to root, we must S-OFF.
andybones said:
Keep in mind the date on that post is from a few years back. You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
Click to expand...
Click to collapse
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
andybones said:
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
Click to expand...
Click to collapse
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
drago10029 said:
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
Click to expand...
Click to collapse
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
andybones said:
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
Click to expand...
Click to collapse
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
drago10029 said:
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
Click to expand...
Click to collapse
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
andybones said:
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
Click to expand...
Click to collapse
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
drago10029 said:
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
Click to expand...
Click to collapse
Fastboot isn't recognized? As in it's not working?
drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
andybones said:
Fastboot isn't recognized? As in it's not working?
Click to expand...
Click to collapse
xunholyx said:
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
Click to expand...
Click to collapse
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
drago10029 said:
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
Click to expand...
Click to collapse
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
xunholyx said:
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
Click to expand...
Click to collapse
oooh i see lol.. too many numbers.