Related
It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....
syntropic said:
It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....
Click to expand...
Click to collapse
SO I said f*ck it... no big deal, and I unlocked the bootloader and flashed the stock recovery (btw, I flashed a stock recovery I found in the TMO forums that had a version number identical to the software version I had installed, this is correct right????). I had no problems flashing the stock recovery....so apparently, you need to unlock the bootloader whenever you are flashing recoveries irrespective of whether you have S-off.
But then, I tried to run the OTA, and got the red triangle error.... — Is this because my bootloader is now unlocked?
This seems to be going against everything I have read numerous times (namely that if you are S-off, the bootloader is not that big of an issue). I am assuming this is because my bootloader is now unlocked... so I will unlock it.
IGNORE
Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ★★★★★★★★★★★★★
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
syntropic said:
Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: DO NOT POST IMEI NUMBER
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
Click to expand...
Click to collapse
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.
BerndM14 said:
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.
Click to expand...
Click to collapse
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But as of now, I have re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number of the recovery matched exactly the version number of the software that is showing on my hboot screen. I thought that was a educated guess that wouldn't be too risky.
I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused....because aside from the recovery, I didn't touch any of the firmware.
NB: I do have a nandroid that I made that is entitled: 2014-09-24-14-06{whatever) release keys I don't know what release keys means.... I have made a lot of nandroids in my time... 95% of them on HTC devices using TWRP (at least since its inception), and I have never seen a "release keys" appended to the name of an nandroid like that.
I could restore this nandroid... but then I would have to unlock the BL, fastboot flash TWRP, flash SuperSU (although I know TWRP now prompts you which is very cool), then restore the nandroid, fastboot flash the stock recovery, then (apparently) re-lock the bootloader, and get the OTAs.... if the OTAs even work...
syntropic said:
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But I have no re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number matched exactly the version number of the software as shown in the hboot screen. So I assumed it was the right one. I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused.
Click to expand...
Click to collapse
Ok stock recovery flashed back is good then, you need to be completely stock to do OTA's i.e If you made changes to the system even removed pre-installed apps like Facebook, Twitter etc you need to restore those back as well. As the OTA will do a verification check to see that all those things are intact before it continues the update. If it's not stock then you're not getting OTA. Bootloader status won't make a difference, you can keep it unlocked.
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.
BerndM14 said:
{...}
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.
Click to expand...
Click to collapse
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.
syntropic said:
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.
Click to expand...
Click to collapse
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
BerndM14 said:
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
Click to expand...
Click to collapse
They also have the 2.22.531.6 stuff there so just make sure you select the correct versions, it's under the "clickable" buttons so...
OK.... I used a app called Nandroid Manager (very helpful app) which extracts anything you want from a nandroid. Since I had already disabled the Android Tweaker 2 App, and realized I had an original build.prop in that nandroid, I just extracted that and renamed the old one, and used the extracted one. I did a chmod 644, and then attempted OTA install.. And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
EDIT: Actually.... I would really like to avoid the htc unlock token as that erases the data partition as some kind of existential pennace ordained by HTC for unlocking your bootloader.
syntropic said:
[...] And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Click to expand...
Click to collapse
Glad it worked out :good:
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
Click to expand...
Click to collapse
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
Click to expand...
Click to collapse
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.
BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.
Click to expand...
Click to collapse
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!
syntropic said:
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!
Click to expand...
Click to collapse
how did you get S-OFF? Firewater?
BerndM14 said:
how did you get S-OFF? Firewater?
Click to expand...
Click to collapse
He said SunShine on OP.
OP - try towelroot to gain root then use scotty's guide to unlock bootloader
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
Really ?
Read his problem again... His device has no root so can't do what you suggested
ckpv5 said:
Really ?
Read his problem again... His device has no root so can't do what you suggested
Click to expand...
Click to collapse
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.
jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.
syntropic said:
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.
Click to expand...
Click to collapse
Yeah, I had a bit of a brain fart on that one. I forgot you have to be able to su to execute that dd command, even s-off. However, I do know for a fact that you don't actually have to flash TWRP to re-root. When I did the same thing you are doing, I simply booted TWRP instead of installing it to preserve the stock recovery.
TWRP did have an issue booting for a while when using the firmware that came along with 4.4.3, but they appear to have fixed it in the last two versions. I ended up using CWM instead, but the effect is the same.
jshamlet said:
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.
Click to expand...
Click to collapse
That is another good potential solution...and I know it works.... I will try and let you know!
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
mtt_73 said:
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
Click to expand...
Click to collapse
im going to assume your phones is s-off?
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Thank you.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Click to expand...
Click to collapse
You can't install custom recovery with a (re)locked bootloader.
With s-off, you shouldn't ever relock the bootloader, as its no longer a requirement to RUU once s-off. But that's neither here nor there at this point, just info for future reference.
Any response to: fastboot devices
Make sure the phone is in fastboot mode.
Try to run the GPE RUU with phone in fastboot mode, to get the phone back up and running at least. Assuming you are still on the GPE CID and MID.
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Click to expand...
Click to collapse
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT.............8
(bootloader) imei: 35...........30
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
redpoint73 said:
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Click to expand...
Click to collapse
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Click to expand...
Click to collapse
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
mato123 said:
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
Click to expand...
Click to collapse
I would highly suggest not to post to another user's troubleshooting thread like this, as it doesn't look like the same problem at all (and in my experience rarely is, even when folks will post "I have the same issue"). You really should have just started your own thread, and would have been justified doing so IMO. Posting here just confuses matters for you, the OP and those trying to help.
But DON'T start another thread now (and add even more confusion). I'll ask the mods if they can move this post to its own thread.
ok, sorry
redpoint73 said:
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
Click to expand...
Click to collapse
Thanks for reply.
I went now in fastoob mode and tried to flash the RUU GPE again.
The error is:
macbooks-MacBook-Proownloads macbook$ ./fastboot-mac flash RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
unknown partition 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
error: cannot determine image filename for 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
Just to clarify. I successfully when in GPE (with conversation). The problem was when going back to Sense. I do not know exactly what I did wrong.
My CID is 11111111
My MID is 0P6B10000
Really do not know how to proceed.
M
I unfortunately don't know jack about how to use fastboot and other actions on a Mac. I'm also not that familiar with running the RUU as a zip (I always do it on a PC with the RUU .exe).
But it looks like you just have the command syntax wrong. I think it should be:
fastboot oem rebootRUU
fastboot flash zip filename.zip
But it also look to me like nothing is actually "wrong" (aside from adb not working?). The phone not booting after relocking the bootloader is normal and intentional. You should just be able to run the desired Sense RUU, provided you have the right MID.
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
mtt_73 said:
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
Click to expand...
Click to collapse
hehe try watch this movie: https://www.youtube.com/watch?v=CCGj0rOuiR4
Most important is the firmware flash... so partition layout etc is changed to sense like after that you can flash sense roms etc. (for example viper rom as in video)
0kk0 said:
Most important is the firmware flash... so partition layout etc is changed to sense
Click to expand...
Click to collapse
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
redpoint73 said:
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
Click to expand...
Click to collapse
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Sent from my HTC One_M8 using xda Forum
mtt_73 said:
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Click to expand...
Click to collapse
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
redpoint73 said:
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
Click to expand...
Click to collapse
I did it. I am back to Sense now.
Any advice to remove tell HTC problem? I mean it says that I have a testing device. Is it because I am s-off? Should I go for s-on again? And how?
TY!
Hey guys!
I really hope anyone can help me out with this.
So, today I thought "Why not upgrading to 5.1 and unbranding it?". I followed a tutorial on a german android forum to unbrand it.
But I was unlocked and rooted so I had to return the changes in order to update it. I changed the CID to HTC__102, made it S-ON again and even locked it, then tried flashing a non branded european RUU via my microSD card, which somehow failed and I ended up having a bootloop. So I upgraded my firmware aswell to 2.10.401.1 but now the recovery is not even working i only get a red triangle, which might be a common problem with 5.1 on our M9, as I read later on.
Download mode, fastboot etc is working fine
edit: stock recovery is working as well
Can anybody help me get my M9 going again?
I thought about try another flash with a unlocked ROM via microSD card but I'm not sure which one as the one I mentioned failed.
Here are some more details about my current situation:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: XXXXX
(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
Click to expand...
Click to collapse
edit: In another thread I read how to boot into the stock recovery and it's working. But still not booting
easy...soff again unlock bootloader, then download dev 2.8 zip rom, place it on sdcard and enter download mode, press volume up to start flash and you will have a brand new developer edition 2.8 (you will loose all info) you must have mid 0JPA11000 cid BS_US001., read a topic on this on xda how to change att to developer...
LLegion said:
easy...soff again unlock bootloader, then download dev 2.8 zip rom, place it on sdcard and enter download mode, press volume up to start flash and you will have a brand new developer edition 2.8 (you will loose all info) you must have mid 0JPA11000 cid BS_US001., read a topic on this on xda how to change att to developer...
Click to expand...
Click to collapse
Thanks, but how do i set it to S-Off again? I've used Sunshine's S-Off app before. But I'm not able to boot anymore.
At first never post your IMEI number online.
If you are not S-OFFed any more you cannot flash anything to recovery partition as long as you are not at least htc_dev unlocked.
The only thing that could help you now is to flash a custom recovery in boot partition and then to try to fix the recovery partition from it.
In order to do this you should unlock your bootloader again by using Unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
or if it has "relocked" status you could possibly use the command
Code:
fastboot oem unlock
then you should reboot in download mode again
Code:
fastboot oem rebootRUU
and flash the boot partition with a custom recovery
Code:
fastboot flash boot recovery.img
Now logically you should be able to boot into recovery (probably from bootloader) or by using the command
Code:
fastboot reboot recovery
If for some reason you cannot flash a custom recovery on boot partition you could try to extract the system.img from (probably any German RUU [HTC-GER] as long as you have HTC__102 cid number) and flash it with fastboot command
Code:
fastboot flash system system.img
By this way you could probably fix your breaked system partition
You should also erase the /cache and /data partitions so you could avoid the bootloop (even without to flash an original system.img)
Gatosbil said:
At first never post your IMEI number online.
Click to expand...
Click to collapse
Thanks. I've corrected it.
Gatosbil said:
In order to do this you should unlock your bootloader again by using Unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I can't generate a new one because OEM unlock is turned off :\
Same goes with reflashing the previous Unlock_code.bin
> htc_fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY
Execution time is 20(ms)
Click to expand...
Click to collapse
Gatosbil said:
or if it has "relocked" status you could possibly use the command
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Indeed, it is "relocked". But when I'm using the command I'll get "[ERR] Command error !!!"
Any suggestions for that? I'll try the other steps once I solved this.
Edit: I can't use ADB because I'm using the stock recovery atm.
Also there is no RUU for 2.10.401.1 yet so I guess I have to sent it in?
Btw: I'm already hating the new 5.1 oem lock feature.
This was your mistake:
Army92 said:
made it S-ON again
Click to expand...
Click to collapse
I don't care what anyone tells you, don't ever, ever go back to s-on once you are s-off. It's totally unnecessary and a potential risk, as you've discovered. By doing it, you've locked your phone into a bad configuration. You can't unlock unless you can boot to the OS and check "allow OEM unlocking." You can't flash a recovery because you're locked. You can't run a RUU because none exists for your CID. You're going to have to return it and hope HTC will fix it.
iElvis said:
This was your mistake:
I don't care what anyone tells you, don't ever, ever go back to s-on once you are s-off. It's totally unnecessary and a potential risk, as you've discovered. By doing it, you've locked your phone into a bad configuration. You can't unlock unless you can boot to the OS and check "allow OEM unlocking." You can't flash a recovery because you're locked. You can't run a RUU because none exists for your CID. You're going to have to return it and hope HTC will fix it.
Click to expand...
Click to collapse
That's what I thought. Thanks, I'll contact HTC and see if they can fix it.
Edit: I'm sending it to HTC today. Just a warning to all users out there: Do not lock your bootloader and uncheck "Enable OEM unlocking" because you are not able to do anything about it when your devices isn't working properly!
Army92 said:
Just a warning to all users out there: Do not lock your bootloader and uncheck "Enable OEM unlocking" because you are not able to do anything about it when your devices isn't working properly!
Click to expand...
Click to collapse
If it's any consolation, you're far from the first person to get tripped up by this new feature. Lots of Nexus 6s got bricked when it first rolled out because of situations just like yours.
iElvis said:
If it's any consolation, you're far from the first person to get tripped up by this new feature. Lots of Nexus 6s got bricked when it first rolled out because of situations just like yours.
Click to expand...
Click to collapse
Yeah I've read that too. Thanks for your condolence. Will report again when I get my M9 back in 2 weeks (I hope).
Update: So today I got my lovely One M9 back it lasted 10 days until I got it back in my hands.
They changed the mainboard and haven't charged anything. My phone status went back to official, S-Off and locked bootloader.
Army92 said:
Update: So today I got my lovely One M9 back it lasted 10 days until I got it back in my hands.
They changed the mainboard and haven't charged anything. My phone status went back to official, S-Off and locked bootloader.
Click to expand...
Click to collapse
They sent you an s-off phone?
iElvis said:
They sent you an s-off phone?
Click to expand...
Click to collapse
Oh, sorry my bad. I meant S-On of course
soft breaked htc one m9 s-off please help
hy
rom: cm13 himaul
device:htc one m9 unlocked/developer edition
statue:s-off
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) version-main: 1.32.617.30
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US001
ok i have rooted cm13 20160603 nighties by supersu 2.74 beta with xposed 85 arm 64
yesterday i was disabling my boot image when it restarted by itself and never boot in to system again so i went to my custom recovery twrp latest version to reflash the whole cm13 again it didnt work then i wiped the whole internal storage and reflashed the cm13 and it said fail cant flash cm thats when my battery died so i charged it after 3 hours i came back went to bootloader menu then clicked on custom recovery it didnt even start so i plugged it to usb used fastboot to flash custom frimware from here (used the no wipe zip)
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
it flashed but custom frimware didnt fix it so i used the wipe zip version with viper one latest system image to flash it failed so now i am stock in bootloader (download mode works) without access of recovery and no system.img or recovery and i cant find a way to fix it
websites i visited just in case
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
any help would be appreciated
:crying::crying::crying:
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
unlock with fastboot
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
yotamh said:
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
Click to expand...
Click to collapse
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
yotamh said:
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
Click to expand...
Click to collapse
It seems like you're talking about the android version not the firmware version since there is no 5.0.XXX.X firmware for the M9. For now it might be the best solution to wait until you're home.
yotamh said:
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
Click to expand...
Click to collapse
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
LLegion said:
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
Click to expand...
Click to collapse
the problem is I can't unlock the bootloader. ADB devices doesn't work
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
yotamh said:
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
Click to expand...
Click to collapse
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in my google sheet (link can be found in my signature). Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Flippy498 said:
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in the google sheet in my signature. Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Click to expand...
Click to collapse
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
yotamh said:
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
Click to expand...
Click to collapse
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Flippy498 said:
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Click to expand...
Click to collapse
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
yotamh said:
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
Click to expand...
Click to collapse
yotamh said:
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
Click to expand...
Click to collapse
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Click to expand...
Click to collapse
Hi thanks for the top about the IMEI I've changed it.
and sorry, I didn't understood the the original comment and got in to the a wrong line in the comment. I'll try again with the correct file (2gb will take some to download). Again, thank you for your answer and patient. It's nice to see people try to help. :good:
THANK YOU so much! everything is working and even updated! thanks!
it seems i have a strange issue after all.
my phone doesn't detect my htc headphones. It recognize other headphone and the HTC headphones works with other devices.
it looks like a software issue.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. [REMOVED BECAUSE I'M A NEWBIE]I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature[/URL].
Click to expand...
Click to collapse
Hi I know this is probably old but I was in this exact same predicament and I had "tried everything" and your instructions brought my phone back to life!! I am so grateful after almost a week of adb commands and zip files that got me nowhere! THANK YOU SO MUCH!!!:good:
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...