I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!
Related
I have been trying to go back to stock and I am sure that I have missed it in the threads but is it even possible to do if I am s on? Iif I can't then is there a s off for 1.54.401.5 that I am missing. I have tried to relock bootloader and tried installing the stock backup but then the phone just stays in bootloader and I can't reboot into the system.
jdmohn12 said:
I have been trying to go back to stock and I am sure that I have missed it in the threads but is it even possible to do if I am s on? Iif I can't then is there a s off for 1.54.401.5 that I am missing. I have tried to relock bootloader and tried installing the stock backup but then the phone just stays in bootloader and I can't reboot into the system.
Click to expand...
Click to collapse
You can't with S-ON, at best, it will show RELOCKED
What have you actually changed? If you want s-off use firewater.
ashyx said:
What have you actually changed? If you want s-off use firewater.
Click to expand...
Click to collapse
Unfortunately I have one of the phones that can't s off with firewater. I have been trying for a wile. Plus I can't find any other way to get s off or that would solve all my problems. I have tried all the dab and fast boot commands and 3 or 4 other all in one programs that say they do it but one of the prerequisite of tho use is to be s off.
I'm not flaming, but S-OFF is not recommended for general users. You can live fine with S-ON. Going back to S-ON is ruled out for now, until someone finds a new way !
Sent from my S-ON unlocked M8
I've got the fuzzy lens problem and I want to get the phone replaced (preferably via T-Mobile but I'll go directly to HTC if I have to). I know you can scratch off the coating on the lens and get some camera improvement but I'm not interested in that solution.
My goal: Return the phone to completely stock condition. No root, locked bootloader and preferably S-ON. I've read a few stories where HTC insisted on replacing the motherboard (with an additional full price fee) because the device was S-OFF and I don't want to go there.
Background: I used firewater to S-off the phone as soon as I got it (it was running 1.12 at the time). I have flashed the Harmon Kardon audio stuff (http://forum.xda-developers.com/showthread.php?t=2737498). I have turned off the tamper flag (http://forum.xda-developers.com/showthread.php?t=2708565). I am running the Stock+ rom which is based on 1.57 (http://forum.xda-developers.com/showthread.php?t=2716843).
My plan:
1) Reset my bootloader to locked (http://forum.xda-developers.com/showthread.php?t=2708571)
2) Wipe the phone and restore my very first nandroid backup I made with TWRP. That will get me back to unrooted 1.12 firmware but without the stock bootloader and still S-OFF. Staying with 1.12 will allow me to S-OFF again with firewater if it comes to that. If some kind of emergency came up, I'd hate to spend $25 on sunshine for a one time use on a phone that is going back to HTC forever.
3) Install the stock bootloader that matches 1.12 firmware. Not sure how to do this yet. I'm afraid I won't be able to achieve this with a locked bootloader and no root.
4) Verify everything is back to stock.
5) Set the phone back to S-ON (http://forum.xda-developers.com/showthread.php?t=2758818)
6) Run the 1.57 RUU (http://forum.xda-developers.com/showthread.php?t=2714456)
7) Proceed with the warranty exchange.
I'm not sure running the RUU is 100% necessary, but I figure it's the best bet I have to make the phone completely stock.
Questions: Is this a sane plan? Am I doing anything in the wrong order? Are there any steps that won't work because I've lost root or unlocked bootloader? Am I setting myself up for a brick anywhere?
There is a thread about doing this on a EU M8 (http://forum.xda-developers.com/showthread.php?t=2735235) but I can't tell what, if any, modifications need to be done for the USA T-Mobile version of the M8. There is talk about having to flash a firmware file twice or risk a hard brick when setting S-ON. Do I need to be worried about any of that?
UPDATE: T-Mobile gave me a warranty replacement to fix the camera lens problem. I did get the old phone back to completely stock with locked bootloader and S-on before sending it back.
I found it was easiest to use the sunshine installer to gain temp root. You don't need to pay anything since you stop before it goes through the whole S-Off process. Just run the APK and select temp root. When sunshine shows you the next screen, you can exit out and still have root. (http://theroot.ninja/)
In the end I didn't bother with the old nandroid and keeping the exploitable version. I also had the order messed up in my initial post. Here is what worked for me:
1) factory reset the phone (in TWRP I did advanced wipe and also wiped internal storage). This step kills root. Rebooted the phone and verified it was back to factory defaults. Go through the setup wizard and skip all the steps. I couldn't find a way to bail out without going through every step in the wizard.
2) flashed stock recovery (the bootloader was unlocked and the phone was S-Off). Root is not necessary for this since it is done in fastboot. (http://forum.xda-developers.com/tmo...l/ota-recovery-ruus-firmware-dumps-t-t2852107). Rebooted the phone.
3) achieved temp root using sunshine APK
4) locked the bootloader (required before running the RUU). You must have root since you need a SU # prompt in the shell. (http://forum.xda-developers.com/showthread.php?t=2708571). I rebooted again for good measure but it's probably not necessary.
5) reset the phone back to completely stock using the latest 2.22.531.5 RUU. This step does not require root. I found it was easiest to put the phone into fastboot mode before running the RUU. (http://www.htcdev.com/devcenter/downloads)
6) Once the phone booted back up, I looked over everything and made sure it is all completely stock. Checked HBOOT said locked (not relocked) and dis not say tampered.
7) OPTIONAL - set S-On. Again root is not required since this is a fastboot command. (http://forum.xda-developers.com/showpost.php?p=52823014&postcount=2)
My actual process wasn't this streamlined. I ended up doing the RUU a couple of times because I didn't flash the stock recovery first and I didn't think the RUU installed the stock recovery right. Turned out I just didn't know what the stock recovery looked like (it was very confusing since I had never actually used a HTC stock recovery).
Thanks to the authors of the various threads I pulled info from. They are the real MVP's.
I flashed the stock HTC RUU via the .EXE and wasn't able to get the "RELOCKED" off the phone. Tried some steps here:
http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
however I wasn't able to get "SU" to properly run in terminal.
No w the phone says *** RELOCKED ***
and im S-On
anything I can do?
Hello fellow TMO brethren....
I just got the M8 maybe a week ago... I was busy and had to wait before I could pull up XDA and start reading about this phone (getting root, etc.). Before this, I unfortunately allowed a few updates (2 maybe?) to install, which I believe will prevent me from using Firewater for S-Off... but no big deal....will get sunshine when I need it. However, though firewater won't work, I had no problem using HTCDev to unlock the bootloader (didn't know of towelroot at the time), flashing TWRP 2.8.0.1, and installing SuperSU....so I am currently rooted with stock Rom...
Further...I have not touched any applications. And although I have unlocked the bootloader using HTCDev, my calculator and flashlight are still available. I have read in this M8 general forum that the flashlight and calculator are deleted when you unlock the bootloader using HTCDev... This did not happen to me. Does anyone know if this is this just a T-Mobile thing? or has this changed for all carriers?
Anyway, I am now getting notice for yet another update...So I might as well install it. As we all know, I need to re-flash the stock recovery to get the OTA. Here is where I am confused. My current firmware is 2.22.531.5. I don't know what firmware I had a week ago when the phone was purchased.
This was the info on the bootloader screen yesterday, immediately prior to unlocking the BL or rooting the phone:
[btw, can someone tell me how to do a info dump from the bootloader?? is it just an option I missed?]
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio-1.19.213311491.03G
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.22.531.5
eMMC-boot 2048MB
Jul 16 2014,03:33:24.0
1. My first question is what version of the stock recovery do I use?? On the page that contains the stock recoveries, it only shows these two:
Stock Recovery - 1.12.531.19
Stock Recovery - 1.57.531.7
2. Secondly, and I am really irritated about this.... but I never went and accepted the Google Drive free 65GB promo offered by HTC. When I start google drive it states it cannot determine the user (or something like that). I read elsewhere that this is because I unlocked the bootloader. I will do whatever it takes to get HTC to give me this because I think it is pretty low that they would invalidate the offer to anyone who has unlocked the bootloader pursuant to their website, their instructions, and their so-called "open atitude". Obviously I can re-lock the bootloader, but I do not know if that will matter. Plus... if they say that I requested a token .bin file to unlock, I can say that I changed my mind and decided not too. OR, I can get Sunshine, get s-off, and use the s-off ability to relock the bootloader. Does anyone have any advice on any of this?
3. Any general advice from anyone based on the info above??? (lI don't want to foreclose any other options by upgrading or whatever... ).
Thank you very much in advance!
P
NB: Wanted to mention that last night I was about to use Titanium to freeze and/or uninstall some crap software I didn't want, and to that end, disabled Amazon, Facebook, Facebook for HTC, and Kid Zone (and uninstalled Amazon MP3, which is not a system app). Just an FYI... disabling one (or more) of these apps (maybe Kid Zone?) prevented Wifi calling from functioning correctly...it would not let me call and every in-call received while on wifi calling went straight to VM. I have renabled the above apps to get wifi-calling working again, but also because I want to install this update and figured that disabling/freezing any original stock apps might cause problems. I will look around for a thread on safely deleting apps after I get this udpate...
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
phil.culler said:
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
Click to expand...
Click to collapse
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
syntropic said:
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
Click to expand...
Click to collapse
It looks like you will need S-Off to factory lock the bootloader. S-Off allows you to make changes to otherwise protected areas of the file system. To clarify, I haven't tried this method myself as I haven't had a need to factory relock my device yet. I ran full stock for months before I rooted. As for HTC knowing whether or not you unlocked your bootloader, if you used the HTCDEV method then they have record of you receiving an unlock token from them but if they go into bootloader for any reason and see Locked instead of Relocked they shouldnt give you any trouble I would think. I believe you can also reset it to S-On but again I've never tried and I'm not sure its entirely safe. You'll have to look into that.
Greetings- I have an M8 running CM12 (nightly)
main 4.20.666.1
hboot 3.19.0.0.0000
S-On
CM12 nightly
twrp2.6
SuperSU
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to. My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Tried Firewater and got the PIE error.
You guys are doing a great job here- I've learned alot lurking and hope to continue...
cheerss
Superflous said:
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to.
Click to expand...
Click to collapse
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Superflous said:
My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Click to expand...
Click to collapse
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Superflous said:
Tried Firewater and got the PIE error.
Click to expand...
Click to collapse
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
redpoint73 said:
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Click to expand...
Click to collapse
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
ckpv5 said:
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
Click to expand...
Click to collapse
Certainly great to have it in one place, and thanks for doing so!
redpoint73 said:
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
Click to expand...
Click to collapse
tx for recovery link, sorry if it wasn't explained right but i want to restore my phone back to Bell firmware and lollipop . I spoke with the Root ninja via email ans Sunshine won't work on my phone(their words). I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware. If this isn't right I would sure appreciate the path to the correct way to put my phone back to original. Tx for you help
Superflous said:
I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware.
Click to expand...
Click to collapse
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
'
so then I'm looking for a stock ROM from the carrier for firmware 4.20.666.1
tx again Redpoint
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Superflous said:
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Click to expand...
Click to collapse
You're very welcome. Glad to see it worked out well for you.
Please click the "Thanks" button for any posts you found helpful.
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.
Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?
Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!