Related
Hello,
I'm on telus and have rooted and gotten the s-off flag. I'm running Viper Rom currently. In settings, my version shows the build number 2.10.401.1 CL576582 release-keys
Am I correct that the recovery files with version 1.3 will not work? (e.g. 2015-07-27--21-18-11_LRX22G_release-keys.zip) will not work? I would like to go all the way back to stock, complete with the original splash screen without the red text. If this will not work, what would one do?
Apologies for the novice question. Any guidance would be appreciated
So if I understood you correctly you want to return your M9 to full stock.
If so, it would be useful to post the information given to you by performing the "fastboot getvar all" command in bootloader mode, and post it (WITHOUT serial no. and IMEI) to make sure which kind of device you are running and which firmware and ROM is needed to do so.
By your post I could only assume, that it is a WWE device given by your SKU (x.xx.401.x). If so - and given you are S-OFF - you could have used the search and would have found @Flippy498's thread, where he describes how to go back to stock in his google sheet. To do so you could download (assuming your information are correct) the 3.35.401.12 RUU from the afore mentioned thread and follow the instructions in the google sheet. Thus you'd be fully stock again and already updated tithe latest MM ROM.
HTCNerdYoda said:
So if I understood you correctly you want to return your M9 to full stock.
If so, it would be useful to post the information given to you by performing the "fastboot getvar all" command in bootloader mode, and post it (WITHOUT serial no. and IMEI) to make sure which kind of device you are running and which firmware and ROM is needed to do so.
By your post I could only assume, that it is a WWE device given by your SKU (x.xx.401.x). If so - and given you are S-OFF - you could have used the search and would have found @Flippy498's thread, where he describes how to go back to stock in his google sheet. To do so you could download (assuming your information are correct) the 3.35.401.12 RUU from the afore mentioned thread and follow the instructions in the google sheet. Thus you'd be fully stock again and already updated tithe latest MM ROM.
Click to expand...
Click to collapse
Thanks for the post. I had tried a whole bunch of things, including the post you mentioned. But no luck. I suspect now it was because my sku was originally . 661. And when I installed viper rom, I perhaps didn't change the cid to super and used a. 401 sku version. Not sure if this would be a cause, but I was getting system freezes all the time. Anyway, that was months ago, and I clearly messed it up somewhere. Now time for a cleanup.
Thanks again.
CrazyRom said:
Thanks for the post. I had tried a whole bunch of things, including the post you mentioned. But no luck. I suspect now it was because my sku was originally . 661. And when I installed viper rom, I perhaps didn't change the cid to super and used a. 401 sku version. Not sure if this would be a cause, but I was getting system freezes all the time. Anyway, that was months ago, and I clearly messed it up somewhere. Now time for a cleanup.
Thanks again.
Click to expand...
Click to collapse
Hey again, so I went and grabbed the ruu for htc wwe... Went to download mode and started flashing. Unfortunately it stopped working and threw up error 10, saying the model Id is incorrect.
My mid is 0PJA11000... Is necessary to change it in the ruu? Thanks.
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 1.32.661.31
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440221_62.05.50320G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: 11111111
CrazyRom said:
Hey again, so I went and grabbed the ruu for htc wwe... Went to download mode and started flashing. Unfortunately it stopped working and threw up error 10, saying the model Id is incorrect.
My mid is 0PJA11000... Is necessary to change it in the ruu? Thanks.
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 1.32.661.31
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440221_62.05.50320G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: 11111111
Click to expand...
Click to collapse
Ok I see you got a TELUS001 device. Thus you'd need to change the CID back to "TELUS001" an could revert back to stock using this TWRP Backup.
After this you need the stock recovery, but I'm still searching for it.
Send by the swarm intelligence of my coffee machine ?.
HTCNerdYoda said:
Ok I see you got a TELUS001 device. Thus you'd need to change the CID back to "TELUS001" an could revert back to stock using this TWRP Backup.
After this you need the stock recovery, but I'm still searching for it.
Send by the swarm intelligence of my coffee machine ?.
Click to expand...
Click to collapse
Thanks HTCNerdYoda!! I'll give that a try!
I had been working under the logic that having a supercid set negates the need for a backup with the carrier cid. Maybe this is why I was having issues. Thanks again!
Hello and good evening,
before I start I have to say that I'm actually not a HTC user myself but today I was given a HTC One M8 which should have been resetted and updated to the latest android version. As a Nexus user it shouldn't be that hard but I have some issues, esp. with latest firmware I need some help/advice. I'm pretty sure that 90% of my questions have been answered already but I didn't want to bump old threads from 2014/2015.
Apparently the phone has an o2_uk branding. I was looking on HTC's site but I couldn't find any matching firmware or even info where to download such a file, at least not on HTC UK. HTC US publishes their firmware on their support site for each carrier. The phone still has warranty for a couple of months so unlocking bootloader or s-off are no option as of now. Where does the average joe find all those stock firmware for HTC devices? I'm not even sure if there is new firmware for this kind of branding available. I've have seen plenty of OTAs and RUUs posted on here but you either need to be S-Off or a globel unlocked device.
In case I need to unlock bootloader and go with a custom ROM - is it possible to flash certain radios, basebands from unlocked devices etc.? I've seen that some ROMs require that you update your firmware to the latest version to avoid weird behaviour. But when there is no latest firmeare available what do you do?
Device info: M8
Build number: 4.20.206.2 CL463267 release-keys
Android: 5.0.1
I'm more than thankful for any idea, tip etc. and appreciate your time helping me out.
maultasche said:
Device info: M8
Build number: 4.20.206.2 CL463267 release-keys
Android: 5.0.1
Click to expand...
Click to collapse
Don't really understand what your problem is. There is an update and the latest is 6.13.206.5
Have you tried checking software update in settings - about - software update ?
More than once. It only says there is no update available for your phone. Software information says it's on Android 5.0.1.. I installed Sys-I from Play Store which states that the phone apparently has a branding.
O2 is a branding device but it shouldn't stop the OTA even when you are not on their network. I used to have one too as you can see all the files that I have in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I don't know why it says no update when there is one.
As the device is still on warranty, I don't want to advise anything further related to unlocking bootloader.
Have you tried factory reset the device then check the update ?
If it is already bootloader unlocked .. then you can manually update the firmware to the latest.
I did two factory resets. After the second one it only updated some HTC apps. Android version was still 5.0.1.
If I unlock the bootloader would it be possible to manually update? Or even use one of the twrp backups from your thread?
maultasche said:
I did two factory resets. After the second one it only updated some HTC apps. Android version was still 5.0.1.
If I unlock the bootloader would it be possible to manually update? Or even use one of the twrp backups from your thread?
Click to expand...
Click to collapse
If the bootloader is unlocked, you can restore non-rooted 6.13.206.5 stock backup with the latest TWRP 3.0.2-0
then you need to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
then fastboot flash the fw_6.13.206.5.zip (that you can download from post #5)
fastboot oem rebootRUU
fastboot flash zip fw_6.13.206.5.zip
you'll get ERROR
repeat - fastboot flash zip fw_6.13.206.5.zip
done ... but your warranty most probably will be void.
BUT .. can you post fastboot getvar all result without serial and imei no. first.
I need to see the details of your device to make sure these instructions are correct for your device variant.
Wow, thank you for that tip. So S-Off and changing CID is not needed for this operation? Because that was always confusing me. As stated I'm not an expert with HTC and it's the first time someone asked me for help with that device.. Apparently the device has just four months left of warranty. So I guess it should be fine unlocking it.
maultasche said:
....So S-Off and changing CID is not needed for this operation?
Click to expand...
Click to collapse
S-Off is needed when you want to change the device variant from O2 to EU for example (where you need to change CID) but most of the time normal user doesn't need S-Off.
Once it is unlocked, and the firmware is updated ... a user can install any Custom ROM that he like .. not necessarily be on stock O2. If he prefer stock .. he can restore a stock EU ROM ..so no O2 bloatware.
I guess it is alright to unlock bootloader now ... there is no further OTA from HTC, HTC stop support for M8 after two years which already ended end of April.
Thank you so mich for your help. I appreciate it. Now I completely understand what I have to do now. Have a nice day!
@ckpv5
Hey there,
I wanna say thank you once again for your instructions the other day. I haven't spent much time invastigating. You asked me for getvar all so I wanna share the output I got for that device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.0
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: d9e7383b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
There has been provided another update after a factory reset, firmware is still on Lollipop. I got the OK to unlock bootloader and flash TWRP. I assume your steps just work fine. Haven't flashed any TWRP backup as of yet.
maultasche said:
There has been provided another update after a factory reset, firmware is still on Lollipop. I got the OK to unlock bootloader and flash TWRP. I assume your steps just work fine. Haven't flashed any TWRP backup as of yet.
Click to expand...
Click to collapse
The getvar result show that the device was previously bootloader unlocked and the outdated TWRP 2.7.x.x (that's explain the missing version-main detail).
Just follow the steps .. should work. It seems many variants currently when check for OTA, none available. Not sure what actually is going on with HTC server.
Could probably be. The phone was bought "second hand" with warranty left. The original owner said everything is stock. Looks like it wasn't.
To make things short: I did follow your instructions. Flashed the correct twrp backup, flashed the firmware from your linked thread and everything was fine. OS, baseband etc. all got updated to latest version available.
Thank you again for your help.
My HTC One M8 got stuck on bootload shortly after I asked O2 to unlock it. The bootload said ***software status: modified***
After a lot of research, I came accross a tutorial to fix a soft bricked device via TWRP and managed to flash a new ROM on it. I choose Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9)/ stock HTC system dump that I found on android-revolution HD website and everything went very smoothly.
So my M8 is now starting and working fine, BUT doesn't read sim cards. It doesn't tell me whether a sim card is inserted, and if I put my Vodafone Malta sim card in, nothing happens, no error of reading, nothing. (if was working fine after the unlock code was put in).
I also noticed that HTC SDK API level now says unknown. And under mobile data>Network mode where I don't see 4G anymore.
I've received OTA update but can't install them. I get the "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at www . htc . com".
I thought that maybe installing a new ROM would be the solution and tried various RUU to no avail (159 error). I also tried using fastboot to flash 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
But it failed with 42 Wrong Customer ID (wrong CID).
I tried to amend android-info.txt but 1/windows won't open the zip (I am on Windows 7) - 2/ 7zip will but won't let me copy or edit the file (unsupported compression method error).
I am very much a newbie and I am not very keen on going S-Off as yet and would like to have opinions on what my next move could be, staying S-On.
My main concern isn't the updates but the non reading of my sim card. That's the main thing I'd like to resolve (and I thought that flashing a new ROM could be the solution - correct me if I am wrong!)
here is a reading of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(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: O2___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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance for any advice!
Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?
ckpv5 said:
Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?
Click to expand...
Click to collapse
Hi ckpv5,
Thanks for your advice, really appreciate it.
Definitely sure about the phone being SIM unlocked as the Vodafone Malta SIM card worked for a while until everything went pear shaped and the phone stopped booting.
I'll try both and will let you know how it went.
ckpv5 said:
Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?
Click to expand...
Click to collapse
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?
No imei no baseband
JenovaXIII said:
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?
Click to expand...
Click to collapse
I have got the same problem. On my One M8 it reads unknown imei unknown baseband. But when I type "fastboot getvar all" everything seems OK. This might be due to corrupted EFS or other partitions I think. I've found an article written by mike1986. (Android Revolution HD developer) about how to fix a corrupted DATA partition on the HTC One[/URL] but couldn't still find chance to restore/recreate/fix partitions. I send the device to a private service in Istanbul and they called me and told me that my phone requires a new motherboard. The device is running well but it can't detect the simcards. Actually it was, but in Turkey our network operators managed to give 4.5G service or (LTE?) and when I changed my simcard to 4.5G simcard itwas unable to detect it. I thought it was due to radio/cid/mid problem and I changed them all. Afterwards It couldn't detect any simcards. No imei no baseband.
Anybody willing to help these poor are appriciated. Thanks.
JenovaXIII said:
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?
Click to expand...
Click to collapse
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.
ckpv5 said:
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.
Click to expand...
Click to collapse
I am going through your tutorial on how to restore nandroid backup and am a bit confused:
once restored, I need to proceed to steps 11 - 12 - 13 (flash the recovery img) ?
Then relock bootloader, then flash 6.13.206.5 signed firmware.zip using adb and fastboot ?
Sorry I just want to make sure I'm not doing something stupid!
ckpv5 said:
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.
Click to expand...
Click to collapse
And it did! After following your tutorial, I re-locked the bootloader, and flashed the signed firmware.zip.
My M8 is now recognising sim cards and my vodafone Malta one is read no problem. So glad to have my phone back.
Thank you ckpv5!
So, I had a marshmallow update on my phone, and later i converted into GPE, but didn't like it. Went back to Sense, but it just doesn't feel as good as before. One day, the battery died, and when i tried turning it on, it would give me all sorts of errors. This never happened while i was on marshmallow before conversion to GPE. Had to reset it from the recovery. I think it hasn't returned to Sense properly.
As i am S-Off, i was thinking of flashing it with a RUU which is compatible with my device. Please suggest me which is compatible.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21450002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.708.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------------------
(bootloader) imei: --------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
Based on your MID, looks like you're on a GSM M8? I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
I have read here that flashing carrier RUU can brick the device radio for good. So, this is why I wanted to confirm.
cytherian said:
I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
Click to expand...
Click to collapse
HTC does not post the RUU for his version on HTC Dev.com (many versions are not posted there)
OP's version doesn't have a carrier forum sub-section.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
xexux said:
(bootloader) version-main: 6.16.708.1
Click to expand...
Click to collapse
I don't know if there is an RUU for this version number.
One alternative, is to restore the TWRP backup 6.16.708.1 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 09:42 AM ---------- Previous post was at 09:38 AM ----------
xexux said:
Went back to Sense, but it just doesn't feel as good as before.
I think it hasn't returned to Sense properly.
Click to expand...
Click to collapse
How exactly did you go back to Sense?
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
xexux said:
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Good to hear that it worked out and thanks for posting. :good:
cytherian said:
Good to hear that it worked out and thanks for posting. :good:
Click to expand...
Click to collapse
This is how I got Sense back, and after that, I started experiencing bugs with M8 as explained in my first post.
xexux said:
So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
redpoint73 said:
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
Click to expand...
Click to collapse
I restored it with the latest TWRP backup for my model. About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
xexux said:
I restored it with the latest TWRP backup for my model.
Click to expand...
Click to collapse
What version number exactly? Perhaps you still have the files on your computer, and can look?
I've seen a number of times, folks say and think they restored the right version for their model, and once we ask for version numbers, we see they actually got it wrong.
xexux said:
About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Click to expand...
Click to collapse
I can see it too. But doyou actually remember manually download and flash the firmware in RUU mode?
Did you convert to GPE using the RUU?
xexux said:
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
Click to expand...
Click to collapse
It's possible. But flashing another region's RUU will also change the radio baseband, and therefore changes the specific bands supported. It may have undesirable results (not support the 3G or LTE band or bands used by your local carrier).
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Bukss said:
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Click to expand...
Click to collapse
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
c:\miniadb_m7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 99000499834418
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: RUU
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
Abnova said:
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B12000
Click to expand...
Click to collapse
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
redpoint73 said:
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
Click to expand...
Click to collapse
Yeah I realised how big of a mess I was in when I got it back. Anyway
1.)On further investigation it seems like the the phone is in a wierd RUU mode. So it still can interface with the laptop through fastboot. Like I said earlier, trying to reboot to bootloader brings you to the same black screen with the silver Logo (see attached). When the phone is plugged in to the laptop or switches to the HTC silver Logo screen however when it's unplugged, it goes to a wierd bootloader like screen but black and only has the option for RUU. ( See attached)
2.) I took it to them to replace the battery because . The phone would switch off even at 100% battery. It only worked when it stayed plugged in , like a PC. I'm guessing the repair guys saw I had modified the software (I was running Dirty Unicorns, Android 7.1.2, Latest TWRP with a relocked Bootloader, S-Off) and had thought the problem actually had to do with the software. I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Anyway I hope this information helps. Thanks for your help.
Abnova said:
I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Click to expand...
Click to collapse
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Abnova said:
1.)On further investigation it seems like the the phone is in a wierd RUU mode.
Click to expand...
Click to collapse
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Thanks for your contribution, will definitely try tomorrow
redpoint73 said:
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Click to expand...
Click to collapse
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Abnova said:
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Click to expand...
Click to collapse
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
redpoint73 said:
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
Click to expand...
Click to collapse
I tried that, it would flash then refuse to reboot to the recovery. I've tried so many things but none of them worked. My only hope is if someone edited the Android.txt file inside the Rom Zip so that the model ID is the same as that of my corrupt phone. That way it'll flash and hopefully fix it. I've tried myself but everytime I tried to edit it says the zip/archive is corrupt on WinRAR. I don't know whether it's a problem with my laptop or if it's a complication related to the rom.zip. I've downloaded it again but it still does the same thing. So basically I'm stuck because there is no way I can change the MID. This probably means the phone is bricked.
Hi there, I bought a htc m9 from ebay uk for use in Ireland.
It seems to work fine no problem. But it is on marshmallow and would like to update it.
OTA system update doesn't work.
I read through the m9 readme here and fastboot getvar gives
D:\Delete\m9\android>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himawl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) version-main: 3.37.605.7
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA30000
(bootloader) cid: 11111111
Which to my disappintment, seems to indicate it's a Verizon cdma version (how does it do gsm,4g,lte then ??)
However I am not sure if any of that fastboot info might have been modified (or even if it's possible) in the past sometime. Eg. the cid seems to be incorrect.
The sticker on the back of the phone and on the white box says p/n 99HVJ002-00. Does that match or is consistent with the fastboot info ?
The phone is unlocked and its S-OFF which I can see when boot into download mode.
Also, the phone settings, Boomsound is missing from the options. Has something called 'JBL LiveStage'. Which doesn't seem to do anything and is hardly mentioned anywhere in relation to this device.
So in an effort to restore Boomsound would like to go to a stock firmware.
So how can I confirm 100% this is a Verizon cdma phone ? I don't want to stupidly flash gsm firmware on it or something.
If could restore Boomsound in some other way I 'd probably leave it alone. Factory reset didn't have any effect on it.
thanks,
It's a verizon phone with an audio mod flashed to it.
Now, the problem you have is verizon is cdma and your Irish networks are gsm. Even though the phone can take sim cards there's a chance it won't work on the networks, but it will be a working phone, just only on cdma networks.
You need to change the cid from Supercid 11111111 (no longer valid) to the cid for verizon. Use fastboot on a pc and download mode on the phone.
Then download and flash the stock verizon firmware 3.37.605.x (x can be any number but the rest MUST MATCH EXACTLY). Use the zip version of the ruu and flash from the external sd and rename it to 0PJAIMG.ZIP.
Boot to download mode and you should be prompted to press vol up to flash.. If no prompt then check filename as it could be different. It will tell you in download mode what file it is looking for!.
DO NOT S-ON. DO NOT LOCK/RELOCK THE BOOTLOADER. It is not necessary.
Once flashed the phone is stock. You can then accept the ota updates over WiFi.
Thanks, that worked good. Boomsound is back and sounds really good.
I flashed with the 3.37.605.7 Ruu in download mode which I found here:
https://forum.xda-developers.com/ve...t-unlock-s-verizon-m9-mm-3-37-605-13-t3457717
I didn't change the Supercid 11111111 though. Do I really need to change that back to the default ? If so do you know what's the correct CID for this particular Verizon m9 ?
Also, not too bothered but OTA System Update still doesn't work. Just keeps saying try again when connected to the Verizon 4G Lte Network.
This thread seems to have all the nougat information:
https://forum.xda-developers.com/ve...t/6-0-verizon-htc-one-m9-marshmallow-t3316279
But it's not clear what firmware you need to be up to in order to flash, say, 4.49.605.16_NoBoot-NoRecovery_firmware.zip
thanks a lot
Even if you were connected to the Verizon network you wouldn't be able to receive OTAs. Since the M9 the SuperCID (11111111) prevents HTC's servers from sending the files to your phone.
The correct CID is listed in the RUU section of the ReadMe thread.
Sent from my HTC One M9 using XDA Labs