Hey guys,
First post and thread, unfortunately. May have been done before, so sorry if that's the case (and if it is I guess a quick link can clear this confusion up!)
I've got a tmobile HTC One M8 running Android 4.4.4 with an unlocked boot loader, clockworkmod 6.0.4.8 with s-on.
New android update is out and while I'm not necessarily keen on updating it, the icon is annoying. As well, I originally rooted the phone for some apps and sorts that I don't even use and I'm mainly interested in just bringing the phone back to a stock recovery so I can unroot it.
Tried using the RUU posted but I believe due to the s-on and unlocked boot loader, it doesn't work for me. Step one is an error on it.
What can I do here to bring the phone back to stock recovery? I'm not 100% I made a backup before I put cwm on it. May have but for arguments sake let's say I didn't.
Any and all help is appreciated. thanks so much everyone.
Metilinos said:
Tried using the RUU posted but I believe due to the s-on and unlocked boot loader, it doesn't work for me. Step one is an error on it.
Click to expand...
Click to collapse
RUUs run fine with s-on, and I don't know why folks keep posting that it doesn't.
But you do however, need to relock the bootloader (since you are s-on) to run the RUU. Its absolutely mandatory (with s-on), and almost certainly why the RUU fails. THe RUU also needs to match your CID (but if you are properly trying a T-Mob RUU on a T-Mob version M8, that is not the issue), and further you cannot "downgrade" or run an older version RUU (older hboot) than what is on the phone.
But again, unlocked bootloader alone will make the RUU fail.
I haven't really seen a whole lot of s-off since firewater hasn't worked any longer. I kind of figured the unlocked bootloader was an issue as well. Mobile right now and working so not a whole lot I can do. Basically make sure the CID matches the RUU and relock the bootloader and I should be good to go? I picked up the T-Mobile RUU and I have a tmobIle M8, I didn't really think to check the CID, I just mainly assumed the failed run was from other sources.
Metilinos said:
I haven't really seen a whole lot of s-off since firewater hasn't worked any longer. I kind of figured the unlocked bootloader was an issue as well. Mobile right now and working so not a whole lot I can do. Basically make sure the CID matches the RUU and relock the bootloader and I should be good to go? I picked up the T-Mobile RUU and I have a tmobIle M8, I didn't really think to check the CID, I just mainly assumed the failed run was from other sources.
Click to expand...
Click to collapse
As long as you have the right carrier RUU, the CID will also match. I assume T-Mobile US? As there is also T-Mobile in Europe.
As long as its right carrier (CID) and not trying to run an older version RUU, the unlocked bootloader is the only problem.
Yes T-Mobile US.
I'll have to double check the RUU, I'm pretty sure I grabbed it off here from a different thread, but like you said, the unlocked bootloader obviously was an issue.
In the case, and I'm assuming it's rare, that it could be that, is there an easy way to tell whether or not I have the most current RUU?
Thanks a bunch, really appreciating the help. I've been kind of at a standstill with this and haven't really tried much in fear of killing the phone.
Metilinos said:
In the case, and I'm assuming it's rare, that it could be that, is there an easy way to tell whether or not I have the most current RUU?
Click to expand...
Click to collapse
Do you mean its rare to run the wrong version RUU? If so, I'd say no, its not rare at all. Folks are often not aware of the version requirement (with s-on, this requirement is bypassed with s-off) and try to run an "old" RUU.
All the T-Mob US RUUs are posted here: http://forum.xda-developers.com/showthread.php?t=2714456
3.32 is Android 4.4.4
4.20 is Android 5.0
3.32 is what I have at the moment. With android 5 coming over the air a week or so ago for myself and 4.4.4 being on the phone when I got it just a couple months back, that's what I guess I was insinuating by rare. But thank you a bunch for your help. Again it's very much appreciated. Obviously got myself in a little over my head here.
Related
I currently hate myself for my silly failure. Oh jeez, its embarrassing to explain but I was in a rush and didn't realize I was in the HTC One international ROM section and downloaded and installed ARHD not knowing my Verizon HTC One wouldn't work. Sigh, big failure on my part, I was trying to go skate but looks like I'm spending my Friday fixing my issues :crying:
Well, when in bootloader it tells me that my phone is unlocked and currently S=OFF. I have CWM Recovery flashed on it at the moment. I tried sideloading CM11 on, but ADB doesn't detect my device. Yet the strange part is Fastboot does. I have work in a little and desperately need my phone up and running before hand. (as my job revolves around my phone.)
Please, anyone out there know my situation? I've spent all day trying to find my solutions so i decided to turn to the experts. :fingers-crossed:
Find a ruu on this forum
Sent from my HTC One VZW using Tapatalk 4
coldconfession13 said:
Find a ruu on this forum
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
I've actually just recently been looking into that. Can I do it with s=off, the tutorials I've been reading for sprint HTC One's are saying to relock it?
Yea I believe Santod has a thread
Sent from my HTC One VZW using Tapatalk 4
coldconfession13 said:
Yea I believe Santod has a thread
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
I hate to be the n00b, but I already freaked up my phone once. (Thankfully its not really bricked) I can't lie, I'm pretty scared to fully mess it up haha. Is there anyone who can help me through it? I understand the steps on which through fastboot, but its the little things that I am not sure of.
Just do the ruu. No need to relock or s-on. What little things are you worried about? Ive seen threads that say you need to relock it too. But i knkw for a fact its not needed, as i did an ruu yesterday while s-off and unlocked in order to take the kk ota. Never lost s-off and never lost my unlocked status, despite hboot being downgraded and then upgraded.
cmlusco said:
Just do the ruu. No need to relock or s-on. What little things are you worried about? Ive seen threads that say you need to relock it too. But i knkw for a fact its not needed, as i did an ruu yesterday while s-off and unlocked in order to take the kk ota. Never lost s-off and never lost my unlocked status, despite hboot being downgraded and then upgraded.
Click to expand...
Click to collapse
Where do you get the correct Verizon RUU? Just purchased a used phone with S off / Rooted / with custom recovery.
Thanks. Trying to get the OTA Kit Kat to work..
http://forum.xda-developers.com/showthread.php?t=2485319
Bottom of second post.
cmlusco said:
http://forum.xda-developers.com/showthread.php?t=2485319
Bottom of second post.
Click to expand...
Click to collapse
Thank you for the lead. So any of these will work?
1.10.605.08 Decrypted RUU
1.10.605.10 Signed RUU
1.10.605.15 Decrypted RUU
1.10.605.15 Signed RUU
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Decrypted if you are S Off?
Signed if you S on?
Is my understanding correct in that I would need to Re-Lock the bootloader as well?
Yes they will all work, it dosent matter if its signed or not since your unlocked and s-off. 2.10.605.1 is obviously the newst. And no you do not need to relock the bootloader, i dont know how that mith ever got started.
Hi there.
So In short I'm a Nexus 5 user and as you can imagine unlocking that phone is literally 2 minutes at most using fastboot.
I got myself a brand spanking new HTC One m8 on Vodafone UK, however I hate Sense UI and would love to "transform" my phone to GPE edition.
I have few questions hopefully easy to answer. reading through the forums gives me a headache.
1. Do I need a S-Off if I want to convert my GSM to GPE? Thought its just a matter of flashing a rom? (I do know the answer to this but just cant believe it)
2. My phone is network locked, should I unlock it first and than run sunshine or the other way around (I've heard people having problems when they try to unlock after sunshine)
3. Do I need to backup my stock Vodafone Image if I want to return to stock at some point? I had HTC Desire/HD and returning back to stock was matter of flashing RUU back in the days (these seem to be provided on HTCDev now). But it looks like a lot has changed since then.
4. What order of operations? Please correct me if I'm wrong: Unlock Bootloader (Any other way than HTC Dev?) --> TWRP-->Root-->Sunshine-->Backup Image-->Convert to GPE
I'm absolutely fine with using fastboot etc (no toolkits for the wicked ) although most guides involve Windows and im on Mac... Anyone had any issues ?
Appreciate any help
Thanks
Nexus phones are designed to be developer phones, so they make it as easy as possible. (Though, and this is an important note, they still keep secure boot enabled...) The HTC One, like most consumer oriented devices, isn't quite the same.
First off, yes, you will need to S-off your phone to do a complete version change. You will also need to change your CID/MID if you want OTA updates. None of this has anything to do with SIM locking, though there is a thread you might consult once you are S-off. It may or may not work with HBOOT 3.19, but once you are S-off, you can downgrade to an older HBOOT that does fully support SIM unlocking.
If you want to ever go back, you will also need to install TWRP or CWM like always and make a nandroid backup. You don't have to be S-off to do this, but Sunshine unlocks your bootloader in the process, which you WILL need to do.
If your device is supported (because some newer firmware versions aren't) I would suggest using Sunshine S-off to unlock your bootloader and S-off your phone. At that point, flash over a custom recovery and backup your current install. Then, use the instructions here to switch your CID/MID and install the appropriate GPE version. Note! You *CAN* use a GPE RUU, but that will change the partitioning on the device making it very hard to go back.. I would strongly recommending using using a GPE backup and leaving the partition tables alone, but that's just me.
jshamlet said:
Nexus phones are designed to be developer phones, so they make it as easy as possible. (Though, and this is an important note, they still keep secure boot enabled...) The HTC One, like most consumer oriented devices, isn't quite the same.
First off, yes, you will need to S-off your phone to do a complete version change. You will also need to change your CID/MID if you want OTA updates. None of this has anything to do with SIM locking, though there is a thread you might consult once you are S-off. It may or may not work with HBOOT 3.19, but once you are S-off, you can downgrade to an older HBOOT that does fully support SIM unlocking.
If you want to ever go back, you will also need to install TWRP or CWM like always and make a nandroid backup. You don't have to be S-off to do this, but Sunshine unlocks your bootloader in the process, which you WILL need to do.
If your device is supported (because some newer firmware versions aren't) I would suggest using Sunshine S-off to unlock your bootloader and S-off your phone. At that point, flash over a custom recovery and backup your current install. Then, use the instructions here to switch your CID/MID and install the appropriate GPE version. Note! You *CAN* use a GPE RUU, but that will change the partitioning on the device making it very hard to go back.. I would strongly recommending using using a GPE backup and leaving the partition tables alone, but that's just me.
Click to expand...
Click to collapse
Thanks a lot for that.
Could your please clarify your last 2 sentences. This is first I hear about. If I use GPE backup will I be able to get OTA updates? Where can I find GPE backup rather than RUU. I think most here are RUU's.
Or do you mean GPE ROM vs GPE RUU?
MattSkeet said:
Thanks a lot for that.
Could your please clarify your last 2 sentences. This is first I hear about. If I use GPE backup will I be able to get OTA updates? Where can I find GPE backup rather than RUU. I think most here are RUU's.
Click to expand...
Click to collapse
The partition sizes are different between GPE and Sense, with Sense having a much larger /system partition than GPE. If you convert from Sense to GPE fully (using an RUU), then you will have to use an RUU to go back to Sense or the /system partition won't be large enough. If you just restore a nandroid backup of GPE to a Sense partitioned device, it will still work fine and you can revert back without any special effort.
S-off yes carrier unlocking yes and I'm an ex nexus 5 user as well
Sent from my HTC One_M8 using XDA Free mobile app
MattSkeet said:
3. Do I need to backup my stock Vodafone Image if I want to return to stock at some point? I had HTC Desire/HD and returning back to stock was matter of flashing RUU back in the days (these seem to be provided on HTCDev now). But it looks like a lot has changed since then.
Click to expand...
Click to collapse
I don't believe HTC posts RUUs to HTCDev.com any longer. There is a RUU floating around for the "generic" WWE version, but for Vodaphone or other carrier branded versions outside the US, you probably won't find any RUUs.
Therefore, its always good to at least make a nandroid before making any other changes. Or you can find the stock nandroid for your CID here:
http://forum.xda-developers.com/showthread.php?t=2701376
MattSkeet said:
4. What order of operations? Please correct me if I'm wrong: Unlock Bootloader (Any other way than HTC Dev?) --> TWRP-->Root-->Sunshine-->Backup Image-->Convert to GPE
Click to expand...
Click to collapse
I believe you can temp root, sunshine s-off and use sunshine to unlock the bootloader and bypass HTCDev.com. But I haven't done it that way personally, so I'm not 100% on that.
redpoint73 said:
I don't believe HTC posts RUUs to HTCDev.com any longer. There is a RUU floating around for the "generic" WWE version, but for Vodaphone or other carrier branded versions outside the US, you probably won't find any RUUs.
Therefore, its always good to at least make a nandroid before making any other changes. Or you can find the stock nandroid for your CID here:
http://forum.xda-developers.com/showthread.php?t=2701376
I believe you can temp root, sunshine s-off and use sunshine to unlock the bootloader and bypass HTCDev.com. But I haven't done it that way personally, so I'm not 100% on that.
Click to expand...
Click to collapse
http://www.htcdev.com/devcenter/downloads/P00 there are RUU's here which is very strange and makes it confusing in regards to backing everything up if its there
MattSkeet said:
http://www.htcdev.com/devcenter/downloads/P00 there are RUU's here which is very strange and makes it confusing in regards to backing everything up if its there
Click to expand...
Click to collapse
The only RUU there is T-Mobile US. All the rest are kernel source (and a couple framework support) files. Keep in mind, the RUU is something like 1.6 GB.
Note that there are other RUUs, they just aren't posted there. The Developer Edition has an RUU, and there is an older one for AT&T floating around somewhere as well.
I really don't understand why HTC doesn't make these more available, as they are a great way to reset a phone short of warranty service. I would think they would want people to have these as an option.
jshamlet said:
Note that there are other RUUs, they just aren't posted there. The Developer Edition has an RUU, and there is an older one for AT&T floating around somewhere as well.
Click to expand...
Click to collapse
Yes, in fact AT&T has RUUs for every major OTA build its released so far. Sprint and T-Mobile US also have RUUs. Of the major US carriers, only Verizon does not have RUUs.
I haven't seen any official RUU releases outside the US. I know there is a WWE 3.28.401 RUU think is being linked lately, but I don't know if that is a leak, or something more official. But otherwise, RUUs don't exist outside the US (or only as leaks). What makes the US so special, I don't know.
jshamlet said:
I really don't understand why HTC doesn't make these more available, as they are a great way to reset a phone short of warranty service. I would think they would want people to have these as an option.
Click to expand...
Click to collapse
I don't get it either. On past devices, I've seen specific reports of HTC support directing folks to RUU when they have software issues (after the "usual" solutions like factory reset didn't help).
I'm currently bone-stock AT&T, 4.4.2. I'm frustrated by the lack of OTAs from AT&T, especially given that the 4.4.4 was reportedly pulled. So I'm considering converting to Dev Edition to get timely updates and I'd like to make sure I have all of my ducks in a row before I begin.
Am I correct with these steps and order?
1. Unlock bootloader (htcdev key)
2. s-off
3. Change MID and CID as appropriate
4. Run the 5.0.1 RUU that HTC posted
5. ???
6. Profit
Thanks!
Close
Skip HTCDev, because Sunshine will take care of that for you. Once you are S-off, you can trivially lock/unlock your bootloader, and by skipping HTCDev, you can potentially avoid losing your warranty.
jshamlet said:
Close
Skip HTCDev, because Sunshine will take care of that for you. Once you are S-off, you can trivially lock/unlock your bootloader, and by skipping HTCDev, you can potentially avoid losing your warranty.
Click to expand...
Click to collapse
I literally just saw (and did) this with Sunshine. Thanks for the tip. Everything else looks good on the list though, right?
OGhoul said:
I literally just saw (and did) this with Sunshine. Thanks for the tip. Everything else looks good on the list though, right?
Click to expand...
Click to collapse
Yup, except I forgot to mention that you only have to change the CID. The MID is already correct. (The Developer Edition is essentially the same as the AT&T edition, but has a different CID)
You would have figured that out on your own, and it wouldn't have hurt to attempt to change it, but it's not necessary on your device.
jshamlet said:
Yup, except I forgot to mention that you only have to change the CID. The MID is already correct. (The Developer Edition is essentially the same as the AT&T edition, but has a different CID)
You would have figured that out on your own, and it wouldn't have hurt to attempt to change it, but it's not necessary on your device.
Click to expand...
Click to collapse
I've already got the tabs open for the adb steps for that on my home PC. Thanks a bunch; you've confirmed that I actually have learned something from lurking around here all this time.
I have the Tmobile version. Will this same thing work as well, just changing the CID and flashing the 5.0.1 RUU?
I already have S-Off and unlocked bootloader. Everything else is the same from when I got it. Stock 4.4.4 Sense, Stock recovery (No CWM or TWRP), with T-Mobile CID.
vjaamm said:
I have the Tmobile version. Will this same thing work as well, just changing the CID and flashing the 5.0.1 RUU?
I already have S-Off and unlocked bootloader. Everything else is the same from when I got it. Stock 4.4.4 Sense, Stock recovery (No CWM or TWRP), with T-Mobile CID.
Click to expand...
Click to collapse
Yes, except you *DO* have to change your MID.
http://forum.xda-developers.com/showthread.php?t=2708581
And slightly off topic, the 5.0.1 RUU will update my firmware to what would be required for any of the (Sense-based) Lollipop ROMS (like ARHD) right? I won't have to incrementally flash firmwares, will I?
OGhoul said:
And slightly off topic, the 5.0.1 RUU will update my firmware to what would be required for any of the (Sense-based) Lollipop ROMS (like ARHD) right? I won't have to incrementally flash firmwares, will I?
Click to expand...
Click to collapse
No you won't. The Developer edition has the latest firmware needed by the latest ROMs 4.x
So you'll be good to go.
I actually had to do some monkey business to get this to work.
I changed my CID to Super CID, then adb fastboot bootloader. Then ran the RUU .exe. This started to work, however it failed at I think step 5 telling me my CID was wrong, and the .exe told me to hold power for 10 seconds to reboot.
This then booted back into 4.4.2, and settings > about still said 4.4.2.
fastboot getvar all however, revealed all of the lollipop firmware settings.
So I rebooted to fastboot again, then changed my CID to the BS_US002.
Ran the RUU again. It took, and it's currently optimizing apps.
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!
So I bought this 'new' phone with the intention of rooting it and got to the point of updating to the latest firmware before root. turns out the phone is already 'modified'. contacted htc support looking for a means to restore factory specs but they say it has been rooted and it'll take another 2-3 days before i can further pursue the issue.
wondering if someone here can enlighten me as to how i'd restore stock before i re-root (there's no telling what mischief the rooter was up to). it was pretty easy on my old samsung with odin but this is my first htc so i'm in unknown territory here. the phone is in an otherwise impeccable state so i'm not really bothered about returning it since i can't imagine anything that might survive a factory reflash.
a little guidance would be much appreciated!
Take a look at the ReadMe thread. The RUU section most likely contains everything you need. I personally recommend the SD card method. It's the easiest and most fail-safe one.
Sent from my HTC One M9 using XDA Labs
Been poring through it but frankly it is overwhelming. Wonder if you could answer a few noob questions.
1. the ruu section says not to re-lock the bootloader. will flashing an ruu re-lock the bootloader?
2. found my ruu which seems to be a sprint cdma version (sku:651). however the cid (SPCS_001) does not match with mine (11111111). not sure where to find the MID. where does this mismatch leave me?
3. will flashing the sprint cdma fw lock my carrier (ie prevent me from using other sim cards)
4. does the ruu rewrite/restore all of the partitions e.g. including recovery? (considering an unknown person has rooted and tinkered with the phone).
jbonetwo said:
Been poring through it but frankly it is overwhelming. Wonder if you could answer a few noob questions.
Click to expand...
Click to collapse
Yes, you can. Follow-up questions are always welcome. (In contrast to questions that obviously show that people were too lazy to read anything. )
jbonetwo said:
the ruu section says not to re-lock the bootloader. will flashing an ruu re-lock the bootloader?
Click to expand...
Click to collapse
No. Re-locking the bootloader requires the usage of a certain fastboot command.
jbonetwo said:
found my ruu which seems to be a sprint cdma version (sku:651). however the cid (SPCS_001) does not match with mine (11111111). not sure where to find the MID. where does this mismatch leave me?
Click to expand...
Click to collapse
Your phone currently uses the SuperCID. That CID had a whole bunch of benefits on older HTC devices. It lost most of them on the M9, though. Changing the CID is only possible with S-OFF. I highly recommend you to use the conversion guide for restoring your phones original CID. (CDMA versions of the M9 can't get converted to different variants without breaking them. If you're able to get mobile reception with that phone then it didn't get converted and you definetely own a Sprint M9. You don't have to look for the MID in this case.)
jbonetwo said:
will flashing the sprint cdma fw lock my carrier (ie prevent me from using other sim cards)
Click to expand...
Click to collapse
I can't answer that question since sim locks don't exist in the European firmware versions of this phone and I therefore don't have much experiences with them.
jbonetwo said:
does the ruu rewrite/restore all of the partitions e.g. including recovery? (considering an unknown person has rooted and tinkered with the phone).
Click to expand...
Click to collapse
Yes, it does. RUUs overwrite everything on your phone with their files.
thank you for taking the time!
Flippy498 said:
If you're able to get mobile reception with that phone then it didn't get converted and you definetely own a Sprint M9. You don't have to look for the MID in this case.)
Click to expand...
Click to collapse
definitely a sprint m9 then. i wonder if they're rooting/unlocking sim-locked sprints and reselling them as unlocked phones.
will have to confirm the sim lock detail with htc support either way. but it's starting to look like i may have to return the phone. disappointing but at least rooting and flashing a genuine one is gonna be a breeze now