I have a rooted HTC One from Telus.
I know you cannot OTA update the phone when its rooted it keeps giving an error during the update.
I want to unroot and return to stock.
I found found a Nandroid backup for TELUS as the RUU is not available.
Can someone please help with steps on how to restore the device so I can do the carrier updates on the device.... I don't care about the tamper stuff...
I know Telus will be releasing the KIT KAT update shortly and I want to do the carrier update.
Please help!!!
I am really sorry if this has already been discussed in a thread but I have searched high and low and I can't find any clear information for the Telus device.
Please if we can keep this just to the TELUS variant I will really appreciate it as I see so many threads go sideways!
Thank you for any help anyone can shed!!
CMD line is just fastboot oem lock. If you are looking at Nandroids, I am guessing you have installed custom recovery, maybe a custom ROM? If not, re-locking will give OTA updates, I am pretty sure of. I also think that the AIO toolkit works on TELUS http://forum.xda-developers.com/showthread.php?t=2183942. Worth a shot. Maybe someone else who has tried can chime in.
Hey Thanks for the reply I actually figured it out... long process but easy...
http://forum.xda-developers.com/showthread.php?t=2383992&page=6
I left out a few steps listed in the original thread... worked like a charm.. i didn't care for the tamper .. I left S off and was able to do all of the OTAs..... if anyone else needing help this is what I did... if not refer to the original thread to reset the tamper and re-lock....
1. changed CID back to ATT (CWS__001)
2. re-ran ATT RUU
3. changed CID back to TELUS001
4. booted TWRP
5. ran a simple backup so I could know the correct location to copy the TWRP stock nandroid
6. booted the phone
7. copied the stock twrp nandroid to the right location ( /TWRP/BACKUPS/XXXX/...
8. booted twrp
9. restored backup
hack14u said:
CMD line is just fastboot oem lock. If you are looking at Nandroids, I am guessing you have installed custom recovery, maybe a custom ROM? If not, re-locking will give OTA updates, I am pretty sure of. I also think that the AIO toolkit works on TELUS http://forum.xda-developers.com/showthread.php?t=2183942. Worth a shot. Maybe someone else who has tried can chime in.
Click to expand...
Click to collapse
software update
hello here I have a TELUS HTC ONE here are the details:
LOCKED
S-ON
H-BOOT 1.55.0000
M7-UL-PUT
September 17.2013
CID TELUS001
then here I would like to have the latest international day is that I have to change a SUPER CID glass but I do not how it is.
then here if you could help me thank you
Related
I have been trying to find a way to unroot my AT&T HTC One and revert back to stock, but I keep reading that I need a RUU and the AT&T one is now out. I have had success in unlocking and locking the boot loader, but in doing so, a nandroid backup was wiped. I currently have the bootloaded unlocked and twrp recovery with SuperSU installed, but I would like to remove SuperSU.
Is there any way to remove it for good or reflash my device to bring it back to stock?
Thanks
aophyz said:
I have been trying to find a way to unroot my AT&T HTC One and revert back to stock, but I keep reading that I need a RUU and the AT&T one is now out. I have had success in unlocking and locking the boot loader, but in doing so, a nandroid backup was wiped. I currently have the bootloaded unlocked and twrp recovery with SuperSU installed, but I would like to remove SuperSU.
Is there any way to remove it for good or reflash my device to bring it back to stock?
Thanks
Click to expand...
Click to collapse
http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
You have probably already read this, I'm not aware of the RUU being available for the AT&T variant yet. Where did you find it?
You have probably already read this, I'm not aware of the RUU being available for the AT&T variant yet. Where did you find it?
Click to expand...
Click to collapse
Terribly sorry, but I meant to write "not out" instead of "now out"
And yes I have read that and keep checking back every couple of days to see if the AT&T one ever shows up.
Info:
Bell Mobility HTC One 32GB
S-OFF
H-Boot 1.54 Currently
Fully converted to Google Edition using 4.3 RUU
CID Changed to the Google One
I've literally been on here all day trying to figure this out. I need to sell the phone and can't afford to brick it.
Unfortunately, my Hard drive containing my Nandroids crashed and I lost them.
I cannot find a Bell Mobility RUU. There is a Nandroid backup on HTC1 Guru Here - Very first one listed under CWM Nandroids
http://www.htc1guru.com/dld/m7-cwm-n...-29-666-5-zip/
How can I revert to stock with this?
Is that Nandroid a 4.1.2 Rom? Bell never got 4.2.2, they are still on 4.1.2 so I assume so?
I think I can do this - Any help would be appreciated, need to get this done ASAP.
1) Change my CID back to BM_001 using ADB/Fastboot commands
2) Flash Custom Recovery - CWM in this case using ADB/Fastboot commands
3) FIRMWARE? I'm on the stock 4.3 Google Edition Rom - Do I need to flash old firmware? (Hboot, Radios, etc). If so, what files do I flash and how? Can somebody provide a link here?
4) Restore the Nandroid Backup
5) Flash the Stock Recovery back? Where do I get this from for the Bell 4.1.2 rom?
I will leave the phone S-OFF for whoever buys it. Is this it? I need help with Part 3 specifically if this is the procedure.
If anyone can help I'd gladly buy ya a beer!
I know I'm probably over complicating this.... just little experience with HTC phones. My main questions are regarding the CID and Firmware.
Anyone?
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
Hi All,
So need some help. I have an ATT m8 that I did a GPE conversation following the tutorial at
http://sakitechonline.com/fully-convert-your-htc-one-m8-to-google-play-edition-w-ota-updates/
as well as a youtube video.
So there's a section about CID's and in the tutorial link, it says if my CID matches one of the ones listed, I can skip down to step #6 and install the GPE (which it did match, so I didn't change my CID to GOOGL001.) My question is, will I have issues with future OTA's? If so, do I have to start from scratch to change my CID, or can I do it as my phone currently sits right now? Also, if I do it as my phone currently sits, will it wipe my phone? Lastly, how do I go about changing my CID at this time? I know there are a few tutorials out there, but I'm not sure if I can follow them since most of the instructions to change CID's are midway through a tutorial and I'm already converted. I just don't want to brick my phone, and I've had bad luck and what not.
Any help would be great as I'm now using this phone as my primary and I don't wan't to have issues when android L finally decides to roll out. Thank you in advance!
jm0327 said:
Hi All,
So need some help. I have an ATT m8 that I did a GPE conversation following the tutorial at
http://sakitechonline.com/fully-convert-your-htc-one-m8-to-google-play-edition-w-ota-updates/
as well as a youtube video.
So there's a section about CID's and in the tutorial link, it says if my CID matches one of the ones listed, I can skip down to step #6 and install the GPE (which it did match, so I didn't change my CID to GOOGL001.) My question is, will I have issues with future OTA's? If so, do I have to start from scratch to change my CID, or can I do it as my phone currently sits right now? Also, if I do it as my phone currently sits, will it wipe my phone? Lastly, how do I go about changing my CID at this time? I know there are a few tutorials out there, but I'm not sure if I can follow them since most of the instructions to change CID's are midway through a tutorial and I'm already converted. I just don't want to brick my phone, and I've had bad luck and what not.
Any help would be great as I'm now using this phone as my primary and I don't wan't to have issues when android L finally decides to roll out. Thank you in advance!
Click to expand...
Click to collapse
So I ended up changing my CID to GOOGL001 from CWW__1 (or something). Is there any "prep" work I need to do to my phone besides having S-OFF before changing my CID so as not to brick it later or have issues with OTA's? Again, just don't want issues down the line that I may not foresee and wasn't sure if I can just freely change my CID without doing anything beforehand.
jm0327 said:
So I ended up changing my CID to GOOGL001 from CWW__1 (or something). Is there any "prep" work I need to do to my phone besides having S-OFF before changing my CID so as not to brick it later or have issues with OTA's? Again, just don't want issues down the line that I may not foresee and wasn't sure if I can just freely change my CID without doing anything beforehand.
Click to expand...
Click to collapse
Dude, fire is going to rain down from the skies onto your phone. JK, if I remember correctly, the only thing I did was make sure that I had the GPE recovery installed and relock bootloader and got OTA's just fine. I am thinking about playing with the GPE again too.
hack14u said:
Dude, fire is going to rain down from the skies onto your phone. JK, if I remember correctly, the only thing I did was make sure that I had the GPE recovery installed and relock bootloader and got OTA's just fine. I am thinking about playing with the GPE again too.
Click to expand...
Click to collapse
haha,, i wouldn't be surprised if my phone spontaneously combusted. Hmm, I haven't read anything about relocating the boot loader to make it work with OTA's. I only remember the CID thing. Thanks for the tip, I'll look into it.
jm0327 said:
Hmm, I haven't read anything about relocating the boot loader to make it work with OTA's. I only remember the CID thing.
Click to expand...
Click to collapse
That's because its not correct. You don't need to relock the bootloader to get or install OTAs. You do need stock recovery, and all system files need to be intact (if any are modified/deleted/frozen by root, they need to be restored to stock condition).
redpoint73 said:
That's because its not correct. You don't need to relock the bootloader to get or install OTAs. You do need stock recovery, and all system files need to be intact (if any are modified/deleted/frozen by root, they need to be restored to stock condition).
Click to expand...
Click to collapse
Sounds like I'm good to go now. I used the Stock Non-Rooted 4.4.4 2.12.1700.1 RUU Zip. Thanks for the heads up!
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.