Related
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.
Hello XDA-Community,
I have an HTC One M8 (M8_UL) with the following details:
Software Status: Modified
*** UNLOCKED ***
And I have Cyanogenmod installed (latest nightly build 12.1-20151118-NIGHTLY-m8 Android 5.1.1) and TWRP 2.8.7.0
Now my GPS is not working since a while now (I can't really tell if it has even started when I moved to CM or if it happened afterwards).But GPS Status never gives me a single satellite. I have read in another topic here in the board, that getting back to Sense Stock could help. Then back to CM and everything could be fine.
But here my questions start:
1) What exactly does this S-ON mean?
2) So how do I know which firmware/recovery/system (I figured out that there is some difference between all this and that now my TWRP 2.8.7.0 obviously is my Recovery Tool installed at the moment.
3) What is RUU and OTA ? As I understood its like a Operating System Update out of windows? I once downloaded a version but it always claims my battery would not be full so it would not let me update/upgrade/recover?
4) Why is my version-main info empty? (see below)
Sorry for all these questions and thanks in advance for your help
C:\Users\fsc>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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!
finished. total time: 0.053s
Click to expand...
Click to collapse
My answers below in blue font.
damarges said:
1) What exactly does this S-ON mean?
S-on/s-off is a HTC specific security flag. S-off means "security off" and in the past meant that all security checks are bypassed. On the M8, its a little more complicated than that, some things are bypassed, some are not. But it allows you to do things like flashing modified hboots, radios, unsigned RUUs and downgrade firmware. S-off is kind of a "back door" that HTC leaves for itself. But when exploited by users, such as the devs here at XDA, is handy for some pretty useful things. S-on is the "stock" condition, and means you don't have the ability to do these things. In order to get s-off, you need to use the sunshine method, which costs $25. But s-off is not required to flash ROMs, root, or return to stock.
2) So how do I know which firmware/recovery/system (I figured out that there is some difference between all this and that now my TWRP 2.8.7.0 obviously is my Recovery Tool installed at the moment.
Firmware number is indicated by main version in getvar output, or by the "OS" number on the bootloader screen.
If you want to go back to stock recovery, you will want the stock recovery file that matches your firmware number. But for what you describe, I don't think you need or want to flash stock recovery.
System is the ROM version number, and again if you are returning to stock, you should find the nandroid that has the same number as your firmware.
Don't confuse any of the above with the software number in the phone's settings (common mistake). That number is related to the current ROM. So if you flash a custom ROM, that number just corresponds to the custom ROM, not the firmware or stock ROM number.
3) What is RUU and OTA ? As I understood its like a Operating System Update out of windows? I once downloaded a version but it always claims my battery would not be full so it would not let me update/upgrade/recover?
RUU and OTA are related, but two very different things:
RUU = ROM update utility. Its a Windows executable, normally an official HTC tool that will completely re-image your phone to stock, every single partition, and will also wipe your phone. The CID and MID of your phone need to match what the RUU is intended for. Does not require stock ROM or stock recovery to run, but has to be same or greater version number than main version (or hboot) on the phone - meaning you can't "downgrade" (unless you have s-off). Relocking the bootloader is required to RUU (again, unless you have s-off).
OTA = over the air. Its an incremental OS update, sent out by HTC. It normally requires the software number directly proceeding it, meaning you need to install them in sequence, and can't skip any. And may not be a complete image, but simply a "patch". It also requires stock recovery to be present, as well as the stock ROM. No need to relock bootloader to OTA (unlike RUU). Also, OTA will not typically wipe the phone (but you should backup before OTA to be safe, as it does sometimes wipe data).
4) Why is my version-main info empty?
Common issue. This is usually because an outdated 2.7 version of TWRP was installed at some point, wiping out the main version info (known TWRP bug).
On the bootloader screen, does it read a number after "OS" in green letter?
Click to expand...
Click to collapse
Thanks a lot for these detailed descriptions. Makes it more clear to me.
Firmware number is indicated by main version in getvar output, or by the "OS" number on the bootloader screen.
Click to expand...
Click to collapse
>> as it is empty on my getvar output I don't know which firmware/recovery to choose?
On the bootloader screen, does it read a number after "OS" in green letter?
Click to expand...
Click to collapse
>> no. its just empty "OS- " thats it.
But for what you describe, I don't think you need or want to flash stock recovery.
Click to expand...
Click to collapse
>> no actually I don't want stock recovery. I am happy with TWRP. I actually just want to have my GPS issues fixed. else I am really happy with Cyanogenmod.
>> do you have knowledge on how to fix the GPS issue? or if returning to Sense ROM could fix it maybe?
So if I don't know my firmware/OS - number? how do I choose a proper nandroid backup? and does a nandroid backup does return my phone to sense ROM?
damarges said:
I am really happy with Cyanogenmod.
>> do you have knowledge on how to fix the GPS issue? or if returning to Sense ROM could fix it maybe?
Click to expand...
Click to collapse
I'm not a CM user on this device, so I'm not too familiar with the issue.
damarges said:
So if I don't know my firmware/OS - number? how do I choose a proper nandroid backup? and does a nandroid backup does return my phone to sense ROM?
Click to expand...
Click to collapse
I believe your firmware is 4.16.401.x (possibly "8" where the "x" is), based on your CID, and hboot and radio numbers indicating you are on Lollipop firmware.
Are you sure its a nandroid that is being discussed in the "fix" and not RUU to stock? If you direct me to the thread/post that discusses the fix, maybe I can take a look and see if I can figure anything out.
But yes, a stock nandroid for 4.16.401 will return you to the Sense ROM.
redpoint73 said:
Are you sure its a nandroid that is being discussed in the "fix" and not RUU to stock? If you direct me to the thread/post that discusses the fix, maybe I can take a look and see if I can figure anything out.
Click to expand...
Click to collapse
The links I used to gather information:
https://www.reddit.com/r/cyanogenmod/comments/3gw7fm/htc_one_m8_cm121_the_gps_doesnt_work/
On http://forum.xda-developers.com/showthread.php?t=2701376 I can not find a nandroid stock backup that is working. The link to 4.16.401.10 - TWRP Thanks to sneakyghost is not working anymore on mega :/
How do I create a nandroid backup myself (after hopefully I get fixed everything)?
I could replace my Cyanogenmod with a stock nandroid backup of htc sense. but it did not fix the GPS problem. Still not a single satellite to receive :/
Even erase modemst1 and erase modemst2 did not fix anything :/
Anyone has a hint what to do?
Hello everyone!
I want to install ARHD 45.0 but after installation Wifi dosent work.
I think i have wrong firmware, but when i want to change it i have Error code 99.
My bootloader have S-On and i can't change it to S-OFF, is there any step by step instruction to change it?
Piszu said:
Hello everyone!
I want to install ARHD 45.0 but after installation Wifi dosent work.
I think i have wrong firmware, but when i want to change it i have Error code 99.
My bootloader have S-On and i can't change it to S-OFF, is there any step by step instruction to change it?
Click to expand...
Click to collapse
You need to use sunshine ($25 US) to get s-off: http://theroot.ninja/
Although, you may still be able to flash the firmware if its signed and matches your CID. Where did you get the firmware from, and what is your device's CID?
Alternately with s-on, you can return to stock ROM (for your CID and present firmware number), and corresponding stock recovery. Then OTA to update the firmware: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
redpoint73 said:
You need to use sunshine ($25 US) to get s-off: http://theroot.ninja/
Although, you may still be able to flash the firmware if its signed and matches your CID. Where did you get the firmware from, and what is your device's CID?
Alternately with s-on, you can return to stock ROM (for your CID and present firmware number), and corresponding stock recovery. Then OTA to update the firmware: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Hi,
Thanks for advice, but I think i stock.
If I ried to install some newest ROM I have problem with my Wifi - it dosen't works..
Bootloader configuration:
M8_UL PVT SHIP S-ON
HBOOT: 3.19.0.0000
RADIO: 1.22.21331147A1.29G
CID: HTC__032
OS: 3.28.401.9
I tried to do everything like this thead:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I tried to:
CID HTC__001, HTC__J15, HTC__E11, HTC__203, HTC__102, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__032, HTC__016, HTC__M27, HTC__K18, HTC__002, HTC__A48
MID 0P6B10000
3.28.401.6 - does't exists
3.28.401.9 - does't exists
4.16.401.10 - not this one
4.16.401.13 - this one
and
4.16.401.13_recovery
Every time I hae this:
I:\Flash_recovery_3.28.401.7\fastboot\adb>fastboot flash zip hb.zip
target reported max download size of 1826418688 bytes
sending 'zip' (495 KB)...
OKAY [ 0.220s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.521s
I:\Flash_recovery_3.28.401.7\fastboot\adb>fastboot flash zip 4.16.401.10.zip
target reported max download size of 1825906688 bytes
sending 'zip' (52100 KB)...
OKAY [ 2.693s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.995s
Now when i go to recovery and try "apply from sd card" I have error:
"find no match partition for package path sdcard/ptt.zip.."
When I go back to TWRP I can install ROM and its work.
Last running configuration is ARDH v. 11.
Anyone help?
Piszu said:
Hi,
Bootloader configuration:
M8_UL PVT SHIP S-ON
HBOOT: 3.19.0.0000
RADIO: 1.22.21331147A1.29G
CID: HTC__032
OS: 3.28.401.9
3.28.401.6 - does't exists
3.28.401.9 - does't exists
4.16.401.10 - not this one
4.16.401.13 - this one
and
4.16.401.13_recovery
Click to expand...
Click to collapse
Since OS version 3.28.401.9 is listed on your bootloader screen (this is your current firmware version number), you want to restore the same stock nandroid and recovery in order to OTA and update your firmware. You can't just pick any one, it has to be 3.28.401.9
The author of that thread (ckpv5) is pretty responsive about re-uploading dead links. Ask him nicely in that thread to re-upload 3.28.401.9, and I bet he will do so.
Piszu said:
I tried to do everything like this thead:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Every time I hae this:
I:\Flash_recovery_3.28.401.7\fastboot\adb>fastboot flash zip 4.16.401.10.zip
Click to expand...
Click to collapse
Dude, what the heck are you trying to do???
Those are not firmware zips, and you can not flash them that way!!!
The files from those threads are stock nandroids and stock recovery, completely different from firmware. If you don't know the difference, you need to read and learn before doing anything more.
Restoring stock nandroid and stock recovery in order to OTA (and update firmware) is a completely different approach than flashing a firmware.zip. A completely valid one, yes. But if you are trying to restore 3.28.401.9 nandroid, as I mentioned above, you need to follow the instructions in the first post of that thread. Why do you think those instructions are there???
Hey,
I have ARHD 43.0 on my HTC M8 and now want to update to ARHD 45.0.
Theoretically I could just flash ARHD 45.0 zip in TWRP and restart?
But now I want to know if there are certain advantages if I upgrade other things. (If there are upgrades).
For example I have TWRP 2.8.1.0. Is there an advantage for TWRP 2.8.7.0?
Or in my bootloader, the following Information stands:
"M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.22.21331147A1.29G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.401.9"
Is there a new kernel/firmware I can upgrade and if yes, does it has advantages?
Greetings
Tim0theus said:
I have ARHD 43.0 on my HTC M8 and now want to update to ARHD 45.0.
Theoretically I could just flash ARHD 45.0 zip in TWRP and restart?
But now I want to know if there are certain advantages if I upgrade other things. (If there are upgrades).
For example I have TWRP 2.8.1.0. Is there an advantage for TWRP 2.8.7.0?
Or in my bootloader, the following Information stands:
"M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.22.21331147A1.29G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.401.9"
Is there a new kernel/firmware I can upgrade and if yes, does it has advantages?
Click to expand...
Click to collapse
The info you posted indicated your firmware is old (KitKat). So you need to update to Lollipop firmware by one of the methods I've described above in order to run LP based Sense ROMs. Otherwise you will encounter severe bugs like extreme long boot times (or not boot) and broken WiFi.
redpoint73 said:
The info you posted indicated your firmware is old (KitKat). So you need to update to Lollipop firmware by one of the methods I've described above in order to run LP based Sense ROMs. Otherwise you will encounter severe bugs like extreme long boot times (or not boot) and broken WiFi.
Click to expand...
Click to collapse
Omg ok. Thank you. After the update my WiFi seems to work normal again. ^^
Hi there,
I need to upgrade the bootloader in order to upgrade my Cyanogenmod.
But the problem is, that I lost S-OFF, I don't know when it happened...
Sunshine doesn't, work, it requires stock ROM.
The other thing is, that I can't flash stock ROM for the same reason!
How do I fix this issue? ._.
Thank you!
BloodySword said:
Hi there,
I need to upgrade the bootloader in order to upgrade my Cyanogenmod.
But the problem is, that I lost S-OFF, I don't know when it happened...
Sunshine doesn't, work, it requires stock ROM.
The other thing is, that I can't flash stock ROM for the same reason!
How do I fix this issue? ._.
Thank you!
Click to expand...
Click to collapse
You don't need S-OFF to flash a stock ROM. Flash the latest FW, run the RUU. You only need to relock the BL before running the RUU. If you have used Sunshine in the past (purchased it for your device) it should recognize that and you should be able to use it again on the same device without purchasing it again.
1) LOCK BL (not s-on, just relock) Steps are in the FW thread.
2) Flash FW zip (again, steps in FW thread)
2) Run RUU (steps in the RUU thread)
3) Reboot into ROM, install Sunshine, use it.
4) install whatever you want.
Thanks for trying to help me but I can't even flash the latest HTC firmware because my bootloader is too old (3.18, expected is 3.19)...
I didn't use SunShine back then, I used the HTC Developer Unlock...
Looks really bad for this device. It was replaced with an OPO3 anyway but I would like to give it to a poor friend for free. Without the doze bug!
Good Night from Germany
dopy25 said:
You don't need S-OFF to flash a stock ROM. Flash the latest FW, run the RUU. You only need to relock the BL before running the RUU. If you have used Sunshine in the past (purchased it for your device) it should recognize that and you should be able to use it again on the same device without purchasing it again.
1) LOCK BL (not s-on, just relock) Steps are in the FW thread.
2) Flash FW zip (again, steps in FW thread)
2) Run RUU (steps in the RUU thread)
3) Reboot into ROM, install Sunshine, use it.
4) install whatever you want.
Click to expand...
Click to collapse
Wait! Does flashing the HTC firmware also flashes the bootloader?
If yes, that could be a way out of this problem!
I will try it later.
Thanks!
Edit:
NOTHING WORKS!!
I flashed SuperSU 2000 times and I get no S-OFF!
WHY?? I just want to upgrade the freaking HBOOT so that I can flash the new CWM13!!!
Why do they even require a new bootloader version. The 3.18 was fine until now. Why did they abandon it????
I am realy mad!
Edit2:
fastboot oem lock failed, too! Unknown error... So, nothing works on this device!
I was in the same boat as you, and finally managed to get the boot loader updated and CM13 installed. All while S-ON.
I can't post links yet, but look up thread ID 2701376 on XDA. It has everything you need.
You only need to get to where you can get the OTA updates. So, you'll need a nandroid, and the stock recovery. I didn't even need to re-lock the boot loader. Good luck.
reckless76 said:
I was in the same boat as you, and finally managed to get the boot loader updated and CM13 installed. All while S-ON.
I can't post links yet, but look up thread ID 2701376 on XDA. It has everything you need.
You only need to get to where you can get the OTA updates. So, you'll need a nandroid, and the stock recovery. I didn't even need to re-lock the boot loader. Good luck.
Click to expand...
Click to collapse
Hey. Ugh, I will give it a try this weekend. Wish me luck. Thanks!
This device is meant as a gift to a friend who cannot afford any usable phone...
But I don't wanna give it away with the doze bug. I hope it is fixed in the latest CM13 builts.
BloodySword said:
Thanks for trying to help me but I can't even flash the latest HTC firmware because my bootloader is too old (3.18, expected is 3.19)...
I didn't use SunShine back then, I used the HTC Developer Unlock...
Looks really bad for this device. It was replaced with an OPO3 anyway but I would like to give it to a poor friend for free. Without the doze bug!
Click to expand...
Click to collapse
There's nothing wrong with the device, its likely perfectly fine to be updated, if done properly. The main issue is pilot error; as it appears you have a poor understanding of the processes and terms.
There is no limitation that prohibits updating firmware, if your hboot is older (3.18). Its more likely you are simply trying to flash the wrong firmware (not correct CID, MID).
HTCDev.com bootloader unlock is not the same thing as s-off. If you didn't use Sunshine to s-off (or Firewater when it worked, but that was before Dec 2014), then you never had s-off. But as described, you don't need s-off to flash custom ROMs (all you need in an unlocked bootloader) and you don't need s-off to flash the proper signed firmware.
Need more info on the device to properly advise. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what firmware are you trying to flash (exact file name)?
---------- Post added at 10:53 AM ---------- Previous post was at 10:01 AM ----------
BloodySword said:
Wait! Does flashing the HTC firmware also flashes the bootloader?
If yes, that could be a way out of this problem!
Click to expand...
Click to collapse
Yes, firmware contains hboot, along with a number of other partitions you need to update (since they are outdated) like radio, media, WiFi, Bluetooth etc.
That is the whole point of the suggestion of flashing the firmware.
BloodySword said:
NOTHING WORKS!!
I flashed SuperSU 2000 times and I get no S-OFF!
Click to expand...
Click to collapse
Not sure what you are saying here. SuperSU in itself just give you root, not s-off.
Or do you mean, that rooting the current ROM doesn't allow Sunshine to s-off the device? If so, its not what you typed, and that makes it confusing. Also, if you are still talking about CM, its already rooted, and you don't need to root it with SuperSU (and doing so often creates more problems).
Also, Sense ROMs (preferabley stock, or stockish - only certain custom ROM Sense ROMs will work) are best for Sunshine compatibility (and rooted).
BloodySword said:
WHY?? I just want to upgrade the freaking HBOOT so that I can flash the new CWM13!!!
Why do they even require a new bootloader version. The 3.18 was fine until now. Why did they abandon it????
Click to expand...
Click to collapse
Why? Because outdated hboots are known to cause issues on newer ROMs. In addition, older firmware (not just hboot) may cause issues on newer ROMs as well. So its highly advised to keep all firmware updated, not just hboot.
redpoint73 said:
There's nothing wrong with the device, its likely perfectly fine to be updated, if done properly. The main issue is pilot error; as it appears you have a poor understanding of the processes and terms.
Click to expand...
Click to collapse
I must admit, I thought SuperSU and root makes me able to also unlock the special areas on the eMMC like HBOOT, RADIO etc.
There is no limitation that prohibits updating firmware, if your hboot is older (3.18). Its more likely you are simply trying to flash the wrong firmware (not correct CID, MID).
HTCDev.com bootloader unlock is not the same thing as s-off.
Click to expand...
Click to collapse
Aha! That explains it!
If you didn't use Sunshine to s-off (or Firewater when it worked, but that was before Dec 2014), then you never had s-off. But as described, you don't need s-off to flash custom ROMs (all you need in an unlocked bootloader) and you don't need s-off to flash the proper signed firmware.
Click to expand...
Click to collapse
Is there a way to S-OFF it with the current state of the device? Variables further below. I would rather like to have S-OFF, so I can flash HBOOT, RADIO, etc manually anytime I need it.
Need more info on the device to properly advise. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what firmware are you trying to flash (exact file name)?
Click to expand...
Click to collapse
This is what I want to flash in the end:
http://download.cyanogenmod.org/get/jenkins/174461/cm-13.0-20160815-NIGHTLY-m8.zip
The HTC firmware is deleted from my HDD.
Yes, firmware contains hboot, along with a number of other partitions you need to update (since they are outdated) like radio, media, WiFi, Bluetooth etc.
That is the whole point of the suggestion of flashing the firmware.
Not sure what you are saying here. SuperSU in itself just give you root, not s-off.
Or do you mean, that rooting the current ROM doesn't allow Sunshine to s-off the device? If so, its not what you typed, and that makes it confusing. Also, if you are still talking about CM, its already rooted, and you don't need to root it with SuperSU (and doing so often creates more problems).
Click to expand...
Click to collapse
Sure? CM itself in its fresh installed form was NOT rootet for me, because Xposed didn't work... It didn't even install before I rooted the ROM.
Also, Sense ROMs (preferabley stock, or stockish - only certain custom ROM Sense ROMs will work) are best for Sunshine compatibility (and rooted).
Why? Because outdated hboots are known to cause issues on newer ROMs. In addition, older firmware (not just hboot) may cause issues on newer ROMs as well. So its highly advised to keep all firmware updated, not just hboot.
Click to expand...
Click to collapse
Ah okay.
So here are the vars:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.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: <CENSORED>
(bootloader) imei: <CENSORED>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: <CENSORED>
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So, what firmware can I flash via TWRP? Or MUST it be done via adb push?
BloodySword said:
Is there a way to S-OFF it with the current state of the device?
Click to expand...
Click to collapse
You need to be on stock ROM (or close to stock, some Sense custom ROMs work, with root, in order to use Sunshine.
BloodySword said:
Sure? CM itself in its fresh installed form was NOT rootet for me, because Xposed didn't work... It didn't even install before I rooted the ROM.
Click to expand...
Click to collapse
Yes, I'm absolutely sure that CM comes pre-rooted. Its a common mistake to think its not rooted, as you need to "enable" root in Settings. Do so by going into Settings>Developer's Options, and toggle root "on". If no Developer's Options in Settings, go to About>Software information, and tap Build Number 7 times, and you will see a message that "you are now a developer" (seriously, not joking, it says that!) and the Dev Options will appear in Settings.
You made some error posting getvar output (my comments in red):
BloodySword said:
(bootloader) serialno: DELETE THIS
(bootloader) modelid: <CENSORED> Don't censor this
Click to expand...
Click to collapse
There was no need to censor modelid (MID) as its not personal info, and thousands of phones have the same MID. Yours is probably 0P6B10000 (or it may display with one less zero, can't remember).
Serial number on the other hand, is unique to your device, and should be removed (as I previously instructed).
BloodySword said:
So, what firmware can I flash via TWRP? Or MUST it be done via adb push?
Click to expand...
Click to collapse
No, it can't be flashed in recovery. And not with adb push. Its flashed with fastboot.
You can flash the stock firmware (full wipe) 6.12.401.4 from here (includes instructions to flash with fastboot): http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Alternately, you may choose to RUU back to full stock (in order to run sunshine s-off). File and instructions here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6&nocache=1&z=2525208588331338
Then unlock the bootloader again, flash TWRP 3.0.2, and flash SuperSU 2.76 to root. Then you can run sunshine app ($25 US) to s-off the device.
In either case (flash stock firmware or install RUU) backup any personal data from the phone that you want to keep. Either route will wipe your data.
Ugh.. I ran over three times and I didn't see serialno? Give me a break. I need more sleep...
I then thought modelid is the same...
The MID you guessed is correct.
I censored the serialno in the post above.
So Variant A is when I just want to upgrade to the latest CM, just flash the firmware with fastboot, then immediately after CM again?
Variant B would also be alright, too. The device can be wiped, I have already migrated to stock OnePlus3 with O2OS3.
BloodySword said:
I then thought modelid is the same...
The MID you guessed is correct.
Click to expand...
Click to collapse
Not as much a guess, as a result of some prior knowledge about the CIDs and MIDs (or call it detective work, if you will).
The MID identifies if its the Euro version, which in this case I can also determine from the CID.
But its good of you to confirm, as sometimes the MID can be modified by a previous owner or vendor. Or CIDs can also be the same for other versions (such as dual SIM - although in that case the product name would be different from "m8_ul" - so another clue there).
Not the same as serial number, which is unique to your individual M8.
BloodySword said:
So Variant A is when I just want to upgrade to the latest CM, just flash the firmware with fastboot, then immediately after CM again?
Variant B would also be alright, too.
Click to expand...
Click to collapse
Basically, yes.
Method A (relock bootloader, flash signed firmware) would be best if you want to then install CM, but stay s-on.
Method B (relock bootloader, RUU) would probably be best if you want full stock Marshmallow Sense (for instance to s-off).
BloodySword said:
I have already migrated to stock OnePlus3 with O2OS3.
Click to expand...
Click to collapse
How you liking that phone? I'm actually pretty curious about it as an upgrade, also.
Obviously, any current "flagship" phone is going to be a significant CPU/GPU upgrade, as well as a lot more RAM in the case of the OnePlus3. And the displays and camera modules in general have come a long way in 2 years. But how is the speaker sound quality compared to the M8? That is really my main concern with the OnePlus3, since sound is important to me. And that is one area where HTC is still striving to be provide a superior experience with the HTC 10 (although of course its much more expensive).
I know the OnePlus 3 just has a single bottom facing speaker, and its not going to match stereo front-facing Boomsound on the M8. But is the sound at least decent and passable; or a big downgrade?
I usually don't like to go off topic like this. But given the age of our beloved M8, I'd say its pretty fair game, as many of us are probably looking to upgrade soon (or have already).
redpoint73 said:
Not as much a guess, as a result of some prior knowledge about the CIDs and MIDs (or call it detective work, if you will).
The MID identifies if its the Euro version, which in this case I can also determine from the CID.
But its good of you to confirm, as sometimes the MID can be modified by a previous owner or vendor. Or CIDs can also be the same for other versions (such as dual SIM - although in that case the product name would be different from "m8_ul" - so another clue there).
Not the same as serial number, which is unique to your individual M8.
Click to expand...
Click to collapse
So just logic in the end.
Method A (relock bootloader, flash signed firmware) would be best if you want to then install CM, but stay s-on.
Method B (relock bootloader, RUU) would probably be best if you want full stock Marshmallow Sense (for instance to s-off).
Click to expand...
Click to collapse
Relock bootloader. I'm feeling sick... This is what also failed last time.
Code:
fastboot oem relock
threw an unknown error or file missing. :crying:
Then the device was basically bricked, it only booted into fastboot with a security warning. If it occurs again, I will post a log. Will happen Saturday or Sunday as I am back to work after hospital amusement... Not related to this phone.
Offtopic
>> One Plus 3
How you liking that phone? I'm actually pretty curious about it as an upgrade, also.
Obviously, any current "flagship" phone is going to be a significant CPU/GPU upgrade, as well as a lot more RAM in the case of the OnePlus3. And the displays and camera modules in general have come a long way in 2 years. But how is the speaker sound quality compared to the M8? That is really my main concern with the OnePlus3, since sound is important to me. And that is one area where HTC is still striving to be provide a superior experience with the HTC 10 (although of course its much more expensive).
I know the OnePlus 3 just has a single bottom facing speaker, and its not going to match stereo front-facing Boomsound on the M8. But is the sound at least decent and passable; or a big downgrade?
I usually don't like to go off topic like this. But given the age of our beloved M8, I'd say its pretty fair game, as many of us are probably looking to upgrade soon (or have already).
Click to expand...
Click to collapse
The speaker itself is very loud and can deliver loud sound without distortion, but little at full volume. Much better as the ones in m8. However, the low frequencies are not as defined as with HTC's BoomSound(TM) technology.
In fact, the speaker is so loud and efficient at the mid-range and highs, that notification and ringtone volume level 1 is too loud for work. The only workarounds are low volume sound files for notification or vibration-only mode, which is bit annoying.
Besides that, the display is very bright and very readable in the sun. However, it also suffers from pen-tile fly screen issues. In everyday life it is no big deal but it's noticable. For VR applications I imagine this is very bad. I hope they go for S-IPS and 100% AdobeRGB in the OnePlus 4 next time... Not a fan of Scamscum Displays.
I first had the dark grey one, but it has dust between the glass and the AMOLED!! I then ordered the new available soft gold version and did a return RMA. I am currently waiting for the results and refund.
The processor is very fast and the 6GB ram are really a step forward.
However, Oxygen OS still suffers from the "doze" bug, some push notifications are postponed or only fetched when waking the device up. The last update should fix it, but it just got better instead of fully resolved... I hope they will fix this soon.
Oxygen OS doesn't have many ringtones built-in, I miss the Google stock ones. But I grabbed them from CyanogenMod out of my m8 and put them on the internal UFS. :victory:
OTA updates are fast and reliable, too.
/Offtopic
BloodySword said:
Relock bootloader. I'm feeling sick... This is what also failed last time.
Code:
fastboot oem relock
threw an unknown error or file missing. :crying:
Click to expand...
Click to collapse
Wrong command. It should be: fastboot oem lock
Also, thanks for the "off topic" comments!
Code:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Invalid argument))
finished. total time: 1.178s
Failed. Sticks in fastboot until I unlock again using HTC-DEV. :crying:
BloodySword said:
Failed. Sticks in fastboot until I unlock again using HTC-DEV. :crying:
Click to expand...
Click to collapse
Does it still say UNLOCKED on the bootloader screen, or RELOCKED?
This is what it displays:
http://i.imgur.com/GNEVHyt.jpg
Oh and you're welcome!
BloodySword said:
This is what it displays:
http://i.imgur.com/GNEVHyt.jpg
Click to expand...
Click to collapse
That is exactly what is supposed to happen. The phone won't boot after being relocked, that is normal and intended.
Flash the RUU, or the firmware I linked previously, using fastboot (whichever method you prefer).
After RUU or firmware, you should see the OS number changed to 6.12.401.4, and hboot should be 3.19.
Failed.
MD5 sum was correct after download.
Code:
C:\adb>fastboot flash zip fw.zip
target reported max download size of 1830477824 bytes
sending 'zip' (82794 KB)...
OKAY [ 3.470s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.643s
Edit:
Tried:
stock 6.12.401.4 International
Also tried:
M8_6.12.1540.4_DevEd_FullStock
BloodySword said:
Failed.
MD5 sum was correct after download.
Code:
C:\adb>fastboot flash zip fw.zip
target reported max download size of 1830477824 bytes
sending 'zip' (82794 KB)...
OKAY [ 3.470s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.643s
Edit:
Tried:
stock 6.12.401.4 International
Also tried:
M8_6.12.1540.4_DevEd_FullStock
Click to expand...
Click to collapse
That's a big size firmware .... you can't flash unsigned firmware on S-On device.
Get the htc signed 6.12.401.4 firmware in post #5 on my backup thread linked in my signature.
http://imgur.com/a/BvaYN
Console locked up.
I don't have the balls to CTRL+C it...
hi,
i bought a htc one m9 "0PJA100 ve FCC ID: NM80PJA100 M9u". it can bootloop only in bootloader and not any more. when select the download mode screen was blue and restarted again. i flashed the some *.img files in adb folder just like this this message
http://forum.xda-developers.com/one-m9/help/htc-m9-corruted-bootloader-blue-screen-t3164927/page2
it went good and i could boot in download mode. when i wrote "fastboot getvar all"
mid: 0PJA10000 and cid:11111111 so this one is international version.
i flashed many kind of rom (*.**.401.*--*.**.617.*--*.**.605.* with change with suitable mid number also and many custom rom) but all of them had not recognised "empty imei ,emty baseband and no sim card" but no problem with the imei number it was original. last one i flashed stock rom (3.35.401.12) with zip file. with 0PJAIMG.zip in download mode all went good but same thing happened. "empty imei ,emty baseband and no sim card"
"fastboot getvar all" screen is
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 3***************
(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: 11111111
what can be done ? is it a solution to flash firmware file one by one ( so i flashed some of them firts)
Cid is supercid. Compatible?. Yes updates are incremental.
Beamed in by telepathy.
no baseband no imei
shivadow said:
Cid is supercid. Compatible?. Yes updates are incremental.
Beamed in by telepathy.
Click to expand...
Click to collapse
hi,
i also tried with international cid number (htc__m27) but no luck. I tried almost every stock rom (international, developer, asian and europe version) but same result no baseband no imei. i dont think its a hardware problem. what else can be done?
no IMEI no Baseband, no sim, no solution
It is same with me, I just flashed Multirom and then uninstalled it -> now no IMEI no Baseband and cannot do anything with the phone, it works normally just does not accept sim card so no signal. I do not think it is hardware as so many people have the same problem. Could someone please look into this?
Same problem for me!!m9 verizon himawl gsm, unknown baseband!help us??
It could be problem of fabric
Maybe is inside of hardware
Mine Htc One M9 has problem of Radio Fm
Doesen't work even when was on lollipop and now on Nougat
I gone on alot of phone services and told me that is not a big deal that ,dont screw your phone only that has no radio
I was thinking that is better this way
I told my friend who bought my phone from Ebay to complain to the seller but is a long way of getting my money back
So for every thing you done check it with the seller you bought it your phone
Cause was from the alterations to the boot firmware when SuperSU was installed. I flashed the original boot.img back to the phone and baseband were restored. I re-installed SuperSU 2.78 and Baseband and imei were gone. SuperSU is the cause. When you restore the boot image, you loose root.
Solution: flash original unaltered boot.img back to phone using fastboot. Then install SuperSU-v2.82.