I'm aware of the OTA update next week that'll update me to Sense 6.
Currently displays in recovery:
Tampered
Unlocked
S-OFF
Currently on stock 4.4.2 rooted, no other kernel changes, etc. but the ROM I'm using has custom black boot screens added (literally just black instead of default white boot background).
Rooting is nice and all but getting tired and would just like to revert to pretty much locked bootloader, unrooted, factory condition, etc. and be able to also do OTA for future updates.
Any help is appreciated. Baby steps please.
Anyone?
First, relock your bootloader. To do that, start your phone in bootloader mode, connect your phone to pc via usb cable and type "fastboot oem lock" on command prompt. Next, download the proper ruu exe file from htc1guru.com. By proper,I mean the one that matches your phones actual model number and custom id. Execute the ruu while connecting your phone to pc in fastboot mode. Follow the on screen instructions and when finished, you will have s phone that says re locked and s-off. You will get ota in this condition and will be able to install ota and upgrade to Sense 6.0 without any problems.
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
SaHiLzZ said:
If you are only rooted with stock ATT software, unroot using the SuperSU app, make sure you have stock recovery, and you are golden. DO NOT turn S-ON, and also no need to lock bootloader, as with S-OFF, you will get updates with unlocked bootloader
Click to expand...
Click to collapse
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Yes you can flash the decrypted ruu. It is the same as using the ruu exe.
If you haven't changed your mid and/cid,then what you need to is just lock the bootloader and flash the ruu (zip or exe). You will be on stock with s-off which is fine for getting ota.
Yes you can convert to developer edition. The DE and the at&t version are the same hardware-wise (except DE have 64gb storage instead of 32gb on at&t version) and have the same radio bands. You will get faster Android upgrades with no at&t bloats.
mch277 said:
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Click to expand...
Click to collapse
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
mb_guy said:
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
Click to expand...
Click to collapse
My understanding is that, if there's any modification in system files, applying OTA may result in a bootloop/brick. I agree that rooted devices remain rooted after OTA. As the OP said that s/he us using a rom with modified boot animation, I suggested him/her to return to stock first.
Related
(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!
FOUND THE RECOVERY (See below)
Right now my goal is to go back to stock to flash the OTA Update. I am running my nandroid back up I first made when which is the 4.4.4 w/ Software # 1.58.502.1. and right now I have TWRP as my recovery.
Also can someone confirm something for me. This nandroid I am running is rooted obviously and has SuperUser on it. If I go back to the stock recovery can I still do the OTA update even though SuperUser is there and the phone is unlocked?
Also in order to get the stock recovery back on the phone I need to use ABD and the windows command prompt method correct?
Thanks
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
magicbumm328 said:
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
Click to expand...
Click to collapse
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
redpoint73 said:
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
Click to expand...
Click to collapse
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine. And as mentioned I found the stock recovery as well.
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Thanks for the help and suggestion too btw
magicbumm328 said:
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine.
Click to expand...
Click to collapse
SuperUser is same as root, and is fine.
When I say "modifed by root" that often is when a user deletes "bloatware" they don't want, or adds apps, or modifies apps in the system partition.
If you didn't explicitly do any of those things, you should be fine. You will know this is the problem when you install the OTA, as the install will fail with the error message that the "system has been modified".
magicbumm328 said:
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Click to expand...
Click to collapse
RUU = ROM update utility
RUU is super easy, you don't really need much guidance to use it. LOCKED or RELOCKED bootloader is required to run it (UNLOCKED if okay if you have s-off). PC required, and the RUU will wipe the phone (so backup any personal data you want to keep, into your PC, cloud, etc.). Aside from those points, RUU is a self-explanatory executable (.exe) program that runs from your PC, and simple to use.
Relocking the bootloader is accomplished easily with a single fastboot command (after connecting phone to PC and booting into fastboot mode): fastboot oem lock
This is also assuming you did the bootloader unlock yourself, and therefore have fastboot/adb setup on your computer.
Running the RUU itself (after relocking the bootloader) is very easy. Boot into OS (some folks have better success being booted into fastboot mode, but I think the RUU is designed to run when booted into OS), connect to PC, then just run the RUU executable on your PC. The RUU executable will then just guide you what you need to do. Its mostly automated, you just need to confirm a few dialogue screens, etc. The RUU will reboot the phone a couple times, install the needed files automatically, and that's really it.
However, since you seem confidant you already have a stock ROM and corresponding stock recovery, I suppose the RUU doesn't gain you too much. But if you hadn't done those steps already, it often saves folks the hassle of tracking down the right stock ROM and recovery for their CID and current firmware. RUU in my opinion is a cleaner install, as it installs a complete stock image (not just updating piecemeal, like an OTA often does).
Also, since OTAs typically need to be installed in sequence, you will probably need to OTA to 2.23 software, than another OTA to 3.42 software. As RUU is a complete image, it would get you to 3.42 software in one fell swoop.
One other thing to note, is that if you are for some reason not connected to AT&T's network (using another carrier, another country, etc.) you will not get any OTAs on the AT&T branded device. AT&T oddity here, most other version will still OTA, even when not connected to a specific carrier. In contrast the AT&T RUU is able to be downloaded and run by anyone with an internet connection and PC (regardless of country, carrier, etc.). I'm under the assumption that most folks on this forum section are on AT&T's network, although I know that some are not (you haven't stated either way).
RUU links are included on my Index thread under heading "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
Aside from wiping the phone (OTA keeps user data, but you may end up wiping anyway if you run into bugs after OTA), the other downside to RUU is that you need to relock the bootloader. Then you need to unlock the bootloader again (via the HTCDev.com site, or alternately sunshine) if you want to install custom recovery, install custom ROMs, root, etc.
So the choice is really yours (RUU versus OTA). I'm just giving it as an alternative.
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
Software up to date issue
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
Android version 5.0.2
HTC Sense Version 6.0
Software Number 4.28.502.1
HTC SDK API Level
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
I believe this phone was originally purchased from ATT on May of 2016 if it makes any difference , figured I post it. since it could be a newer version of HTC M8.
Also is there a way to back up my current stock rom, without Rooting phone ? Thanks for all your help.
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
My responses below in red font:
ELEVO said:
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
That is correct, the AT&t version (and most US versions) can only OTA update if connected to the proper branded carrier (AT&T in this case). Therefore, the RUU is your best option to update.
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
You can. But you need to flash the 6.20.502.5 firmware first, before you can flash the RUU. See instructions to flash the firmware here: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Then run the RUU. Keep in mind, that RUU will wipe the phone. So backup your data to an off-phone location (cloud, computer, etc.) before RUU.
Also is there a way to back up my current stock rom, without Rooting phone ? The current Lollipop ROM? No, there will be no way to revert to LP by official means, once you RUU to Marshmallow. I doubt you will find the need or desire to "downgrade" to obsolete LP version. If for some reason you did want to, there are options, but would require unlocking the bootloader (to install custom recovery and flash a Lollipop ROM), or s-off (which would allow you to "downgrade" by RUU - which is not allowed with s-on).
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
You are misunderstanding a couple things:
1) s-off is not a setting in Developer Options. s-off can only be obtained with sunshine app ($25)
2) You don't need s-off to root this device. Simply unlock the bootloader, install TWRP, and flash SuperSU to root
Click to expand...
Click to collapse
Detailed
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks for the detailed reply, really helpful and greatly appreciated :good:
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device? or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Again, my responses in red font:
ELEVO said:
Thanks for the detailed reply, really helpful and greatly appreciated :good:
You're welcome. Always happy to help!
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device?
You can't flash the Dev Edition RUU with s-on. Even though the versions are very similar (same model ID - MID) the two versions have different carrier ID (CID). Wrong carrier ID will make the Dev Ed RUU fail, by definition. And the only way to change CID is with s-off. Further, its not really necessary to flash the Dev Ed RUU (and not worth spending money of s-off) to accomplish what you want (see more below)
or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Its correct that the AT&T stock ROM disables tethering. Flashing most custom ROMs (or the Dev Ed ROM) will enable tethering - as well as remove annoying AT&T branding and bloat apps. Flashing the Dev Ed RUU is not necessary to accomplish this.
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
You need to relock the bootloader in order to flash firmware and RUU (command: fastboot oem lock). Once the RUU is complete, the phone will be on a fully stock "factory" image. So you will be unrooted. You will also be back to stock recovery (no longer have TWRP installed). From there, what you want to do:
1) Unlock the bootloader again. Either use the same unlock bin code you used to unlock BL before. Or get a new code from HTCDev.com
2) Flash TWRP back to the phone with fastboot. TWRP 3.0.2 is recommended for compatibility with MM firmware.
3) Flash the desired custom ROM. The custom ROM will be rooted (if you flash the Dev Ed ROM, you can select root in the AROMA installer).
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Always good to make backups. Although be aware, that RUU will wipe the phone, including internal storage. So if you picked internal storage as your backup location, you'll want to move/copy to another location (removable SD is okay, otherwise to computer or cloud).
Also note that restoring app data (as well as call logs, SMS) using Titanium, after RUU or ROM flash should be okay. But don't restore any system data, as this can cause problems.
Click to expand...
Click to collapse
redpoint73 said:
Again, my responses in red font:
Click to expand...
Click to collapse
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Bricked ?
ELEVO said:
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Click to expand...
Click to collapse
I think i may have bricked my phone? I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Phone would not reboot into anything but dark screen. even when i restarted it with power button. the only thing that worked for me, was Holding Down Power/Volume and quickly hit the volume down button before device would vibrate to reboot, that took me into recovery. Below is what i see in Recovery.
Phone now has new software
***RELOCKED***
m8_UL_CA PVT SHIP S-ON
HBOOT-3.1.0.0000
RADIO-4.0 [email protected]
OpenDSP-V56.2.2-00593-M8974_FO.0126
0S-6.20.502.5
eMMC-boot 2048MB
APR 14 2016,19:39:46.0
HBOOT
<Vol UP> to previous item
<Vol Down> to next item
<Power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
I was able to run and "IMAGE CRC" via boot loader. it gave me alot of numbers after calculating. not sure if that is a good sign ?
Things I've tried in Recovery.
1. Recovery goes back to black screen.
2. SHOW BARCODE Works- 3 bar codes showed up.
3. Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
4. Tried to do a factory reset and tries to do it, then a black phone pops up on screen with green arrow sgoing in circles for like 10 seconds. then reboots to dark screen.
Please Help :crying: Thanks
Can anyone help me with this? I bought the phone with me on vacation and now using an HTC Developer Edition that the button down doesn't work and Volume down button us sunk in But at least i have my phone with all my contacts and apps , For now ?
I would like to know if i can unbrick my other HTC . Thanks.
Late in responding, as I was on work travel myself, and not on XDA for over a week.
ELEVO said:
I think i may have bricked my phone?
Click to expand...
Click to collapse
It's basically impossible for you to do anything with an s-on M8 that will actually brick it. That is the good thing about s-on.
ELEVO said:
I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Click to expand...
Click to collapse
I think you only flashed the firmware.zip and not the RUU. Based on the condition here, and your other thread you created here: https://forum.xda-developers.com/htc-one-m8/help/htc-one-e-m8-fastboot-issues-t3757628
I clearly described above to flash the firmware.zip then the RUU. They are 2 completely different things. Firmware is about 80 MB and only contains hboot, radio, and a few other things. RUU is a full image that is 1.5 GB.
No boot after flashing signed firmware is normal, as it expects the RUU to be run afterwards.
ELEVO said:
Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
Click to expand...
Click to collapse
adb doesn't work in fastboot mode. Only fastboot commands will work in fastboot mode. You can only use adb when booted to OS (not an option for you, obviously) or alternately in custom recovery TWRP. So what you describe (adb not working) is normal and expected.
However, fastboot is enough to get the phone working from the described condition.