Variant System Version OTA Update Error - One (M9) Q&A, Help & Troubleshooting

After a long wait I finally got my ota update to Nougat.
But there is another problem, I cant finish the update because my phone showed that error.
I'm on stock M9 in bootloader it says software status official, locked, and s-on. No root, as I have checked it using root checker. Recovery is there.
I never modified my phone. And its fine back when I updated from lollipop to mm via ota, there is no problem.
And as far as I know, my phone is on correct mid and cid, SKU 708, mid 0PJA10000 exactly the same with mid engraved on my phone, and cid HTC__044
But when I update mm to nougat, this variant system version error shows up
I have tried to flash RUU of my current firmware, but still nothing.
Please help me, where did I do wrong? or how can I solve this problem?

Bumping this because I got the same thing too.
My device is not even rooted!

Did you guys flash a RUU for your current firmware and try to download the OTA, again?

Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I did, but the problem stays there.

Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I dont know how to flash the RUU.
But anyway, is there a way to check whether i can flash the OTA on my own?

vglaksana said:
I did, but the problem stays there.
Click to expand...
Click to collapse
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
-marco- said:
I dont know how to flash the RUU.
Click to expand...
Click to collapse
Well, there is a thread pinned above all the other threads in this section that is even called "ReadMe" and people still tend to completely ignore it...
-marco- said:
But anyway, is there a way to check whether i can flash the OTA on my own?
Click to expand...
Click to collapse
If you can't flash an OTA via the software update function then you can't flash it via fastboot, either. Your phone doesn't pass the security checks that google implemented with android 5 so the method you use for flashing the OTA doesn't matter.
Flash a RUU and re-try to install the OTA. If that still doesn't matter then please copy and paste your fastboot getvar all output here (without your IMEI!), as well.

Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
Here it is
C:\Users\Vito G. Laksana\Desktop\New folder>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114,10801_97.64.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC 044
all: inished. total time: 0.016s
Above is getvar all from before I flashed my current RUU. I believe it wouldn't change anything, as I can't get fastboot getvar all working now.

vglaksana said:
(bootloader) cid: HTC 044
Click to expand...
Click to collapse
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ah my bad. The correct CID is HTC__044, as I mentioned in the thread first post.
I just using image to text converter because I have screencap of the output and didn't see that straight away.

Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for helping me figuring out the problem.
If that is the problem, then why I have successfully update from lollipop to mm?
Yes i did buy it second hand, he said that the phone is from Singapore, and from the getvar output it is make sense that my phone came from Singapore.
Soo...I believe my only option is to S-OFF and convert to other version to get the update, is that correct?

I just re-read your opening post. Looks like I missed the part with the engraving. The US variant has a different engraving than the one you mentioned. So my assumption is probably wrong.
Since I have no clue what might cause your problem I actually don't see any other solution than getting S-OFF and converting the phone.
If there was a publicly available 4.x RUU for your SKU you could have asked Sneakyghost whether he creates a firmware package for you. By flashing that (S-OFF needed) you would have been able to use the 4.x RUU although you never installed the corresponding OTA. This way you could have kept your SKU. However, I haven't seen a public download link for such a RUU, yet. Therefore, you'll need to convert to a different SKU if you want the latest firmware.
Since you're still on firmware 3.x you need to flash one of Sneakyghost's 4.x packages before you can flash a 4.x RUU of the SKU that you want to convert to. Or you use a 3.x RUU for converting and try to install the OTA of the new SKU, afterwards. (The latter will probably take longer in total.)
Alternatively, you can wait some more days and see if some else has a better idea.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
I rebooted into bootloader to get the getvar but it doesnt work.
adb lists no devices.
Also, see the enclosed pic. that's as far as i managed to get.

Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
booted to system: adb sees device but says it's offline
booted to dl mode: adb can't see the device.
anyway, i took picture of what dl mode looks like. Attached.

Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
apparently i had a problem with drivers. i have fixed it now, that's why it gave empty devices.
Ok went back to bootloader mode. run fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54GYJ05021
all:
finished. total time: 0.132s
this is instead the same taken from dl mode:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
all:
finished. total time: 0.006s
what now?

Mhm, there's nothing strange in that output, either.
Can you flash a RUU and re-try installing the OTA? If that doesn't fix the problem then the only other option is converting the phone as I already suggested to vglaksana.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Can you flash a RUU and re-try installing the OTA?
Click to expand...
Click to collapse
can you point me to a guide on how to do this?
and also where can i find my relevant RUU?
thanks.

I already did so in my first reply to you.
Sent from my HTC One M9 using XDA Labs

Related

HTC ONE M8 stuck in bootloop

Hey guys
I know there are similar posts out there but none who describe my exact problem^^
It's like this: Earlier today, I wanted to go back to stock, fully. Which means I downloaded the stock backup and put it on my phone with TWRP. Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
As far, as good, everything worked just fine. And to have it completely back to stock (except for the still unlocked bootloader) I came up with the glorious idea of restoring to factory settings using the options in the phone's settings... aaaand now I'm stuck in the bootloop.
I meanwhile figured out how to enter the bootloader (volume up + power til screen turns fully black, then volume down) and I'm also able to access stock recovery through that... I of course tried factory resetting it through the bootloader and the recovery, I also took the sim card out as somewhere was suggested... but ultimately, it always goes back to the bootloop.
When connecting to the PC I hear the connecting sound... but that's it. It doesn't show up and thus I also can't access it through fastboot/adb
I ran out of ideas myself, do you have any?^^
Thanks!
M4C00kie said:
Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
Click to expand...
Click to collapse
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
M4C00kie said:
I also can't access it through fastboot/adb
Click to expand...
Click to collapse
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
adb requires being in OS or recovery (and I'm not sure if stock recovery supports adb). And for the most part, fastboot is what you need to recover.
Need more info to help further. What CID version of the phone? If OS version number is shown on hboot screen, post it here. What are the version numbers or the stock nandroid, and the stock recovery you installed? If you can get fastboot work, do fastboot getvar all, and post the output.
redpoint73 said:
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
Click to expand...
Click to collapse
That's because I was using an older guide... good to know^^
redpoint73 said:
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
Click to expand...
Click to collapse
That's what's strange... on the phone, it's showing FASTBOOT USB and it even makes this sound when connecting... fastboot commands still don't work though: "error: device not found"
the CID number is HTC__102, he version number of the stock nandroid and recovery was 4.16.401.10
regarding the OS number: on the hboot screen there's just written OS- <- is this the place where it's supposed to be?
thanks a lot for helping!
OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
C:\Users\aaron_000\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.25.2145000
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
my version & radio number are matching the ones in this RUU
so...
what now?^^ before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
oh, and would doing this even help in my current situation?
Thanks for helping
M4C00kie said:
OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
Click to expand...
Click to collapse
Did you do anything different to get it working?
M4C00kie said:
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=f...4a4f68918d8199)
Click to expand...
Click to collapse
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
M4C00kie said:
before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
Click to expand...
Click to collapse
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
M4C00kie said:
oh, and would doing this even help in my current situation?
Click to expand...
Click to collapse
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!
redpoint73 said:
Did you do anything different to get it working?
Click to expand...
Click to collapse
I might have confused adb and fastboot... pretty sure it was working all along
redpoint73 said:
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
Click to expand...
Click to collapse
I initially posted this on another forum... realised too late that this one here was more appropriate and posted it here xD
redpoint73 said:
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
redpoint73 said:
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
Click to expand...
Click to collapse
done.
redpoint73 said:
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!
Click to expand...
Click to collapse
deleted it. thanks for all your help so far!
M4C00kie said:
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
Click to expand...
Click to collapse
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.
redpoint73 said:
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.
Click to expand...
Click to collapse
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ or should I rather download a zip version of it?
M4C00kie said:
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ ?
Click to expand...
Click to collapse
As long as "fastboot" is selected in bootloader it will work.
redpoint73 said:
As long as "fastboot" is selected in bootloader it will work.
Click to expand...
Click to collapse
it worked!!
never heard a sweeter sound before than the HTC boot sound^^
thank you so much for all your help!

Htc One M8 help

So here's my predicament, a long while ago i had installed a rom to my phone assuming i had done everything correctly. This ROM i installed is the Bad Boys One M8 L Sense 7 v 1.0, it is currently still what I'm currently using. What I've been trying to do for days now to return my phone back to stock. My bootloader is unlocked and s-off. I have been unable to install any ROM whatsoever besides the current bad boyz rom. Also when trying to use sunshine, it seems to also encounter problems. If anyone can offer some help or a method to go about fixing this it would greatly appreciated.
Jdp2510 said:
So here's my predicament, a long while ago i had installed a rom to my phone assuming i had done everything correctly. This ROM i installed is the Bad Boys One M8 L Sense 7 v 1.0, it is currently still what I'm currently using. What I've been trying to do for days now to return my phone back to stock. My bootloader is unlocked and s-off. I have been unable to install any ROM whatsoever besides the current bad boyz rom. Also when trying to use sunshine, it seems to also encounter problems. If anyone can offer some help or a method to go about fixing this it would greatly appreciated.
Click to expand...
Click to collapse
For Sunshine to work, flash MaximumHD , or you could also flash ViperOneM8 (suggested by JCase, one of the Sunshine devs) for it to work.
If you want to go back to stock, you need to provide more info. Post the results of fastboot getvar all here (minus your IMEI and serial#), and I or someone else here will be able to give you proper directions.
xunholyx said:
For Sunshine to work, flash MaximumHD , or you could also flash ViperOneM8 (suggested by JCase, one of the Sunshine devs) for it to work.
If you want to go back to stock, you need to provide more info. Post the results of fastboot getvar all here (minus your IMEI and serial#), and I or someone else here will be able to give you proper directions.
Click to expand...
Click to collapse
I have tried the maximus hd with it getting stuck at the recovery screen. As for the other I'll do what i can to figure out that info for you
Jdp2510 said:
I have tried the maximus hd with it getting stuck at the recovery screen. As for the other I'll do what i can to figure out that info for you
Click to expand...
Click to collapse
Not much to figure out.
Hook your phone up to your PC, get into ADB/fastboot, and enter the command fastboot getvar all.
xunholyx said:
Not much to figure out.
Hook your phone up to your PC, get into ADB/fastboot, and enter the command fastboot getvar all.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.25.651.18
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499318193
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_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: 0f94b3b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I've tried running the appropriate RUU; I've tried flashing other roms with no success; I just can't seem to get the correct directions on what I need to do. If anyone has any ideas it will all be very appreciated.
Jdp2510 said:
I've tried running the appropriate RUU; I've tried flashing other roms with no success; I just can't seem to get the correct directions on what I need to do. If anyone has any ideas it will all be very appreciated.
Click to expand...
Click to collapse
You are S-On, so to run the RUU successfully you'll need to re-lock your bootloader first.
In fastboot : fastboot oem lock
Then run the RUU again
I did try that but it kept failing, I'll try one more time.
Like I thought, it failed again, error 155:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I'm downloading the correct RUU. http://www.htc.com/us/support/rom-downloads.html - The HTC One M8.
Jdp2510 said:
Like I thought, it failed again, error 155:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I'm downloading the correct RUU. http://www.htc.com/us/support/rom-downloads.html - The HTC One M8.
Click to expand...
Click to collapse
Error 155 is common for MM RUUs, as there is a peculiarity with the MM RUUs, in which you can't upgrade from LP (or KK for that matter) by RUU unless you first run the MM firmware.zip.
Try flashing the full signed firmware 6.20.651.3 from the following thread (with instructions on how to flash) then run the RUU 6.20.651.3 again:
http://forum.xda-developers.com/showthread.php?t=2729173
Or your other option is to flash the 4.25.651.18 RUU (same thead) and OTA to MM.
---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------
Jdp2510 said:
I have been unable to install any ROM whatsoever besides the current bad boyz rom.
Click to expand...
Click to collapse
Hard to know what you are talking about, if you don't supply the required specifics (what ROMs exactly).
But only ROMs that specifically support Sprint, will work on your phone, due to kernel differences between Sprint and most other versions of the M8.
Running the MM RUU isn't going to change this fact. It seems your goal is to be able to install other ROMs?
What kind of specifics do you need?
I haven't been able to get any other roms to work. The ruu meant for my phone keeps failing, the name of the ROM is what details my phone says,
Jdp2510 said:
What kind of specifics do you need?
Click to expand...
Click to collapse
I already asked exactly what ROMs you tried.
You say you can't get "any ROMs" to work, and only name one (that does work).
You probably are trying to flash ROMs that don't support the Sprint version M8.
---------- Post added at 10:05 AM ---------- Previous post was at 10:04 AM ----------
Jdp2510 said:
The ruu meant for my phone keeps failing, the name of the ROM is what details my phone says,
Click to expand...
Click to collapse
Yup, and it will keep failing, if you just try the same thing over and over.
Did you try to do as I suggested in my post #10 above (flash MM firmware.zip, then try the RUU again)?

Help, my Htc one m9 is bricked from relocking the bootloader.

Hi, I am new on this forum.
I have a problem with my M9. About a year ago, I installed TWRP recovery and rooted android 6.0. Since then I hadn't made any changes to my phone. Once android nougat came out, i couldn't update it with ota update so i decided to return to stock recovery. I flashed the recovery and everything worked fine. I decided to update it with a RUU as the safest bet, and i read somewhere that you need to relock the bootloader. I relocked it and everything seemed fine, it was relocked in bootloader mode but now I can't boot to recovery mode and cannot boot the phone. I can access download mode and bootloader mode. I also can't update it with the ruu because I get signature error 132. I also can't unlock the bootloader, everything goes fine and at the end it still says "relocked". My cid is htc_032 european. What should I do now?
Razor2211 said:
Hi, I am new on this forum.
I have a problem with my M9. About a year ago, I installed TWRP recovery and rooted android 6.0. Since then I hadn't made any changes to my phone. Once android nougat came out, i couldn't update it with ota update so i decided to return to stock recovery. I flashed the recovery and everything worked fine. I decided to update it with a RUU as the safest bet, and i read somewhere that you need to relock the bootloader. I relocked it and everything seemed fine, it was relocked in bootloader mode but now I can't boot to recovery mode and cannot boot the phone. I can access download mode and bootloader mode. I also can't update it with the ruu because I get signature error 132. I also can't unlock the bootloader, everything goes fine and at the end it still says "relocked". My cid is htc_032 european. What should I do now?
Click to expand...
Click to collapse
You shouldn't have relocked it... As far as I know, relocking the m9 is not required... Try searching for solutions or wait for someone with more knowledge regarding your situation...
Sent from my HTC One M9 using Tapatalk
teddy0209 said:
You shouldn't have relocked it... As far as I know, relocking the m9 is not required... Try searching for solutions or wait for someone with more knowledge regarding your situation...
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I think that I may have been using a wrong RUU, but is can't find the correct one. Since I am s-on, it must be for atleast android 6.0 i think.
Here are my details
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
all:
finished. total time: 0.016s
Razor2211 said:
I think that I may have been using a wrong RUU, but is can't find the correct one. Since I am s-on, it must be for atleast android 6.0 i think.
Here are my details
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: -
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
all:
finished. total time: 0.016s
Click to expand...
Click to collapse
What RUU are you using?
Also, I recommend editing your post to remove your IMEI.
computerslayer said:
What RUU are you using?
Also, I recommend editing your post to remove your IMEI.
Click to expand...
Click to collapse
Thanks for the tip about IMEI.
I tried the developer ruu version from the HTC website but i saw that it isn't compatible. I can't find a ruu for my phone that is compatible. I only found zips, but i have no clue how to use them. I know how to flash them, but my bootloader won't unlock. Do you have any idea how to proceed?
Razor2211 said:
I tried the developer ruu version from the HTC website but i saw that it isn't compatible. I can't find a ruu for my phone that is compatible. I only found zips, but i have no clue how to use them. I know how to flash them, but my bootloader won't unlock. Do you have any idea how to proceed?
Click to expand...
Click to collapse
Read the ReadMe thread and all you questions should be answered since that's what that thread is made for.

HTC One M8 Sprint

Hi, I have a htc one m8 and I believe it is a sprint. I bought this of ebay and did not realise it was a sprint version as I wanted a GSM version. I noticed the phone is s-off and has a cidnum of 11111111.
It has problems. If you boot into fastboot, it will stay in fastboot for say 10 seconds then reboot back into the system automatically. OS is not working correctly.
I have downloaded the up to date sprint RUU and this is titled 'RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe'
I tried flashing this from windows 10 as an exe file but this does not work. (Error 155)
Here is the getvar all data minus imei and serial number:
C:\Users\uggitt\Desktop\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.654.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499237405
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d4c3cae5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
I need to get the phone working again and any help would be most appreciated. If anyone needs any further info please let me know.
Mark
Try this RUU: link
lucyr03 said:
Try this RUU: link
Click to expand...
Click to collapse
Thank you and I will give it a go later today
uggitt said:
Thank you and I will give it a go later today
Click to expand...
Click to collapse
Just tried the RUU from your link and I get the same error 155.
uggitt said:
Just tried the RUU from your link and I get the same error 155.
Click to expand...
Click to collapse
Hmm error 155 is related to bootloader status(needs to be locked/relocked) but your device is s-off so you don't need to relock for ruu.
Anyway try to relock your bootloader and come back with the results.
lucyr03 said:
Hmm error 155 is related to bootloader status(needs to be locked/relocked) but your device is s-off so you don't need to relock for ruu.
Anyway try to relock your bootloader and come back with the results.
Click to expand...
Click to collapse
I tried to relock the bootloader but it came back as already locked.
uggitt said:
I tried to relock the bootloader but it came back as already locked.
Click to expand...
Click to collapse
What says in hboot? locked/relocked/unlocked ?
lucyr03 said:
What says in hboot? locked/relocked/unlocked ?
Click to expand...
Click to collapse
locked in hboot
uggitt said:
locked in hboot
Click to expand...
Click to collapse
So.. you have s-off but never unlocked the bootloader? This is strange...
Try to unlock it and see if works.
I have tried to unlock the bootloader but as it keeps rebooting when in Fastboot on the phone after 10-15 seconds. I cannot seem to get the token.
I feel something is wrong with the phones fastboot/hboot but this is only a guess.
I bought the phone like this and I did not s-off etc.
uggitt said:
I have tried to unlock the bootloader but as it keeps rebooting when in Fastboot on the phone after 10-15 seconds. I cannot seem to get the token.
I feel something is wrong with the phones fastboot/hboot but this is only a guess.
I bought the phone like this and I did not s-off etc.
Click to expand...
Click to collapse
I think it's because the battery, I just saw in your getvar the battery reported charged capacity is 0...
lucyr03 said:
I think it's because the battery, I just saw in your getvar the battery reported charged capacity is 0...
Click to expand...
Click to collapse
Ok, phone is on and showing 100%.. Do you think the actual battery is faulty and is causing the problems?
uggitt said:
Ok, phone is on and showing 100%.. Do you think the actual battery is faulty and is causing the problems?
Click to expand...
Click to collapse
If the battery acts normally when phone is on it's not because a battery problem...
The phone stay in hboot without cable connected more than 10 secs?
Sent from my HTC One M9 using Tapatalk
lucyr03 said:
If the battery acts normally when phone is on it's not because a battery problem...
The phone stay in hboot without cable connected more than 10 secs?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, reboots out of hboot with cable or without cable plugged in
uggitt said:
No, reboots out of hboot with cable or without cable plugged in
Click to expand...
Click to collapse
In RUU mode too?(fastboot oem rebootRUU)
Sent from my HTC One M9 using Tapatalk
lucyr03 said:
In RUU mode too?(fastboot oem rebootRUU)
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Hi Just tried and goes into ruu mode and then restarts after say 10 seconds
uggitt said:
Hi Just tried and goes into ruu mode and then restarts after say 10 seconds
Click to expand...
Click to collapse
That's strange behavior... Idk what to say..
Sent from my HTC One M9 using Tapatalk
lucyr03 said:
That's strange behavior... Idk what to say..
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying and for your help. I think it is destined for the bin....
uggitt said:
I have downloaded the up to date sprint RUU and this is titled 'RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe'
I tried flashing this from windows 10 as an exe file but this does not work. (Error 155)
Click to expand...
Click to collapse
You need to flash firmware 6.20.651.3. before the RUU will install. It's a peculiar requirement on US Marshmallow RUUs, that updating by RUU from any lower version (Lollipop, Kitkat) you need to flash firmware first, before RUU, otherwise you will have Error 155.
Firmware and instructions for flashing if can be found here (as well as all Sprint RUUs):
https://forum.xda-developers.com/showthread.php?t=2729173
But if the phone will not stay in hboot (or RUU mode) it may be a problem flashing firmware and/or RUU. May possibly even brick the phone. If flashing firmware or RUU, the process is interrupted when updating hboot partitions, a brick is almost certain. But on the other hand, it looks like you are close to binning it anyway, so maybe the risk is not significant (and worth trying). It's up to your judgment.
redpoint73 said:
You need to flash firmware 6.20.651.3. before the RUU will install. It's a peculiar requirement on US Marshmallow RUUs, that updating by RUU from any lower version (Lollipop, Kitkat) you need to flash firmware first, before RUU, otherwise you will have Error 155.
Firmware and instructions for flashing if can be found here (as well as all Sprint RUUs):
https://forum.xda-developers.com/showthread.php?t=2729173
But if the phone will not stay in hboot (or RUU mode) it may be a problem flashing firmware and/or RUU. May possibly even brick the phone. If flashing firmware or RUU, the process is interrupted when updating hboot partitions, a brick is almost certain. But on the other hand, it looks like you are close to binning it anyway, so maybe the risk is not significant (and worth trying). It's up to your judgment.
Click to expand...
Click to collapse
Thank you for the reply and I may give it a go later when back from work

Please help me just get on the right track with upgrading rom?

I just bought a T-Mobile HTC 10 that has been unlocked through T-Mobile and bootloader unlocked by the last guy that owned it.
This is my first new Android phone since 2013. Since then I've been through a lot, and I've forgotten how quite a bit of this whole modding thing works.
Basically I just want that LeeDroid ROM that everyone seems all excited about. I think it would be really nice on my phone.
I have ADB and the right drivers and everything ready to go on my PC. I understand I need to get the firmware upgraded but that's where I start researching myself into circles.
It seems very unclear to me which firmware I should be using, how to apply it properly, whether I need root or S-ON (are those the same thing?)
Please, I have great intentions, I'm just confusing myself a lot in how to get my phone the way I want it. I really want to LOVE this device but the guides I come across so far are just getting over my head really fast. It is frustrating because this used to come very easily to me.
Can someone just take 5-10 mins out of their day, and very clearly point me in the right direction with maybe a link to a guide that I'd have to be a complete idiot to mess up?
what I've attempted so far
I've looked at the guide for upgrading firmware and discovered I likely need to get my device to S-OFF.
Alright, So i look into that and everyone points to this Sunshine app. Download that. It tries to temproot device and fails.
What next? Do I try to flash superSU in recovery mode? What is the best way to do that? After that, how does one flash a firmware. The "guide" for that just has a bunch of zip files, but not much info on what to do with them.
thebrokn19 said:
I've looked at the guide for upgrading firmware and discovered I likely need to get my device to S-OFF.
Alright, So i look into that and everyone points to this Sunshine app. Download that. It tries to temproot device and fails.
What next? Do I try to flash superSU in recovery mode? What is the best way to do that? After that, how does one flash a firmware. The "guide" for that just has a bunch of zip files, but not much info on what to do with them.
Click to expand...
Click to collapse
If you're still fully stock, just take all the latest OTA updates so you can be on the latest firmware.
Then, install twrp, instructions are on the twrp website.
https://twrp.me/htc/htc10.html
Then, install Leedroid. Instructions are in the Leedroid thread on xda.
You don't need s-off for any of this, only need your bootloader unlocked which you already have.
Tarima said:
If you're still fully stock, just take all the latest OTA updates so you can be on the latest firmware.
Then, install twrp, instructions are on the twrp website.
Then, install Leedroid. Instructions are in the Leedroid thread on xda.
You don't need s-off for any of this, only need your bootloader unlocked which you already have.
Click to expand...
Click to collapse
I appear to be fully stock, but the LeeDroid instructions specifically mention needing to be on the Oreo firmware. I am still on android 7 OS and firmware after performing all OTA updates (there were none available). That was my only hangup. I don't want to break anything. But the more I looked into upgrading my firmware past what was available to me OTA, i started to get very confused about how to go about it.
Which build version do you have on your phone? As far as i know you should be in 2.51.531.32 version. (http://www.htc.com/us/support/htc-10-t-mobile/news/) (you can see version under: All apps > Settings > About and locate the Software version)
If so, then i think you should get S-OFF via sunshine (if i remember correctly) and convert your phone into WWE/US Unlocked version (change CID into super CID, and Flash appropriate RUU). RUU contains firmware and software, so you will have fresh clean system.
It's just my thinking, and i have WWE version from the start, so i have oreo via OTA.
Some info:
Root and S-ON/OFF isn't the same thing.
With root you have access to everywhere in system, and you can give administrative rights to some programs which needs them.
Here's info about S-ON/OFF
https://forum.xda-developers.com/showthread.php?t=1680928
ShadoV90 said:
Which build version do you have on your phone? As far as i know you should be in 2.51.531.32 version. (http://www.htc.com/us/support/htc-10-t-mobile/news/) (you can see version under: All apps > Settings > About and locate the Software version)
If so, then i think you should get S-OFF via sunshine (if i remember correctly) and convert your phone into WWE/US Unlocked version (change CID into super CID, and Flash appropriate RUU). RUU contains firmware and software, so you will have fresh clean system.
It's just my thinking, and i have WWE version from the start, so i have oreo via OTA.
Some info:
Root and S-ON/OFF isn't the same thing.
With root you have access to everywhere in system, and you can give administrative rights to some programs which needs them.
Here's info about S-ON/OFF
Click to expand...
Click to collapse
THANK YOU. You filled in the information gap I still had. I think I've got all that I need to pull this off now. Just gotta pony up $25 through Sunshine to be able to change that CID, eh? I guess there's worse things.
thebrokn19 said:
THANK YOU. You filled in the information gap I still had. I think I've got all that I need to pull this off now. Just gotta pony up $25 through Sunshine to be able to change that CID, eh? I guess there's worse things.
Click to expand...
Click to collapse
Before paying for sunshine boot to download mode and using Fastboot type fastboot getvar all. Post the output here but delete your serial number and imei before posting.
yldlj said:
Before paying for sunshine boot to download mode and using Fastboot type fastboot getvar all. Post the output here but delete your serial number and imei before posting.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxxx
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 2.51.531.32
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: T-MOB010
all:
finished. total time: 0.046s
thebrokn19 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxxx
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 2.51.531.32
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: T-MOB010
all:
finished. total time: 0.046s
Click to expand...
Click to collapse
OK so looks like oreo isn't out yet for T-Mobile then. Like @ShadoV90 suggested the only way would be to S off then Change to US unlocked or WWE. You will most likely lose VOLTE if your on T-Mobile network tho. Or you could wait for them to release Oreo.

Categories

Resources