[Q] Reflashing to stock / RUU - HTC One X

Hi Folks,
Having some serious issues with my HTC One X
Upon recieving the device I left it on stock for a couple days and then flashed to ARHD 5.2 by unlocking the bootloader via HTCDev and flashed the rom, allwas awesome.. I have now since seen that yellow tea marks are appearing on one side of the screen, so I would like to return the handset to a stock state so that I may return under warranty.
Here is what I did:
Relocked the boot loader
Flashed stock recovery
This resulted in a security error and the phone refused to boot into anything but the boot loader...
almost identical to this thread:
http://forum.xda-developers.com/showthread.php?t=1649737
I have now solved this boot issue by reflashing the latest custom recovery, and the phone now boots into a nandroid backup that I have restored of the stock ROM.
I have tried to use several RUU's and they all halt after the reboot into bootloader phase (where it erases user data, writes the rom and then does something with signatures)...and the handset itself just stays on a black screen with a HTC logo and there are no progress bars or indication of things happening.. until the RUU errors with 155 (unknown error)
After looking at several threads I have become stuck and would really appreciate some advice
Here are the current details of my phone:
Sim free UK handset
HBOOT-0.94.0000
Radio-1.1204.104.14
CID - I have tried to gather this via fastboot, but it comes up as NONE
(also tried getprop ro.cid via the adb shell but this just errors)
Not sure if it makes any difference but I have also tried the HTC One X AIO Kit.. but any commands it sends error with indications that It cannot locate a device
Please please help

Gomezie said:
Hi Folks,
Having some serious issues with my HTC One X
Upon recieving the device I left it on stock for a couple days and then flashed to ARHD 5.2 by unlocking the bootloader via HTCDev and flashed the rom, allwas awesome.. I have now since seen that yellow tea marks are appearing on one side of the screen, so I would like to return the handset to a stock state so that I may return under warranty.
Here is what I did:
Relocked the boot loader
Flashed stock recovery
This resulted in a security error and the phone refused to boot into anything but the boot loader...
almost identical to this thread:
http://forum.xda-developers.com/showthread.php?t=1649737
I have now solved this boot issue by reflashing the latest custom recovery, and the phone now boots into a nandroid backup that I have restored of the stock ROM.
I have tried to use several RUU's and they all halt after the reboot into bootloader phase (where it erases user data, writes the rom and then does something with signatures)...and the handset itself just stays on a black screen with a HTC logo and there are no progress bars or indication of things happening.. until the RUU errors with 155 (unknown error)
After looking at several threads I have become stuck and would really appreciate some advice
Here are the current details of my phone:
Sim free UK handset
HBOOT-0.94.0000
Radio-1.1204.104.14
CID - I have tried to gather this via fastboot, but it comes up as NONE
(also tried getprop ro.cid via the adb shell but this just errors)
Not sure if it makes any difference but I have also tried the HTC One X AIO Kit.. but any commands it sends error with indications that It cannot locate a device
Please please help
Click to expand...
Click to collapse
Please specify which RUU's you have tried

Hey thanks for your prompt reply, It is greatly appreciated.
Here are the RUU's i have tried:
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed
RUU_ENDEAVOR_U_ICS_40_Vodafone_UK_1.26.161.2_Radio_1.1204.90.13_release_251227_signed
Thanks

Where did you get the unit from originally? Was it branded?
This is why you should get the RUU BEFORE flahsing a new ROM

EddyOS said:
Where did you get the unit from originally? Was it branded?
This is why you should get the RUU BEFORE flahsing a new ROM
Click to expand...
Click to collapse
It was purchased from phones4u online.. the phone came unbranded, and is on a vodafone contract.
I am sorry about the RUU.. I wasnt aware it was something you had to acquire first..

You don't HAVE to get it first, it just means you don't have to panic about which one to use!!!
If it's unbranded then 1.29.401.7 or 1.29.401.11 will do the job (I'd go for .11)
Relock the bootloader and run the RUU when in fastboot and you should be good to go!

EddyOS said:
You don't HAVE to get it first, it just means you don't have to panic about which one to use!!!
If it's unbranded then 1.29.401.7 or 1.29.401.11 will do the job (I'd go for .11)
Relock the bootloader and run the RUU when in fastboot and you should be good to go!
Click to expand...
Click to collapse
Thanks mate.. just waiting on the download slots and Ill grab it

Get it here, MUCH quicker
http://www.geeks0.com/downloads/mob...04.105.14_release_260491_signed_c9d22.exe.zip
RUU is in the ZIP file. No idea why it's been changed to lower case but it's the one I used and I maxed out my 8Mbps connection getting it

EddyOS said:
Get it here, MUCH quicker
http://www.geeks0.com/downloads/mob...04.105.14_release_260491_signed_c9d22.exe.zip
RUU is in the ZIP file. No idea why it's been changed to lower case but it's the one I used and I maxed out my 8Mbps connection getting it
Click to expand...
Click to collapse
Spot on mate, I relocked the bootloader and the status reads "*** RELOCKED ***"
The RUU also ran perfectly, thanks for that
Would I just flash a stock recovery to restore the bootloader now? (so that it doesnt say RELOCKED)
I want to ensure that the phone is in the exact shape it needs to be before sending back.
Thanks again

It'll always say relocked - you can't do anything about that...

Ah thats a shame, should be a doorstep swap for a replacement handset anyways so thats probably no issue.
Thanks again mate, you have saved my bacon

-Run your RUU and wait for a complete load.
-go to windows>run and write: %temp%. Find a folder that contains a file called: rom.zip. Get the boot_signed.img and recovery_signed.img.
-flash boot_signed.img and recovery_signed.img.
-fastboot erase cache
-fastboot oem lock
-Do a factory reset with the new recovery.
-Now run your RUU and everything gonna be ok
Sent from my HTC One X using XDA

wolfraim said:
-Run your RUU and wait for a complete load.
-go to windows>run and write: %temp%. Find a folder that contains a file called: rom.zip. Get the boot_signed.img and recovery_signed.img.
-flash boot_signed.img and recovery_signed.img.
-fastboot erase cache
-fastboot oem lock
-Do a factory reset with the new recovery.
-Now run your RUU and everything gonna be ok
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
OP has already got it done, just asked if you could change the bootloader to say 'LOCKED' as it does out the box as opposed to 'RELOCKED'

RUU
So I have kind of a problem, I wanted to unlock my bootloader, only HTCDEV servers are a couples of days now overloaded.
So I can't get the unlock code bin.
I need to use my phone and it won't start normally because new firmare was flashed in RUU mode with JBWFTOOL.
So I want to flash a stock RUU. Only my main version is 3.14.401.41.
My phone was repaired by HTC and I got it back LOCKED and well.
Can I flash a other version RUU or do I have to wait for HTCDEV becoming normal again.
HOX E11 Europe.
H.BOOT 1.39
3.14.401.41
I am not doomed right?

Are you sure.....you don't have 3.14.401.31 as a software number ?
Try this one
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
Put the phone in the bootloader/fastboot usb mode and right click the ruu.exe and select
Run as adminstrator

Mr Hofs said:
Are you sure.....you don't have 3.14.401.31 as a software number ?
Try this one
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
Put the phone in the bootloader/fastboot usb mode and right click the ruu.exe and select
Run as adminstrator
Click to expand...
Click to collapse
Yeah I'm sure, it suprises my also I will try now!
EDIT: Oh no Im not wearing my eyecontacts XD It is 31! XD

jelmer-p said:
Yeah I'm sure, it suprises my also I will try now!
EDIT: Oh no Im not wearing my eyecontacts XD It is 31! XD
Click to expand...
Click to collapse
Yeah i knew that, im on the same cid

Mr Hofs said:
Yeah i knew that, im on the same cid
Click to expand...
Click to collapse
YEAH it worked thanks!

jelmer-p said:
YEAH it worked thanks!
Click to expand...
Click to collapse
Top ! Have fun :thumbup:

Related

I think I've properly broken my desire :(

I downloaded the new 2.3 RUU as I wanted stock unrooted GB on desire.
I had/have oxygen R2 hboot on vodafone UK and I didnt make a goldcard (didnt think I needed one stupidly with an official RUU)
so I tried to run the RUU and now my screen is black with HTC logo and exclamation marks in all four corners.
is this now a bit fat brick or is there anything I can do?
please help..
don't panick. Just flash this RUU
bortak said:
don't panick. Just flash this RUU
Click to expand...
Click to collapse
but will i need a goldcard to run this RUU?
If you are branded, yes.
k3lcior said:
If you are branded, yes.
Click to expand...
Click to collapse
how can I make one when I have zero functionality with my phone? I can only see recovery screen :/
That's a vodafone RUU, it works for my phone, it will work for yours, so AFAIK you don't need a goldcard to use that one.
Turn off your phone (battery pull), hold back + power which will boot you into fastboot mode, then run the RUU from your pc (plug your phone via usb obviously)
k3lcior said:
If you are branded, yes.
Click to expand...
Click to collapse
you'd only need a goldcard if you are unbranding a phone i.e. having a vodafone one and running a WWE RUU.. if you have the right RUU you don't need one.. since the CID et. etc. matches the RUU.
bortak said:
That's a vodafone RUU, it works for my phone, it will work for yours, so AFAIK you don't need a goldcard to use that one.
Turn off your phone (battery pull), hold back + power which will boot you into fastboot mode, then run the RUU from your pc (plug your phone via usb obviously)
Click to expand...
Click to collapse
i cant get into fastboot.
Only a black screen with HTC logo in middle and exclamation marks in 4 corners. Where it usually says "HBOOT" etc it just Says RUU
tried running the one you sent and it just fails with a 152 Image Error
yeah thats what happens, but you should still be able to get fastboot* (*I think), and then flash it..
okay when this happened to my phone, I ran the HTC Europe RUU, which finished installing and restored my hboot (no idea why), then I was able to flash recovery and simply flash a new ROM from there. You can try it. No promises though.
bortak said:
yeah thats what happens, but you should still be able to get fastboot* (*I think), and then flash it..
okay when this happened to my phone, I ran the HTC Europe RUU, which finished installing and restored my hboot (no idea why), then I was able to flash recovery and simply flash a new ROM from there. You can try it. No promises though.
Click to expand...
Click to collapse
i Cant get fastboot as far as I'm aware - I tried getting into it I just get the HTC logo and when I unplug from PC I get recovery looking page (white screen) but it just says RUU and nothing else?!
umm yeah it doesn't say fastboot USB, says RUU.. meaning you need to flash a RUU. Keep trying.. maybe you'll find one that works for me (I did the trial and error method lol)

[Q] Can't flash system.img via fastboot

Hi,
My One X got the OTA update yesterday to go to 1.28
today I was flashing a ROM via recovery but something went wrong and afterwards the phone wouldn't boot up just got stuch at the HTC logo page.
Since then I've been trying to sort it out but with limited success.
I've essentially followed the advice given on this thread;
http://forum.xda-developers.com/showthread.php?t=1599748&page=4
However nothing has worked for me. I've tried flashing the RUU from here:
http://forum.xda-developers.com/showthread.php?t=1543604
But it won't install as I was already on 1.28.
After that I tried taking a boot_signed.img and system.img from the RUU. i was able to flash the boot_signed.img ok but when I try to flash the system.img I get an error as follows:
" FAILED (remote: (00000006))"
Does anyone know what this means? Is it something to do with the size of the system.img?
apart from getting this working there doesn't seem to be anything I can do other than wait for the 1.28 RUU to be released.
If anyone has any ideas I'd be really appreciative as I've got a pretty useless phone right now.
Thanks in advance.
Hi all
I have the same problem, i flashed the 3 dot fix from http://forum.xda-developers.com/showthread.php?t=1582506, not fully paying attention at the time that it was only for custom roms.
I am now stuck at the htc beats screen. Have done all the above and get the same error with system.img.
I have left it a few days without being able to use my phone in the hope that i could find a fix to very little success.
So please if anyone could help in any way would be much appreciated.
Thanks
- you need to have ruu of .28 (i don't think there is yet) and run the EXE file as you can't fastboot flash as of now
- you need to install htc software before you run ruu exe.
as for russel if you did not OTA read this
http://forum.xda-developers.com/showthread.php?t=1599748
same problem, waiting for a 1.28 ruu (chinese one didn't work (of course, but had to try anyway)). going to a Vodafone shop that has a technician on site, see if they can help (maybe they already have a 1.28 ruu).
noromamai said:
same problem, waiting for a 1.28 ruu (chinese one didn't work (of course, but had to try anyway)). going to a Vodafone shop that has a technician on site, see if they can help (maybe they already have a 1.28 ruu).
Click to expand...
Click to collapse
Where did you find the chinese version? We may be able to flash the system.img from that RUU
The moral of the story...always nandroid.
can't remember from which site it was, but there was a thread here about it (maybe in the dev section) with a link to a chinese site. took about 5 hours to download (i'm in europe).
was just in the vodafone shop, spoke to a technician, they don't have ruu 1.28, but he was going to ask around and told me to contact him in a week to see if he managed to get it.
A week? Hopefully someone will have posted it before then, hope so anyway, I need my phone back
If anyone could confirm what the fastboot error "remote:000000006" means I might be able to get around it.
Maybe it is because it is the wrong version.
"remote:000000006" = file too large. There is a way to by-pass it, but can't remember how exactly. There should be another fastboot? a "gray htc one"? Just my 2 cents.
disclaimer: (for all other readers) note that flashing boot.img and system.img is not recommended. use RUU's instead
riemervdzee said:
"remote:000000006" = file too large. There is a way to by-pass it, but can't remember how exactly. There should be another fastboot? a "gray htc one"? Just my 2 cents.
disclaimer: (for all other readers) note that flashing boot.img and system.img is not recommended. use RUU's instead
Click to expand...
Click to collapse
Thanks for this, I'll have a dig around and see if there is another fastboot available.
In work now so will have a play around later.
EDIT: If you remember what the workaround for that issue was please let me know.
jedi5diah said:
-
as for russel if you did not OTA read this
http://forum.xda-developers.com/showthread.php?t=1599748
Click to expand...
Click to collapse
I have try that method, but when it says "install RUU" how? i took the ROM.zip out and tried to flash the recovery.img that went fine and then when it came to the system.img says failed with the error from the 1st post.
I cannot run the RUU.exe as it say device cannot be found. (Have htc sync and drivers.)
Also tried differnt fastboots.
Lastly does the bootloader have to be locked or unlocked?
you have to flash back the original recovery, relock (fastboot oem lock) the phone, boot back into bootloader (power + volume down), make sure you have hts sync installed with the drivers, run ruu exe and follow onscreen instructions.
I think you need to be in fastboot then connect your phone to the pc and then run the exe and it should recognise your phone.
As mentioned above you also need to relock your bootloader before running the RUU.
When i run the RUU.exe and follow on screen instructions says device not found. I have htc sync installed and the drivers.
when i load back into bootload (the step before run RUU) do i enter back into FASTBOOT or stay in HBOOT?
EDIT: now got error battery below 30% so ill recharge and try again later. Thank you all for helping (wether this works or not) really appreciate it. (Sorry to the Op for deviating slightly from post. Didn't realize my issue was slightly differnt from yours.)
when this happen to me i just put the usb wyre en another usb port and restart my computer, this solve the problem
I finally got it to run the RUU, but now get the error 140: BOOTLOADER VERSION ERROR.
Have i downloaded the wrong RUU? as far as i have found there only 2 for Europe?
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_release_251208_signed.exe
Thats the one i have. Im on contract (O2), live in south east england.
Thanks.
You may have the same issue as me. Did you update your firmware via an over the air update this week?
If yes you will have to wait for the 1.28 RUU to be released.
Sadly yes. Just minutes before applying the 3 dot fix. Was late at night wasnt paying attention.. So now its the waiting game. Thanks all.
russelblack said:
Sadly yes. Just minutes before applying the 3 dot fix. Was late at night wasnt paying attention.. So now its the waiting game. Thanks all.
Click to expand...
Click to collapse
Hopefully we won't have to wait too long. The OTA came out on Thursday I think so we should have the RUU in the next few days....
The new RUU should be available for download tonight:
http://forum.xda-developers.com/showpost.php?p=25125579&postcount=381

S-OFF restore stock rom

I have a one x tegra 3 device which i got a couple of days back.it was brand new and it was on 4.1.1(i guess)out of the box..
Everything was fine and there were no problems at first then i did 3 ota updates and now it's on 4.2.2 but non of the sensors are detected by the phone now.hence auto-rotate,etc are not working.
i guess something must have gone wrong with the ota updates since this issue started right after that..
So i guess flashing the complete stock rom from scratch like how i do using odin with samsung phones might solve this..
Can someone pls tell me how to do this..
I read many other threads but it seems very confusing with htc phones since this is my first htc..i have done it countless times with samsung phones..
Moreover my phone shows s-off in the bootloader with cid-11111111.. so it's all the more confusing for me as i don't know much about this security thing implemented by htc..i've seen that being s-off i can easily brick the device..
Also let me know if i can downgrade back to 4.1.1 since everything was working perfect on that..the hboot was 1.39 on 4.1.1 and now it's 1.72 on 4.2.2
I am also including photos of the device..
Pls bear with me and forgive me for being such a noob
Sent from my GT-N7000 using XDA
http://androidruu.com/getdownload.p...Radio_5.1204.162.29_release_302015_signed.exe
Try this ruu
Mr Hofs said:
http://androidruu.com/getdownload.p...Radio_5.1204.162.29_release_302015_signed.exe
Try this ruu
Click to expand...
Click to collapse
can you please tell me how to install this ruu in my one x?
also is there any special precaution that i should take since my device is s-off.
Please don't ask me to refer other threads because i'm getting confused if it's the same procedure since other devices are s-on and there are some confusing things like unlocking the bootloader etc,
Keep the bootloader locked, put the phone in fastboot usb mode and execute the ruu with admin rights on the pc. It should flash the phone back to full stock 4.1.1 with bootloader 1.39.
Mr Hofs said:
Keep the bootloader locked, put the phone in fastboot usb mode and execute the ruu with admin rights on the pc. It should flash the phone back to full stock 4.1.1 with bootloader 1.39.
Click to expand...
Click to collapse
i tried running the ruu multiple times..it's always stuck at waiting for bootloader :crying:
Is the phone in the bootloader before you execute the ruu and do you see in red "FASTBOOT USB" ?
Mr Hofs said:
Is the phone in the bootloader before you execute the ruu and do you see in red "FASTBOOT USB" ?
Click to expand...
Click to collapse
I tried it with phone in the bootloader and it shows FASTBOOT USB but the ruu shows getting device information after the first few steps and then just minimises..a new window does'nt open up and there is no progress etc,
when i run the ruu with the phone turned on..the phone shuts down and shows a black screen with htc written on it and on the computer it shows waiting for bootloader and then nothing else happens..
both the times after a while i removed the usb and and rebooted the phone..
Hmm try a 2.17.401 ruu from the androidruu.com site subsection ENDEVOURU
I reinstalled all the htc drivers on my pc,disabled the antivirus and ran the 3.14 ruu ..
This time it ran without getting stuck anywhere but after showing sending file for a while it gives an image error and says get the correct ruu or something like that..
I tried both in fastboot usb and with the device turned on..
Should i still download the 2.17 ruu and try it or any different version??
i've been doing a lot of reading on xda and i've seen that s-off supercid devices can accept any ruu??so idk why im getting this error
Sent from my GT-N7000 using XDA

[Q] HTC One bricked, need help

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!

Bricked my HTC 10, What to do next?

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.

Categories

Resources