Hi everyone,
I've just bought an used HTC One M7 that was locked to Three UK but I managed to get it unlocked via a code from ebay. The phone is on 4.1.2 and the recovery mode shows S-ON, LOCKED so I'm guessing its all stock. The CID is H3G_001 and the OTA updater keeps saying that I'm already on the latest update. The phone isn't rooted either. I've already tried resetting to factory settings but that didn't help. I've had a look at RUU's but couldn't find anything for Three UK/H3G_001.
Could anyone tell me how I could get the Sense 6 update? I've tried clearing the data/cache in the updater and google services framework but still nothing. I don't want to tamper with the bootloader etc if possible.
Thanks,
Anthony
Anzzle said:
Hi everyone,
I've just bought an used HTC One M7 that was locked to Three UK but I managed to get it unlocked via a code from ebay. The phone is on 4.1.2 and the recovery mode shows S-ON, LOCKED so I'm guessing its all stock. The CID is H3G_001 and the OTA updater keeps saying that I'm already on the latest update. The phone isn't rooted either. I've already tried resetting to factory settings but that didn't help. I've had a look at RUU's but couldn't find anything for Three UK/H3G_001.
Could anyone tell me how I could get the Sense 6 update? I've tried clearing the data/cache in the updater and google services framework but still nothing. I don't want to tamper with the bootloader etc if possible.
Thanks,
Anthony
Click to expand...
Click to collapse
Updates are dependent on the carrier for carrier locked phones. It is possible that H3G has not updated their phone. A lot of people will S-OFF their phone to change their CID & MID to get the updates quicker by going to either the Int'l (.401) version or the DevEd (.1540) version which are updated directly from HTC. Your version is .771. For carrier updates, you must remain on the carrier's network to receive them. Check with H3G to see if an update is available and when or if you can expect to receive it.
majmoz said:
Updates are dependent on the carrier for carrier locked phones. It is possible that H3G has not updated their phone. A lot of people will S-OFF their phone to change their CID & MID to get the updates quicker by going to either the Int'l (.401) version or the DevEd (.1540) version which are updated directly from HTC. Your version is .771. For carrier updates, you must remain on the carrier's network to receive them. Check with H3G to see if an update is available and when or if you can expect to receive it.
Click to expand...
Click to collapse
Hey there, thanks for your reply.
I've had a look around the internet and I've found the OTA update zip for my phone from 4.1.2 to 4.2 (1.28.771 to 2.24.771), then another one OTA zip for 4.2 to 4.3 (2.24.771 to 3.62.771). However the issue now is, I can't flash it using the stock recovery as I have S-ON I believe and it throws back an "invalid operation" error when I try to apply an update via internal storage. I'm trying to get S-OFF but I'm not having any luck at the moment, as ideally I don't want to mess with the bootloader. I'll give it another go tomorrow, given up for tonight.
The phone is for my brother and he's fine with 4.1.2/Sense 5 tbh but would like Sense 6 features if possible.
Anzzle said:
Hey there, thanks for your reply.
I've had a look around the internet and I've found the OTA update zip for my phone from 4.1.2 to 4.2 (1.28.771 to 2.24.771), then another one OTA zip for 4.2 to 4.3 (2.24.771 to 3.62.771). However the issue now is, I can't flash it using the stock recovery as I have S-ON I believe and it throws back an "invalid operation" error when I try to apply an update via internal storage. I'm trying to get S-OFF but I'm not having any luck at the moment, as ideally I don't want to mess with the bootloader. I'll give it another go tomorrow, given up for tonight.
The phone is for my brother and he's fine with 4.1.2/Sense 5 tbh but would like Sense 6 features if possible.
Click to expand...
Click to collapse
if you don't want to mess with the bootloader then try Sunshine to s-off: http://forum.xda-developers.com/showthread.php?p=53624322
Anzzle said:
Hey there, thanks for your reply.
I've had a look around the internet and I've found the OTA update zip for my phone from 4.1.2 to 4.2 (1.28.771 to 2.24.771), then another one OTA zip for 4.2 to 4.3 (2.24.771 to 3.62.771). However the issue now is, I can't flash it using the stock recovery as I have S-ON I believe and it throws back an "invalid operation" error when I try to apply an update via internal storage. I'm trying to get S-OFF but I'm not having any luck at the moment, as ideally I don't want to mess with the bootloader. I'll give it another go tomorrow, given up for tonight.
The phone is for my brother and he's fine with 4.1.2/Sense 5 tbh but would like Sense 6 features if possible.
Click to expand...
Click to collapse
OTA update is flashed in stock recovery. Here is a post explaining the OTA process. This post might explain what you are missing for the OTA to work. I think you must select from "internal storage" instead of "sdcard" when you install the OTA.
majmoz said:
OTA update is flashed in stock recovery. Here is a post explaining the OTA process. This post might explain what you are missing for the OTA to work. I think you must select from "internal storage" instead of "sdcard" when you install the OTA.
Click to expand...
Click to collapse
I've tried following the process but it just gives a "Invalid Operation" message when ever I select from Internal Storage. I'm losing patience with this, why can't OTA just work.
Thanks for your help anyways.
Anzzle said:
I've tried following the process but it just gives a "Invalid Operation" message when ever I select from Internal Storage. I'm losing patience with this, why can't OTA just work.
Thanks for your help anyways.
Click to expand...
Click to collapse
you can't manually flash ota with a s-on phone, only s-off.
Anzzle said:
I've tried following the process but it just gives a "Invalid Operation" message when ever I select from Internal Storage. I'm losing patience with this, why can't OTA just work.
Thanks for your help anyways.
Click to expand...
Click to collapse
Try following this post. Make sure that your version number matches exactly the second version in the file name. Change the name to "update.zip" and place in the SDCARD.
Related
Hi, I have an Unlocked 32GB HTC One (BS_US001) and I'm having a hard time trying to find info about stock recoveries.
My phone currently is on stock 4.1.2, bootloader unlocked, S-Off and rooted. I was using the TWRP recovery, used to root my phone. Since the 4.3 update came out, I was searching for the stock recovery to proceed with the update, but too many different files seems to exist. I just want to install the right recovery and apply the 4.3 update, no full ROM flash.
Yesterday I flashed this recovery file (9MB) and got icons similar of those on the right of this image.
Today, I flashed this one (7.9MB) and got something like this, the little android icon.
Later, I've found another one (9.8MB).
Edit: and another one, a few bytes shorter than the third.
But now I'm little afraid of flashing again, just for the sake of it.
So, first of all, which one is the right file for my phone (yet another one)?
Second, I flash recoveries through fastboot command line (fastboot flash recovery recovery.img). Can this method and command brick my phone?
Third, how the stock recovery behaves on your phone? Both times, when I flashed the files and entered in recovery mode, my phone would boot 2 or 3 times straight into recovery mode again, until it boot itself properly, into the system. Also, recovery mode goes from the green to the red icon and awaits until I reboot the phone again.
Thanks in advance.
Final edit: For the sake of others lost in the lack of good info, I'm editing this old post.
I found some crap advices here and there. One of them was the need to relock the bootloader to accept OTAs. It doesn't make any sense, but if you are seeking help, you will take **** as good advice. Don't do it.
Another bad advice was about the stock recovery. Just open the last update you got (Downloads folder on your phone or get the OTA from HTC website) and extract the recovery.img file. Flash it and you have the proper stock recovery for your phone.
All of this is about the stock HTC One - no custom roms, no xposed changes, nothing. The only thing I did prior to this was to flash TWRP and root. That's how I want my phone for now - stock with root.
I kind of went through this today. Ended up just wiping it, running a RUU and reapplying OTAs.
I'll tell you this… after I went through this I attempted to salvage the stock recovery before rerooting etc. I was stuck trying to get fastboot to boot a recovery instead of flash one. I did find an alternate way to harvest the recovery. I got it out of the ota. I'm not done testing it yet, but my phone was still showing tampered. Flashed cwr and called it a day at that point
Sent from my HTC One
Thank you for your answer. I'm trying to avoid the whole RUU thing, but I'll keep it as a last resource, for sure. Also, I'm trying to understand more about this piece of software called recovery.
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
kibmikey1 said:
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
Click to expand...
Click to collapse
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
bjg222 said:
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
Click to expand...
Click to collapse
I pulled it directly from my decrypted RUU zip of 1540.16.
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
kibmikey1 said:
I pulled it directly from my decrypted RUU zip of 1540.16.
Click to expand...
Click to collapse
Would you be willing to share it? I haven't found a decrypted version of the 1540.16 RUU since Bugsy's hosting server stopped hosting downloads (The new thread only has 1540.3 last I checked).
Guich said:
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
Click to expand...
Click to collapse
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
bjg222 said:
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
Click to expand...
Click to collapse
Is the 3.22 in the folder
Guich said:
Is the 3.22 in the folder
Click to expand...
Click to collapse
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
bjg222 said:
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
Click to expand...
Click to collapse
1.29.1540.16 Developer Edition signed stock recovery.
Has anyone else flashed stock recovery while on custom ROM? I was pleasantly surprised to discover my SD card was wiped Is this normal, and was there some way I could have figured out this was what was going to happen? I don't really understand what stock recovery does/is for. The only other time I'd flashed stock recovery was after restoring to stock ROM from nandroid.
kibmikey1 said:
1.29.1540.16 Developer Edition signed stock recovery.
Click to expand...
Click to collapse
Awesome, thanks!
bjg222 said:
Awesome, thanks!
Click to expand...
Click to collapse
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
arikah said:
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
Click to expand...
Click to collapse
If you're rooted, unroot through SU, then do a factory reset and try it again.
kibmikey1 said:
If you're rooted, unroot through SU, then do a factory reset and try it again.
Click to expand...
Click to collapse
I haven't been rooted since one of the last 4.1.2 updates, because that's when I went back to stock recovery. I was able to accept those OTA packs, why is this one different? I'm really trying to save factory resets or RUU's for the absolute last ditch effort, in fact I'm more likely to stick with 4.1.2 until I can find a way to do this.
help
I have att htc one dev edition, its in soft brick state and i cny get it to do anything, i have tried running the recovery kit, and that get to the end then error 131...
could somebody please suggest some help for me please, thanks in advance
Hello -- I cannot do the T-Mobile (USA) Sense 6 for M7 update OTA. I believe the problem was the custom recovery (TW) which I had, so I flashed a variety of stock recoveries (4.20.707.7, 4.19.401.11, 4.06.1540.2). My telephone is software version: 4.19.531.10 which I cannot find a stock recovery for. The update downloads, reboots, then the progress bar goes about half-way before a red-triangle appears. Not sure what else I need to do to the phone. I only have OTA ROMs on the phone, S-OFF and the device is rooted. Any one with any experience with this and how did you resolve? Many thanks in advance!
LAChris67 said:
Hello -- I cannot do the T-Mobile (USA) Sense 6 for M7 update OTA. I believe the problem was the custom recovery (TW) which I had, so I flashed a variety of stock recoveries (4.20.707.7, 4.19.401.11, 4.06.1540.2). My telephone is software version: 4.19.531.10 which I cannot find a stock recovery for. The update downloads, reboots, then the progress bar goes about half-way before a red-triangle appears. Not sure what else I need to do to the phone. I only have OTA ROMs on the phone, S-OFF and the device is rooted. Any one with any experience with this and how did you resolve? Many thanks in advance!
Click to expand...
Click to collapse
The ota update might fails because of bad recovery installed or because the md5 checksum fails because of some missing or modified /system files or missing preloaded apps like flashlight, calculator etc etc that get wiped during bootloader unlock. Since your phone is s-off, you could run the 3.24.531.3 ruu.zip (don't s-on and don't relock bootloader) and apply each ota updates from 3.24.531.3 to 5.xx.531.x,
Ok, I have one really nooby question. Are T-Mobile USA and T-Mobile Germany branded phones the same? Because my phone is T-Mobile Germany, and I've seen that for T-Mobile branded phones Sense 6 update is out, so I'm wondering if that's for all phones or just USA.
Thank you
It's for T-Mobile USA for now. Europe roll out would soon occur.
Sent from my HTC One using XDA Premium 4 mobile app
LAChris67 said:
Hello -- I cannot do the T-Mobile (USA) Sense 6 for M7 update OTA. I believe the problem was the custom recovery (TW) which I had, so I flashed a variety of stock recoveries (4.20.707.7, 4.19.401.11, 4.06.1540.2). My telephone is software version: 4.19.531.10 which I cannot find a stock recovery for. The update downloads, reboots, then the progress bar goes about half-way before a red-triangle appears. Not sure what else I need to do to the phone. I only have OTA ROMs on the phone, S-OFF and the device is rooted. Any one with any experience with this and how did you resolve? Many thanks in advance!
Click to expand...
Click to collapse
T-Mobile makes the OTA updates not work with ANY modification (other than S-OFF), so even if you relock the bootloader and install the stock recovery, the OTA update will fail. I've even tried to unroot, but it still fails. Only way to update is to install the RUU, either the exe or the zip. I just installed the last ruu.zip that I could find (3.24.531.3) then let it do the OTA update to 4.19.531.10, reboot, then do the OTA update to 5.14.531.1. A pain in the ass, but after getting everything restored and set up, it works and looks great.
---------- Post added at 03:52 PM ---------- Previous post was at 03:51 PM ----------
hrvoje334 said:
Ok, I have one really nooby question. Are T-Mobile USA and T-Mobile Germany branded phones the same? Because my phone is T-Mobile Germany, and I've seen that for T-Mobile branded phones Sense 6 update is out, so I'm wondering if that's for all phones or just USA.
Thank you
Click to expand...
Click to collapse
Just the USA.
So I'm still stucked with 4.3. Yes, they also removed 4.4 and Sense 5.5 update.
alray said:
The ota update might fails because of bad recovery installed or because the md5 checksum fails because of some missing or modified /system files or missing preloaded apps like flashlight, calculator etc etc that get wiped during bootloader unlock. Since your phone is s-off, you could run the 3.24.531.3 ruu.zip (don't s-on and don't relock bootloader) and apply each ota updates from 3.24.531.3 to 5.xx.531.x,
Click to expand...
Click to collapse
Thanks for the help. This took half a day to resolve. I used Guru Reset to get things going. I had to go from RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed_2 and work my way up to v3 (via RUU) and then started to get the OTA v4 and v5. I could not immediately go to installing the v3 (tried a couple) RUUs. Also, I think part of my own personal problem was downloading the ZIP or the EXE for the v3 RUU was becoming corrupt each time (different file sizes, etc). I know my network is solid, but this was a real problem and I could never get a decent download of an RUU for htc1guru (tried different browsers, etc too).
Thanks for the help! I'm glad I got the help and the new upgrade --- seems very nice. And, thanks too to Titanium Backup -- it quickly got a lot of my user data back in place being I had to start from scratch.
LAChris67 said:
Thanks for the help. This took half a day to resolve. I used Guru Reset to get things going. I had to go from RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed_2 and work my way up to v3 (via RUU) and then started to get the OTA v4 and v5. I could not immediately go to installing the v3 (tried a couple) RUUs. Also, I think part of my own personal problem was downloading the ZIP or the EXE for the v3 RUU was becoming corrupt each time (different file sizes, etc). I know my network is solid, but this was a real problem and I could never get a decent download of an RUU for htc1guru (tried different browsers, etc too).
Thanks for the help! I'm glad I got the help and the new upgrade --- seems very nice. And, thanks too to Titanium Backup -- it quickly got a lot of my user data back in place being I had to start from scratch.
Click to expand...
Click to collapse
Were you trying to download the RUU using the phone? I have found in the past that can corrupt the files, not sure why. I located the RUU zip for the 3.14.531.3 release in a post here on XDA (a collection of RUUs from various sources). I prefer using the zip instead of the exe (the zip is less sensitive, the exe can check too many things, making it fail more often). Once the 3.14 RUU was applied, I could then do the OTA for the 4.19 and the 5.14 releases easily. Then I re-unlocked the bootloader, installed TWRP and then rooted it.
Fuzi0719 said:
Were you trying to download the RUU using the phone? I have found in the past that can corrupt the files, not sure why. I located the RUU zip for the 3.14.531.3 release in a post here on XDA (a collection of RUUs from various sources). I prefer using the zip instead of the exe (the zip is less sensitive, the exe can check too many things, making it fail more often). Once the 3.14 RUU was applied, I could then do the OTA for the 4.19 and the 5.14 releases easily. Then I re-unlocked the bootloader, installed TWRP and then rooted it.
Click to expand...
Click to collapse
Thanks Fuzi -- yeah, I was downloading on the PC. I tried it numerous times. I agree with you and tried going with the ZIP. All times, the file was coming up in different sizes and could not extract, but I finally got it to work. Once I got the download going for the first one, I basically followed what you said here and it worked. Thanks much again.
I gave my mom my old HTC ONE M7, which she loves. It started having the audio problem recently in calls, and I couldn't fix it over the phone troubleshooting, so I had her send it to me. To make things easier in the future, I decided to return to stock so it could get OTA updates in the future. It is unlocked with s-off and I had a custom ROM on it for her.
It had a 1.55 HBOOT version and I read that I should flash down to 1.44 HBOOT and then RUU (RUU_M7_UL_JB_50_Cingular_US_1.26.502.15...etc) to stock image which I have done.
The phone is now running AT&T stock:
hboot: 1.44
firmware: 1.26.502.15
model: pn0712000
cid: 11111111
So now here's my particular issue. I don't have a sim card that will fit into the phone. My mom lives far away, she kept the card to put in her backup phone while I fixed this one. I can't update the phone on AT&T's network without a sim card, so I can't do OTA updates to get it up to date.
I have done some searching but found nothing definite. Are there no downloadable OTA files from AT&T? If so, i'm assuming every update must be done in order (in other words, i can't just find the latest OTA and apply it, they would need to be applied incrementally)?
Anyone have any suggestions?
If I was to forget about AT&T and go to straight HTC image or Google Edition, (where it could still get OTA) what should I do from here?
I suppose if I can't find anything at all, I can go to an AT&T store and see if they can let me use a sim card or something (I have AT&T as well, the same account as hers, but my M8 uses a smaller sim card).
neogrinch said:
So now here's my particular issue. I don't have a sim card that will fit into the phone. My mom lives far away, she kept the card to put in her backup phone while I fixed this one. I can't update the phone on AT&T's network without a sim card, so I can't do OTA updates to get it up to date.
I have done some searching but found nothing definite. Are there no downloadable OTA files from AT&T? If so, i'm assuming every update must be done in order (in other words, i can't just find the latest OTA and apply it, they would need to be applied incrementally)?
Click to expand...
Click to collapse
You can't update AT&T M7 is the phone isn't connected to at&t network but with s-off you can manually flash ota update from stock recovery, and yes it must be done incrementally.
Anyone have any suggestions?
Click to expand...
Click to collapse
Change your cid to BS_US001 and use the latest dev edition version. You'll get ota updates even if not on the at&t network.
alray said:
You can't update AT&T M7 is the phone isn't connected to at&t network but with s-off you can manually flash ota update from stock recovery, and yes it must be done incrementally.
Change your cid to BS_US001 and use the latest dev edition version. You'll get ota updates even if not on the at&t network.
Click to expand...
Click to collapse
Such a simple, yet brilliant suggestion. I was making it over complicated. I changed CID to BS_US001 and installed RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16 and the device is now doing OTA updates.
Thanks for the suggestion.
neogrinch said:
Such a simple, yet brilliant suggestion. I was making it over complicated. I changed CID to BS_US001 and installed RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16 and the device is now doing OTA updates.
Thanks for the suggestion.
Click to expand...
Click to collapse
no problem
Even simpler: you could have used a newer RUU like the 4.19.1540.9 RUU and do all ota updates to 6.09.1540.2
Or you could have flashed the latest dev edition stock rom and the matching firmware available in my thread to avoid downloading 10 ota updates.
But the final result will be the same, just a little longer and consume much more bandwidth.
Hey guys,
I have an M7 from Orange UK, which I now use on slovak Orange. Now I wanted to get the update for Lollipop, but unless I'm in the UK my options are limited. I don't have s-off, I am not rooted, I am 100% stock. So I can either flash a slovak RUU on the phone (I don't want to go through root, s-off etc) or I could possibly get the update file I would normally download from servers (from UK Orange), put it onto my phone and run it. I have found some on the Net, but only for WWE, since my CID is orang001 I'm not sure if it would work. Could you advise? Or, even better, would anyone be able to route me to the file for UK Orange? Thanks in advance for any tip, it really is appreciated.
Maybe this helps : androidruu.com/index.php?developer=M7
Sorry, can´t post links. i´m just a noob.
bodymaker said:
Hey guys,
I have an M7 from Orange UK, which I now use on slovak Orange. Now I wanted to get the update for Lollipop, but unless I'm in the UK my options are limited. I don't have s-off, I am not rooted, I am 100% stock. So I can either flash a slovak RUU on the phone (I don't want to go through root, s-off etc)
Click to expand...
Click to collapse
Flashing a ruu not intended for your phone require s-off.
or I could possibly get the update file I would normally download from servers (from UK Orange), put it onto my phone and run it.
Click to expand...
Click to collapse
Manually installing ota update require s-off.
So your option are to achieve s-off or to unlock ythe bootloader only and use custom roms.
Well...you know how when you download the update and not install it right away? Then your phone says "an update was found, would you like to install it?" - this is where I wanted to get to. But the more I think about it the more I understand I would need root to get to the folder where android keeps updates. So it would be easier to get the root, put there RUU with slovak Orange CID and then get the update the usual way.
bodymaker said:
Well...you know how when you download the update and not install it right away? Then your phone says "an update was found, would you like to install it?" - this is where I wanted to get to.
Click to expand...
Click to collapse
You can't start this process yourself. The phone must detect that there is an ota update by itself when searching for it in settings--> about-->sotware update
But the more I think about it the more I understand I would need root to get to the folder where android keeps updates.
Click to expand...
Click to collapse
No you don't need root. Ota updates are stored in /sdcard/Download. But you will need S-OFF to start the update process from stock recovery.
So it would be easier to get the root, put there RUU with slovak Orange CID and then get the update the usual way.
Click to expand...
Click to collapse
You can't change your phone to another version using a RUU without having s-off
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
tw39515 said:
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
Click to expand...
Click to collapse
Welcome back to HTC
It really depends on what you plan to do with your M9.
If you plan on using custom roms then yes unlock and install TWRP. Root is not required to flash roms.
Sunshine does not root or unlock but removes secure write (S-Off) which allows you to install different firmware's etc.
With S-on you can only move forward with firmware's. Lots of people complain about the 25.00, But its well worth it.
If you are not concerned about the cost, then unlock, twrp, flash superSu, and install sunshine and S-off then your free to do anything.
backup if you like but there is a thread with stock backups etc...
hope this helps
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
will do viperone had issues on initial firmware so i flashed the latest ruu, sunshine is next. thanks for the advice.
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
umangilu said:
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
Click to expand...
Click to collapse
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
kc6wke said:
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
Click to expand...
Click to collapse
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Miguel_Lancaster said:
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Click to expand...
Click to collapse
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
kc6wke said:
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
Click to expand...
Click to collapse
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Miguel_Lancaster said:
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Click to expand...
Click to collapse
The RUU will not relock bootloader or rewrite S-On. To accept OTA, you need to have stock unmodified device.
You could run the RUU again or just unroot and flash stock recovery. The OTA will not wipe the device but the RUU will.
Hope this helps.
kc6wke said:
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
Click to expand...
Click to collapse
Thanks for this! Im having trouble with my computer and have been looking for a ruu zip all day lol. Will give this a shot on my TMOUS S-Off M9 tomorrow so I can jump to my next device.