Related
Hey,
So I smashed my screen totally. Cant see anything at all on it, and my insurance through my carrier is coming to pick it up and fix it.
However, I have S-OFF and rooted rom. And I don't think they will fix it. Is there any way I can go back to totally stock, S-ON and carrier RUU without using the screen? I am guessing some way through adb, or from the bootloader, but I dont know how to without having a screen.
Can anyone help?
Thanks
Maybe this can help you:
http://tjworld.net/blog/htc-desire-tear-down
Thanks,
But I am not looking to replace the screen myself, the insurance company are going to do that, I just need to put my phone back to s-on before they take it away
Which method did you use to S-OFF your phone?
Alpha Rev. It is a pvt 04 desire. I have been doing some reading about how to flash a generic HTC unrooted RUU, but all of them seem to involve turning the phone on and using the HTC Sync software.
Is there a way to flash that over adb? If I can do that, am I right in thinking that the htc ruu will have an hboot update in it which will give me s-on?
Thanks
O crap. I have just read my post title. ARG. I am needing S-ON. Stupid me
One step after another. I will do my very best to set your Desire S-ON.
Did you flash any hboot from AlphaRev?
Thanks.
Yeh I flashed an alpha rev hboot. Pretty sure it was just the stock one, it was a long time ago that I did it. But I have just been running LeeDroid with sense 1.0, so cant see why I would have flashed one with any other partition table.
Okay. Sounds well. From which carrier is your phone?
Turn off your phone. Then press and hold first the back and then the power button for nearly five seconds. Then connect phone to computer, open CMD there, change to Android SDK folder and post the output of this command here:
Code:
fastboot devices
Hey, the output is:
Code:
SH0AMPL02350 fastboot
And my phone is vodafone, but I think it might have been a generic HTC one. I never had to make a goldcard or anything, and I dont remember there being any voda stuff on it
Is it necessary to be S-ON though? Surely, it would only matter if the repair was going to be carried out under warranty, which it clearly won't be if you've badgered the screen??
Having said that, I had to send a rooted, S-OFFd custom ROMd Desire back to HTC for repair a few months ago fully expecting to pay. They just put a new motherboard in it and sent back under warranty
mickgeorge said:
Is it necessary to be S-ON though? Surely, it would only matter if the repair was going to be carried out under warranty, which it clearly won't be if you've badgered the screen??
Having said that, I had to send a rooted, S-OFFd custom ROMd Desire back to HTC for repair a few months ago fully expecting to pay. They just put a new motherboard in it and sent back under warranty
Click to expand...
Click to collapse
If I send it back after I have hacked it, then they will say that I have broke it, and no way they will fix it. How I am to prove that I didnt fux it while flashing, and broke it to get a new one.
fewesttwo said:
If I send it back after I have hacked it, then they will say that I have broke it, and no way they will fix it. How I am to prove that I didnt fux it while flashing, and broke it to get a new one.
Click to expand...
Click to collapse
Didn't you say that your screen is broken physically? Software can't crack screens, just like how your mind can't bend spoons.
Yes, but it will be against the T&C's of the insurance policy. Anything that they see that shouldnt be there will stop them fixing it
Okay fastboot sees your phone.
Now do the with fastboot again, but before you should download the alpharev-downgrader from here:
http://alpharev.nl/bravo_downgrade.img
MD5: 6c482ccfa6b7093de4ee1a5804ccbdfc (ALWAYS CHECK BEFORE DOING ANYTHING!!!!)
Commands are:
Code:
fastboot devices
If fastboot "sees" your phone (like in #10), then enter these commands (assuming the downloaded img-file is stored on C:\):
Code:
fastboot flash C:\bravo_downgrade.img
fastboot reboot-bootloader
Also post the output of the commands above here.
EDIT:
I got it working, output:
Code:
C:\Users\name\android-sdk\platform-tools>fas
.img
sending 'hboot' (512 KB)...
OKAY [ 0.092s]
writing 'hboot'...
OKAY [ 0.137s]
finished. total time: 0.230s
C:\Users\name\android-sdk\platform-tools>
and
Code:
C:\Users\name\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.162s]
finished. total time: 0.163s
C:\Users\name\android-sdk\platform-tools>
Okay, now download RUU from here:
http://www.htcdev.com/download
Then boot phone in fastboot mode, connect it computer and run the downloaded RUU.
Do not do anything until you get the message that the RUU was flashed successfully.
Sent from dGB using Transparent XDA App
The link doesnt work, 404??
I grabbed the RUU from the official RUU thread on here, http://forum.xda-developers.com/showthread.php?t=695667, connected the phone in fastboot, and ran it. But I got an error saying that the phone was not connected. It definitely is, and fastboot sees it in the terminal. I assume it is because I do not have the right file, but I am not sure what the right one is, or where to get it from. Should it be another .img rather than an .exe?
My bad! Here is the correct link:
http://www.htcdev.com/devcenter/downloads
O wow, how did I not find that link!? I am not at my laptop just now, but I will get it later. Thanks Very much for your help
Sent from my X10i using XDA App
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
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:
Yep, got it bricked. No, don't think it can be sorted out on my own.. unless someone knows how to revert neccessary partitions to rw, they seem to be all in read-only mode except cache. Have only bootloader/recovery available.
Since I'm guessing that if I send it to the repair, they will change the mainboard, as usual.. my questions are, what's the price/how much did you pay for it, and where are you from?
How did you end up in such situation? A RUU might do the trick. If you do not have an S-OFF HOX then it should be recoverable.
I can try flashing a RUU only if I can somehow do it without a relocked/locked bootloader. I don't have S-off HOX.
Trip had a faulty kernel 004 that came along with the his latest CM10.1 (do NOT worry, faulty kernel is no longer available for download, so you're as safe as you can be with your rooted phones) which caused a couple of ours devices, including his own, to brick. Some of them got into APX mode, some didn't, but the result is pretty much the same - I don't know which exactly but lets say that most if not all partitions are now read only.. so far only cache partition seems to be fine. Fastboot appears to have gone through with locking the bootloader successfuly, but that is not the case. Any attempts to copy over a ROM or any kind of file through mounting the phone as USB doesn't stick upon the next reboot, only those files that were available before are still there, and unable to delete.. and ofcourse, flashing anything isn't possible in read only.
Recovery?
Which recovery are you using?
I was using a version of CWM which had USB mount issues, updated and was able to push files from the laptop to the phone.
May be worth looking at?
BlueSingA said:
I can try flashing a RUU only if I can somehow do it without a relocked/locked bootloader. I don't have S-off HOX.
Trip had a faulty kernel 004 that came along with the his latest CM10.1 (do NOT worry, faulty kernel is no longer available for download, so you're as safe as you can be with your rooted phones) which caused a couple of ours devices, including his own, to brick. Some of them got into APX mode, some didn't, but the result is pretty much the same - I don't know which exactly but lets say that most if not all partitions are now read only.. so far only cache partition seems to be fine. Fastboot appears to have gone through with locking the bootloader successfuly, but that is not the case. Any attempts to copy over a ROM or any kind of file through mounting the phone as USB doesn't stick upon the next reboot, only those files that were available before are still there, and unable to delete.. and ofcourse, flashing anything isn't possible in read only.
Click to expand...
Click to collapse
Oh yeah, I saw that some ppl got bricked by his kernels/roms. You had really bad luck mate...
Trip said he bricked his bootloader on purpose to get his handset fixed for free, and guess what, he got a new mainboard free of charge. Ask him how he'd do it.
Sent from my One X
I gave a shot at bricking the bootloader intentionally but no success, I guess any kind of changes you try to apply to a read only simply doesn't stick, as intended.. can't even remount as read/write.. so back to the original question: 1.) What did you pay for your mainboard replaced? 2.) Where are you from?
The saddest thing is that HTCs centre in Serbia is in Belgrade, and I'm in a distant place, so I actually had to give my phone to the carrier first, and they will send it to HTC.. so any attempt at trying to manouver them by saying that I have been running the ROM/Kernel without any issues with an unlocked bootloader fails, as all they need to do is enter the hboot and the warranty becomes void.
for me with apx mode ... i sent my device to htc and after 2 days ( today ) they called me to pick my phone with new mainboard and all is free
so u are in the same problem so u should try steps we used to get into apx mode and then send it to htc to replace ur mainboard for free if u still in warranty
i think u read all comments in trip kernel thread so it's easy to get into apx mode with read only devices
Did you try reflashing your bootloader ? that deletes a lot of custom stuff in the process
if it works then you might be able to format /data and /system from your custom recovery
OH, and btw if you brick your bootloader(or APX), HTC can simply unbrick it and find all your nasty work(but it seems they didn't notice it yet)
here are instructions if interested
find your current boot.img(it gets deleted in the process)
find your current custom_recovery.img(it gets deleted in the process)
re-lock bootloader: Fastboot oem lock,
reboot to ruu: fastboot oem rebootRUU
flash firmware.zip fastboot flash zip Link/to/firmware.zip
then unlock like first time you did it, Fastboot flash unlocktoken Link/to/unlock_code.bin
restore boot.img: fastboot flash boot boot.img
restore recovery: fastboot flash recovery custom_recover.img
Vcek said:
Did you try reflashing your bootloader ? that deletes a lot of custom stuff in the process
if it works then you might be able to format /data and /system from your custom recovery
OH, and btw if you brick your bootloader(or APX), HTC can simply unbrick it and find all your nasty work(but it seems they didn't notice it yet)
here are instructions if interested
find your current boot.img(it gets deleted in the process)
find your current custom_recovery.img(it gets deleted in the process)
re-lock bootloader: Fastboot oem lock,
reboot to ruu: fastboot oem rebootRUU
flash firmware.zip fastboot flash zip Link/to/firmware.zip
then unlock like first time you did it, Fastboot flash unlocktoken Link/to/unlock_code.bin
restore boot.img: fastboot flash boot boot.img
restore recovery: fastboot flash recovery custom_recover.img
Click to expand...
Click to collapse
i don't think so .. as if they were able to unbrick it, they will do for sure and won't change mainboard for free
i don't think that they like to do repairs for free
Vcek said:
Did you try reflashing your bootloader ? that deletes a lot of custom stuff in the process
if it works then you might be able to format /data and /system from your custom recovery
OH, and btw if you brick your bootloader(or APX), HTC can simply unbrick it and find all your nasty work(but it seems they didn't notice it yet)
here are instructions if interested
find your current boot.img(it gets deleted in the process)
find your current custom_recovery.img(it gets deleted in the process)
re-lock bootloader: Fastboot oem lock,
reboot to ruu: fastboot oem rebootRUU
flash firmware.zip fastboot flash zip Link/to/firmware.zip
then unlock like first time you did it, Fastboot flash unlocktoken Link/to/unlock_code.bin
restore boot.img: fastboot flash boot boot.img
restore recovery: fastboot flash recovery custom_recover.img
Click to expand...
Click to collapse
I cannot reflash anything, I guess because even the partition where the bootloader is becomes read only. Fastboot oem lock doesn't relock or lock the device for me, and fastboot oem rebootRUU just does a normal reboot. There's literally no changes that I can apply. I guess it would be impossible for me to brick the bootloader as well because of this problem. HTC can get into APX mode easily, yes, but they cannot unbrick the bootloader.
It can be easily solved by flashing a new rom and recovery using android download tool (ADT)
my phone has bricked a hundredes of times an I only soved it using this method
HIT THANKS IF I HELPED
I don't think he can flash stuff with nearly all partitions r/o.
Sent from my One X
Please read. Partitions are read-only in my case. Unless ADT can flash partitions and repartition as intended for HOX, I would have use of it.
Dont go such deep just download any ADT flashable rom and flash it using ADT not ADB
HIT THANKS IF HELPED
Androyash said:
Dont go such deep just download any ADT flashable rom and flash it using ADT not ADB
HIT THANKS IF HELPED
Click to expand...
Click to collapse
lol. I'm fairly certain the only thing that stands any chance of helping us is signed HTC Diag files + Javacard or a route to S-off using APX mode.
Anyway, where to next: I can get a replacement HOX motherboard of unknown quantity from eBay for £150...If I do that, do I keep it, or flog it and get something else...? Or do I just sell the good LCD from my HOX to somebody who's broken theirs? (Can't flog the whole phone for parts, it's got all my data on it)
I don't really want an HTC any more after this experience.
Okay, I think I need to revise my plan of trying to have my HOX fixed without getting charged. :laugh:
Can they prove a non-stock kernel is faulty for rendering all partitions read-only if I'm not in the APX, or they're not really going to go into such details and look at the kernel's code and find where the problem is within it?
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.