I have a "manufacturer refurbished" AT&T branded M7 purchased almost a year ago from eBay. I'm not located in the US and the phone hasn't seen any updates (still in an older revision of KitKat from memory). Is that due to the phone not being on the AT&T network?
It's my SO's phone and I've not made it my concern until now with obvious concerns of the Stage Fright exploit known to be in the wild. The phone is rooted with TWRP and is S-ON. I have my own M7 which is S-OFF typically running an ASOP rom (XenonHD currently).
So what are my options here. I know my SO would be OK sticking with something stock and if things go sideways then it's not something I've done On the other hand, going S-OFF and super CID seems to be the easiest path to me.
So what I am asking for:
What's the easiest path to stock on this phone given that I'm not physically in the US with it or even have an AT&T SIM? RUU? If I go the S-OFF route should I flash interim firmware or just the most recent lollipop?
genseng said:
Is that due to the phone not being on the AT&T network?
Click to expand...
Click to collapse
yes
What's the easiest path to stock on this phone given that I'm not physically in the US with it or even have an AT&T SIM? RUU? If I go the S-OFF route should I flash interim firmware or just the most recent lollipop?
Click to expand...
Click to collapse
Imo, better to s-off change your CID to BS_US001 convert to the developer edition using a RUU.
Related
I acquired my device from T-Mobile UK and it came with 1.28.61.7 and cid ORANG001.
As far as I can see, there is no network branding on my device and it appears to be identical to a device running stock 1.xx.401.x firmware.
Why do carriers do this? I could understand them wanting to push their own bloatware to their devices but, in my case, all they are doing is holding my device back from receiving the latest updates. Most infuriating.
bobsie41 said:
I acquired my device from T-Mobile UK and it came with 1.28.61.7 and cid ORANG001.
As far as I can see, there is no network branding on my device and it appears to be identical to a device running stock 1.xx.401.x firmware.
Why do carriers do this? I could understand them wanting to push their own bloatware to their devices but, in my case, all they are doing is holding my device back from receiving the latest updates. Most infuriating.
Click to expand...
Click to collapse
Just unlock bootloader and install ARHD, then you'll be running the latest base 1.29.401.13.
shrubz said:
Just unlock bootloader and install ARHD, then you'll be running the latest base 1.29.401.13.
Click to expand...
Click to collapse
Thanks, I'm fully aware of that but it will not give me a full firmware update.
bobsie41 said:
Thanks, I'm fully aware of that but it will not give me a full firmware update.
Click to expand...
Click to collapse
No it won't. You'll have to wait for S off, there was a thread created today on supercid, but nothing that works yet.
Sent from my HTC One using Tapatalk 2
I want to update my HTC one to 4.2.2 but mine is the US variant (HTC_001 and not locked to any carrier) so I guess it will be a while before the update goes OTA??
Anywho, I understand that there is away to change the MID to get OTA from UK (http://forum.xda-developers.com/showthread.php?t=2322820)
But it says that I require "s-off".
Can you be kind enough to explain what it is and how I can get it?
uzman1243 said:
I want to update my HTC one to 4.2.2 but mine is the US variant (HTC_001 and not locked to any carrier) so I guess it will be a while before the update goes OTA??
Anywho, I understand that there is away to change the MID to get OTA from UK (http://forum.xda-developers.com/showthread.php?t=2322820)
But it says that I require "s-off".
Can you be kind enough to explain what it is and how I can get it?
Click to expand...
Click to collapse
S-off means security off.
There are certain partitions in the phone which contain the firmware, drivers, etc which are protected with s-on (security on). The reason for this is that if incorrect data is written to these areas your phone can become a permanent brick.
Obtaining s-off is a relatively easy process but can be risky if you don't know what you are doing.
My suggestion to you if you don't know what s-off is is to research and then some more and be familiar with the benefits vs risks.
In my signature below is a guide by vomer which provides details and links to the various processes you have to go through.
rider5512 said:
S-off means security off.
There are certain partitions in the phone which contain the firmware, drivers, etc which are protected with s-on (security on). The reason for this is that if incorrect data is written to these areas your phone can become a permanent brick.
Obtaining s-off is a relatively easy process but can be risky if you don't know what you are doing.
My suggestion to you if you don't know what s-off is is to research and then some more and be familiar with the benefits vs risks.
In my signature below is a guide by vomer which provides details and links to the various processes you have to go through.
Click to expand...
Click to collapse
Thank you.
I looked into it, and the whole process is a very arduous task. You have to unlock the bootloader, then root it, then s off, then use that tutorial to change the MID.
I think there is too much risks given my knowledge of android hacking.
I guess ill just have to wait for OTA for the US variant.
uzman1243 said:
Thank you.
I looked into it, and the whole process is a very arduous task. You have to unlock the bootloader, then root it, then s off, then use that tutorial to change the MID.
I think there is too much risks given my knowledge of android hacking.
I guess ill just have to wait for OTA for the US variant.
Click to expand...
Click to collapse
Why wait for an ota update when you could just unlock the bootloader, install a custom recovery, and install something like ARHD 12.0 which is rock stable and is way more faster than the stock rom.
Sent from my HTC One using xda premium
uzman1243 said:
Thank you.
I looked into it, and the whole process is a very arduous task. You have to unlock the bootloader, then root it, then s off, then use that tutorial to change the MID.
I think there is too much risks given my knowledge of android hacking.
I guess ill just have to wait for OTA for the US variant.
Click to expand...
Click to collapse
Yea..u dnt hv to s-off to flash custom rom...
uzman1243 said:
I want to update my HTC one to 4.2.2 but mine is the US variant (HTC_001 and not locked to any carrier) so I guess it will be a while before the update goes OTA??
Anywho, I understand that there is away to change the MID to get OTA from UK (http://forum.xda-developers.com/showthread.php?t=2322820)
But it says that I require "s-off".
Can you be kind enough to explain what it is and how I can get it?
Click to expand...
Click to collapse
Just wait for the OTA, should be soon.. I just got mine updated OTA 2 days ago HTC_044.
Sent from my HTC One using Tapatalk 4 Beta
akk60 said:
Why wait for an ota update when you could just unlock the bootloader, install a custom recovery, and install something like ARHD 12.0 which is rock stable and is way more faster than the stock rom.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmmm well I prefer the Stock 4.2.2 with sense 5. And since mine is USA variant so the only way to get it will be to change the MID. so thats unlock the bootloader, then root it, then s off, then use that tutorial to change the MID.
alanchai said:
Just wait for the OTA, should be soon.. I just got mine updated OTA 2 days ago HTC_044.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
USA man, its always the last one that gets the updates. But thank god mine is not given to an carrier.
Hey all,
After a couple of years away from HTC and my EVO 4G, I'm glad to be back as I just bought a HTC One. Looks like an AT&T UL variant still on HBOOT 1.44, S-ON, and 4.1.2. I know the dev devices are starting to get KitKat, and I know I want Sense 5.5 and KitKat versus AT&T bloat and AOSP senseless, so I think this means I should be thinking about converting to a Dev Ed. That said, I'd think the 4.4 update will be modified for use in other standard device ROMs pretty quickly. Is there any reason NOT to convert to a dev device based upon my inclinations above?
THANKS!!!
vettejock99 said:
Hey all,
After a couple of years away from HTC and my EVO 4G, I'm glad to be back as I just bought a HTC One. Looks like an AT&T UL variant still on HBOOT 1.44, S-ON, and 4.1.2. I know the dev devices are starting to get KitKat, and I know I want Sense 5.5 and KitKat versus AT&T bloat and AOSP senseless, so I think this means I should be thinking about converting to a Dev Ed. That said, I'd think the 4.4 update will be modified for use in other standard device ROMs pretty quickly. Is there any reason NOT to convert to a dev device based upon my inclinations above?
THANKS!!!
Click to expand...
Click to collapse
Imo go for dev edition or wwe, and your M7 will be bloatware free and receive ota directly from htc instead of at&t. Its a pretty easy process, but im sure you already know how to convert from what you said above. The only thing to consider imo is warranty void after unlocking bootloader
Thanks so much! I got my phone off eBay but it looks and seems to function just fine so I like my chances. No worries here about the warranty. Thanks again!
vettejock99 said:
Thanks so much! I got my phone off eBay but it looks and seems to function just fine so I like my chances. No worries here about the warranty. Thanks again!
Click to expand...
Click to collapse
Unlock that boot loader, s-off son. (Probably revone if you're on hboot 1.44). Fastboot flash the Google edition 4.4 ruu. I promise you you will not be disappointed! Once flashed the. Fastboot flash twrp (latest) and make a backup of your stock GE 4.4.
From there you can flash any rom (sense, GE, aosp). Even from the HTC one, HTC one at&t, or other gsm HTC ones.
I don't worry about warranty. You can always lock boot loader, s-on and change cid back to stock then ruu and they never know.
Sent from my HTC One using Tapatalk
I got an unlocked HTC One that was originally on AT&T's network, but now I use it on T-Mobile. The OTA updates won't work since I'm not on AT&T's network and the RUU file has not been released yet. I'm debating whether I should root the device, wait for the RUU file, or bug a friend to use their AT&T sim card to get the update. I'm currently running android 4.1.2 and sense 5 (software number 1.26.502.10). Also if the RUU file does come out can I use it from 4.1 to get to 4.4 or will there be issues?
Thanks
wbrianw said:
I got an unlocked HTC One that was originally on AT&T's network, but now I use it on T-Mobile. The OTA updates won't work since I'm not on AT&T's network and the RUU file has not been released yet. I'm debating whether I should root the device, wait for the RUU file, or bug a friend to use their AT&T sim card to get the update. I'm currently running android 4.1.2 and sense 5 (software number 1.26.502.10). Also if the RUU file does come out can I use it from 4.1 to get to 4.4 or will there be issues?
Thanks
Click to expand...
Click to collapse
The easiest way is to borrow your friend's sim card but that just keeps you locked into AT&T's network. Since, you are running on T-Mobile it may be better to change your phone to look like T-Mobile so you can get all of the benefits of T-Mobile including their OTA updates. You can use this guide Complete Flashing Guide | Rooting to Unlock your bootloader, install custom recovery and root. Then I would use this guide get S-OFF. Once you are S-OFF, then change your MID using this tool MID change without ENG HBOOT then change the CID. You can use this guide nkk71's SuperGUIDE to returning 100% back to stock to show the steps to install the latest T-Mobile RUU. Once the RUU is installed you are set with a stock T-Mobile rom, recovery and S-OFF. Keep S-OFF as long as you can, don't return to S-ON!
majmoz said:
The easiest way is to borrow your friend's sim card but that just keeps you locked into AT&T's network. Since, you are running on T-Mobile it may be better to change your phone to look like T-Mobile so you can get all of the benefits of T-Mobile including their OTA updates. You can use this guide Complete Flashing Guide | Rooting to Unlock your bootloader, install custom recovery and root. Then I would use this guide get S-OFF. Once you are S-OFF, then change your MID using this tool MID change without ENG HBOOT then change the CID. You can use this guide nkk71's SuperGUIDE to returning 100% back to stock to show the steps to install the latest T-Mobile RUU. Once the RUU is installed you are set with a stock T-Mobile rom, recovery and S-OFF. Keep S-OFF as long as you can, don't return to S-ON!
Click to expand...
Click to collapse
Thanks so much for the help, I'll try that when I get the chance.
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.