Develop Bugs

HELP PLEASE! (brick)

Hi, I have been the happy owner of an international HTC One X for just over a month now. I'm from Australia and my carrier is Vodafone.I have been using the Lee-Droid One Xtreme Rom without issue for almost the entire time I've owned the phone, however two days ago some huge issues appeared.
First the handset resest itself, this had happened before but this time it was stuck on the "HTC Quietly Brilliant" splash screen. I tried to wipe the cache from recovery but recovery wouldn't boot. I plugged the phone into my laptop and used "fastboot erase cache" which seemed to work but did not solve my problem, still hanging at the splash screen.
I then noticed that my bootloader had somehow locked itself again so I flashed my Unlock_code.bin again, the handset displayed the usual prompts which I followed but when my phone reset I was greeted with the now familiar hanging bootsplash plus a warning about the ROM being for internal HTC use only.
I also noticed this message in my terminal:
FAILED (status read failed (Cannot send after transport endpoint shutdown))
Can someone please help me here? I'm hesitant to send the phone away because I unocked the bootloader via htcdev.com so my warranty is invalid most likely.
Thanks for your time and sorry if this is a duplicate thread, I had done a few searches already and found nothing that spunded like my problem though.

Did your bootloader say locked or relocked
Sent from my HTC One X using Tapatalk 2

Did u flash de cwm last recovery? There are some problems with usb, try to use another One, install drivers, restart pc.
Htc One X Venom ViperX Rom & Show-p Kernel

@KrisPerry - the bootloader says either :
***LOCKED***
or
***LOCKED***
***SECURITY WARNING***
@drangonesdenano
last recovery I flashed CWM 5.8.4.0
have tried restarting pc, no change.
i use linux so there are no drivers to reinstall.
none of the cables i have fit, but this is the original htc cable, it seems to be in decent condition, i'll try and see if i can borrow one from a friend though.
sorry for taking a while to reply to you guys, i've been having login troubles with the xda site. thankyou for your help thusfar. any ideas?

Try closing and opening bootloader again, then flash recovery if not working properly. Has to do with usb ... I think ..not to cable. Then tell us
Htc One X Venom ViperX Rom & faux123 b004b7 Kernel

dragonesdenano said:
Try closing and opening bootloader again, then flash recovery if not working properly. Has to do with usb ... I think ..not to cable. Then tell us
Htc One X Venom ViperX Rom & faux123 b004b7 Kernel
Click to expand...
Click to collapse
hi, sorry for taking so long to reply, i have been having some major troubles with both my computer and then getting enough charge into the phone. i ended up writing this script:
Code:
#!/bin/sh
while true
do
./fastboot getvar battery-voltage
./fastboot reboot-bootloader
sleep 10
done
writing from a different pc with a fresh linux mint install i've tried unlocking the bootloader again but this time i'm getting this from the terminal:
Code:
./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (No such device))
finished. total time: 9.179s
what do you think? i bought a second usb cable and have been switching between the two but it makes no difference... i can't flash recovery because the bootloader is locked and i seem to be stuck in a bootloop so i can't boot into CWM either.
i've been reading about people flashing RUU's, is that what i need to do?

Just a gentle bump on this thread, I've been without a phone for over a week now and it's getting pretty annoying (first world problems). Has anyone seen this before? What should I do? Any help would be greatly appreciated.
Cheers, Toby.

RUUs
So I'm looking into the possibility of flashing an RUU, what are my options for doing so under Linux?
I've found this link: http://forum.xda-developers.com/showthread.php?t=1465747
Has anyone used openRUU? Does it work for the HOX?
The only other option I can see is making a Windows virtual machine... My only concern is installing the drivers, will that work seeing as I can only access fastboot?
Also I'm not sure exactly where to find an RUU... I've checked out this link: http://www.filefactory.com/f/7cc7b2fbdd03c031/
but my RUU (1.29.862.11) wasn't there and I've struggled to find a download elsewhere....
any clues?
Any help would be devoured thankfully.
Toby.

Free bump...
Sent from my HTC One X using xda premium

TobyJamesJoy said:
So I'm looking into the possibility of flashing an RUU, what are my options for doing so under Linux?
I've found this link: http://forum.xda-developers.com/showthread.php?t=1465747
Has anyone used openRUU? Does it work for the HOX?
The only other option I can see is making a Windows virtual machine... My only concern is installing the drivers, will that work seeing as I can only access fastboot?
Also I'm not sure exactly where to find an RUU... I've checked out this link: http://www.filefactory.com/f/7cc7b2fbdd03c031/
but my RUU (1.29.862.11) wasn't there and I've struggled to find a download elsewhere....
any clues?
Any help would be devoured thankfully.
Toby.
Click to expand...
Click to collapse
The RUU doesn't do anything fancy, it just packages the boot.img, recovery? and ROM, and uses the same method we would use to flash the bits individually.
If there is no RUU for your version, I hope you took the advise of making a backup.

Update
whynot66 said:
Free bump...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks man!
So I've set out on a mission and made a Virtualbox Windows XP install, installed the sdk and HTC sync, configured the usb settings, and the virtual install seems to be able to detect my handset in fastboot.
Good times.
I was able to run all the fastboot commands I wanted, including "fastboot oem get_identifier_token" which wasn't previously working on the Linux side and now through some kind of voodoo works a charm under Linux too. After running this command I visited the htcdev site and requested a new Unlock_code.bin but that didn't work, still getting FAILED errors...
One thing I have noticed is that every time I run "fastboot oem get_identifier_token" I get a dramatically different token, wil this result in a different Unlock_code.bin? Maybe one of the will work eventually (doubtful).
On the other hand it seems that I've got everything ready to flash an RUU, I just need that RUU... So does anyone know where I can find it?

BenPope said:
The RUU doesn't do anything fancy, it just packages the boot.img, recovery? and ROM, and uses the same method we would use to flash the bits individually.
If there is no RUU for your version, I hope you took the advise of making a backup.
Click to expand...
Click to collapse
I've read this thread:
http://forum.xda-developers.com/wiki/HTC_One_X
and flashing the RUU seems to be the only way to go seeing as my bootloader is locked and won't unlock. Becuase you flash RUUs with a locked bootloader right?
I've read about vodafone releasing this RUU so I'm pretty sure it exists, I'm just not sure how to get it.
I did make a nandroid backup of the stock rom, is it possible to flash that?
I don't care how much data I lose, so long as I get a functional telephone in return.

TobyJamesJoy said:
I've read this thread:
http://forum.xda-developers.com/wiki/HTC_One_X
and flashing the RUU seems to be the only way to go seeing as my bootloader is locked and won't unlock. Becuase you flash RUUs with a locked bootloader right?
I've read about vodafone releasing this RUU so I'm pretty sure it exists, I'm just not sure how to get it.
I did make a nandroid backup of the stock rom, is it possible to flash that?
I don't care how much data I lose, so long as I get a functional telephone in return.
Click to expand...
Click to collapse
Hmmm, so you were unlocked but.now it won't unlock? Odd.
With a stock recovery, you should still be able to flash signed ROMs, perhaps not your backup though.
If it's not on filefactory, it's probably not widely available. Google is your friend, I guess.

BenPope said:
Hmmm, so you were unlocked but.now it won't unlock? Odd.
With a stock recovery, you should still be able to flash signed ROMs, perhaps not your backup though.
If it's not on filefactory, it's probably not widely available. Google is your friend, I guess.
Click to expand...
Click to collapse
yeah, weird huh?
forgive my ignorance but what exactly is a signed rom?
i'm not sure what recovery i've got at the moment, last one i flashed was CWM 5.8.4.0 but that won't boot anymore.. do i need recovery to flash my backup?
in my backup i have a boot.img, recovery.img the md5 sum and a few tarballs (cache, data, system), if i flash recovery.img will i get the stock recovery? or do i need an unlocked bootloader to do that?
and if i get stock recovery what can i flash from there with a locked bootloader?
you were saying that an RUU does the same things as flashing the components individually, but also you say that i might not to be flash my backup, so i'm a bit confused.... n00bdom......

TobyJamesJoy said:
yeah, weird huh?
forgive my ignorance but what exactly is a signed rom?
i'm not sure what recovery i've got at the moment, last one i flashed was CWM 5.8.4.0 but that won't boot anymore.. do i need recovery to flash my backup?
in my backup i have a boot.img, recovery.img the md5 sum and a few tarballs (cache, data, system), if i flash recovery.img will i get the stock recovery? or do i need an unlocked bootloader to do that?
and if i get stock recovery what can i flash from there with a locked bootloader?
you were saying that an RUU does the same things as flashing the components individually, but also you say that i might not to be flash my backup, so i'm a bit confused.... n00bdom......
Click to expand...
Click to collapse
A signed ROM is an official one from HTC, signed by their private key. The CID also has to match your phone. Then the standard recovery will allow it to be flashed.
I find it strange that you are locked.with a nonstandard recovery. I think you should get back to unlocked before proceeding.
Try unlocking your phone from scratch using the normal procedure.
Why doesn't that work? What stage fails? What error do you get?

BenPope said:
A signed ROM is an official one from HTC, signed by their private key. The CID also has to match your phone. Then the standard recovery will allow it to be flashed.
I find it strange that you are locked.with a nonstandard recovery. I think you should get back to unlocked before proceeding.
Try unlocking your phone from scratch using the normal procedure.
Why doesn't that work? What stage fails? What error do you get?
Click to expand...
Click to collapse
I've tried this numerous times, everything works right up to the final stage. My device is recognised by fastboot, I can get the identifier token, flash the Unlock_code.bin, it writes to the handset properly, the handset displays the black screen with "yes" and "no" options and the warnings about voiding your warranty, i choose "yes" and the phone reboots into fastboot while the terminal reads like so:
Code:
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (No such device))
that's under Linux, in my Windows XP virtual box it reads the same except the final line is:
Code:
FAILED (status read failed (Unkown error))
I've tried this on two different PCs, one running arch linux, another on ubuntu 12.04, also on a fresh install of Linux Mint 13. I've tried every different usb port available and I've tried generating different Unlock_code.bin files - nothing seems to work.......
Brickland.

Idea
This may have something to do with my udev rules, these are the ones i'm currently using, I can't remember now where i found them but they govern how the OS handles certain devices. Here's my /etc/udev/rules.d/51-android.rules
Code:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="tobias"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c01",SYMLINK+="android_fastboot"
does anyone with some linux knowhow see anything wrong with them?
or am i barking up the wrong tree?

TobyJamesJoy said:
This may have something to do with my udev rules, these are the ones i'm currently using, I can't remember now where i found them but they govern how the OS handles certain devices. Here's my /etc/udev/rules.d/51-android.rules
Code:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="tobias"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c01",SYMLINK+="android_fastboot"
does anyone with some linux knowhow see anything wrong with them?
or am i barking up the wrong tree?
Click to expand...
Click to collapse
I think you only need this (and a fraction of it at that) if adb devices shows nothing.

TobyJamesJoy said:
I've tried this numerous times
Snip
Brickland.
Click to expand...
Click to collapse
I have no idea, I've never unlocked mine.
Sorry dude, but I'm sure it can be recovered, you just to find the right incantation.

BenPope said:
I think you only need this (and a fraction of it at that) if adb devices shows nothing.
Click to expand...
Click to collapse
hmm, i'm not sure i follow you but you have hit on one glaring omission of mine, i've never been able to get adb working.... maybe i should forage around for tips in that area.
are you saying that i only need the proper udev rules to get adb working and i should be able to do it with a fraction of the code? what do you mean by "if adb devices shows nothing"?

[Q] My HOX 9mo/old(unmodded) went bonkers after 4.2 update.

Right, as this is my first post i come here with major problem with my HOX (european version), after i updated my phone to the latest android 4.2.2 things suddenly went downhill - The phone is in pristine condition and nothing has been tampered with after i purchased it 9 months ago, but now it doesnt want to work when required, sometimes when i try to unlock it (something around 7-10times) the screen is stil black and i cannot do anything on it, the softkeys light up as normal but stil nothing happens, that forces me to reboot it completely (ive tried factory reseting a few times but that doesnt change anything) and sometimes the screen when im using it goes total tivoli on me, ive yet to send it in for service as it takes a whole century for the techies to even look at the phone and i need the phone for my daily work. Im not a avid programmer that wants to screw around with my phone so i got sent here by a friend to ask for help. Currently the problem seems to be the update that renders my phone useless.
If anyone can give me either pointers on how to do a complete wipe of the phone so i can either reinstall the software it came with or a fix for the 4.2 madness that has occured i would give you my kidney and babies.
Sincerly, pissed of guy that wants his phone to work.

Well hello there ""pissed of guy that wants his phone to work
SO here is the deal,
You'll most likely need to reinstall the ROM, and there are a couple of options...
First of all, make sure you have the international version, code-named endavorU and not the evita...
To do that you'll need to go into the bootloader. Power off the device, wait a couple of seconds, then hold the volume - and power button and don't let go until you are in the bootloader.
Now read the first line...
If you are endeavorU, than continue reading...
You can start by unlocking your bootlaoder with the official method (htcdev.com)
Once that is done download this all-in-one kit... For the HTC ONE X
Now you'll need to flash a custom recovery...
Go to the clockworkmod website and download their CWM Touch 5.4.8.0 recovery, and flash it using the kit.
Now boot into recovery (first into booloader, and then choose recovery) and do a factory reset and data wipe... also do a dalvik cache wipe in the advanced section and reboot... if it now works fine than good, if not, continue reading...
Now go into bootloader, and select fastboot...
go into the data folder of your aio kit and while holding shift right click on the empty space, and choose open with command prompt...
then type in
fastboot oem readcid
IF you have a WWE cid go here and download the odexed rom, recovery, and boot.img
http://forum.xda-developers.com/showthread.php?t=1546970
and flash them...
flash the odexed.zip with recovery,
and the two .img files using fastboot commands...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
you'll need to place both boot and recovery img into the data folder of the kit for it to work

desmond1303 said:
Well hello there ""pissed of guy that wants his phone to work
SO here is the deal,
You'll most likely need to reinstall the ROM, and there are a couple of options...
First of all, make sure you have the international version, code-named endavorU and not the evita...
To do that you'll need to go into the bootloader. Power off the device, wait a couple of seconds, then hold the volume - and power button and don't let go until you are in the bootloader.
Now read the first line...
If you are endeavorU, than continue reading...
You can start by unlocking your bootlaoder with the official method (htcdev.com)
Once that is done download this all-in-one kit... For the HTC ONE X
Now you'll need to flash a custom recovery...
Go to the clockworkmod website and download their CWM Touch 5.4.8.0 recovery, and flash it using the kit.
Now boot into recovery (first into booloader, and then choose recovery) and do a factory reset and data wipe... also do a dalvik cache wipe in the advanced section and reboot... if it now works fine than good, if not, continue reading...
Now go into bootloader, and select fastboot...
go into the data folder of your aio kit and while holding shift right click on the empty space, and choose open with command prompt...
then type in
fastboot oem readcid
IF you have a WWE cid go here and download the odexed rom, recovery, and boot.img
http://forum.xda-developers.com/showthread.php?t=1546970
and flash them...
flash the odexed.zip with recovery,
and the two .img files using fastboot commands...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
you'll need to place both boot and recovery img into the data folder of the kit for it to work
Click to expand...
Click to collapse
Actually even getting into bootloader is a process that makes me more furious, since the graphics are bugging their ass of whatever i do. The version is endavorU so thats settled. However my only fear is that i potentially brick my phone or lose the warranty by unlocking since the thirdpart here is really nazi on that stuff from previous experiences.

charliebc said:
Actually even getting into bootloader is a process that makes me more furious, since the graphics are bugging their ass of whatever i do. The version is endavorU so thats settled. However my only fear is that i potentially brick my phone or lose the warranty by unlocking since the thirdpart here is really nazi on that stuff from previous experiences.
Click to expand...
Click to collapse
On stock, there is not much beyond the factory reset that can be done from the user end.
Return it for repair! That's what the warranty is for, let HTC deal with it.
And DO NOT unlock the bootloader and flash anything because it does void the warranty and HTC are under no obligation to fix it.

Yes, sending it in is your best bet
Sent from my HTC One X using xda app-developers app

Thats what my conclusion was after doing some extensive googling, i dont want to tamper with stuff that might void my warranty. Thanks anyway.

charliebc said:
Thats what my conclusion was after doing some extensive googling, i dont want to tamper with stuff that might void my warranty. Thanks anyway.
Click to expand...
Click to collapse
Update: As the shops here in my town actually dont take phones from the place i bought it in for service, im gonna do it myself and take the risk of a potential bricked phone. Currently i have no other option than DIY fixing.

charliebc said:
Update: As the shops here in my town actually dont take phones from the place i bought it in for service, im gonna do it myself and take the risk of a potential bricked phone. Currently i have no other option than DIY fixing.
Click to expand...
Click to collapse
Relax, since we are S-ON it's not that easy to brick and HTC ONE X... everything you do can be fixed.

desmond1303 said:
Relax, since we are S-ON it's not that easy to brick and HTC ONE X... everything you do can be fixed.
Click to expand...
Click to collapse
You make it sound good, i will see what i have time for later on and do an attempt to try the method you posted. Thanks alot for providing the info.

charliebc said:
You make it sound good, i will see what i have time for later on and do an attempt to try the method you posted. Thanks alot for providing the info.
Click to expand...
Click to collapse
Just one more thing...
I said that you should install a certain version of CWMT, but it doesn't matter, just make sure its the latest one.
Also I see there is no link to the All-in-one kit I mentioned so here it is: http://www.hasoon2000.info/getdownload.php?file=One X (International)/One_X_All-In-One_Kit_v2.5.rar

[Q] Help to restore my waranty

Hi everyone,
I recently bought a htc one M8 to a french company which import them from Poland.
I unlocked the bootloader of my phone with HTCDEV, I flash twrp, and I rooted the phone.
Today, I have a problem with the duo camera, when i run the camera, a pop up comes to say that the duo camera is covered and I need to pull my finger somewhere else but i have this from a week and nothing is in front of the camera.
So the reseller said that I need to make work the waranty of the phone to solve the problem.
Of course, i can't use the waranty because my Hboot is unlocked.
I read this Thread :
http://forum.xda-developers.com/showthread.php?t=2708571
To relock the bootloader. I read that I t would work for me.(I'm s-on for the moment but I think I will be able to find a tuto to s-off )
I just fine this thread to remove tampered flag :
http://forum.xda-developers.com/showthread.php?t=2708565
I didn't read all commentarys but it seems to works.
But i'm wondering what else should I do to restore waranty, I read that flash the ruu will be ok but I think my phone don't have the international rom because there isn't super eco battery mode and when I ask on an other forum someone answer me that was because I got a Polish phone.
Could somewone guide me? Is my request possible? In what order apply tutos? Where download polish RUU?
Sorry if the english is bad..
Thx,
Allan

Allan9914 said:
Hi everyone,
I recently bought a htc one M8 to a french company which import them from Poland.
I unlocked the bootloader of my phone with HTCDEV, I flash twrp, and I rooted the phone.
Today, I have a problem with the duo camera, when i run the camera, a pop up comes to say that the duo camera is covered and I need to pull my finger somewhere else but i have this from a week and nothing is in front of the camera.
So the reseller said that I need to make work the waranty of the phone to solve the problem.
Of course, i can't use the waranty because my Hboot is unlocked.
I read this Thread :
http://forum.xda-developers.com/showthread.php?t=2708571
To relock the bootloader. I read that I t would work for me.(I'm s-on for the moment but I think I will be able to find a tuto to s-off )
I just fine this thread to remove tampered flag :
http://forum.xda-developers.com/showthread.php?t=2708565
I didn't read all commentarys but it seems to works.
But i'm wondering what else should I do to restore waranty, I read that flash the ruu will be ok but I think my phone don't have the international rom because there isn't super eco battery mode and when I ask on an other forum someone answer me that was because I got a Polish phone.
Could somewone guide me? Is my request possible? In what order apply tutos? Where download polish RUU?
Sorry if the english is bad..
Thx,
Allan
Click to expand...
Click to collapse
[GUIDE] Return your M8 to 100% Stock Follow the instructions in that thread, it'll be the same for most devices just use the correct software applicable to your phone. You need to be S-OFF to achieve the removal of tampered banner and other goodies.
So first thing you'll need to do is get S-OFF, you could either try the old Firewater S-OFF method found here: Firewater S-OFF Instructions it worked on most devices but the newest patches released by HTC blocked it. If it doesn't work for you you can try [Android][HTC S-OFF] SunShine for modern HTC devices . It should make you S-OFF fore sure however it costs $25 through an in app payment method. It's "per" device, so if you pay $25 to S-OFF and they give you a new phone you'll have to pay another $25 to S-OFF the new one... Worth considering though if firewater doesn't work...
After you get S-OFF just follow the general instructions in the Guide provided above and you should be set to go :good:
What is your software version number, I don't see it on the pic? Are you still on stock ROM, if so check in settings >>> about >>> software information.
I'm not familiar with the various different main-versions that comes from Poland. If we can get the version you're on it'll make things a bit easier. Having said that here is the thread with a lot of nandroid backups that you can look into as well COLLECTION of Stock backup's

BerndM14 said:
[GUIDE] Return your M8 to 100% Stock Follow the instructions in that thread, it'll be the same for most devices just use the correct software applicable to your phone. You need to be S-OFF to achieve the removal of tampered banner and other goodies.
So first thing you'll need to do is get S-OFF, you could either try the old Firewater S-OFF method found here: Firewater S-OFF Instructions it worked on most devices but the newest patches released by HTC blocked it. If it doesn't work for you you can try [Android][HTC S-OFF] SunShine for modern HTC devices . It should make you S-OFF fore sure however it costs $25 through an in app payment method. It's "per" device, so if you pay $25 to S-OFF and they give you a new phone you'll have to pay another $25 to S-OFF the new one... Worth considering though if firewater doesn't work...
After you get S-OFF just follow the general instructions in the Guide provided above and you should be set to go :good:
What is your software version number, I don't see it on the pic? Are you still on stock ROM, if so check in settings >>> about >>> software information.
I'm not familiar with the various different main-versions that comes from Poland. If we can get the version you're on it'll make things a bit easier. Having said that here is the thread with a lot of nandroid backups that you can look into as well COLLECTION of Stock backup's
Click to expand...
Click to collapse
Hi ! Thanks you for taking time for me !
I'll try to follow yours instructions, don't know if I'll have time this week-end !
I'm still on the stock Rom, I only unlock bootloader, install recovery and root !
My software nimber is :1.57.118.2 is that the information you expected ?
Thanks again !

Allan9914 said:
Hi ! Thanks you for taking time for me !
I'll try to follow yours instructions, don't know if I'll have time this week-end !
I'm still on the stock Rom, I only unlock bootloader, install recovery and root !
My software nimber is :1.57.118.2 is that the information you expected ?
Thanks again !
Click to expand...
Click to collapse
Yeah that's for T-Mobile Poland...
Well if you're still on Stock ROM then you only need S-OFF to remove the tampered banner, show bootloader as locked and you'll also need a stock recovery, which might be a bit more difficult to get. I've seen a few people on here asking for it and not sure if they found it yet or not I also don't think there's an RUU available for it...
There is a TWRP Stock Nandroid in this guy's post, don't know if it includes the stock recovery though.
CID T-MOB009 - 1.57.118.2 TWRP ( hboot 3.16)
Direct link: Mega Uploads link for 1.57.118.2 TWRP

Well,
My phone is S-off, I don't really thing about consequences because it cost me 25$ and I start looking for T-Mobile Poland stock recovery AFTER.
And it's hard to find... Lots of result for the m7.This post appeared often ans by curiosity, I type " m8 T-Mobile Poland", this post appeared in fisr page... I will continue but if someone have it, i would be great to tell me where I can get it !
Edit : Do you think T-Mobile from other country could work? Germany? Thxs!
Edit 2 : I found this Thread on polish forum : http://forum.android.com.pl/f1288/kolekcja-backup-ruu-ota-416860/
On the first post, in the signature, we can read : Backup : CID T-MOB009 - 1.57.118.2 TWRP (HBOOT 3.16)
I'm not sure to understand everything with google trad but do you think it's a full backup with the recovery and i can use it ?

Well,
My phone is S-off, I don't really thing about consequences because it cost me 25$ and I start looking for T-Mobile Poland stock recovery AFTER.
And it's hard to find... Lots of result for the m7.This post appeared often ans by curiosity, I type " m8 T-Mobile Poland", this post appeared in fisr page... I will continue but if someone have it, i would be great to tell me where I can get it !
Edit : Do you think T-Mobile from other country could work? Germany? Thxs!
Edit 2 : I found this Thread on polish forum : http://forum.android.com.pl/f1288/ko...uu-ota-416860/
On the first post, in the signature, we can read : Backup : CID T-MOB009 - 1.57.118.2 TWRP (HBOOT 3.16)
I'm not sure to understand everything with google trad but do you think it's a full backup with the recovery and i can use it ?
Click to expand...
Click to collapse
Up ?

Allan9914 said:
Well,
My phone is S-off, I don't really thing about consequences because it cost me 25$ and I start looking for T-Mobile Poland stock recovery AFTER.
And it's hard to find... Lots of result for the m7.This post appeared often ans by curiosity, I type " m8 T-Mobile Poland", this post appeared in fisr page... I will continue but if someone have it, i would be great to tell me where I can get it !
Edit : Do you think T-Mobile from other country could work? Germany? Thxs!
Edit 2 : I found this Thread on polish forum : http://forum.android.com.pl/f1288/kolekcja-backup-ruu-ota-416860/
On the first post, in the signature, we can read : Backup : CID T-MOB009 - 1.57.118.2 TWRP (HBOOT 3.16)
I'm not sure to understand everything with google trad but do you think it's a full backup with the recovery and i can use it ?
Click to expand...
Click to collapse
That's the exact same link I shared with you already. I think it is the full backup(Not sure about Recovery though) as I tried to download it on my phone and it's a big file. You can just download it to PC though and open the .zip file and make sure everything is there, boot.img system.img radio.img etc If it's just a TWRP on its own I don't think there will be a recovery.img, hopefully there is though. I didn't download it fully myself, on data plan and not going to spend it downloading a 1gb+ file that isn't even applicable to me :angel:
As for the T-Mobile from another country. You can convert to any device once you're S-OFF(Apart from the obvious CDMA vs GSM so Verizon/Sprint won't work I think) so you could flash T-Mobile Germany(will have to change CID/MID I think MID might be the same though) yes, BUT, you probably won't get OTA updates then and will probably have to download the OTA updates as they are released and collected(at xda for example) and then flash it manually.

BerndM14 said:
That's the exact same link I shared with you already. I think it is the full backup(Not sure about Recovery though) as I tried to download it on my phone and it's a big file. You can just download it to PC though and open the .zip file and make sure everything is there, boot.img system.img radio.img etc If it's just a TWRP on its own I don't think there will be a recovery.img, hopefully there is though. I didn't download it fully myself, on data plan and not going to spend it downloading a 1gb+ file that isn't even applicable to me :angel:
As for the T-Mobile from another country. You can convert to any device once you're S-OFF(Apart from the obvious CDMA vs GSM so Verizon/Sprint won't work I think) so you could flash T-Mobile Germany(will have to change CID/MID I think MID might be the same though) yes, BUT, you probably won't get OTA updates then and will probably have to download the OTA updates as they are released and collected(at xda for example) and then flash it manually.
Click to expand...
Click to collapse
Oh, I'm sorry... Well à donwloaded it and I think this is not good, in the ?zion there is :
boot.emmc.win
boot.emmc.win.md5
cache.ext4.win
cache.ext4.win.md5
data.etx4.win
data.etx4.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
This is just a TWRP, right?
About flahs T-mobile Germany RUU, would it permit me to make the waranty works?
Edit : If I found someone with the same software number than me, I would be able to do the backup, right? I find this :
How do i backup the stock HTC recovery ?
Boot the custom recovery, preferably with Philz touch recovery as it will back up the stock recovery for sure, you need the following command to boot it and not flash it over the stock recovery :
fastboot boot recovery_filename.img
Then make a full nandroid backup, the stock recovery is located inside the backup folder
Click to expand...
Click to collapse
But I don't understand, they said boot the custom recovery with an other recovery? oO Are you able to explain it to me ?

Up?

Allan9914 said:
Oh, I'm sorry... Well à donwloaded it and I think this is not good, in the ?zion there is :
boot.emmc.win
boot.emmc.win.md5
cache.ext4.win
cache.ext4.win.md5
data.etx4.win
data.etx4.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
This is just a TWRP, right?
About flahs T-mobile Germany RUU, would it permit me to make the waranty works?
Edit : If I found someone with the same software number than me, I would be able to do the backup, right? I find this :
But I don't understand, they said boot the custom recovery with an other recovery? oO Are you able to explain it to me ?
Click to expand...
Click to collapse
Yes that's a TWRP backup, like suspected though, no recovery.img file to go back to stock recovery.
German RUU - You could convert device to German T-Mobile sure, will it pass warranty? If you're very lucky and they don't look deeper into this then sure, I suppose it could pass. Though somehow I doubt that'll happen
Same software number...? Is this physical access to a phone that has the same software as yours or did you get it online somewhere? I don't understand your edit part there... But regardless, you can make a backup of his device yes or ask him to do it or if he already made a backup with CWM/Philz Touch then it'll help a lot too as it'll have the recovery.img. I won't say much more about this though..need more clarity from your side about that...
They don't boot a recovery with another recovery, they boot the custom recovery from fastboot in order to make a backup of the system + stock recovery. You should have done this before you flashed a custom recovery as well, preferably with CWM/Philz Touch Recovery. If you're going to use TWRP then you'll first have to manually "dump" the recovery as a backup, if you use Philz, Philz could at least have made a backup of the stock recovery.
But yeah, you can boot into a custom recovery. Connect the phone to the device, reboot into bootloader, open command prompt change directory to where adb.exe is. Type in fastboot boot name_of_custom_recovery.img then you can make a backup of system including recovery(IF you booted Philz/CWM) .
It's a bit too late for you now though, you already flashed a custom recovery which over wrote the stock you had.

Hi!
Last week I checked for my recovery backup on google and I found this post :
http://forum.xda-developers.com/htc-one-m8/help/t-mobile-poland-1-57-118-2-stock-t2852647/page2
And this guy was looking for the same thing than me! An I could donwload the file, so, I will be able to return 100% sotck!
But i just have one question : In the guide that you post
[GUIDE] Return your M8 to 100% Stock Follow the instructions in that thread, it'll be the same for most devices just use the correct software applicable to your phone. You need to be S-OFF to achieve the removal of tampered banner and other goodies.
Click to expand...
Click to collapse
I don't find when and how I'm supposed to install the stock recovery...
Can someone help me ?
Thanks a lot!

Allan9914 said:
Hi!
Last week I checked for my recovery backup on google and I found this post :
http://forum.xda-developers.com/htc-one-m8/help/t-mobile-poland-1-57-118-2-stock-t2852647/page2
And this guy was looking for the same thing than me! An I could donwload the file, so, I will be able to return 100% sotck!
But i just have one question : In the guide that you post
I don't find when and how I'm supposed to install the stock recovery...
Can someone help me ?
Thanks a lot!
Click to expand...
Click to collapse
Reboot your phone into bootloader mode (Volume Down + Power button)
Connect Phone to PC
Open command prompt in adb folder
Type fastboot devices to make sure device is connected.
Type fastboot flash recovery recovery.img - It should be recovery.img I don't think anyone would change the name of the recovery.
Type fastboot reboot - Phone will reboot back into OS.
Recovery is flashed and you can do updates. Of course the rest of your phone needs to be stock as well but seeing as you only mentioned the recovery now I take it that your phone is back to stock.

BerndM14 said:
Reboot your phone into bootloader mode (Volume Down + Power button)
Connect Phone to PC
Open command prompt in adb folder
Type fastboot devices to make sure device is connected.
Type fastboot flash recovery recovery.img - It should be recovery.img I don't think anyone would change the name of the recovery.
Type fastboot reboot - Phone will reboot back into OS.
Recovery is flashed and you can do updates. Of course the rest of your phone needs to be stock as well but seeing as you only mentioned the recovery now I take it that your phone is back to stock.
Click to expand...
Click to collapse
Ok, thx, but if I understand correctly, I have to dos this instead of ste the step 6 of the guide?
6. Flash stock FW package
Now your phone is back to 100% stock, we need to get the stock recovery back on the phone. To do this, you have to flash the 2.22.401.4 FW package from HERE. To flash this file, do the following:
a. Reboot phone into fastboot
b. Copy the FW file to your fastboot folder on your PC (if you don't have fastboot in your system path)
c. Rename the FW file firmware.zip (NOT firmware.zip.zip)
d. Type: fastboot oem rebootRUU and wait for device to reboot
e. Type: fastboot flash zip firmware.zip and wait for process to complete. Although you don't have to do this twice as you used to do with RUU ZIPs, it's STRONGLY recommended that you run this command a second time after the first has finished to make sure it 'takes' properly
f. Type: fastboot reboot
The phone will now reboot
Click to expand...
Click to collapse
Right?

Allan9914 said:
Ok, thx, but if I understand correctly, I have to dos this instead of ste the step 6 of the guide?
Right?
Click to expand...
Click to collapse
Nah it's not necessary, just flash back the stock recovery. You'll get the latest firmware for your device when you do the OTA update anyways and at least this way you know that things won't go wrong.
I think they included that method because the latest recovery.img file is already in the firmware package and flashing it will restore the recovery back. You can just restore/flash it normally and let the system update itself. Like I said above, not a lot can go wrong that way.

BerndM14 said:
Nah it's not necessary, just flash back the stock recovery. You'll get the latest firmware for your device when you do the OTA update anyways and at least this way you know that things won't go wrong.
I think they included that method because the latest recovery.img file is already in the firmware package and flashing it will restore the recovery back. You can just restore/flash it normally and let the system update itself. Like I said above, not a lot can go wrong that way.
Click to expand...
Click to collapse
Ok, well i will do this when i find the time!
Thanks again for all you've done for me! you'r my hero!

Hi!
Well, I found time to do this!
- I restored my nandroid backup with the stock rom
- I reseted the tampered flag
-I reseted the Unlocked flag and now it's "Locked"
-I unrooted my phone
but I have a probleme with the recovery...
When I type "fastboot flash recovery recovery.img", I get an error :
c:\miniadb_m7>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (15236 KB)...
OKAY [ 1.431s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.440s
I did something wrong? The phone is int fastboot USB, the computer recognize it. For adb I use the miniadb_v1031, recomended in topics to remove tampered flags and to remove unlocked flag.
Can you help me with this ?
Thx!
Allan
edit : I also try to do "fastboot oem rebootRUU" before trying flash recovery.img!

Allan9914 said:
Hi!
Well, I found time to do this!
- I restored my nandroid backup with the stock rom
- I reseted the tampered flag
-I reseted the Unlocked flag and now it's "Locked"
-I unrooted my phone
but I have a probleme with the recovery...
When I type "fastboot flash recovery recovery.img", I get an error :
c:\miniadb_m7>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (15236 KB)...
OKAY [ 1.431s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.440s
I did something wrong? The phone is int fastboot USB, the computer recognize it. For adb I use the miniadb_v1031, recomended in topics to remove tampered flags and to remove unlocked flag.
Can you help me with this ?
Thx!
Allan
edit : I also try to do "fastboot oem rebootRUU" before trying flash recovery.img!
Click to expand...
Click to collapse
Flash a recovery with a locked bootloader
Unlock bootloader, flash stock recovery, lock bootloader.

Yeah... I understood my mistake 1min before you post..
YOU ARE THE BEST!! haha
So, it worked!
Now, when I go into the recovery I have a phone with a red "!" inside a triangle, is it okay?

Allan9914 said:
Yeah... I understood my mistake 1min before you post..
YOU ARE THE BEST!! haha
So, it worked!
Now, when I go into the recovery I have a phone with a red "!" inside a triangle, is it okay?
Click to expand...
Click to collapse
Yeah that's the stock recovery. Just hold Volume Up and then TAP power button and you'll enter the recovery options.

Thanks a lot! Really. What you've made for me is huge.
Just hope thaht they could repare my phone, because I don't wan't to pay again for s-off
Thanks again!
Cya!

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.

RESOLVED! [SOS!] Phone can't boot past bootloader

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.