Related
Debranded my handset with a stock HTC ROM, and now instead of getting OTA updates earlier I get them later. The check for update box does absolutely nothing.
Can anyone help me ascertain why? Running 2.2.1 build 1.72.405.3
Or at least help me update.
Thanks,
Jake
How did you debrand? I also debranded my phone (was on T-mobile) by using a goldcard and using that to install a stock ROM but that wasn't enough. You'll need to change your phone's CID (an ID that determines which ROMs you can install - stock, Vodafone, T-Mobile etc), or SuperCID (install any ROM).
In order to do that, you will probably need to downgrade your ROM. Simply follow this guide:
http://forum.xda-developers.com/showthread.php?t=905003
After the downgrade, follow these steps:
http://forum.xda-developers.com/showthread.php?t=857537
The author's Easy Radio Tool allows you to do various things (S-OFF, SimUnlock, SuperCID). The only thing you need to do to get the OTA is to perform the last command in the list on the application (Stock CID), although of course you can do all the other stuff as well.
I just simply did the Stock CID and immediately afterward could get the update notification. My previously T-Mobile Desire HD is now running the shiny new 2.3 update nicely.
How do I check whether I have SuperCID, as I followed this tutorial here:
http://forum.xda-developers.com/showthread.php?t=857444
So I *should* have it.
I debranded by following the above tutorial and installing a stock ROM which I downloaded from here.
According to this post,
Checking the device state:
- Go to the bootloader (turn fastboot off, turn off phone, hold vol- and power)
- If it says ACE PVT SHIP S-OFF in the first line, your device is Radio S-OFF
- If it says ACE PVT ENG S-OFF, you have ENG S-OFF, go to System info
- If system info CID is 11111111, your device is SuperCID
- And if you can verify either Radio S-OFF or SuperCID (and you did both), it worked fine and you have both of them
- You can check your original CID by going to radio tool folder with cmd and typing: "adb shell getprop ro.cid"
Click to expand...
Click to collapse
Although SuperCID allows you to install RUUs from anywhere, I wonder if it would also prevent you from getting the OTA update. It's possible that, when you preform a check, the phone sends your CID to HTC's servers which see if your CID has an update, and a CID of 11111111 will never have. If all else fails, try setting your CID to the stock HTC one rather than SuperCID.
Ah I don't have ENG S-OFF, and when I go into FASTBOOT and select BOOTLOADER it returns me to the 'main menu', followed by a short period where everything is non responsive and a brief message flashed in green about a few files. Is this normal when attempting to access the BOOTLOADER menu with ENG S-OFF?
Yes that's normal. I believe the delay is the bootloader scanning the SD card for a firmware file.
So I can't check my SID?
To check it I have to get ENG S-OFF, and to get ENG S-OFF I have to permroot my phone, for which I have to flash back to a 1.32 build...
Also, if I flash back to 1.32 to permroot and S-OFF etc, and *then* I finally update OTA to the latest will that not remove my permroot and S-OFF like it did with the 1.72 OTA update? Would I have to install a full RUU rather than update? But then surely I can never update...
This confuses me.
If you update using the OTA, you will lose your root but you won't lose your S-OFF as far as I'm aware. According to the instructions on the One click Radio S-OFF tool, in order to revert back to stock you have to use the tool again to S-ON, which implies that S-OFF is retained between firmware updates.
So, if you permroot (downgrading to 1.32 if needs be) and then use the Radio S-OFF tool to set your CID to stock you should be able to get the OTA update and get future ones too.
*Edit* just looking at the instructions for the One Click tool, it looks like you can do a temproot if you just want to set the CID to stock.
Every time I run visionary and try to temproot it gets stuck on the plain black screen after the "attempting to temproot now". Have to press the home key (and wait) to back out of the app, any successive launches just take me straight back there.
Are you sure you've downgraded and running the 1.32.405.6 ROM? Have you got USB debugging enabled?
Sent from my Desire HD using XDA App
So I have been out of the loop for HTC devices and came to a brick wall known as S-Off for current devices.
I am trying to convert two phones for a friend and he is willing to pay the $25 for each for Sunshine, I want to try FireWater but cannot locate the APK just to try, I am aware of the low percentage of success, but if I can save him $50 I'll give that a try. I want to make both phones STOCK T-Mobile, no Root, DeOdexed, etc. After much reading, found out can't change CID and MID without S-Off
MMS was the main issue not receiving, also them wanting WiFi calling. I have unlocked bootloader and have put a 4.4.2 T-Mobile ROM that works fine, but don't want the "updates" to be a issue. I then tried applying a TWRP Restore of 5.0.1 Lollipop and everything EXCEPT WiFi works, bummer and since I can't flash a radio without S-Off.
So in order:
1) Should I even try FireWater at this point (also, can't locate the APK so if any of you have it PM me please)?
2) Changing CID and MID will allow me to do use the HTC RUU Stock T-Mobile ROM?
3) I want to S-On after I convert, should I or just leave it?
quedijo said:
So I have been out of the loop for HTC devices and came to a brick wall known as S-Off for current devices.
I am trying to convert two phones for a friend and he is willing to pay the $25 for each for Sunshine, I want to try FireWater but cannot locate the APK just to try, I am aware of the low percentage of success, but if I can save him $50 I'll give that a try. I want to make both phones STOCK T-Mobile, no Root, DeOdexed, etc. After much reading, found out can't change CID and MID without S-Off
MMS was the main issue not receiving, also them wanting WiFi calling. I have unlocked bootloader and have put a 4.4.2 T-Mobile ROM that works fine, but don't want the "updates" to be a issue. I then tried applying a TWRP Restore of 5.0.1 Lollipop and everything EXCEPT WiFi works, bummer and since I can't flash a radio without S-Off.
So in order:
1) Should I even try FireWater at this point (also, can't locate the APK so if any of you have it PM me please)?
2) Changing CID and MID will allow me to do use the HTC RUU Stock T-Mobile ROM?
3) I want to S-On after I convert, should I or just leave it?
Click to expand...
Click to collapse
I would s-off an leave s-off. Once s-off. Myself I would change mid/cid with eng-hboot to T-Mobile then fastboot T-Mobile firmware wirh no boot.img an no stock recovery.img an thena T-Mobile stock ROM guessing your not going to find a stock unrooted ROM but maybe if not just remove root. Then I would fastboot the stock recovery an your friends devices should now be T-Mobile m8's stock unrooted.
So I have ended up keeping S-Off since there's no indication that I could 100% S-Off later according to their F.A.Q.
However if anyone else was thinking of doing the same, I did just have to change CID and MID then used the HTC Stock T-Mobile RUU package and it's like a M8 straight out of the T-Mobile store.
In case anyone would want to know, this is the process I did:
1) HTC Stock RUU to start clean as a AT&T M8 (http://www.htc.com/us/support/rom-downloads.html)
2) Followed instructions to unlock Bootloader (http://www.htcdev.com/bootloader/)
3) Used this toolkit to flash TWRP (http://forum.xda-developers.com/showthread.php?t=2699065)
4) Installed and Ran (and paid) Sunshine to S-Off the phone (http://theroot.ninja/download.html)
5) Followed instructions to change CID (http://www.droidviews.com/change-cid-mid-htc-one-devices/) *** ONLY THE CID INSTRUCTIONS *** DIDN'T USE SUPERCID, USED T-MOBILE CID ***
6) Followed instructions to change MID (http://forum.xda-developers.com/showthread.php?t=2708581)
7) Put phone in FastBoot, download and ran the HTC Stock T-Mobile RUU (http://www.htc.com/us/support/rom-downloads.html)
8) Stock, Locked Bootloader, *** Software status: Official *** with S-Off. T-Mobile ROM v.4.20.531.4 (Android Lollipop v.5.0.1)
quedijo said:
So I have ended up keeping S-Off since there's no indication that I could 100% S-Off later according to their F.A.Q.
However if anyone else was thinking of doing the same, I did just have to change CID and MID then used the HTC Stock T-Mobile RUU package and it's like a M8 straight out of the T-Mobile store.
In case anyone would want to know, this is the process I did:
1) HTC Stock RUU to start clean as a AT&T M8 (http://www.htc.com/us/support/rom-downloads.html)
2) Followed instructions to unlock Bootloader (http://www.htcdev.com/bootloader/)
3) Used this toolkit to flash TWRP (http://forum.xda-developers.com/showthread.php?t=2699065)
4) Installed and Ran (and paid) Sunshine to S-Off the phone (http://theroot.ninja/download.html)
5) Followed instructions to change CID (http://www.droidviews.com/change-cid-mid-htc-one-devices/) *** ONLY THE CID INSTRUCTIONS *** DIDN'T USE SUPERCID, USED T-MOBILE CID ***
6) Followed instructions to change MID (http://forum.xda-developers.com/showthread.php?t=2708581)
7) Put phone in FastBoot, download and ran the HTC Stock T-Mobile RUU (http://www.htc.com/us/support/rom-downloads.html)
8) Stock, Locked Bootloader, *** Software status: Official *** with S-Off. T-Mobile ROM v.4.20.531.4 (Android Lollipop v.5.0.1)
Click to expand...
Click to collapse
Nothing against the way you did it at all. But using toolkits are very bad idea I have seen many things go wrong an have fix phones soft brick after toolkit/app to flash. Just a friendly tip... An if you don't want to wipe your whole device you can use the way I stated above but glad you are converted. An good choice to keep s-off. Once you r s-off I would never turn s-on again for any reason..Also glad it went smooth for you
Thanks. I've never had an issue with Toolkits, I can see where things would go wrong, but I don't rely on them fully. I am aware it's all pretty much ADB or FastBoot commands that you're running. I like them for confirmation of commands or just as simple click, wait, done.
I'm invested in the Samsung and Sony family now and was a HTC guy in the early days of their product, back when WM6.1 only had RUU options. I actually prefer Odin stuff, which is why I prefer RUU's still, directly to hardware, so have to triple check what I'm doing. I have yet to brick a phone, of course that's thanks to having Download Mode/FastBoot as a final option
quedijo said:
So I have ended up keeping S-Off since there's no indication that I could 100% S-Off later according to their F.A.Q.
However if anyone else was thinking of doing the same, I did just have to change CID and MID then used the HTC Stock T-Mobile RUU package and it's like a M8 straight out of the T-Mobile store.
In case anyone would want to know, this is the process I did:
1) HTC Stock RUU to start clean as a AT&T M8 (http://www.htc.com/us/support/rom-downloads.html)
2) Followed instructions to unlock Bootloader (http://www.htcdev.com/bootloader/)
3) Used this toolkit to flash TWRP (http://forum.xda-developers.com/showthread.php?t=2699065)
4) Installed and Ran (and paid) Sunshine to S-Off the phone (http://theroot.ninja/download.html)
5) Followed instructions to change CID (http://www.droidviews.com/change-cid-mid-htc-one-devices/) *** ONLY THE CID INSTRUCTIONS *** DIDN'T USE SUPERCID, USED T-MOBILE CID ***
6) Followed instructions to change MID (http://forum.xda-developers.com/showthread.php?t=2708581)
7) Put phone in FastBoot, download and ran the HTC Stock T-Mobile RUU (http://www.htc.com/us/support/rom-downloads.html)
8) Stock, Locked Bootloader, *** Software status: Official *** with S-Off. T-Mobile ROM v.4.20.531.4 (Android Lollipop v.5.0.1)
Click to expand...
Click to collapse
Hi, I just gained access to my bootloader, rooted my phone, bought sunshine and was able to get the phone to S-off, Changed my CID and MID and got the most current RUU from T-Mobile and am flashing now! initially the dialog box that pops up advises that it will take 10 minutes or more...well I am at about 2 hours now and the flash is still not completed...how long does this take????....
quedijo said:
So I have ended up keeping S-Off since there's no indication that I could 100% S-Off later according to their F.A.Q.
However if anyone else was thinking of doing the same, I did just have to change CID and MID then used the HTC Stock T-Mobile RUU package and it's like a M8 straight out of the T-Mobile store.
In case anyone would want to know, this is the process I did:
1) HTC Stock RUU to start clean as a AT&T M8 (http://www.htc.com/us/support/rom-downloads.html)
2) Followed instructions to unlock Bootloader (http://www.htcdev.com/bootloader/)
3) Used this toolkit to flash TWRP (http://forum.xda-developers.com/showthread.php?t=2699065)
4) Installed and Ran (and paid) Sunshine to S-Off the phone (http://theroot.ninja/download.html)
5) Followed instructions to change CID (http://www.droidviews.com/change-cid-mid-htc-one-devices/) *** ONLY THE CID INSTRUCTIONS *** DIDN'T USE SUPERCID, USED T-MOBILE CID ***
6) Followed instructions to change MID (http://forum.xda-developers.com/showthread.php?t=2708581)
7) Put phone in FastBoot, download and ran the HTC Stock T-Mobile RUU (http://www.htc.com/us/support/rom-downloads.html)
8) Stock, Locked Bootloader, *** Software status: Official *** with S-Off. T-Mobile ROM v.4.20.531.4 (Android Lollipop v.5.0.1)
Click to expand...
Click to collapse
Funny I can get to step 7, but when I do step 7, I get ERROR [159] Image Error
Hi there im new with htc phones i have buy htc one m8 and there was 4.4.3 android operating system when i buy there was unlocked bootloader but s-on and i have tryed install with twrp android 5.0.1 but its only boots once and bick after reboot so i wanna stock rom to use phone normal and all the rom's ruu dosn't installs i get error so can any one say what firmware version are for my htc ? here is bootloader info
imei:
imei2: Not Supported
meid: 00000000
product: m8_ul
platform: hTCB
modelid: 0P6B10000
cidnum: ORANGB10
battery-status:Good
battery-voltag
partition-layoout:Generic
security: on
build-mode: SH
boot-mode: FAS
commitno-bootl
hbootpreupdate
gencheckpt: 0
After Xperia phone this phone gives me to many questions about software ...
Ainster said:
was unlocked bootloader but s-on and i have tryed install with twrp android 5.0.1 but its only boots once and bick after reboot
Click to expand...
Click to collapse
You need to update your firmware to run Android 5.0 ROMs.
Ainster said:
all the rom's ruu dosn't installs i get error
Click to expand...
Click to collapse
What error number(s)?
You need to run the RUU that matches your CID and MID. It sounds like you may have tried more than one (and possibly RUUs not meant for your CID,MID).
Also, since you are s-on, you need to relock the bootloader to RUU. This is done with fastboot, using the command: fastboot oem lock
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Ainster said:
here is bootloader info
imei: Delete
imei2: Not Supported
meid: 00000000
product: m8_ul
platform: hTCB
modelid: 0P6B10000
cidnum: ORANGB10
battery-status:Good
battery-voltag
partition-layoout:Generic
security: on
build-mode: SH
boot-mode: FAS
commitno-bootl
hbootpreupdate
gencheckpt: 0
Click to expand...
Click to collapse
You left out much of the important getvar data, while leaving in something you should never post online (IMEI) since its personal data. I've notified the mods to delete your IMEI.
I have deleted imei i got error that ruu cant read bootloader if i remember 199 error and what kind of information you need to help me find what software match for my htc ? By the way i was tryed with locked bootloader still same error
Ainster said:
i got error that ruu cant read bootloader if i remember 199 error
Click to expand...
Click to collapse
Not familiar with that error. Are you sure that is what it says? You can run the RUU again to make sure.
Ainster said:
what kind of information you need to help me find what software match for my htc ?
Click to expand...
Click to collapse
hboot number
main version number
What RUUs you are trying.
redpoint73 said:
Not familiar with that error. Are you sure that is what it says? You can run the RUU again to make sure.
hboot number
main version number
What RUUs you are trying.
Click to expand...
Click to collapse
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .
Ainster said:
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .
Click to expand...
Click to collapse
I don't know if there is an RUU for your CID. I'm guessing no.
If that is the case, you can try to return to stock 4.4.2 ROM (for your CID) and stock recovery, OTA update all the way up to Lollipop (which will update the firmware). Then you can run the current custom ROMs.
redpoint73 said:
I don't know if there is an RUU for your CID. I'm guessing no.
If that is the case, you can try to return to stock 4.4.2 ROM (for your CID) and stock recovery, OTA update all the way up to Lollipop (which will update the firmware). Then you can run the current custom ROMs.
Click to expand...
Click to collapse
So i whould try the RUU of 4.4.2rom with this CID ? By the way did i need to find my cid rom becouse when i buy phone there was unoficial rom with sence ... And bootloader unlocked only this CID can match on my htc ?
Ainster said:
So i whould try the RUU of 4.4.2rom with this CID ? By the way did i need to find my cid rom becouse when i buy phone there was unoficial rom with sence ... And bootloader unlocked only this CID can match on my htc ?
Click to expand...
Click to collapse
You can flash most 4.4.2 ROMs (stock or custom), and it will at least get the running again.
If you can find an RUU for your CID, it doesn't matter which build. It will re-image all software and firmware. The only restriction is that you cannot go backwards ("downgrade") with s-on. Otherwise, you can RUU to 4.4.3, 4.4.4 or 5.0. But the RUU must match your CID and MID.
The only way to change CID and MID is with s-off. S-off is by sunshine, and requires a device that can boot into OS.
Ainster said:
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .
Click to expand...
Click to collapse
Try changing you CID. Just connect your device to a computer and open ADB. Boot your phone into fastboot (it should say "Fastboot USB"). Then copy paste:
fastboot oem writeCID T-MOB010
Sent from my HTC One_M8 using XDA Free mobile app
note_3_t-mo said:
Try changing you CID. Just connect your device to a computer and open ADB. Boot your phone into fastboot (it should say "Fastboot USB"). Then copy paste:
fastboot oem writeCID T-MOB010
Click to expand...
Click to collapse
You need s-off to change CID.
Tryed one got error 130 model id error so id dosn't match ... Maybe some one have ideas how to find RUU with same ID and CID ? Becouse HTC is hard to find Sony much easyer download xperia firm and choose any of words rom's on htc I dosn't think sometink like that program are ??? Or any other solutions maybe with out S-Off?
Ainster said:
Tryed one got error 130 model id error so id dosn't match ... Maybe some one have ideas how to find RUU with same ID and CID ?
Click to expand...
Click to collapse
It seems you are just running RUUs without much reason or methodology? Any saying "one" gave you an error without any info on which RUU doesn't tell us enough for us to help you properly.
The carrier name is usually indicated in the RUU file name, plus the build number is also indicated. For instance, it looks like ORANGB10 corresponds to software build numbers xx.xx.69 where the "69" is specific to your CID. Therefore, you want to be looking for an RUU with the build number xx.xx.69 in the filename, assuming such an RUU exists.
But honestly, I've searched around and don't seen any reference to an RUU for ORANGB10, so I'm inclined to believe you are looking for something that doesn't exist.
Ainster said:
Or any other solutions maybe with out S-Off?
Click to expand...
Click to collapse
I've already given you 2 solutions that will work with s-on:
1) Flash a stock or custom ROM with Android 4.4.2 base, using TWRP. This will at least get the phone bootable again. The firmware will still be outdated, and you won't be able to run any current ROMs. But at least the phone will work.
2) Revert to the stock nandroid backup you made before flashing any ROMs, if you made one (and you really always should before flashing any ROMs on any Android device). From there, return to stock recovery, and you should be able to OTA update in order to update firmware.
Stock recovery files can be found here: http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
Note that if the exact stock recovery for your main/build version is not available, the recovery for the same "base" should work (as noted in Post #3 of the above linked thread). Example, if your stock main version is 1.54.69, than any stock recovery corresponding to build 1.54.xx should work.
3) If you didn't make a nandroid backup, you can try to find the stock nandroid for your CID. You will want the stock nandroid that corresponds to your present main version, which you say is not listed (common TWRP bug) but based on your hboot number (3.16) your main version is proabably 1.xx
I don't see a stock nandroid posted for your CID on the following threads. So you may post to one of those threads, and see if someone can post a nandroid for you:
http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The goal here is to get back to the stock ROM (and the build number that corresponds to your firmware) and stock recovery, same as Method 2 above. Then OTA up to Lollipop in order to update firmware.
4) Get the phone running again, per Method 1 above. Then run sunshine to S-off. Once you have s-off you can "manually" update the firmware. It seems you want to avoid paying for sunshine. But if none of the above methods are satisfactory, this may be your last option.
redpoint73 said:
It seems you are just running RUUs without much reason or methodology? Any saying "one" gave you an error without any info on which RUU doesn't tell us enough for us to help you properly.
The carrier name is usually indicated in the RUU file name, plus the build number is also indicated. For instance, it looks like ORANGB10 corresponds to software build numbers xx.xx.69 where the "69" is specific to your CID. Therefore, you want to be looking for an RUU with the build number xx.xx.69 in the filename, assuming such an RUU exists.
But honestly, I've searched around and don't seen any reference to an RUU for ORANGB10, so I'm inclined to believe you are looking for something that doesn't exist.
I've already given you 2 solutions that will work with s-on:
1) Flash a stock or custom ROM with Android 4.4.2 base, using TWRP. This will at least get the phone bootable again. The firmware will still be outdated, and you won't be able to run any current ROMs. But at least the phone will work.
2) Revert to the stock nandroid backup you made before flashing any ROMs, if you made one (and you really always should before flashing any ROMs on any Android device). From there, return to stock recovery, and you should be able to OTA update in order to update firmware.
Stock recovery files can be found here: http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
Note that if the exact stock recovery for your main/build version is not available, the recovery for the same "base" should work (as noted in Post #3 of the above linked thread). Example, if your stock main version is 1.54.69, than any stock recovery corresponding to build 1.54.xx should work.
3) If you didn't make a nandroid backup, you can try to find the stock nandroid for your CID. You will want the stock nandroid that corresponds to your present main version, which you say is not listed (common TWRP bug) but based on your hboot number (3.16) your main version is proabably 1.xx
I don't see a stock nandroid posted for your CID on the following threads. So you may post to one of those threads, and see if someone can post a nandroid for you:
http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The goal here is to get back to the stock ROM (and the build number that corresponds to your firmware) and stock recovery, same as Method 2 above. Then OTA up to Lollipop in order to update firmware.
4) Get the phone running again, per Method 1 above. Then run sunshine to S-off. Once you have s-off you can "manually" update the firmware. It seems you want to avoid paying for sunshine. But if none of the above methods are satisfactory, this may be your last option.
Click to expand...
Click to collapse
The reasion why im not takes backup of my stock androdi that there was other android system not stock this is freands phone hes buy it in shop but when he buy it phone was unlocked and with other wersion of android not stock one and thet was 4.4.3 android with ones dosn't get updates by default and google play dosn't connect to servers .
Yes searching for that RUU is hard no probliem i have installed 4.4.2 with recovery good thing phone works.
I read about sunshine its easyest way when s-off but there is another probliems thanks for help ill check all the things what you writted me .
Ainster said:
The reasion why im not takes backup of my stock androdi that there was other android system not stock this is freands phone hes buy it in shop but when he buy it phone was unlocked and with other wersion of android not stock one and thet was 4.4.3 android with ones dosn't get updates by default and google play dosn't connect to servers .
Yes searching for that RUU is hard no probliem i have installed 4.4.2 with recovery good thing phone works.
I read about sunshine its easyest way when s-off but there is another probliems thanks for help ill check all the things what you writted me .
Click to expand...
Click to collapse
You can start with 1.54.69.5 backup.
Then do multiple OTA 1.54.69.5 --> 1.70.69.2 --> 2.26.69.1 --> 3.33.69.1 --> 4.19.69.3
Don't have time to upload my TWRP backups but you can get a Philz recovery backup here (belongs to someone else) - https://drive.google.com/file/d/0BxUEBSB4XdsRa3RoS3JBVjVQREk/edit
Please note you need Philz recovery installed then restore the backup which already include a stock recovery in it. Restore (select all) then do OTA.
Hey guys, I know there's a crazy amount of unrooting threads here and everywhere else on the internet, but the more I search the more confused I get. So here's my short situation and my few questions:
Got a T-mobile M8, rooted, S-On, Unlocked, Running S.ROM. I'm trying to do the Tmobile JUMP thing to get the new HTC 10, so I'm trying to unroot this as much as possible. I've found at least 7 different ways with different outcomes on how to do this, so here are my questions:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
-Follow up to previous question: has anyone had any experience with returning a Relocked phone to Tmobile for their JUMP plan? (Not warranty exchange, I feel they're more strict with that)
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Thanks in advance!
TehAsher said:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
Click to expand...
Click to collapse
The statement "no other prerequisites" is not specific enough. If you mean stock ROM and/or stock recovery (which folks sometimes think is needed to RUU), its true that neither are needed in order to RUU.
There are however some prerequisites:
1) PC required. Win7 and USB 2.0 for the best compatibility with RUU.
2) RUU needs to be intended for your version (CID and MID)
3) RUU version needs to be greater or equal to main version on the phone (this requirement is bypassed with s-off)
4) Relocked or locked bootloaded (this requirement also bypassed with s-off)
TehAsher said:
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
Click to expand...
Click to collapse
Correct.
TehAsher said:
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Click to expand...
Click to collapse
T-Mob is not my carrier, and I know nothing of their Jump program. But in most cases, the best bet with returning a phone is to RUU to stock, and make the bootloader LOCKED. Return to s-on (after s-off) is probably not needed.
Thanks for the info! I guess I'll be getting sunshine then and try to follow all of these guides. So if I S-off with sunshine, as long as I check my CID and MID (I got the RUU from the HTC website, but I'll double check it anyways), I can flash that and return to stock. And afterwards I can find a guide on how to reset the tampered flags and the Locked status?
TehAsher said:
And afterwards I can find a guide on how to reset the tampered flags and the Locked status?
Click to expand...
Click to collapse
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571
How I went back to stock
I was rooted and running custom ROMS, but when MM came out I wanted to make sure that my firmware/radio was updated. So for me this is what I did
- first I am s-on
- When I unlocked the bootloader, just before I installed TWRP, I made a copy of the recovery. Also I backed up my stock ROM. Both I kept
So to restore:
- I re-installed via TWRP, the stock ROM, and made sure that I didn't root it
- I re-installed the stock recovery
- rebooted and phone saw the MM upgrade and proceeded to upgrade.
If you don't have the recovery/stock ROM you will need to remember what version of android you were on when you overwrote the recovery with TWRP. If your firmware + recovery + OS do not match the update won't work.
-brad
redpoint73 said:
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Awesome, got my phone S-Off. I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?
TehAsher said:
I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?
Click to expand...
Click to collapse
What error number? If 155 or 159, you can't RUU from LP to MM (this is a new requirement they added with MM). You either need to flash the 6.20.531.5 full stock firmware from here, then run the RUU again. Or run the T-Mobile LP RUU.
Hello,
my HTC 10 has CID 034. I kept S-ON, unlocked bootloader, installed TWRP, then LineageOS 14.1.
Then I wanted to revert back to stock. I tried several things, among them I think I downloaded file from this thread - RUU Zip (Stock Signed) - 1.90.401.5 and tried flashing with "fastboot oem rebootRUU" + "fastboot flash zip firmware.zip", but received errors and gave up. Now I think it was lower version (1.90.401.5) then I should have tried to flash (in download mode I saw 2.41.401.4).
Later I found official RUU.exe in this thread, flashing goes without problems, but when I reboot to bootloader, it still shows "System status: Modified".
Does anyone have any suggestions what I should do to return to status "Official" ?
Thank you in advance.
https://r.tapatalk.com/shareLink?ur...share_tid=3386456&share_fid=3793&share_type=t
[GUIDE] Safely set your bootloader back to "LOCKED" from "UNLOCKED" or "RELOCKED"
Read this. S-off should clear system status. RUU could never do that on HTC phones
Thank you for your reply.
So, you're saying I should turn the phone into S-OFF state and software status will be Official after I reflash with RUU? I'm sorry I'm new at this and it isn't very clear to me from the thread.
Thank you.