Develop Bugs

help with get back stock rom from custom rom

hi, i have this htc one x.
this is fastboot info (fastboot getvar all)
Code:
(bootloader) version: 0.5a
(bootloader) [COLOR="Red"]version-bootloader: 1.39.000[/COLOR]0
(bootloader) version-baseband: 5.1204.164.30H
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) [COLOR="Red"]version-main: 3.14.771.34[/COLOR]
(bootloader) serialno: HT23TW126661
(bootloader) imei: 359188042590570
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) [COLOR="Red"]cidnum: H3G__G04[/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
actually it has running cyanogen rom, but i wanna get back to stock rom.
as info, i haven't nandroid backup or anything else.
i have downloaded latest ruu from Hutchison, but i don't find exactly rom. H3G__G04 (H3G_SWE)
i have downloaded rom from H3G from UK. and i tried flash this rom, but i get bootloader error.
i almost forget it. i was locked bootloader to run RUU, and i have read many threads from forum.
anybody can help me to get back to stock rom please?

hyber_99 said:
hi, i have this htc one x.
actually it has running cyanogen rom, but i wanna get back to stock rom.
as info, i haven't nandroid backup or anything else.
i have downloaded latest ruu from Hutchison, but i don't find exactly rom. H3G__G04 (H3G_SWE)
i have downloaded rom from H3G from UK. and i tried flash this rom, but i get bootloader error.
i almost forget it. i was locked bootloader to run RUU, and i have read many threads from forum.
anybody can help me to get back to stock rom please?
Click to expand...
Click to collapse
What sense version do you want in result: 4+ or 5?
Did you update your phone via OTA earlier?
Post bootloader error here, please. Looks like your bootloader is updated and do not match requirements to flash RUU from Hutchison.

1.- i dont know what is better, if 4+ or 5.
2.- in fact the phone was updated by other person, i don't know what he did :/
3.- let me flash ruu again and post bootloader error.
if it's usefull, it has Team Win Recovery Project v2.4.1.0 installed.
thanks for reply

genocide_ru said:
What sense version do you want in result: 4+ or 5?
Did you update your phone via OTA earlier?
Post bootloader error here, please. Looks like your bootloader is updated and do not match requirements to flash RUU from Hutchison.
Click to expand...
Click to collapse
Error 140, error with bootloader version.
and if i try with Europe RUU i got Error with Carrier ID.

hyber_99 said:
Error 140, error with bootloader version.
and if i try with Europe RUU i got Error with Carrier ID.
Click to expand...
Click to collapse
Well, looks like firmware\hboot was updated and latest RUU for your CID requires older firmware\hboot.
So, you can't use old RUU to go back to stock.
You need to flash stock ROM for 1.39 hboot from recovery
Try to find ROM like this one, but older: http://forum.xda-developers.com/showthread.php?t=1546970&highlight=*stock*
I guess you need to search 3.18 or 3.20 version, don't remember wwich one will work with 1.39

ok, i'll search it.
thank you sir, i'll let you know the results.

one more question, can i use this method posted here? http://forum.xda-developers.com/showthread.php?t=1927048
exactly this:
Nand for H3G__106 - thanks to Jackster88
Part 1
Part 2
Quote:
Instructions:
***For this nand to work you need HBOOT 1.39 and cwm***
1) go into fastboot and enter "fastboot oem lock" - the device will reboot
2) go into fastboot again and enter "fastboot oem rebootRUU" - there will be a black screen with a silverish HTC logo
3) enter "fastboot flash zip firmware.zip" (you need the firmware.zip from page 1 for this)
3a) enter the same again, the green bar under the logo should go to 100% (either after the first or second time)
4) enter "fastboot reboot-bootloader" to go back to your fastboot
5) unlock your device again with the unlock code ("fastboot flash unlocktoken Unlock_code.bin")
6) Restore your old boot.img (fastboot flash boot name_of_boot_file.img) and recovery (fastboot flash recovery name_of_recovery_file.img), make sure you copied them from the nandroid backup folder we created earlier into the folder that contains the fastboot.exe you're using.
7) Reboot and you should now have Hboot 1.39 with your old boot and recovery.
(8) If it won't work we still have the backup ready to restore the old system, Hboot isn't changeable right now on S-ON devices outside of the RUU routine - so even if you restore your nandroid you should still have Hboot 1.39 now)
Confirmed working with H3G__001, H3G__003, H3g__G04
Click to expand...
Click to collapse

hyber_99 said:
one more question, can i use this method posted here? http://forum.xda-developers.com/showthread.php?t=1927048
exactly this:
Click to expand...
Click to collapse
yes, you can try this method
except, I guess you need not flash firmware, because you are already on 1.39

genocide_ru said:
yes, you can try this method
except, I guess you need not flash firmware, because you are already on 1.39
Click to expand...
Click to collapse
thank you very much.
after all i solve my problem installing RENOVATE Final 4 Rom ------ http://forum.xda-developers.com/showthread.php?t=1705334&highlight=3+20
after installing rom, we need flash kernel manually i flashed stock kernel.
my problem was that with cyanogen 10.1 this phone cann't accept unlocking code,
but now with renovate rom, code was accepted and phone now is sim unlocked
thank you very much for your time

hyber_99 said:
thank you very much.
my problem was that with cyanogen 10.1 this phone cann't accept unlocking code,
but now with renovate rom, code was accepted and phone now is sim unlocked
thank you very much for your time
Click to expand...
Click to collapse
No problem, man!
Glad I helped you with this :good:

Brick?

Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo

mtt_73 said:
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
Click to expand...
Click to collapse
im going to assume your phones is s-off?

Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Thank you.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Click to expand...
Click to collapse
You can't install custom recovery with a (re)locked bootloader.
With s-off, you shouldn't ever relock the bootloader, as its no longer a requirement to RUU once s-off. But that's neither here nor there at this point, just info for future reference.
Any response to: fastboot devices
Make sure the phone is in fastboot mode.
Try to run the GPE RUU with phone in fastboot mode, to get the phone back up and running at least. Assuming you are still on the GPE CID and MID.

How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Click to expand...
Click to collapse
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.

Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT.............8
(bootloader) imei: 35...........30
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

redpoint73 said:
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Click to expand...
Click to collapse
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Click to expand...
Click to collapse
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
mato123 said:
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
Click to expand...
Click to collapse
I would highly suggest not to post to another user's troubleshooting thread like this, as it doesn't look like the same problem at all (and in my experience rarely is, even when folks will post "I have the same issue"). You really should have just started your own thread, and would have been justified doing so IMO. Posting here just confuses matters for you, the OP and those trying to help.
But DON'T start another thread now (and add even more confusion). I'll ask the mods if they can move this post to its own thread.

ok, sorry

redpoint73 said:
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
Click to expand...
Click to collapse
Thanks for reply.
I went now in fastoob mode and tried to flash the RUU GPE again.
The error is:
macbooks-MacBook-Proownloads macbook$ ./fastboot-mac flash RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
unknown partition 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
error: cannot determine image filename for 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
Just to clarify. I successfully when in GPE (with conversation). The problem was when going back to Sense. I do not know exactly what I did wrong.
My CID is 11111111
My MID is 0P6B10000
Really do not know how to proceed.
M

I unfortunately don't know jack about how to use fastboot and other actions on a Mac. I'm also not that familiar with running the RUU as a zip (I always do it on a PC with the RUU .exe).
But it looks like you just have the command syntax wrong. I think it should be:
fastboot oem rebootRUU
fastboot flash zip filename.zip
But it also look to me like nothing is actually "wrong" (aside from adb not working?). The phone not booting after relocking the bootloader is normal and intentional. You should just be able to run the desired Sense RUU, provided you have the right MID.

I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M

mtt_73 said:
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
Click to expand...
Click to collapse
hehe try watch this movie: https://www.youtube.com/watch?v=CCGj0rOuiR4
Most important is the firmware flash... so partition layout etc is changed to sense like after that you can flash sense roms etc. (for example viper rom as in video)

0kk0 said:
Most important is the firmware flash... so partition layout etc is changed to sense
Click to expand...
Click to collapse
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.

redpoint73 said:
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
Click to expand...
Click to collapse
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Sent from my HTC One_M8 using xda Forum

mtt_73 said:
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Click to expand...
Click to collapse
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.

redpoint73 said:
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
Click to expand...
Click to collapse
I did it. I am back to Sense now.
Any advice to remove tell HTC problem? I mean it says that I have a testing device. Is it because I am s-off? Should I go for s-on again? And how?
TY!

HELP PLS! Bootloader OS version and software number not the same

Hi All,
I'm not sure how I managed to do this but I think I bricked my phone
My bootloader was unlocked and the phone was rooted. I wanted to bring the phone back to stock in order to be able to install an OTA update.
I flashed the stock ROM and was able to install the OTA update.
After this I ran into a problem where the phone would boot and upgrade apps then right before finishing the boot it would reboot and start the process all over again. Looping everytime that the upgrade apps would finish.
Log story short I ended up restarting the process of going back to stock to try everything from scratch again. Things were not working so I foolishly relocked the bootloader thinking it wouldn't be an issue to unlock again with the unlock_code.bin file that I had used previously.
Now the phone will boot into the bootloader and into download mode but not into recovery.
Ive tried flashing the stock recovery and the TWRP recovery and even the recovery from the OTA update but none will flash as the bootloader is locked.
I tried to unlock the bootloader again but cannot and here is the reason why.
The bootloader thinks my OS is 5.1 but really the OS on the phone is 5.0.2
C:\Users\Dan\Desktop\HTC One\One M9>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.666.2
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.02_U11440601_77.04.50715G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
all:
finished. total time: 0.033s
Software number on my phone is 1.32.666.30 but version-main is 2.11.666.2
Fastboot oem unlock does not work as the bootloader is looking for a flag that is set by selecting the developer option of unlock bootloader but that developer option only exists in android 5.1+
Being as the OS on my phone is 5.0.2 I don't have that option in my developer options.
When I boot into RUU with "fastboot oem rebootRUU" and I try to flash my stock rom I now get this.
C:\Users\Dan\Desktop\HTC One\One M9>htc_fastboot flash zip 0PJAIMG.zip
sending 'zip'... (94347 KB) OKAY
sending time = 5.298 secs
writing 'zip'... (bootloader) HOSD CL#579410
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 10(s)
I found a tool called misctool which can change the main version to whatever I choose - If I could change the main version back to 1.32.666.30 I'm assuming this would allow me to flash the stock ROM again and get me back up and running.
The problem is that misctool requires root and I cannot get root without unlocking the bootloader which I cannot unlock because the OS on my phone does not have the option to do so
I read about using nautilus within ubuntu to be able to push files into root areas of my phone and have tried to go this route but I cant get my phone to appear in ubuntu while its in download mode.
Sigh if only I could find a way to get root to be able to change the version-main I think my troubles would be a thing of the past
Can anyone shed any light on my dismal situation?

Your phone is bricked until there is a ruu for your cid/mid. You've made the same mistake as many people before you, which was relocking your bootloader before ticking the allow oem unlock option.
Sent from my HTC One M9 using Tapatalk

iElvis said:
Your phone is bricked until there is a ruu for your cid/mid. You've made the same mistake as many people before you, which was relocking your bootloader before ticking the allow oem unlock option.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
How.. He didnt have the option to begin with. Like many others dont as 5.1 is the version with the unlock option. 5.0.1/.2 don't have the option so you cannot tick unlock, update and unlock the bl.
If you cannot see the logic, please explain your method.
I wish I stole my HTC M9. It's a pile of ****.

Thats the thing,
I was never able to boot into 5.1. As I mentioned in my OP the phone kept rebooting at finishing boot after optimizing the apps.
I figured flashing the stock ROM back on to the phone would let me start over again..
It wasn't until after I relocked the bootloader and started to get errors when trying to unlock it again that I read about the "Allow OEM Unlock" option within the developer options of the phone.
Now that the original ROM is back on the phone that option does not exist in my develop options as the OS version is 5.0.2
I'm wondering why flashing the stock ROM didn't put the stock bootloader version back on the phone at the same time.
All I know now is that the bootloader requires the "Allow OEM Unlock" option to be checked (as it seems to think my software number is 2.11.666.2) in order to let me unlock my bootloader which I cannot do as I the option does not exist in the developer options of 5.0.2.
If only I could gain root while in the adb shell. With that I could use misctool to set the software version back to 1.32.666.30 which I think would then allow me to re-flash my stock ROM, put the bootloader back to what it was, and allow me to unlock it again.
Who creates the RUUs? HTC? HTC and my carrier? Waiting for that to come around is a terrible outcome. I think I will have better luck waiting for a root shell exploit to come around.
Ahhhh what a crappy situation.
shivadow said:
I wish I stole my HTC M9. It's a pile of ****.
Click to expand...
Click to collapse
Mwahahahaha I'm starting to feel the same way!

Of course you could not have ticked the oem unlock option before starting the process. That wasn't what I meant.
The problem is that you upgraded to 5.1 via ota (that's why your version-main says 2.11), so now you have to tick it to unlock. It was locking after the ota but before getting your OS straightened out that was the mistake. Now you're stuck.
There seems to be a problem with the 2.11 update that causes this boot loop issue. I have not seen a fix since I don't believe HTC has released a RUU for 2.11. But, as you recognized in the OP, relocking in the middle of this was not the solution.

I was able to flash the firmware from the 2.11.666.2 OTA.
Now I can no longer boot into the 1.32.666.30 OS but I can boot into the stock recovery but there is not much I can do from there.
I've tried to sideload the OTA but of course it doesnt work because of the changes to the system partition from when I was rooted.
Ive tried to flash a twrp system.emmc.win from a stock backup of the 1.32.666.30 but it errors out with signature verification failed. Im assuming because its a backup of the 1.32.666.30 and not the 2.11.666.2?
Would it make sense that if I could find a system img of the Bell Mobility 2.11.666.2 I would be able to sideload it? Maybe that would fix the issues with the system partition and allow the OTA to complete s that I could then at least boot into the phone ?
Or am I looking at smashing this thing and going to buy another one?

Try to S-Off your phone. Though it probably won't work without root.

omar302 said:
Try to S-Off your phone. Though it probably won't work without root.
Click to expand...
Click to collapse
Thanks Omar. I don't think I can go for S-OFF as my bootloader is relocked and I can't re unlock it.
Root is gone too except for the mess that it made to the system partition. Which is why I cant sideload the OTA.
If only I could get rid of the OTA verification. It would install and I think my phone would let me boot into the os where I could finally choose the "Enable OEM Unlock" option in the developer options.
Right now im trying to find an OTA for Bell Mobility that updated the OS to 5.0.2 if I could find that I could flash that firmware which would probably put the bootloader back to 1.32.666.30.
That way I could unlock the bootloader through adb etc.
I seriously think Im screwed unless if I could find that firmware or find out a way to fool the OTA into believing nothing changed with the system partition so that it would complete the install sigh

You might try an earlier ruu.zip for your CID and see if you can load it from the sdcard in Download mode. This would downgrade you to something functional. You can downgrade firmware on the M9 even with s-on as long as the aboot has not changed. Not sure if this will work for you, but it's worth a shot.
If it works, get root and s-off, then just flash everything manually. I've seen too many people screw up their phones trying to revert to stock to get OTAs.

iElvis said:
You might try an earlier ruu.zip for your CID and see if you can load it from the sdcard in Download mode. This would downgrade you to something functional. You can downgrade firmware on the M9 even with s-on as long as the aboot has not changed.
Click to expand...
Click to collapse
Sadly that's not true. What I learned during the last weeks (from trying to help others like Amr Nasser or Denis Meissner) is that a downgrade with S-ON is only possible if the first and the second version number are the same before and after the downgrade. That means a downgrade from 1.32.xxx.15 to 1.32.xxx.8 is possible but from 1.40.xxx.8 to any 1.32 version is not. The same applies to downgrades from 2.xx versions.

Flippy498 said:
Sadly that's not true. What I learned during the last weeks (from trying to help others like Amr Nasser or Denis Meissner) is that a downgrade with S-ON is only possible if the first and the second version number are the same before and after the downgrade. That means a downgrade from 1.32.xxx.15 to 1.32.xxx.8 is possible but from 1.40.xxx.8 to any 1.32 version is not. The same applies to downgrades from 2.xx versions.
Click to expand...
Click to collapse
Probably because the aboot version has changed between those versions. At least that was how it was explained to me by someone more knowledgable a while back.

iElvis said:
Probably because the aboot version has changed between those versions. At least that was how it was explained to me by someone more knowledgable a while back.
Click to expand...
Click to collapse
According to my phone it's still version 1.0.0.0000. That's why I don't understand why a downgrade is impossible.
D:\Root>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__102
all:
finished. total time: 0.016s
Edit: Don't get me wrong. I don't want to start an argument. I'm just trying to understand this phone.

Flippy498 said:
Edit: Don't get me wrong. I don't want to start an argument. I'm just trying to understand this phone.
Click to expand...
Click to collapse
No that's what I thought. Someone else insisted the aboot version was what mattered. But I haven't tried it myself so I'm just passing on what I was told.

Cannot lock bootloader? Flashing to stock (1.53.708.3) did not set S-ON.

Hi all, my first post.
I need a little clarification on what is going on with my HTC 10 at the moment.
2 weeks ago I was running version:
Code:
(bootloader) version-main: 1.80.708.6
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__622
And I decided to check for updates after hearing about the new Android release.
To my surprise received the following error:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance
I quickly found a tutorial how to fix this. Basically I needed to flash it with stock RUU. At the same time I decided to change CID to superCID.
So here is what I did:
1. Unlocked bootloader with token file from HTCDEV. Status UNLOCKED
2. Rooted the phone using TWRP and ADB.
3. Used Sunshine to set S-OFF (as it turned out later this step was unnecessary)
4. Wrote new CID with fastboot
5. Downloaded signed RUU 2PS6IMG_PERFU[email protected]60331_39.13_F_release_478389_signed_2_4.zip and flashed it.
6. Phone was back to 1.53.708.4
7. OTA now works and pushing updates.
8. Right now phone is on 2.41.708.3
Code:
INFOmax-download-size: 1579200000
INFOcurrent-slot:*
INFOversion-main: 2.41.708.3
INFOboot-mode: download
INFOversion-baseband: [email protected]
INFOversion-bootloader: 1.0.0.0000
INFOmid: 2PS620000
INFOcid: 11111111
And here is my problem. At the moment phone is in:
Code:
*** UNLOCKED ***
*** S-OFF ***
When I run fastboot oem lock I get the following:
Code:
/fastboot-mac oem lock
... INFO[KillSwitch] : /dev/block/bootdevice/by-name/frp
INFO[KillSwitch] Last Byte is 0X00, disable unlock
INFO[KillSwitch] oem unlock Turn Off!
OKAY
The bootloader seems to be unlocked
Also, I was under impression that if I flash it with stock firmware the S-OFF will change into S-ON but it has not. How do I change it without wiping? Would you recommend to leave it S-OFF? Are there any risks? Despite the fact it's unlocked and S-OFF it runs very smooth on the latest update.
Thanks in advance.

You will always have to wipe. Nothing you can do about that.

payero3491 said:
Hi all, my first post.
I need a little clarification on what is going on with my HTC 10 at the moment.
2 weeks ago I was running version:
And I decided to check for updates after hearing about the new Android release.
To my surprise received the following error:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance
I quickly found a tutorial how to fix this. Basically I needed to flash it with stock RUU. At the same time I decided to change CID to superCID.
So here is what I did:
1. Unlocked bootloader with token file from HTCDEV. Status UNLOCKED
2. Rooted the phone using TWRP and ADB.
3. Used Sunshine to set S-OFF (as it turned out later this step was unnecessary)
4. Wrote new CID with fastboot
5. Downloaded signed RUU 2PS6IMG_PERFU[email protected]60331_39.13_F_release_478389_signed_2_4.zip and flashed it.
6. Phone was back to 1.53.708.4
7. OTA now works and pushing updates.
8. Right now phone is on 2.41.708.3
And here is my problem. At the moment phone is in:
When I run fastboot oem lock I get the following:
The bootloader seems to be unlocked
Also, I was under impression that if I flash it with stock firmware the S-OFF will change into S-ON but it has not. How do I change it without wiping? Would you recommend to leave it S-OFF? Are there any risks? Despite the fact it's unlocked and S-OFF it runs very smooth on the latest update.
Thanks in advance.
Click to expand...
Click to collapse
Not sure about the bootloader lock, but you paid for s-off, no need to go back to s-on unless you want to send the phone in for warranty. Keep it as is, no risk if you just keep it to basics like flashing Roms and kernels. If you don't trust yourself and still need to go back to S-ON, it's done using a fastboot command. Look here:
https://forum.xda-developers.com/htc-10/how-to/guide-safely-set-bootloader-to-locked-t3386456
The above link will also show you how to lock your bootloader with Sunshine. The phone will not s-on itself just from flashing a stock rom.
Also I'm not sure why you even had to change your CID.
And you don't need to ruu each time to take an Ota. You just need to be in an untouched state, meaning restore system image + recovery, and not have superCID. Ruu is a sure way, but is not necessary if the above works for you.

payero3491 said:
Hi all, my first post.
I need a little clarification on what is going on with my HTC 10 at the moment.
2 weeks ago I was running version:
Code:
(bootloader) version-main: 1.80.708.6
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__622
And I decided to check for updates after hearing about the new Android release.
To my surprise received the following error:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance
I quickly found a tutorial how to fix this. Basically I needed to flash it with stock RUU. At the same time I decided to change CID to superCID.
So here is what I did:
1. Unlocked bootloader with token file from HTCDEV. Status UNLOCKED
2. Rooted the phone using TWRP and ADB.
3. Used Sunshine to set S-OFF (as it turned out later this step was unnecessary)
4. Wrote new CID with fastboot
5. Downloaded signed RUU 2PS6IMG_PERFU[email protected]60331_39.13_F_release_478389_signed_2_4.zip and flashed it.
6. Phone was back to 1.53.708.4
7. OTA now works and pushing updates.
8. Right now phone is on 2.41.708.3
Code:
INFOmax-download-size: 1579200000
INFOcurrent-slot:*
INFOversion-main: 2.41.708.3
INFOboot-mode: download
INFOversion-baseband: [email protected]
INFOversion-bootloader: 1.0.0.0000
INFOmid: 2PS620000
INFOcid: 11111111
And here is my problem. At the moment phone is in:
Code:
*** UNLOCKED ***
*** S-OFF ***
When I run fastboot oem lock I get the following:
Code:
/fastboot-mac oem lock
... INFO[KillSwitch] : /dev/block/bootdevice/by-name/frp
INFO[KillSwitch] Last Byte is 0X00, disable unlock
INFO[KillSwitch] oem unlock Turn Off!
OKAY
The bootloader seems to be unlocked
Also, I was under impression that if I flash it with stock firmware the S-OFF will change into S-ON but it has not. How do I change it without wiping? Would you recommend to leave it S-OFF? Are there any risks? Despite the fact it's unlocked and S-OFF it runs very smooth on the latest update.
Thanks in advance.
Click to expand...
Click to collapse
Hello!
Could you share the link you downloaded RUU 1.53.708.4? Really appreciate that!
Thank you.

lilrice said:
Hello!
Could you share the link you downloaded RUU 1.53.708.4? Really appreciate that!
Thank you.
Click to expand...
Click to collapse
**Previously posted link deleted**

xunholyx said:
https://forum.halabtech.com/vb/show...0013-60331_39-13_F_release_4-78389_signed_2_4
Click to expand...
Click to collapse
Hello,
I registered an account on this website, but it says that this file is "featured" and free account cannot download it.
Appreciate your help any way.
If someone could re-upload it somewhere else, it would be nice.
Best regards

lilrice said:
Hello,
I registered an account on this website, but it says that this file is "featured" and free account cannot download it.
Appreciate your help any way.
If someone could re-upload it somewhere else, it would be nice.
Best regards
Click to expand...
Click to collapse
I never realized it was one of those sites you have to pay at. Sorry.
Use this link instead

xunholyx said:
I never realized it was one of those sites you have to pay at. Sorry.
Use this link instead
Click to expand...
Click to collapse
I found and downloaded this file and also the file 1.21.708. on androidfilehost of Stifilz already, but both ZIP files are corrupted, dont know why, but both PC and my phone say so. Thats why im looking for another hosts.
Thanks sir you are nice

lilrice said:
I found and downloaded this file and also the file 1.21.708. on androidfilehost of Stifilz already, but both ZIP files are corrupted, dont know why, but both PC and my phone say so. Thats why im looking for another hosts.
Thanks sir you are nice
Click to expand...
Click to collapse
There not corrupted there signed.

I flashed it any way
It worked! Thank you ! Very happy to go back to MM
Cheers

HTC 10 - Bricked

So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still disabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?

PirateNL said:
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still enabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
Click to expand...
Click to collapse
im in the same situation ,i'm currently looking at data recovery option from gillware since apparently they literally go the extra mile physically to extract data. but im hoping there is options for me to unbrick it before deciding on that option

venom55521 said:
im in the same situation ,i'm currently looking at data recovery option from gillware since apparently they literally go the extra mile physically to extract data. but im hoping there is options for me to unbrick it before deciding on that option
Click to expand...
Click to collapse
Well at least the data on the device is not worth much to my friend. Let me know if you find were able to unbrick it

PirateNL said:
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still disabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
Click to expand...
Click to collapse
ADB won't detect it if USB debugging is turned off.
Can you boot to RUU mode? If so you could restore it perhaps that way. If you are booted to that you can run an RUU.exe
The command is:
fastboot oem rebootRUU

xunholyx said:
ADB won't detect it if USB debugging is turned off.
Can you boot to RUU mode? If so you could restore it perhaps that way. If you are booted to that you can run an RUU.exe
The command is:
fastboot oem rebootRUU
Click to expand...
Click to collapse
Thanks for your reply. I'm not sure on how I can execute that command without ADB/USB debugging being enabled? Any advice there?

PirateNL said:
Thanks for your reply. I'm not sure on how I can execute that command without ADB/USB debugging being enabled? Any advice there?
Click to expand...
Click to collapse
You don't have to have USB debugging on to use fastboot commands, only ADB commands. For many fastboot commands, you need an unlocked bootloader. For this one you don't. Or at least you didn't on the M8 before HTC introduced download mode. I'm pretty sure it will still work.

xunholyx said:
You don't have to have USB debugging on to use fastboot commands, only ADB commands. For many fastboot commands, you need an unlocked bootloader. For this one you don't. Or at least you didn't on the M8 before HTC introduced download mode. I'm pretty sure it will still work.
Click to expand...
Click to collapse
So I only had time to test this today. And you were right i was able to trigger this command:
fastboot oem rebootRUU
The phone then rebooted showed the grey HTC boot screen and soon after it started the boot loop sequence again. What am I suppose to do now? Is there anything I can flash in this RUU mode? Thanks again for your help.

PirateNL said:
So I only had time to test this today. And you were right i was able to trigger this command:
fastboot oem rebootRUU
The phone then rebooted showed the grey HTC boot screen and soon after it started the boot loop sequence again. What am I suppose to do now? Is there anything I can flash in this RUU mode? Thanks again for your help.
Click to expand...
Click to collapse
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.

xunholyx said:
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
Click to expand...
Click to collapse
Unfortunately I do not see the red security warning, it just a grey HTC logo for a few seconds, then it reboots and then shows a white HTC logo + "powered by android" and then its stuck in the boot loop again.
The phone is an EU-model, this is the output you requested:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA69KBN01219
all:
finished. total time: 0.360s
The version-main variable does not seem to be there

xunholyx said:
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
Click to expand...
Click to collapse
Hey man, if you have some time today. Could you please look at the output I sent? Im not sure what to do next.
Thanks in advance

PirateNL said:
Hey man, if you have some time today. Could you please look at the output I sent? Im not sure what to do next.
Thanks in advance
Click to expand...
Click to collapse
The readout doesn't really say anything. With the HTC 10, and starting with the M9 I believe (I never owned one), you can only get a proper getvar from download mode or RUU mode. You can't get one from bootloader anymore like you used to be able to.
You said it was a EU model, so I would suspect it's WWE. The RUUs for that are available, but you can't flash it in bootloader, only download or RUU mode.

exactly the same problem here
PirateNL said:
Unfortunately I do not see the red security warning, it just a grey HTC logo for a few seconds, then it reboots and then shows a white HTC logo + "powered by android" and then its stuck in the boot loop again.
The phone is an EU-model, this is the output you requested:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA69KBN01219
all:
finished. total time: 0.360s
The version-main variable does not seem to be there
Click to expand...
Click to collapse
I have exactly the same problem with my HTC10, i don't have access to download mode, recovey, system, i even tried to boot to an image of twrp and i can't.
Code:
D:\Android\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA661BN06728
all:
Finished. Total time: 0.393s
Click to expand...
Click to collapse
Click to expand...
Click to collapse

xunholyx said:
The readout doesn't really say anything. With the HTC 10, and starting with the M9 I believe (I never owned one), you can only get a proper getvar from download mode or RUU mode. You can't get one from bootloader anymore like you used to be able to.
You said it was a EU model, so I would suspect it's WWE. The RUUs for that are available, but you can't flash it in bootloader, only download or RUU mode.
Click to expand...
Click to collapse
OK that makes sense. But as you know I cannot get into RUU nor download mode. I guess it really is bricked then. Oh well thanks for your time and help.

PirateNL said:
OK that makes sense. But as you know I cannot get into RUU nor download mode. I guess it really is bricked then. Oh well thanks for your time and help.
Click to expand...
Click to collapse
It might not be. A friend reminded me of a method in a conversation about something else. I'm at work right now, but I'll reply again later on when I'm home

Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.

no luck
xunholyx said:
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
Click to expand...
Click to collapse
D:\Android\platform-tools>fastboot flash radio radio.img
Sending 'radio' (54629 KB) OKAY [ 1.341s]
Writing 'radio' FAILED (remote: 'cannot flash
this partition in s-on state')
fastboot: error: Command failed
it says that because it is in S-On state, any ideia ohow can i change the S state?
thank you mate

xunholyx said:
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
Click to expand...
Click to collapse
Tried to revive it today. Unfortunately getting the same error as our friend in the post above me:
Code:
C:\adb>fastboot flash radio radio.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (54629 KB)...
OKAY [ 1.366s]
writing 'radio'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.456s
So to summarize:
- Not able to boot into download/recovery/RUU mode
- Cannot flash images using fastboot due to S-ON
I guess that's it, RIP HTC 10.

PirateNL said:
Tried to revive it today. Unfortunately getting the same error as our friend in the post above me:
Code:
C:\adb>fastboot flash radio radio.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (54629 KB)...
OKAY [ 1.366s]
writing 'radio'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.456s
So to summarize:
- Not able to boot into download/recovery/RUU mode
- Cannot flash images using fastboot due to S-ON
I guess that's it, RIP HTC 10.
Click to expand...
Click to collapse
costum rom was installed on my phone I deleted everything with trwp normally I should have installed a new rom file but I didn't now the htc logo is stuck, there is twrp unlocked but I can't access it the boot loader does not open, because there is no rom, it does not open normally, there is only htc logo and red warning, maybe I can open the security mode or something else I am very tired