I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
Related
Hello all, I used the htc unlock method, but I am not able to flash a different radio version.
Does anyone know how to do that?
(Just booting into bootloader does not do the trick like it would normal unlock methods)
Thanks.
Anyone?
Sent from my PG86100 using XDA App
have you tried the commands
adb reboot bootloader
fastboot boot recovery.img
and flashing the radios from fastboot? or FlashimageGUI (which probably will not work for radios)
I have been wondering this myself. I have not heard of any methods that have come up to allow this recently. Same thing goes for splash images as I havent seen any method for those.
I have an idea of how it may be possible though. Perhaps someone else with a bit more knowledge can chime in to let us know if it is possible or not.
Anyhow.
Being officially unlocked I don't believe that ROOT is an issue like it is on an unofficial method. I know typically you would NOT accept an OTA to prevent the loss of ROOT. However, being an officially unlocked device, I am not sure if it matters.
I know that when I unlocked my device I had to manually unlock it, then I installed my recovery, then I simply flashed SU to it. My thought is that you can take the OTA. If the OTA doesn't work, you may have to re-lock the device, then run the OTA. But I believe the OTA would be safe. Once OTA completed, then flash your unlock token again, put recovery back on, then flash SU again.
Or I believe you could also wait for the new RUU instead of an OTA. Put on stock ROM, re-lock, run RUU, re-unlock, install recovery, flash SU.
The problem is that you may not be able to flash back to the previous radio once you are done.
Any thoughts on this?
UPDATE: I recently (like two minutes ago) learned that an RUU will not update a radio. I was under the impression that they did. Since it will not, I guess the RUU method will not work. Still curious about the OTA method though.
From the HTCDev Q and A:
HTCDev said:
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse
yousefak said:
From the HTCDev Q and A:
Click to expand...
Click to collapse
Well, yeah. The S stays on to protect the radio.
But the S would be on regardless if you never rooted to begin with, but an OTA would allow the radio to update. So, my thought is that you can potentially take an OTA with the HTC unlock method and get the new radio.
If it were me, I would save my titanium file to my PC (just as a precaution), I would re-lock my device using fastboot oem lock, then I would run the RUU that matches my current software version. This would return me to stock/unrooted. At this point you should be able to accept an OTA. The OTA updates your radio/software/etc. Once you update, flash the unlock token again, then flash the superuser binary back onto the phone. Now, this would be contingent that HTC doesn't go back on their word and they dont push an OTA that prevents you from unlocking the phone.
Now, Ill admit I am not a developer, so I am not an expert, but it is my understanding that once it is unlocked putting root on the phone is pretty straight forward. You don't have to come up with a root method such as revolutionary, etc. It should simply allow Superuser because it is unlocked. If this is not the case, then Ill admit that my thought process is flawed. However, if it is the case, then why not return to stock, take an OTA, unlock, re-root, use titanium? Like I said, may not be able to return to previous radio, but why would you anyhow?
mildlydisturbed said:
have you tried the commands
adb reboot bootloader
fastboot boot recovery.img
and flashing the radios from fastboot?
Click to expand...
Click to collapse
Can someone tell me how exactly to accomplish the above?
I ran these commands and the it said "Installing update..." but the radio remains the same.
Thanks again.
Hey,
I currently have a stock, rooted, s-off m8 with TWRP recovery. I have already read the thread on converting to the developer edition but I have a quick question that I could'nt find in the thread. I know that through this conversion, I will lose root so the first thing I will do after following the procedure will be to re-root the device. Since this involves installing a custom recovery, I will also lose the ability to process ota's. If I then go on to flash the stock recovery, will I still maintain root with the ability to process ota's?
Thanks!
neilmopar said:
Hey,
I currently have a stock, rooted, s-off m8 with TWRP recovery. I have already read the thread on converting to the developer edition but I have a quick question that I could'nt find in the thread. I know that through this conversion, I will lose root so the first thing I will do after following the procedure will be to re-root the device. Since this involves installing a custom recovery, I will also lose the ability to process ota's. If I then go on to flash the stock recovery, will I still maintain root with the ability to process ota's?
Thanks!
Click to expand...
Click to collapse
With S-Off, root isn't important. Yes, you will need stock recovery for OTA. Easiest way to convert is change CID to BS_0001 , run RUU from HTC, and be done with it, everything will be overwritten. I even left mine with that CID and get far better signal strength on ATT and instead of hanging on to a weak LTE like ATT does, it will switch to what it needs to. Loving it and wouldn't have it any other way.
hack14u said:
With S-Off, root isn't important. Yes, you will need stock recovery for OTA. Easiest way to convert is change CID to BS_0001 , run RUU from HTC, and be done with it, everything will be overwritten. I even left mine with that CID and get far better signal strength on ATT and instead of hanging on to a weak LTE like ATT does, it will switch to what it needs to. Loving it and wouldn't have it any other way.
Click to expand...
Click to collapse
Thanks for the response! I ended converting it earlier this evening. Could you elaborate on what you mean by saying that root doesn't matter since Im s-off? Should I just now flash a custom recovery so that I can flash the SU .zip and then reflash the stock recovery so that I can continue to get ota's?
Thanks!
S-Off is greater than root. With S-Off you can do anything. I think though that to install SU you do need root, I could be wrong though. But, once you root it again, you can unroot and reroot with a simple command. As far as the rest, yep, you got it now. You can use the custom recovery to flash / install whatever you want, and then go back to stock for OTA.
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'm kind of new to rooting and flashing. But I was wondering how can I update my rooted at&t m8 4.4.4 (s-on) to the new lollipop update and stay rooted? Any help would be greatly appreciated.
natec806 said:
I'm kind of new to rooting and flashing. But I was wondering how can I update my rooted at&t m8 4.4.4 (s-on) to the new lollipop update and stay rooted? Any help would be greatly appreciated.
Click to expand...
Click to collapse
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Thanks redpoint73. Worked liked a charm
Redpoint -
I used the RUU to update, and now I can't get the SU Binary to update.
I think my backup of the app is messing things up. I installed the latest via zip file (TWRP), and am not really rooted yet.
I'm trying a clean install (wiped cache, dalvik), so I'll see if I can get rid of the original SU app I had installed (chainfire).
Edit: Still can't get rid of SU app.
Any ideas?
DanGeorges said:
I think my backup of the app is messing things up. I installed the latest via zip file (TWRP), and am not really rooted yet.
Click to expand...
Click to collapse
Latest being what number? I would suggest SuperSU 2.46.
redpoint73 said:
Latest being what number? I would suggest SuperSU 2.46.
Click to expand...
Click to collapse
That was, indeed, my problem. I was being directed to an older version of SuperSU update.zip.
Once i grabbed the REAL latest version, it worked like a charm!
Thanks, Redpoint.
redpoint73 said:
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Click to expand...
Click to collapse
What is required to run a RUU? I'm completely stock 4.4.4
redpoint73 said:
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Click to expand...
Click to collapse
Would this work if i am living out side the US? i do have an AT&T simcard but still not connected to their network!
polar2792 said:
What is required to run a RUU? I'm completely stock 4.4.4
Click to expand...
Click to collapse
Backup your personal data (RUU will wipe the phone), and own a PC. That's it. RUU is intended to be run on a stock device, so nothing special is required.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Boudjelal said:
Would this work if i am living out side the US? i do have an AT&T simcard but still not connected to their network!
Click to expand...
Click to collapse
Are you saying you are still using your AT&T account while living in a foreign country? In that case, you will usually not get the OTA. I think there are a few exceptions, such as roaming in Mexico or Caribbean areas. But otherwise, not OTA.
The RUU method noted above will work anywhere.
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.