I have a rooted htc one M8 and want to upgrade it to android 5.0.1. Lollipop
But the main problem that I'm worried about is the phone is factory unlocked
Will i loose the sim unlocker after the upadte?? Please Help
You won't loose SIM unlock if you update.
If you have the AT&T version of the M8, and not on AT&T's network, you need to use the Lollipop AT&T RUU to update (relocked bootloader required to RUU if s-on).
Backup any personal data before RUU, as RUU will wipe the phone.
Related
Just wanted to ask a question of you guys, I have an ATT HTC one with S-off and converted to Googgle Play edition. i bought a Sim unlock code and i tried to unlock but code did not work as i read i apparently need to be using an original sense ROM. My question is can i just reboot to boorloader then reboot to RUU and flash original ATT decrypted zip? If so do i need to lock the bootloader still or not? I think i only need to re lock the bootloader when running the original RUU but in this instance all i want to do is shoot the original att.zip to it and the go backl to Google play edition.
So here is what i did. I relocked the bootloader then i changed the CID to CWS__001 from GOOGL001. Then i restored TWRP backup from thethe other thread that bypassed the 1.54 bootloader. Upon booting it would not work. At this point i thought about giivng up then i unlocked the bootloader and changed the CID. Remarkably it booted up to Sense and stock ATT ROM. I was able to SIM unlock my phone and now i am going back to HTC One Google Play Edition! YAY for reading more and more threads!
wait waht?
dfggggggg
I know this thread is a few months old, but I am in the exact same situation. I fully converted my AT&T HTC One to the Google Play Edition (including the CID). I tried to SIM unlock it, but it was unsuccessful. So you just changed your CID back and flashed a backup of an AT&T ROM? Can you point me to the AT&T backup you used? This is a pain to do, but I would really like to SIM unlock my phone. Then I will be going back to GPE.
Figured it Out
So I Googled a little more before I went all the way back to stock AT&T ROM by changing the CID back. I saw a comment somewhere that someone had just flashed any Sense-based ROM and SIM unlocking had worked. So from running 4.4.2 Google Play Edition ROM, I simply flashed the latest version of ViperOne ROM (found in the forums) through TWRP Recovery. Once it booted, I inserted the T-Mobile SIM I have and the SIM unlock code worked! From there I just performed the RUU update back to 4.4.2 GPE and everything is good. By the way, the unlock code I bought was from UnlockCode247.com and it worked perfectly. Plus it was only $3.50 so it was a bargain too.
(SOLVED)
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
conquesoextra said:
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
Click to expand...
Click to collapse
Yes. You can get OTAs while S-OFF. And assuming you haven't unlocked the bootloader since flashing the RUU, all the system files it verifies should be in place to accept OTAs. However, considering you are currently on 4.1.2, you'll need to run through a progression of OTAs to get up to the latest version, 4.4.2 w/ Sense 6. Might be better to just run the latest RUU to bring it up to 4.4.2 w/ Sense 5.5 then OTA to Sense 6. Be aware that you'll need to be on the AT&T network in order to get the updates OTA. If you're not on AT&T, you'll need to flash the updates manually, in which case you'll need to be S_OFF.
Also, once the phone is S-OFF there is no good reason to change that back to S-ON. There's the potential of bricking the phone by doing so. And even if it doesn't brick, the updates in firmware may make it more difficult to obtain S-OFF again.
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
conquesoextra said:
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
Click to expand...
Click to collapse
First off, since you are S-OFF there is no need to relock the bootloader in order to flash an RUU. It will run just fine with an unlocked bootloader. Also when you flash an RUU, all the partitions get wiped so there is no need to do anything within the ROM such as remove xposed & root prior to flashing. The RUU will set the device essentially in a factory state.
As far as I understand it, the OTAs for carrier specific devices are served up by the carrier. So if the phone has been SIM unlocked and is being used on another network, if you go into Settings>AT&T software update, it will not receive any available OTA update. You will need to flash the update file manually using the information in this thread, http://forum.xda-developers.com/showthread.php?t=2659374.
Since you are still on 4.1.2, you will need to run one of the recent RUUs in order to manually flash the OTA updates in that thread. The latest RUU available for AT&T devices is KK4.4.2 w/Sense 5.5.
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_356565_signed_2.exe
Flash that then you can manually flash the OTA update to get Sense 6.
You are the man.
THANK YOU SO MUCH!
I have an at&t branded phone. I recently switched to T-Mobile and would like to get T-Mobile ROM installed on it.
I started with a phone which was NOT rooted, had stock AT&T rom.
I have done the following so far:
*
Unlocked my boot loader - worked flawlessly
Installed TWRP - worked flawlessy
Attempted to install Super SU - I think it worked
Attempted to install a T-Mobile ROM - Getting a "Error flashing zip" error
I download official T-Mobile ROM installer from HTC website. I let the installer run until I saw "Rom.zip" in the temp folder.
A website on google told me that i can use this file to flash my phone. I did have some doubts about this file as I am able to unzip only half the file's contents using winrar. But anyways, I went ahead and used this ROM file.
I rebooted my phone in Recovery mode (TWRP). I clicked on Install and selected rom.zip from my SD Card. When I attempt to install rom.zip, I received following messages:
Installing '/external_sd/tmobile_rom.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip 'external_sd/tmobile_rom.zip'
Updating partition details...
....done
I tried a few different ROM's I found on the internet with the same error message.
So now I am stuck with no OS on the phone. I can only go to bootloader or TWRP.
If someone can suggest a more appropriate ROM file, I can give that a try.
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
I have s-on. Yes, I want the full T-Mobile firmware...mixing up my terms as I am new to this.
Since I don't have an OS right now, I will first try to restore to AT&T firmware by using the stock RUU on htc website. If that's successful, I will proceed with rest of the steps.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
So I was able to get back to AT&T firmware using below steps:
booted my phone to boot fastboot mode
I re-locked my bootloader using following command: fastboot oem lock
I download the AT&T HTC One M8 Stock RUU
Ran the installation until my firmware was flashed again
I am just so happy to have a phone that works now. I will continue soon with the rest of your instructions to get T-Mobile firmware.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
After spending few hours, I have successfully installed T-Mobile firmware on my AT&T M8.
I pretty much followed your instructions. For anyone else looking to this this, here are the complete instructions.
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
And now I am enjoying a beer
Thanks redpoint73 for your helpful reply.
deepak528 said:
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
Click to expand...
Click to collapse
I think this is slightly out of sequence. You need to s-off before changing CID and MID. CID and MID cannot be modified with s-on.
wouldnt a simple rom without the firmware provide wifi calling?
PunishedSnake said:
wouldnt a simple rom without the firmware provide wifi calling?
Click to expand...
Click to collapse
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
redpoint73 said:
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
Click to expand...
Click to collapse
Agreed
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
ad4mydev said:
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
Click to expand...
Click to collapse
The RUU isn't recognizing your phone because you have a non HTC rom on your phone. Just flash one of the various stock roms from this forum and then you can use the RUU. Secondly, you don't have to re-lock your bootloader if you are s-off to run the RUU.
Fixing the Device
ad4mydev said:
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
Click to expand...
Click to collapse
<br />
Hi, Since you do have a working device with a rom on it, all you need to do is find a T-Mobile Rom that is compatible with the At&t version. Make sure this is a stock rom because an accidental flash can hard brick your device. Thanks.
johnnyutah22 said:
The RUU isn't recognizing your phone because you have a non HTC rom on your phone. Just flash one of the various stock roms from this forum and then you can use the RUU. Secondly, you don't have to re-lock your bootloader if you are s-off to run the RUU.
Click to expand...
Click to collapse
AFAIK, the ROM doesn't need to be stock to RUU, only to OTA. There doesn't even need to be a ROM on the device to RUU.
Also, if there was something wrong with the phone's configuration, an error message would have been the result; not failing to connect to the phone.
If the RUU isn't recognizing the device at all, there is probably a fundamental USB connectivity issues. OP should try to :
- Make sure phone is booted into OS, or into bootloader-fastboot mode to RUU. "Regular" bootloader mode or recovery won't work.
- Try another USB cable or port, even another computer if possible (in particular USB 3.0 doesn't play well with RUUs).
- Uninstall and re-install HTC Sync and Drivers.
Also, keep in mind that in order to run an RUU that is different from your version (which is the case for T-Mob RUU or GPE RUU on an AT&T device) you need to change the CID and MID to correspond to the RUU. This won't cause failure to connect, but will cause the RUU to fail with an error message.
---------- Post added at 09:36 AM ---------- Previous post was at 09:31 AM ----------
kps2501 said:
Hi, Since you do have a working device with a rom on it, all you need to do is find a T-Mobile Rom that is compatible with the At&t version.
Click to expand...
Click to collapse
The AT&T variant won't support all 3G (HSPA) and 4G (LTE) bands used by T-Mobile if you just flash a T-Mob ROM. You need to install the T-Mob firmware to enable full T-Mob band support; which the RUU does.
Also, the RUU will "fully convert" to the T-Mob or GPE versions; and allow official OTA updates for that version, if that is what the OP is looking for. But the band support is the more important factor.
kps2501 said:
Make sure this is a stock rom because an accidental flash can hard brick your device.
Click to expand...
Click to collapse
Not sure what is trying to be conveyed here. No ROMs (stock or custom) meant for the "GSM" versions of the M8 (meaning stay away from Sprint and Verizon specific ROMs) will brick your phone.
Flashing a ROM meant for another device can brick your phone (and may be possible with s-off), but again, that isn't what you stated (although may be what you meant)
Thanks to all.
I ended up figuring it out using the steps below.
•ADB sideload CM12 via TWRP
•Once booted started USB debugging
•Changed the MID to the GPe (using ADB shell)
•Changed CID from CWS__001 to GOOGL001
•Rebooted into bootloader (fastboot oem rebootRUU)
•Found the RUU zip (can't post the link- too new)
•Pushed it to the phone (fastboot flash zip)
•Failed
•Flashed again
•Success
Sent from my HTC One_M8 using XDA Free mobile app
HI all I would like to know if there is an RUU Flash could use with TWRP I am currently on Android 5.0.2 Software 4.28.502.1 This is the original Rom that came with the HTC one M8 AT&T Verision.
I tried Doing updates to Marshmallow via AT&T Software Update, But it keeps telling me it there is no update and i can check back in 24 hours I think it may be because i am on Cricket Wireless. Also my phone is Rooted and boot loader "Unlocked" and S on
Would i be able to go into a store and have them update the phone with me with an AT&T Sim Card? Now the real ? is Will they do it?
Anyways, if there is a Marshmallow RUU I can use to Flash Via Twrp, that would be awesome, As I am looking to run Lineage 15.1 but need to be on Marshmallow first
Thanks in advance all.