Hi everyone,
First of all thank you for taking the time to read my problem, and maybe trying to help.
I will try to describe with as many data and images what I have done, that led me to my problem, I hope it's not the end of my M9.
My original goal was to revert my M9 back to stock.
The M9 state before trying to achieve this was:
Root
S-OFF
TWRP Recovery installed
Unlocked Bootloader
cid 11111111
Custom Rom- Viperone M9 version 4.3.0
To revert to stock, I first tried RUU.EXE method.
This procedure always resulted in ERROR 155. After searching the forums, I understood that this sometimes happens because of the unlocked bootloader.
So using the Fastboot I relocked the bootloader. Unfortunately, that didn't help.
After that, I tried flashing RUU.ZIP via Fastboot.
I did several Fastboot commands after searching all forums. Everytime Fastboot command resulted in another error.
Unfortunately, during this process I did S-ON, and I this that because of that, I am currently stuck.
At the moment, the device doesn't manage to execute any command I try.
Also, it doesn't boot into the firmware, so I can't S-OFF again.
I'm afraid already (hope it's not too late) to continue other actions without assistance.
At the end of OP, you will find screenshots of
The current Bootloader Screen
The current Download screen
Result info of Fastboot command: "fastboot getvar all"
A link to the RUU.EXE I tried using
A link to the RUU.ZIP I tried using
To keep thing clear, any other image of actions will be uploaded to OP.
I would very very much appreciate help and advice.
I hope it's not too late, even if this whole thing doesn't succeed, I look forward learning more to prevent this from happening in the future.
Thank you.
Bootloader Screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Screen:
Fastboot getvar all:
RUU.EXE: https://www.dropbox.com/s/9kjf0u8h5iy8rdc/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe?dl=0
RUU.ZIP: https://www.dropbox.com/s/edzwftny23ldsiq/0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip?dl=0
Actions done according to information from this thread:
You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Sent from my HTC One M9 using Tapatalk
You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Click to expand...
Click to collapse
Hi, and thank you for your reply.
Can you please past a link to the thread so that I can be sure I'm following the correct one?
I tried flashing recovery, locking bootloader and flashing stock RUU, all resulting in error.
If you could be more specific about what exactly I should do, I would give you the respected result.
I'm not looking for someone to do the searching or work for me. I just want to be accurate about the actions I need to do and their results so that you I and other helpers would now the exact actions made and their results.
Thank you
http://forum.xda-developers.com/showthread.php?t=3132698
Sent from my HTC One M9 using Tapatalk
shivadow said:
You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
shivadow said:
http://forum.xda-developers.com/showthread.php?t=3132698
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
There are no instructions there. Only all sorts of files.
I have already been to that thread. The files are tried to flash are also from there.
Maybe I flashed the wrong files, or maybe I didn't do the steps properly, but in any case, I can't know from that thread since it is not described there.
Again, please be more specific about what are the steps, or anything else that I need to do.
Thank you
Did you even bother reading the OP of my thread? If you had you would have known where to find the instructions.
Sent from my HTC One S using XDA Labs
Flippy498 said:
Did you even bother reading the OP of my thread? If you had you would have known where to find the instructions.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Lol, I read every letter in the first post.
post 1: Opening post (no instructions)
post 2: TWRP backups (not relevant to me because I can't flash the recovery, again no instructions. Only files)
post 3: OTA Updates (again no instructions. Only files)
post 4: Stock Recoveries (again no instructions. Only files)
post 5: General Info (again no instructions. Only links to other threads regarding the info)
post 6: Useful links to downloads
Did I miss something?:laugh:
henengel said:
Did I miss something?:laugh:
Click to expand...
Click to collapse
Well, obviously you did.
From the OP:
Flippy498 said:
Please take a look at my google sheet if you want to get back to stock and don't know how to flash a RUU or how to correctly restore a TWRP backup. Although the sheet doesn't contain files for every existing firmware version the instructions can be used for every other RUU and TWRP backups that contain at least a Boot Image, the Stock Recovery and a System Image, too.
[...]
RUUs and useful links (e.g. instructions) can be found in the 6th Post.
Click to expand...
Click to collapse
From Post #6:
Flippy498 said:
Flippy498's Google Sheet
Contains download links for all Back-to-Stock files he collected/created (RUUs, OTAs, official Firmware Packs, Stock Recoveries, Boot Images and TWRP Backups) and some instructions how to flash RUUs or how to Restore a TWRP Backup correctly, too
Click to expand...
Click to collapse
Edit: Btw, if you don't want others to use your IMEI for scam you should remove it from your OP.
Flippy498 said:
Well, obviously you did.
From the OP:
From Post #6:
Click to expand...
Click to collapse
First of all thank you for pointing out the instructions.
Obviously, I did...
Just a suggestion, it would be very helpful if you could make the section stand out more, and be clearer that all steps and instructions are placed there.
I personally didn't understand that all of that is located there... again only my opinion.
I'll start right away and be back with all results and images...:good:
I actually prefer it the way it is now. That wasn't my thread from the beginning and I don't want to change too much of the original OP. Besides I don't like the tl;dr attitude (aka "OP? I see no reason why I should waste my time and read it!"-attitude) more and more user seem to have here on xda. You can do a lot of mistakes and ruin your phone in so many ways if you don't know what you're doing (this especially applies to S-OFF users) and this way people are forced to read the OP if they need help. (And maybe one or another user starts reading the basic information in post #5.)
Oh and for your own safety: Please take a look at the edit of my last post.
Flippy498 said:
I actually prefer it the way it is now. That wasn't my thread from the beginning and I don't want to change too much of the original OP. Besides I don't like the tl;dr attitude (aka "OP? I see no reason why I should waste my time and read it!"-attitude) more and more user seem to have here on xda. You can do a lot of mistakes and ruin your phone in so many ways if you don't know what you're doing (this especially applies to S-OFF users) and this way people are forced to read the OP if they need help. (And maybe one or another user starts reading the basic information in post #5.)
Oh and for your own safety: Please take a look at the edit of my last post.
Click to expand...
Click to collapse
I totally understand you...
That is indeed the common attitude...but if it doesn't stand out a bit, it is really easy to miss like I did.
There is a lot of information here, and it's very easy to miss 1 sentence, as I did.
But you are the creator, or in this situation the of the maintainer of the post, so obviously your opinion is what counts.
As far as one is concerned, I'm just appreciate very much and thank you for your help.:good:
Well after doing as the guide said (very easy), my M9 is up and running as normal.
Thank you so very much for your help and guidance.
Related
So...I first started rooting and custom rom'ing back in the Samsung Fascinate days, flash forward...I sold my s3 because I was in love with what I heard about the HTC One!! Found one on Craigslist in great condition. Dude I had bought it from said it had been rooted and I thought GREAT, saves me the trouble!! Well, I'm confused. I am running a modified 4.3, locked with s-on, and rooted. I am able to boot into TWRP. I cannot figure out the tech of the HTC One and need to know 2 things...1. How is this phone rooted with locked bootloader/s-on? 2. Where can I go from here... Can I flash other rom's through TWRP even though bootloader is locked and s-on? I have read everything I can on xda and still can't make sense of this...
Sounds like they unlocked it, flashed a custom rom, and then relocked it. I would use firewatter to get unlocked again and s-off. http://firewater-soff.com/instructions/. Not sure if you could flash in that state or not, but im guessing no.
Hey thanks! I was sort of guessing that is what happened...but couldn't really find a reason to do that? Is it difficult to hard brick an HTC? I was never concerned with the Samsung or Motorola, I could always get my way back from any issue. So, use firewater to unlock/s-off and then I can return to full stock or whatever?
schilly said:
So...I first started rooting and custom rom'ing back in the Samsung Fascinate days, flash forward...I sold my s3 because I was in love with what I heard about the HTC One!! Found one on Craigslist in great condition. Dude I had bought it from said it had been rooted and I thought GREAT, saves me the trouble!! Well, I'm confused. I am running a modified 4.3, locked with s-on, and rooted. I am able to boot into TWRP. I cannot figure out the tech of the HTC One and need to know 2 things...1. How is this phone rooted with locked bootloader/s-on? 2. Where can I go from here... Can I flash other rom's through TWRP even though bootloader is locked and s-on? I have read everything I can on xda and still can't make sense of this...
Click to expand...
Click to collapse
Hey I remember you from the Fascinate forums from a while ago... nice to see a familiar face! I had the S4 for a while but just switched to the HTC One. This phone is a beast. I was lucky enough to get mine on 4.2.2 so I just used rumrunner... you got lucky because up until a few days ago 4.3 was locked down. From what I understand so far, once you get S-Off you're pretty safe on flashing anything just like the Fascinate. The danger is in actually getting S-Off but firewater seems to be a fairly safe and easy method. Happy flashing and let me know if you have any questions, although I'm still learning the HTC ropes but I'll do my best
It is not likley to hard brick it, but it does happen. Mostly to people who dont pay attention and dont follow instructions well. Just make sure what ever your flashing, is for your phone. There are several varations of the one, and flashing the wrong firmware is just asking for an expensive brick. As long as you can get into the bootloader, there is usually always a fix.
Yeah use firewater and then flash a rom of your choosing. If you just want to be complete stock, you can flash an ruu, and then use firewater to unlock and get s-off if so desired.
Crawshayi said:
Hey I remember you from the Fascinate forums from a while ago... nice to see a familiar face! I had the S4 for a while but just switched to the HTC One. This phone is a beast. I was lucky enough to get mine on 4.2.2 so I just used rumrunner... you got lucky because up until a few days ago 4.3 was locked down. From what I understand so far, once you get S-Off you're pretty safe on flashing anything just like the Fascinate. The danger is in actually getting S-Off but firewater seems to be a fairly safe and easy method. Happy flashing and let me know if you have any questions, although I'm still learning the HTC ropes but I'll do my best
Click to expand...
Click to collapse
Hey...HELLO!! I will be sure to ask, thanks!
cmlusco said:
It is not likley to hard brick it, but it does happen. Mostly to people who dont pay attention and dont follow instructions well. Just make sure what ever your flashing, is for your phone. There are several varations of the one, and flashing the wrong firmware is just asking for an expensive brick. As long as you can get into the bootloader, there is usually always a fix.
Yeah use firewater and then flash a rom of your choosing. If you just want to be complete stock, you can flash an ruu, and then use firewater to unlock and get s-off if so desired.
Click to expand...
Click to collapse
Thank you for your reply...I feel a bit more confident. I follow directions well, so as long as I find a great tutorial I don't see any issues.
so as my phone stands right now, I can just flash a RUU (I think I know what that is, is it hard to find correct one?) and be stock, unrooted? And then I can take the upcoming OTA?
Thanks to you both...I just don't quite get the HTC lingo yet, but I'm a fast learner!!
Well it depends what version your on. If your on if your on 4.2 yes you can, if your on 4.3 not at the moment, unless you can find a 2.10.605.1 ruu somewhere. I would use firewater to get s-off then you can flash an older ruu and take the otas. If you take the kk ota before you get s-off, you risk the chance of firewater not working, and then your stuck without root untill a new exploit is found.
schilly said:
Thank you for your reply...I feel a bit more confident. I follow directions well, so as long as I find a great tutorial I don't see any issues.
so as my phone stands right now, I can just flash a RUU (I think I know what that is, is it hard to find correct one?) and be stock, unrooted? And then I can take the upcoming OTA?
Thanks to you both...I just don't quite get the HTC lingo yet, but I'm a fast learner!!
Click to expand...
Click to collapse
As cmlusco said, I'd probably recommend getting s-off with firewater before an OTA. When 4.3 came out it prevented the existing bootloader unlock tool from working. It was a few weeks before firewater came out and while it works with 4.3 there's no guarantee that it will work with 4.4. Also, you can be S-OFF and take OTAs but flashing a ROM is the safer way to go as far as keeping the ability to run custom recoveries, etc.
EDIT: I didn't realize how much I repeated what cmlusco said. I'll go fade back into the woodwork now. Carry on, nothing to see here.
schilly said:
Thank you for your reply...I feel a bit more confident. I follow directions well, so as long as I find a great tutorial I don't see any issues.
so as my phone stands right now, I can just flash a RUU (I think I know what that is, is it hard to find correct one?) and be stock, unrooted? And then I can take the upcoming OTA?
Thanks to you both...I just don't quite get the HTC lingo yet, but I'm a fast learner!!
Click to expand...
Click to collapse
Don't even bother waiting for the OTA... I'm on NuSense 4.4.2 and it's awesome. I'm sure it'll be updated when the OTA hits too, but if you want KitKat early just jump right in, the water is fine.
EDIT: I didn't realize how much I repeated what cmlusco said. I'll go fade back into the woodwork now. Carry on, nothing to see here. [/QUOTE]
Ha! I didn't see nuthin lol...moving on!
I cannot get adb to work on my new laptop running windows 8...ugh! So frustrated.
A modified hboot with the indicators of s-off and unlocked changed to look like locked and s-on might have been flashed also. I would boot into fastboot and see if you can fast boot flash a different recovery before going through the hastle of using the firewater soff exploit
Sent from my HTC6500LVW using Tapatalk
Check out this thread and see if it provides any answers for your Windows 8 dilemma http://forum.xda-developers.com/showthread.php?t=2493458
I would boot into fastboot and see if you can fast boot flash a different recovery before going through the hastle of using the firewater soff exploit
Never did that before...will see what I can find on Google! Need to figure this out, making me mad.
Sent from my HTC6500LVW using Tapatalk[/QUOTE]
schilly said:
I would boot into fastboot and see if you can fast boot flash a different recovery before going through the hastle of using the firewater soff exploit
Never did that before...will see what I can find on Google! Need to figure this out, making me mad.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
[/QUOTE]
Its pretty easy. first obviously make sure you have debugging enabled then Install this package http://forum.xda-developers.com/showthread.php?t=2317790
Then download a recovery IMG from the original dev section and put it in the same folder as where the minimal adb and fastboot package extracted too. Run the batch for minimal that opens a command prompt to that directory.
Type: adb devices(to make sure it sees your phone)
Next: adb reboot bootloader
Next: you will see bootloader options type: fastboot oem rebootRUU (it is case sensitive)
Next: wait for HTC logo on black background to show up and then type: fastboot flash recovery (IMG filename with extension. IE: twrp.IMG)
Example: fastboot flash recovery twrp.img
Next: fastboot reboot
After it boots up reboot into recovery and see if it changed recoveries although you should know when you fastboot flash if it went. It should tell you successful or fail.
Sent from my One using Tapatalk
Its pretty easy. first obviously make sure you have debugging enabled then Install this package http://forum.xda-developers.com/showthread.php?t=2317790
Then download a recovery IMG from the original dev section and put it in the same folder as where the minimal adb and fastboot package extracted too. Run the batch for minimal that opens a command prompt to that directory.
Type: adb devices(to make sure it sees your phone)
Next: adb reboot bootloader
Next: you will see bootloader options type: fastboot oem rebootRUU (it is case sensitive)
Next: wait for HTC logo on black background to show up and then type: fastboot flash recovery (IMG filename with extension. IE: twrp.IMG)
Example: fastboot flash recovery twrp.img
Next: fastboot reboot
After it boots up reboot into recovery and see if it changed recoveries although you should know when you fastboot flash if it went. It should tell you successful or fail.
Sent from my One using Tapatalk[/QUOTE]
Thank you! You rock! Will report back...just annoyed at this point because I can't flash anything, but I can't take update. Sort of stuck. Thank you for the short how to!
Hmmm...was just thinking, why am I flashing a recovery img? It's already running twrp. Am I just seeing if I can flash anything, at this point?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is where I am right now...anyone care to decipher lol
schilly said:
View attachment 2567052
View attachment 2567053
Here is where I am right now...anyone care to decipher lol
Click to expand...
Click to collapse
Yes just trying to see if it will take. If it takes then you have a hex edited custom hboot otherwise you will need to run fire water. That looks like stock firmware.
Sent from my HTC6500LVW using Tapatalk
Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.
eboy_gb said:
Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.
Click to expand...
Click to collapse
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.
Kyuubi10 said:
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.
Click to expand...
Click to collapse
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
eboy_gb said:
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
If you can access TWRP the download a nandroid of stock, and follow the advice I already gave above.
Flash stock nandroid 4.25/4.20, from TWRP, then from fastboot flash stock recovery.
Reboot and wait for OTA updates.
All is well, got the running properly now - thanks everyone!
eboy_gb said:
All is well, got the running properly now - thanks everyone!
Click to expand...
Click to collapse
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems
Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.
xunholyx said:
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.
Click to expand...
Click to collapse
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Sent from my htc_m8 using XDA Labs
Kyuubi10 said:
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Click to expand...
Click to collapse
Corrupting system won't affect the OS number on the bootloader screen. "OS" is a bit misleading, it actually indicates the firmware number, not the ROM version.
The bug is easily reproduced by flashing certain TWRP versions (not sure exactly which ones). Its very common. We see this pop up by folks almost on a daily basis (OS number blank) especially folks using older TWRP versions.
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Kyuubi10 said:
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems
Click to expand...
Click to collapse
Additionally, its not clear whether your suggestion is what actually worked for him (and exactly what nandroid build, etc.). OP should post the solution that worked, 1) for benefit of "helpers" like you, to confirm your fix is what worked; and 2) for the benefit of others that may run into the same issue.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
The phone would not boot since the bootloader was relocked. This is what happens when you relock by definition, as relocking expects RUU to be run.
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
eboy_gb said:
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
RUU existing for the Desire Z (I had the same phone); and in fact for as long as HTC has been making Android devices.
RUU = ROM Update Utility
Its usually a Windows executable (although the zip format can be extracted to work with fastboot flash, or put right on an SD card) that will completely re-image the phone to stock firmware and software. You need to run the RUU that matches the phones carrier version (CID) and model (MID), and not all versions have RUU. Otherwise, the RUU will fail and not install anything.
RUU also requires a locked or relocked bootloader (although this requirement is bypassed with s-off).
RUU will also wipe any user data on the phone (including internal storage "media").
Hi,
Yesterday I started trying to root my phone, needless to say it didn't go too well. As the title says, I'm unable to access recovery mode, and this morning when I tried to update to andriod 6.0, that wouldn't work either.
I successfully unlocked the bootloader, I think. It says unlocked in bootloader anyway. I have now relocked it to see if it will update with a locked bootloader.
Okay, so to describe what happens when I try to boot into recovery: The HTC logo shows up for a second or so, then the screen goes black and I have to boot it up from start. Also, I noticed, don't know if this is relevant, but in order for me to get into bootloader I have to hold vol down and power for at least 20 seconds, that does't seem normal to me.
I have downloaded a RUU from an HTC site(can't link, first post), but of course that wont install because im S-ON, which I don't know what it means. Anyway, the RUU wizard tells me to get the corret one, even though im fairly sure I am using the correct one.
my CID is HTC__Y13, do't know if that is going to help.
When trying to root I followed the htconeroot websites guide. again can't link :/
I have no idea what to do from here, if anyone who actually knows how these things work could help me, I would apreciate it greatly.
Thanks in advance!
Post fastboot getvar all result without serial & imei no.
Then we'll see what you need to do.
You may need these drivers installed : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Hey, thanks for replying!
Here is my getvar stats. If you don't mind me asking, why should I not post serial or ime no.?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh, also my battery is almost fully charged, still says 0mv... Don't know why, maybe somehow my phone incorrectly detects that my battery is too low when trying to run recover/update and quits because of low battery level?
You don't post serial and imei so you don't get your phone stolen. Those numbers can let someone report the phone as stolen, and have it become rejected by the carriers and such. As for the main issue you have, I'm S-OFF personally, so I flash everything manually. I haven't dealt with much of anything with S-ON aside from pure stock which does everything on it's own.
Trauken said:
Hey, thanks for replying!
Here is my getvar stats. If you don't mind me asking, why should I not post serial or ime no.?
Oh, also my battery is almost fully charged, still says 0mv... Don't know why, maybe somehow my phone incorrectly detects that my battery is too low when trying to run recover/update and quits because of low battery level?
Click to expand...
Click to collapse
Because those are personal info .. bad people can use the data to hack or something. So it's best not to post them.
The battery show as 0 on getvar result is normal ...
back to your problem ....
Your device is not a M8 but a different device called M8s
So the custom recovery that you installed most probably for M8 and definitely won't work on M8s.
And be frank with you, I am not familiar with your kind of device. There is a separate thread for M8s - http://forum.xda-developers.com/htc-one-m8/one-m8s-general
You can ask help here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
or here : http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
maybe someone with your device version will help you
Wow! I feel so stupid now...
Thanks alot for your help guys!
I'll try using the correct stuff instead and see if I can solve things, thanks again!
By the way, what would be the easiest way to go about this?
My bootloader is locked and I can't unlock it again since I have used the wrong recovery mod... So I can't just flash the recovery mode now, can I?
Could I use the RUU to somehow restore my recovery mode ? That would be great.
You can unlock the bootloader again with the same unlock_code.bin that you applied to HtcDev.
This time use correct TWRP meant for M8s to root it. You can find it in that M8s thread.
I don't know whether there is RUU for your software version. As I mentioned above, those people in M8s thread know better.
Since your device is not rooted (most probably), why don't you do the update from 1.21.401.1 to Marshmallow 2.10.401.1 ?
You just need to reflash the stock recovery but you need to find either 1.21.401.1 0r 2.10.401.1 stock recovery.img
Well the problem is I can't reflash since my bootloader is locked, and I can't unlock my bootloader because whenever I go into the "do you really want to unlock bootloader" screen and say yes, it shows the HTC logo and then turns off again... Very frustrating.
I know I'm currently in the wrong section, but since I already have your attention and the fact that you seem to know your stuff, what do you think I should do?
Trauken said:
Well the problem is I can't reflash since my bootloader is locked, and I can't unlock my bootloader because whenever I go into the "do you really want to unlock bootloader" screen and say yes, it shows the HTC logo and then turns off again... Very frustrating.
I know I'm in the wrong section currently, but since I already have your attention and the fact that you seem to know your stuff, what do you think I should do?
Click to expand...
Click to collapse
OK .. you need to flash 1.21.401.1 signed firmware.zip
I'll try to find one (hopefully is available) but I'll do this tomorrow. It's already 1.45 am here .. I need to rest soon.
Meantime try to search/google 1.21.401.1 OTA.zip or firmware.zip. If you can find one (but make sure it is for M8s not M9 or any other device) .. you just need to run these command to flash it.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
you'll see error
fastboot flash zip firmware.zip (one more time)
fastboot reboot-bootloader
this should fix your problem . your problem now is wrong recovery installed but unable to reinstall correct recovery alone because bootloader is relocked.
Thanks man!
If only the world was made up of people like you!
Get some rest, I'm not in any hurry!
I'll try to get the RUU version that I fits my phone, I'm guessing I can't use a newer one because I'm S-ON? Anyway, you don't have to answer now.
Thanks alot again, really appreiciate your help!
Trauken said:
I'll try to get the RUU version that I fits my phone, I'm guessing I can't use a newer one because I'm S-ON? Anyway, you don't have to answer now.
Click to expand...
Click to collapse
If there is a newer one 2.10.401.1 yes you can use, you can't use older version than 1.21.401.1 like 1.11.401.1 or 1.11.401.10 , higher version is ok.
Good night.
Hey, hopefully I don't wake you up somehow.
I found what I think is the right file, it was named the same thing you told me to flash.
When using the commands you told me I get this:
I can't understand any of it really, I'll google around some more and see if I can find what is wrong.
It happened that I woke up for a drink.
Just wait for tomorrow, I already have the correct firmware.zip for you.
Edit : try this - https://drive.google.com/file/d/0B4jGj3SfskzMVElpa0MxTlpCRGM/view?usp=sharing
See whether you can download it, posted on mobile.
I'll check your progress tomorrow
The last command to exit that cmd prompt screen is fastboot reboot-bootloader
Have to get some sleep, saw your answer just now lying in bed...
Will continue as soon as I wake up
EDIT- Okay so I couldn't wait lol.
Did as you said but I get this:
Am I supposed to put the firmware.zip in the fastboot folder. I did that, I'm guessing that's right...
Here is a picture of my fastboot folder in case it is somehow useful:
Trauken said:
Did as you said but I get this:
Am I supposed to put the firmware.zip in the fastboot folder. I did that, I'm guessing that's right...
Here is a picture of my fastboot folder in case it is somehow useful:
Click to expand...
Click to collapse
It seems like the generic fastboot.exe is not working for this. You should try using the htc_fastboot.exe
https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
put the htc_fastboot.exe in your fastboot folder, then try again with commands
fastboot oem rebootRUU
htc_fastboot flash zip firmware.zip
error...
repeat htc_fastboot flash zip firmware.zip
fastboot reboot-bootloader
If this also fails, the last thing that you can do (you need microSD) ...
rename the firmware.zip to 0PKVIMG.zip (that's a zero not "O")
put 0PKVIMG.zip on your microSD (not in any folder)
on bootloader select hboot
it will scan the file and ask whether to update
volume up to update
once completed reboot
(remember to remove this 0PKVIMG.zip from microSD after reboot)
Thank you once again.
My phone now propely works thanks to you.
The htc_fastboot.exe seems to have done the trick. What is it that it actually does?
I can't stress enough how grateful I am!
Trauken said:
Thank you once again.
My phone now propely works thanks to you.
The htc_fastboot.exe seems to have done the trick. What is it that it actually does?
I can't stress enough how grateful I am!
Click to expand...
Click to collapse
Most probably the HTC encryption on the htc signed firmware.zip only can be read by htc_fastboot.exe
Great that you solved your problem .. you should update to the latest Marshmallow 2.10.401.1
As this is M8s device matter, I requested moderator to move this thread to M8s section
when i type "htc_fastboo oem rebootRUU" it restarting normally and bootloop
Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!
jdub1983 said:
Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader?
xunholyx said:
What does it say next to "OS" in your bootloader?
Click to expand...
Click to collapse
Nothing is listed next to os in the bootloader mene
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jdub1983 said:
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
Click to expand...
Click to collapse
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
jdub1983 said:
I any attempts using flashboot do not work.
Click to expand...
Click to collapse
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.
redpoint73 said:
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.
Click to expand...
Click to collapse
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
If you give me a few things to do when I'm in front of the computer I'll execute them later on and report back the results.
jdub1983 said:
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
jdub1983 said:
None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
jdub1983 said:
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
Click to expand...
Click to collapse
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?
redpoint73 said:
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?
Click to expand...
Click to collapse
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!
jdub1983 said:
I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
Click to expand...
Click to collapse
I didn't specify that it had to be an error code number. If the response is all text, tell us what it is. Cut and paste, or do a screenshot, if that is easier. Either way, it will probably tell me what is going wrong.
jdub1983 said:
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!
Click to expand...
Click to collapse
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.
jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
No, they aren't.
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
EDIT: I see now that Redpoint has already linked you up. :good: Easier for me
xunholyx said:
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
Click to expand...
Click to collapse
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
redpoint73 said:
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.
Click to expand...
Click to collapse
Gotcha! If I'm s-on though, how did everything get screwed up? Guess it's not important now.
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom. Something simple really, my m8 is my backup phone.
redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!
jdub1983 said:
If I'm s-on though, how did everything get screwed up?
Click to expand...
Click to collapse
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
jdub1983 said:
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom.
Click to expand...
Click to collapse
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.
redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
redpoint73 said:
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.
Click to expand...
Click to collapse
I'll give it a whirl when I get home and let you know of any errors, if any, hopefully not.
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Thanks again!
jdub1983 said:
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Click to expand...
Click to collapse
I doubt it. Rather, I think your syntax was incorrect (if you typed it exactly as you did before) as the part "RUU" (no quotes) should be in caps:
fastboot oem rebootRUU
If the phone is in RUU mode, it will show a black screen, with HTC logo.
jdub1983 said:
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!
Click to expand...
Click to collapse
Here's the RUU.zip for you.
you both are amazing, thank you!
I feel so silly, considering I was using sneaky ghosts unsigned fullwipe firmware... Blah!
Again, you both are awesome, kind to a moron! The universe will provide for you both!
Thanks again!!!
Everything is working wonderful!!!!!
S-OFF is out now for HTC U12+ with Sunshine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://twitter.com/TheRootNinja/status/1017891591531343872
https://twitter.com/firewaterdevs/status/1017152637433761795
https://forum.xda-developers.com/showpost.php?p=77066052&postcount=249
That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!
MNoisy said:
That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!
Click to expand...
Click to collapse
Starting from the HTC U11, you can't permanently S-OFF the device (SunShine never achieved it for the U11). You can find a complete explanation here:
https://forum.xda-developers.com/u11/how-to/s-off-word-t3662712/post73543715
MNoisy said:
That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!
Click to expand...
Click to collapse
Razorbacktrack5535 said:
Starting from the HTC U11, you can't permanently S-OFF the device (SunShine never achieved it for the U11). You can find a complete explanation here:
https://forum.xda-developers.com/u11/how-to/s-off-word-t3662712/post73543715
Click to expand...
Click to collapse
In addition: it has all the same features as permanent S-OFF, with exception of the ability to use custom hboot/aboot. Once you reboot into Android or Recovery, the device will reset back S-ON, so be careful what you do, once you achieved S-OFF.
Permanent S-OFF is to dangerous - and much more risky - on those new devices as the U11 and all more recent ones.
5m4r7ph0n36uru said:
In addition: it has all the same features as permanent S-OFF, with exception of the ability to use custom hboot/aboot. Once you reboot into Android or Recovery, the device will reset back S-ON, so be careful what you do, once you achieved S-OFF.
Permanent S-OFF is to dangerous - and much more risky - on those new devices as the U11 and all more recent ones.
Click to expand...
Click to collapse
Thank you for that information!
So for the basic essential customizers like me, I would start using this when we start getting some custom ROM's if they are unsigned, to change my model, install TWRP, or if I need supercid?
MNoisy said:
Thank you for that information!
So for the basic essential customizers like me, I would start using this when we start getting some custom ROM's if they are unsigned, to change my model, install TWRP, or if I need supercid?
Click to expand...
Click to collapse
Wouldn't recommend SuperCID anymore, as you won't be able to receive OTAs any longer - yes they changed that as well. S-OFF is only needed to change CID and thus the specific software you're running, or to flash unsigned firmware. No more no less to it actually.
And there's no actual recovery partition anymore, due to treble. Instead stock recovery shares its partition with the respective boot.img. Thus I guess TWRP might be flashed as recovery_ramdisk, or as a TWRP patched boot image - we'll see when it's out and available though.
Sent from my HTC U11 using XDA Labs
S-off gives you complete control over YOUR device. You don't necessarily need to receive OTA's if you're S-off. You can flash your firmware on your schedule, not when the carrier or manufacturer says it's ready. Flash it when you're ready. Flash what you want, when you want. If the option is there, I'm getting S-off every time.
Do your homework, research and learn. If you're too lazy to do your due diligence, don't S-off. You can truly brick your phone if you're not 100% sure of what you're doing.
If you're going to just flash ROMs or just get root access but stay stock otherwise, no need to S-off. If you want complete control over flashing everything , go S-off.
But remember with great power comes great responsibility.
Beyond flashing random firmwares willy-nilly, what's the actual point of this when all U12+ ships unlocked (at least here, in the US)...? I really don't see any reason now.
szlevi said:
Beyond flashing random firmwares willy-nilly, what's the actual point of this when all U12+ ships unlocked (at least here, in the US)...? I really don't see any reason now.
Click to expand...
Click to collapse
if there is a temp root solution u can have a completely bootloader locked saftey net passing rooted device, also the us unlocked devices just mean the sim card is unlocked for whatever carrier you want to use not bootloader unlocked
Hi! I can't to obtain s-off.I bought license via app Sunshine, but when the process begins (Sunshine will now set your device S-OFF) my phone no reboot and no to obtain s-off.
I have 1.15.401.4,unlocked,rooted.
May this need to make with LOCKED status?
Help me pls.
Sorry my english
JR 2007 said:
Hi! I can't to obtain s-off.I bought license via app Sunshine, but when the process begins (Sunshine will now set your device S-OFF) my phone no reboot and no to obtain s-off.
I have 1.15.401.4,unlocked,rooted.
May this need to make with LOCKED status?
Help me pls.
Sorry my english
Click to expand...
Click to collapse
You need to be sure you went to HTC Dev and unlocked your bootloader first. After that you need to be rooted.
If you have both of those steps done and you're getting errors, go to: https://therootninja.zendesk.com/hc/en-us and check out how to troubleshoot, and send in a support ticket.
These guys are awesome, jcase and beaups are super legit and are always willing to help with their software. Good luck
Granite1 said:
You need to be sure you went to HTC Dev and unlocked your bootloader first. After that you need to be rooted.
If you have both of those steps done and you're getting errors, go to: https://therootninja.zendesk.com/hc/en-us and check out how to troubleshoot, and send in a support ticket.
These guys are awesome, jcase and beaups are super legit and are always willing to help with their software. Good luck
Click to expand...
Click to collapse
Thank you)
also make sure you are on the stock kernel it doesnt like freak07's
kickyoace said:
also make sure you are on the stock kernel it doesnt like freak07's
Click to expand...
Click to collapse
Sunshine S-Off isn't working for me either, the orange progress bar completes multiple times until it finally reboots but it just boots back up into the ROM. I am on cleanslate kernel, maybe that is the issue?
LibertyMonger said:
Sunshine S-Off isn't working for me either, the orange progress bar completes multiple times until it finally reboots but it just boots back up into the ROM. I am on cleanslate kernel, maybe that is the issue?
Click to expand...
Click to collapse
Seems like I needs to have the stock kernel
mammothjojo88 said:
Seems like I needs to have the stock kernel
Click to expand...
Click to collapse
Yes, this was exactly the problem. I restored stock kernel and it worked first try. Thanks.
---------- Post added at 01:22 PM ---------- Previous post was at 12:32 PM ----------
Temp. S-Off helped me to fix my Slot b, it seemed slot b was corrupt, it wouldn't boot as if there wasn't a ROM on it so reverting back to the old 1.15 ROM and taking the 1.21 OTA seemed to fix it. Seemless updates worked and i am currently back on slot b finally. I tried everything beforehand and nothing would work except this.
Thanks, used sunshine to convert u12+ china to emea ROM
answer from the support:
HTC designed the u12+ to only support temp s-off, all phones after and including the 11 have been this way
I tried to achieve S-Off with 1.30.401.2 but it takes more than 10 minutes and afterwards the phone boots into the system and not bootloader/download mode. Any thoughts?
mdxdave said:
I tried to achieve S-Off with 1.30.401.2 but it takes more than 10 minutes and afterwards the phone boots into the system and not bootloader/download mode. Any thoughts?
Click to expand...
Click to collapse
I just tried it on 1.30 and it is working for me. I have no advice other than that, sorry.