Related
ok so i wanted to get a custom rom my desire hd 2.3.5
at start i have tryed the old way thats in the sticky but that was for 2.3.4 so that didnt work.
what did work was unlocking the bootloader via htc dev site. after that i was clueless.
I've found AAK to root my phone and downgrade so i had used that, but i forgot that the phone was unlocked and it said it had to be locked.
and now the phone is bricked i've tried all possible ways with wiping data and cache but it doesnt work.
i wanted to relock the bootloader with fastboot.
i had entered this command:
fastboot oem lock
but that gave this error
FAILED (status malformed (1 bytes))
so my phone hangs on the boot screen and i cant do anything?
can you guys please help me?
The fact you can get to the bootloader is a great sign, so don't worry! The only time you need to properly panic is when you can't get anything on the screen or even a charge light.
---Double check with someone else that this is correct, but I think this is what you need to do ---
Do you have a custom recovery (i.e clockworkmod)? Can you boot into recovery? Use the volume keys to select recovery, then press the power button. If you get options like "reboot now" and "install zip from sd card" then flash a rom like Android Revolution HD.
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Tamen said:
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Click to expand...
Click to collapse
Simply renaming a ROM PD98IMG.zip wont work it needs to be formatted in a certain way, but if the phone is S-OFF, which wasn't mentioned there are certainly PD98IMG's about for a variety of ROMs. But I suspect Tamens suggestion of flashing the appropriate RUU and starting from scratch is going to be quickest way to get sorted
I had this same problem with mine it got stuck trying to boot up but I had no boot loader or I couldn't get into recovery.so download a took called ANDROID FLASHER and reflash the radio ect.my desire hd is now fine.
Sent from my HTC Sensation XL with Beats Audio X315e using XDA App
well i have tried to flash the ruu but without succes.
ive loaded the PD98IMG.zip on the sd and let the bootloader use it. nothing happened.
also my phone is s-on and could not find a way to go to s-off in recovery mode or boatloader.
Down load the tool above Android flasher.from the tool u can enable fast boot ect from your PC and loads of other stuff.it is a very simple to use and it has loads of folders for recovery, boot loader ect let it do every thing for u.that was the only thing that worked for me
Sent from my HTC Sensation XL
I've tried it but it doesn't work because my phone is s-on...
the description of that utility said that s-off is essential
i am really running out of options..
in short my phone has a unlocked bootloader and after that i've used AAK.
the result is bricked phone with s-on and unlocked bootloader
Hello everyone, I know there is a bunch of topics about similar issues but I still can't get out of that trap.
Here we go, I initially wanted to flash my recovery back to stock to be able to install the HTC's OTA (I was using TWRP), I guess it went terribly wrong, because when I launched the update it crashed and now I only can access my bootloader (fastboot available). Everytime I try to access the OS or the recovery it just get stuck with the HTC logo. I tried to flash the boot.img (stock), went back and forth with TWRP and stock recovery (the flashing works, but I still can't boot any of those things, stuck). I am unlocked (still have the HTC .bin in case I have to relock). I am S-ON so I am not supposed to be able to brick it completely. Moreover I can't seem to find a RUU that fits my radio (1.16.2133156). Screenshot of my "allvars" in attachment.
Thanks a lot, I don't really know what to do as I tried everything I found(except RUU, yet).
-- Edit for clarity --
My phone is not bound to any carrier and West Europe
Peace.
Relock your bootloader (fastboot oem lock) and run the 4.16.401.10 RUU and you should be sorted
EddyOS said:
Relock your bootloader and run the 4.16.401.10 RUU and you should be sorted
Click to expand...
Click to collapse
Thanks, you're the man.
Sorry for double posting, I finally downloaded the RU (the same number as previously said) and I get an error (12 signature verify fail). My device is well relocked. As I understand I must be S-OFF for the RUU to work (European phone), which is problematic as I cannot load anything. I am trying to download the RUU again, in case I got a corrupted file...
You do't need to be S-OFF, only if you want to do some other things. You just need to be relocked and it should work fine
Here is what I get, I am re-downloading the RUU from xda's source. With the crap internet I have it takes a while... Thank you for your time.
I renamed a little the file for you to see the version I used (just in case)
When using RUU zip, you need htc_fastboot.exe instead the usual fastboot.exe
Get it here : http://forum.xda-developers.com/showpost.php?p=52280888&postcount=1
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
But when using RUU exe, just relocked and run RUU
Here is what I get, I am re-downloading the RUU from xda's source. With the crap internet I have it takes a while... Thank you for your time.
Click to expand...
Click to collapse
Not the other guy, but I think you're using the file incorrectly. Did you enter the command "fastboot oem rebootRUU" first?
Anyways you can try this method instead:
1-Rename the zip to 06PBIMG.zip
2-Place it on your sd card
3-Go into the bootlaoder and select hboot
It should detect the ruu automatically.
It's working and I am a dummy.
Thanks a lot!
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
AT&T devices are totally compatible with WWE/International firmware, and S-Off allows you to install that.
You are on AT&T, correct? Because 4.28.502.1 is from that carrier. If not, let me/us know and don't follow these instructions.
This is the easiest way, and you don't need a PC to do it.
Download this firmware.
Rename it to 0P6BIMG.zip (that's a zero, not the letter) using a file explorer and place it onto the root of your extSD (not in a folder).
Boot into bootloader by powering off your phone, then turning it on by holding down both the power button and vol down.
Select hboot if it doesn't automatically (vol buttons to navigate~power button to select) and follow the prompts (vol up to flash~power to reboot).
That should be it. Delete the renamed zip from your extSD, otherwise every time you boot to hboot it'll try to update again.
Then go back to bootloader and confirm that it says 4.16.401.10 next to OS.
Congratulations! You are now on Lollipop firmware and can flash the newest ROMs.
suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
You don't need to relock with s-off. Something else is going on. Post your getvar data (be sure to delete IMEI and serial number as these are personal info).
xunholyx said:
AT&T devices are totally compatible with WWE/International firmware, and S-Off allows you to install that.
You are on AT&T, correct? Because 4.28.502.1 is from that carrier. If not, let me/us know and don't follow these instructions.
This is the easiest way, and you don't need a PC to do it.
Download this firmware.
Rename it to 0P6BIMG.zip (that's a zero, not the letter) using a file explorer and place it onto the root of your extSD (not in a folder).
Boot into bootloader by powering off your phone, then turning it on by holding down both the power button and vol down.
Select hboot if it doesn't automatically (vol buttons to navigate~power button to select) and follow the prompts (vol up to flash~power to reboot).
That should be it. Delete the renamed zip from your extSD, otherwise every time you boot to hboot it'll try to update again.
Then go back to bootloader and confirm that it says 4.16.401.10 next to OS.
Congratulations! You are now on Lollipop firmware and can flash the newest ROMs.
Click to expand...
Click to collapse
It did it but now there is red lettering one the screen. How do I get that taken off and please point me to the directions for wiping the old ROM and installing the new. I had it on my screen in the form yesterday and now I can't find it again.
suzyq42 said:
It did it but now there is red lettering one the screen. How do I get that taken off and please point me to the directions for wiping the old ROM and installing the new. I had it on my screen in the form yesterday and now I can't find it again.
Click to expand...
Click to collapse
Here is the bigger issue, for some reason, the phone can't get past the opening screen. The only way I have found to get past this is to power drain the phone. Once done, you can boot into recovery. Then, I can start again. Must be some sort of circuity blocking this.
suzyq42 said:
Here is the bigger issue, for some reason, the phone can't get past the opening screen. The only way I have found to get past this is to power drain the phone. Once done, you can boot into recovery. Then, I can start again. Must be some sort of circuity blocking this.
Click to expand...
Click to collapse
As @redpoint73 said earlier, post your getvar. Hook up to your PC, get into ADB/fastboot and enter the command fastboot getvar all.
I was helping someone else with AT&T last night on the VenomROMs website, and mistakenly thought you were superCID when it was him. That won't be a problem though. It will abort with a CID mismatch.
The reason I suggested WWE firmware is that Marshmallow is coming out soon and WWE will get it way before AT&T updates.
If you want to stay on AT&T firmware, you could run the official RUU from HTC's US website.
Post your getvar, and we can go from there.
suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
OK here should be the final solution, when you are in fastboot/hboot screen you must enter "fastboot oem rebootRUU" then once you see the black screen with HTC logo then you may flash the firmware, you can not flash firmwares on PC while fastboot is actively running, but of course run the firmware flash command TWICE! first flash it will fail because HBOOT gets updated by it self, then on second flash the rest of the firmware files get updated.
If you have S-OFF then you never have to lock your bootloader again.
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.
I have an HTC One M9 that up until yesterday had an unlocked bootloader and had S-Off.
It was running a pretty old ROM so I decided to update it. My first attempt was Viper.
After installing through TWRP recovery it would only take me to the TWRP boot screen after rebooting.
I attempted another ROM, this time Revolution and got the same results.
I’ve been messing with it for hours and somehow I have S-ON and the bootloader is locked. Actually it says RELOCKED.
It has no OS and it will no longer go to Recovery mode. I think the TWRP I tried to install is too new for it.
I’ve performed the HTC bootloader unlock procedure a few times and although it says successful, after reboot, its still relocked.
Am I screwed, or is there something more I can try?
If bootloader is looked, the only solution is to try to flasher the latest ruu according to the model of your M9. It goes into downloading mode??
Dark Stranger said:
If bootloader is looked, the only solution is to try to flasher the latest ruu according to the model of your M9. It goes into downloading mode??
Click to expand...
Click to collapse
Yes, it goes into download mode. I've tried the only Telus ruu I could find (RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe)
and I get a Error 131 Customer ID Error.
I just tried a Sprint ruu (RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe) and I got Error 155 Unknown Error. They both fail right after it displays Updating Signatures.
I'm in Canada and it's a Telus phone but it's carrier unlocked.
Do I need to use a Telus RUU or should any Canadian RUU work on it?
are you sure yours already s-off?
1. re flash lastest TWRP
2. flash required lastest firmware (s-off)
Firmware 3.35.401.12 is required for proper installation! Download (S-OFF ONLY)
3. flash your fav lastest custom rom
Yes, it's definitely S-On.
Any Canadians out there? After some reading I realize I need an RUU of a specific sku. In my case 661.
I need a Telus RUU of 2.11.661.5 or higher for the M9. I'm hoping that will resolve my issue.