I have At&T HTC One M8 which is rooted and unlocked
Android version: 4.4.2
Software version: 1.58.502.1
Baseband version: 1.16.21331931. LA11G_20.31A.4145.02L
Build number: 1.58.502.1 CL335549 release-keys
Currently the phone is using in india and not able to update to lolipop. Please provide details steps to update.
You won't get the update OTA, since you aren't connected to AT&T's network. This is specific to AT&T (most other versions can update regardless of network). And also probably the reason you are still on 4.4.2 (missed 4.4.4 update also).
Download the latest RUU to a computer (PC required). Connect phone to computer (backup any personal data you want to keep, the phone will be wiped), relock bootloader, and run the RUU.
RUU download and more detailed instruction on running it are at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-att/news/
redpoint73 said:
You won't get the update OTA, since you aren't connected to AT&T's network. This is specific to AT&T (most other versions can update regardless of network). And also probably the reason you are still on 4.4.2 (missed 4.4.4 update also).
Download the latest RUU to a computer (PC required). Connect phone to computer (backup any personal data you want to keep, the phone will be wiped), relock bootloader, and run the RUU.
RUU download and more detailed instruction on running it are at the bottom of the following webpage:
Hi
Thank You for the information. i have downloaded the RUU and ran but after clicking on Accept , just closing the window without any prompt. also can you provide steps how to relock bootlader.
Thank You
Click to expand...
Click to collapse
malli_18arjun said:
also can you provide steps how to relock bootlader.
Click to expand...
Click to collapse
1) Connect phone to PC in fastboot mode.
2) Open command prompt on PC
3) Change command prompt directory to wherever fastboot.exe is located
4) Type command: fastboot oem lock
5) After its done (phone may reboot) you can confirm on bootloader screen that is says RELOCKED
redpoint73 said:
1) Connect phone to PC in fastboot mode.
2) Open command prompt on PC
3) Change command prompt directory to wherever fastboot.exe is located
4) Type command: fastboot oem lock
5) After its done (phone may reboot) you can confirm on bootloader screen that is says RELOCKED
Click to expand...
Click to collapse
Thanks a lot it worked smoothly
same issue
HI,
I'm having the exact same issue with my unlocked AT&T m8. The problem is I'm an android newbie, and i'm unfamiliar with most of the terms and lingo used here.
would u be kind enough to guide me through this update process. jst brief and direct pointers would do.
thanks
Android _Newbie said:
HI,
I'm having the exact same issue with my unlocked AT&T m8. The problem is I'm an android newbie, and i'm unfamiliar with most of the terms and lingo used here.
would u be kind enough to guide me through this update process. jst brief and direct pointers would do.
for instance what does it mean to relock a booloader, and how do you do that.
thanks
Click to expand...
Click to collapse
Can you let us know the current status of your phone? Is it rooted, bootloader unlocked, S-ON?
thinkhope said:
Can you let us know the current status of your phone? Is it rooted, bootloader unlocked, S-ON?
Click to expand...
Click to collapse
its not rooted ( to the best of my knowledge), how do i check if the status of the bootloader lock and S-ON ?
upgraded but sync wont connect
did som snooping around and finally got around to successfully upgrading to lollipop 5.0.2.
redpoint's link was very helpful but i kept having difficulty in getting my phone into fastboot. after a dozen tries, i did some reasearch on youtube and found out that the start up and shut down quickly box under power setting had to be unchecked first. this was checked by default on my device.
After successfully upgrading my device, htc sync no longer connects to it. i have tried disconnecting and reconnecting the device severally, i keep getting the error message "The device needs to connect with the latest version of sync manager please check for update or download " even though i am already running the latest version which is 3.1.44.5
I have tried uninstalling and re-installing the sync manager to no avail.
I really need help with this as I currently cannot restore my contacts, text messages, pictures etc
Is there anyway i can access my backup file without going through the sync manager ?
Android _Newbie said:
did som snooping around and finally got around to successfully upgrading to lollipop 5.0.2.
redpoint's link was very helpful but i kept having difficulty in getting my phone into fastboot. after a dozen tries, i did some reasearch on youtube and found out that the start up and shut down quickly box under power setting had to be unchecked first. this was checked by default on my device.
After successfully upgrading my device, htc sync no longer connects to it. i have tried disconnecting and reconnecting the device severally, i keep getting the error message "The device needs to connect with the latest version of sync manager please check for update or download " even though i am already running the latest version which is 3.1.44.5
I have tried uninstalling and re-installing the sync manager to no avail.
I really need help with this as I currently cannot restore my contacts, text messages, pictures etc
Is there anyway i can access my backup file without going through the sync manager ?
Click to expand...
Click to collapse
If you have a nandroid backup you can use nandroid manager from the play store to restore your contacts
Sent from my HTC One_M8 using Tapatalk
i only backed up with the sync manager
Related
I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
elijahkan14 said:
I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
Click to expand...
Click to collapse
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Kienan said:
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Click to expand...
Click to collapse
I can't get any of these methods to work
elijahkan14 said:
I can't get any of these methods to work
Click to expand...
Click to collapse
1. Make sure you are on the latest software: 2.17.605.2
2. Factory reset your phone
3. Slowly go through the manual instructions here: [Script] Automated Unlock/SuperCID/Temp-Root scripts for Windows and Linux
So, I've unlocked this phone before.
Just got a replacement.
EVERYTIME I put the token code in and summit I get failed!
screenshot of the error:
http://s28.postimg.org/z8obp6h58/Untitled.jpg
I tired a few different codes and nothing.
HELP?
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
BlowUpTheOutsideWorld said:
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
Click to expand...
Click to collapse
I was having difficulty with the SuperCID hack, and it appears that it was due to an OTA update. I was able to following the directions prescribed here, but I had HBOOT 1.15 and not 1.16. The basic idea is to
1. Gain "temp-root" access using the loop-restore trick together with the fake_backup.ab file.
The next steps were failing for me. I was able to verify that mmcblk0p4 had been copied over correctly, with the "modded" version, but each time the boot loader was rebooted, it would be replaced with the original version containing VZW__001, and not 11111111. However apparently all that needed to be done to reach S-OFF status was:
2. Run Rumrunner after obtaining temp-root status. The Rumrunner binary unlocks the phone and places it in S-OFF status.
Hello everyone, I'm a bit of a noob so bare with me. Thanks for taking the time to hear me out.
I have a sim unlocked AT&T HTC One (M7) that I am using on T-mobiles network. I switched over last year and I don't have my AT&T account anymore. The phone is stock, not rooted at all, just sim unlocked.
I have not updated the HTC one at all since I've bought it, and I would like to update to 4.2.2 KitKat but I noticed I cannot update via T-Mobiles network. Help!!!!
P.S. Is there a way for me to update my phone manually without having to find someone with an AT&T sim card?
ricklhswood said:
Hello everyone, I'm a bit of a noob so bare with me. Thanks for taking the time to hear me out.
I have a sim unlocked AT&T HTC One (M7) that I am using on T-mobiles network. I switched over last year and I don't have my AT&T account anymore. The phone is stock, not rooted at all, just sim unlocked.
I have not updated the HTC one at all since I've bought it, and I would like to update to 4.2.2 KitKat but I noticed I cannot update via T-Mobiles network. Help!!!!
P.S. Is there a way for me to update my phone manually without having to find someone with an AT&T sim card?
Click to expand...
Click to collapse
Updates are usually done over wifi rather than the current network, being on T-Mobile should have no effect on the updates. What happens when you check for updates.
Im in Mexico and I have the same problem..
HTC unlocked.. no update via OTA.. looks like ATT punished all the unlocked phones with no-sending the update.
I can't update the phone,
no via OTA
no via ROM
no via adb push rom.zip (access denied)
no nothing..
mb_guy said:
Updates are usually done over wifi rather than the current network, being on T-Mobile should have no effect on the updates. What happens when you check for updates.
Click to expand...
Click to collapse
Hey mb_guy, thanks for the reply.
When I am connected to wifi or 4G-LTE and try to update via settings-->about-->software updates nothing happens. It doesn't even try to search for new updates. Another interesting thing is that when I try to search for updates on the phone, I see AT&T even though I have switched over to T-Mobile and am using the T-Mobile Sim Card.
P.S. I did pay for a sim unlock code from a website, could that be the reason why I am unable to update my phone?
dumitresc said:
Im in Mexico and I have the same problem..
HTC unlocked.. no update via OTA.. looks like ATT punished all the unlocked phones with no-sending the update.
I can't update the phone,
no via OTA
no via ROM
no via adb push rom.zip (access denied)
no nothing..
Click to expand...
Click to collapse
ricklhswood said:
Hey mb_guy, thanks for the reply.
When I am connected to wifi or 4G-LTE and try to update via settings-->about-->software updates nothing happens. It doesn't even try to search for new updates. Another interesting thing is that when I try to search for updates on the phone, I see AT&T even though I have switched over to T-Mobile and am using the T-Mobile Sim Card.
P.S. I did pay for a sim unlock code from a website, could that be the reason why I am unable to update my phone?
Click to expand...
Click to collapse
You can update it yourself with this RUU and a locked bootloader
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
You can update it yourself with this RUU and a locked bootloader
Click to expand...
Click to collapse
Hello. Another newbie here. Could you post directions on how to use the above file? Do I need a PC, or is there some way copy the the directly onto my HTC One.
I have the same problem as the OP. I have a SIM unlocked AT&T HTC One that is stock with a locked boot loader. I have a prepaid AT&T SIM. But I cannot get the OTA update. I've tried several times to get the KitKat update, but each time it says no update available.
Casual Adventurer said:
Hello. Another newbie here. Could you post directions on how to use the above file? Do I need a PC, or is there some way copy the the directly onto my HTC One.
I have the same problem as the OP. I have a SIM unlocked AT&T HTC One that is stock with a locked boot loader. I have a prepaid AT&T SIM. But I cannot get the OTA update. I've tried several times to get the KitKat update, but each time it says no update available.
Click to expand...
Click to collapse
the RUU is a windows EXE file just click it and follow the instructions
Back up your phone ! a RUU totally wipes everything from the phone
clsA said:
You can update it yourself with this RUU and a locked bootloader
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Actually when I try to update via ruu, I got an error.. fastboot.exe in windows.. and the installer shows in the messages in: checking header 1/5….
If I disconnect the cellphone.. There is an error with invalid copy or something like that..
A few days ago I tried with adb push rom.zip and I got an error with: permission denied (when I was trying to copy the rom to media/0/ etc..
Im starting to think that the problem is the "memory or storage" because I guess all the problems or the methods stuck trying to copy the files or something like that..
I stuck with all the methods basically :S
clsA said:
the RUU is a windows EXE file just click it and follow the instructions
Back up your phone ! a RUU totally wipes everything from the phone
Click to expand...
Click to collapse
OK I've tried running the RUU from two different computers. One computer was running Windows XP and the other was running Windows 7. Each time I get to the point where the set-up wizard asks me to accept the license agreement. When I click on the "I accept" radial button and then click on next, the set-up wizard just shuts down.
I've tried it three times on the computer running Windows XP. On the third attempt I had the Task Manager running and the process just stops and disappears.
Can anyone offer any help.
I read on another forum that replacing the SIM card can help. So I went to my locate AT&T corporate store and got a new SIM card. No luck with that either.
I purchased this phone used It is in great shape. It looks new. It is running Build Number 3.17.502.3 CL246232 release-keys.
Because I bought a used phone, I just downloaded Connectbot and verified that the phone was not rooted.
Casual Adventurer said:
OK I've tried running the RUU from two different computers. One computer was running Windows XP and the other was running Windows 7. Each time I get to the point where the set-up wizard asks me to accept the license agreement. When I click on the "I accept" radial button and then click on next, the set-up wizard just shuts down.
I've tried it three times on the computer running Windows XP. On the third attempt I had the Task Manager running and the process just stops and disappears.
Can anyone offer any help.
I read on another forum that replacing the SIM card can help. So I went to my locate AT&T corporate store and got a new SIM card. No luck with that either.
I purchased this phone used It is in great shape. It looks new. It is running Build Number 3.17.502.3 CL246232 release-keys.
Because I bought a used phone, I just downloaded Connectbot and verified that the phone was not rooted.
Click to expand...
Click to collapse
the RUU works fine ..did you md5 check your downloaded file ?
clsA said:
the RUU works fine ..did you md5 check your downloaded file ?
Click to expand...
Click to collapse
I'm sorry? what does that mean?
Casual Adventurer said:
I'm sorry? what does that mean?
Click to expand...
Click to collapse
your download was corrupt ...use an MD5 checker to test your downloaded files
clsA said:
your download was corrupt ...use an MD5 checker to test your downloaded files
Click to expand...
Click to collapse
Can you tell me where I can find this MD5 checker software?
I downloaded the software direct from the RUU Web site to the two computers I tried. How could the file become corrupt?
thank you.
If I try to install via RUU..
I got this error..
http://postimg.org/image/nzjyou0dd/
dumitresc said:
If I try to install via RUU..
I got this error..
http://postimg.org/image/nzjyou0dd/
Click to expand...
Click to collapse
There is a log file for the RUU process in C:\ruu_log\RUU_xxxxxxx.log. Please attach the log file.
cschmitt said:
There is a log file for the RUU process in C:\ruu_log\RUU_xxxxxxx.log. Please attach the log file.
Click to expand...
Click to collapse
Thank you so much..
here you go..
dumitresc said:
Thank you so much..
here you go..
Click to expand...
Click to collapse
It's looks like you have HTC sync installed? If so, uninstall it and try the ruu again.
cschmitt said:
It's looks like you have HTC sync installed? If so, uninstall it and try the ruu again.
Click to expand...
Click to collapse
Same problem..
I unninstalled the htc sync and restart the pc.. but same problem
here is the log
(if I disconnect the cellphone there is a message: loading zip info fail , update fail
dumitresc said:
Same problem..
I unninstalled the htc sync and restart the pc.. but same problem
here is the log
(if I disconnect the cellphone there is a message: loading zip info fail , update fail
Click to expand...
Click to collapse
The phone is s-on, correct? Is the bootloader locked?
cschmitt said:
The phone is s-on, correct? Is the bootloader locked?
Click to expand...
Click to collapse
That's correct.
when the error appears.. (fastboot.exe) the screen in black with HTC then if I disconnect the cellphone this is the error.. then I have to plug again and push power button until the phone restart again normally.
thank you so much for your help.
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 am rooted, have TWRP, am running stock sense 6 with 4.4.2, s-on. I want to completely get rid of anything and everything including the root. Is there a foolproof, simple way to do that? Just a heads up I am not very good at any of this, installing an RUU or anything of the like is way out of my level. All im asking is a simple breakdown of what I have to do. I also have a Mac, so some options seem to be crossed out for me.
RUU is not above your head. Especially if you unlocked the bootloader, rooted, etc. yourself. Even if not, the RUU is a tool issued by HTC for "regular" folks (with no knowledge whatsoever of modding phones) to recover their devices in various situations.
RUU is easy:
- Relock the bootloader with the command: fastboot oem lock
- Connect the phone to PC
- Run the RUU, and the RUU program leads you through the rest.
I know you said you have a Mac, but surely you have a friend or family member with a PC that you can use for a half hour.
Honestly, IMO opinion its still easier than returning to stock by other methods, which would require:
- Finding the right stock ROM or stock nandroid for your firmware number
- Putting the stock ROM on the phone and flash with TWRP
- Find the right stock recovery for your stock ROM
- Flash using fastboot
- Relock the bootloader (depending on how "full stock" you want to go)
- Additionally, if you intend to update to current OS (Lollipop) you then need to install 4.4.4 and 5.0 OTAs to get fully current. RUU will update everything at one time.
With the above method, finding the right files is the potential pitfall; and one where many folks have trouble. So in addition to just having more steps, there is also much more potential for having problems with those steps (making the process even more time consuming and stressful).
On another note, you haven't given any background why you want to return to "stock". Once a phone is rooted, I seldom recommend going back to stock, with the exceptions of:
- You are selling or giving the phone away (you should still tell the buyer that the phone was previously modded)
- The phone was rooted by a previous owner, you have no intent to use such features, and just want to return to a fully stock condition
- You are suffering some issue that you think a return to stock will resolve (RUU is better in this case)
redpoint73 said:
RUU is not above your head. Especially if you unlocked the bootloader, rooted, etc. yourself. Even if not, the RUU is a tool issued by HTC for "regular" folks (with no knowledge whatsoever of modding phones) to recover their devices in various situations.
RUU is easy:
- Relock the bootloader with the command: fastboot oem lock
- Connect the phone to PC
- Run the RUU, and the RUU program leads you through the rest.
I know you said you have a Mac, but surely you have a friend or family member with a PC that you can use for a half hour.
Honestly, IMO opinion its still easier than returning to stock by other methods, which would require:
- Finding the right stock ROM or stock nandroid for your firmware number
- Putting the stock ROM on the phone and flash with TWRP
- Find the right stock recovery for your stock ROM
- Flash using fastboot
- Relock the bootloader (depending on how "full stock" you want to go)
- Additionally, if you intend to update to current OS (Lollipop) you then need to install 4.4.4 and 5.0 OTAs to get fully current. RUU will update everything at one time.
With the above method, finding the right files is the potential pitfall; and one where many folks have trouble. So in addition to just having more steps, there is also much more potential for having problems with those steps (making the process even more time consuming and stressful).
On another note, you haven't given any background why you want to return to "stock". Once a phone is rooted, I seldom recommend going back to stock, with the exceptions of:
- You are selling or giving the phone away (you should still tell the buyer that the phone was previously modded)
- The phone was rooted by a previous owner, you have no intent to use such features, and just want to return to a fully stock condition
- You are suffering some issue that you think a return to stock will resolve (RUU is better in this case)
Click to expand...
Click to collapse
What you said about how infuriating it is finding the right files and all is what motivated me to want to start anew, maybe I will keep root then. I read up some guides online and have a better understanding of how RUUs work now. I only have one question left, how would I input the command to relock the bootloader? I understand you have to go into the command prompt window, but do i just type it in? I thought I had to navigate to my phone through it somehow. Hopefully that made sense in some way.
xeamless said:
I only have one question left, how would I input the command to relock the bootloader? I understand you have to go into the command prompt window, but do i just type it in? I thought I had to navigate to my phone through it somehow. Hopefully that made sense in some way.
Click to expand...
Click to collapse
You still haven't provided any background on whether you rooted the phone yourself. If you did, you should already have fastboot setup on your computer; as you would have needed it to issue the bootloader unlock command. So open the command prompt, than you need to change directory to whatever folder your fastboot files (fastboot.exe if on a PC) are located. Then simply type the command.
If you don't have fastboot setup on your computer, that is a different story, and you would need to do so (can give details if you indicate that is the case).
redpoint73 said:
You still haven't provided any background on whether you rooted the phone yourself. If you did, you should already have fastboot setup on your computer; as you would have needed it to issue the bootloader unlock command. So open the command prompt, than you need to change directory to whatever folder your fastboot files (fastboot.exe if on a PC) are located. Then simply type the command.
If you don't have fastboot setup on your computer, that is a different story, and you would need to do so (can give details if you indicate that is the case).
Click to expand...
Click to collapse
So I followed everything you said and it all worked out! Thanks
xeamless said:
So I followed everything you said and it all worked out! Thanks
Click to expand...
Click to collapse
Sweet, glad it worked out for you. You're quite welcome.
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.