Hi guys,
I can't install OTA update. It says that my phone may be running a modified version of its system software. So can someone help me please.
Here is the info:
INFOversion: 0.5
INFOversion-bootloader: 3.16.0.000
INFOversion-baseband: 1.15.2133156
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.54.401.5
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: HT45WWM07657
INFOimei: ****************
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul_ca
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B12000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: ab0efa49
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s
You need to restore the stock ROM for the phone's original CID/MID in order to install an OTA.
Based on your main version number (with "401" in it) you are running a stock or custom ROM based on the Euro ROM.
My CID is 11111111. I think, my phone is an at&t variant "ul_ca". So, if I install the stock rom at&t, it will be sim-locked? Anyway, I can't install a custom recovery on my phone .
rvaaness said:
My CID is 11111111. I think, my phone is an at&t variant "ul_ca".
Click to expand...
Click to collapse
I take back what I said earlier. SuperCID should be okay.
Stock ROM won't relock the SIM.
You need to re-install the stock ROM to OTA. But you might find it easier to just RUU (which will also update your phone to the latest version) rather than searching around for the right stock ROM; as long as you don't mind your data being wiped (which the RUU will do).
rvaaness said:
Anyway, I can't install a custom recovery on my phone .
Click to expand...
Click to collapse
Is your bootloader unlocked?
Fastboot/adb connectivity?
The bootloader is unlocked. But I can't access to recovery. Trying to install different custom recovery, and the phone stuck on it.
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
The bootloader is unlocked. But I can't access to recovery. Trying to install different custom recovery, and the phone stuck on it.
Click to expand...
Click to collapse
Fastboot erase cache, the try installing recovery again. Use current version TWRP (version 2.8)
Fastboot erase cache. And try to install to twrp.
Always recovery boot stuck.
Sent from my HTC One_M8 using XDA Free mobile app
Try running the Lollipop RUU to update the phone.
As long as you don't mind your data being wiped (RUU will wipe your data), the RUU is a better/cleaner install anyway.
I have read somewhere that we must change the cid matching with the RUU. So, I will lose the superCID, right?
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
I have read somewhere that we must change the cid matching with the RUU. So, I will lose the superCID, right?
Click to expand...
Click to collapse
SuperCID is fine. SuperCID by definition passes any CID check. Its only if you are on another carrier's CID, that you need to change it (to match what the RUU is looking for).
Hello,
I was very afraid to do the update by RUU because I had already brick my htc one m8. But finally, I done it. Everything was working but at the step 5/7, my computer said that the fastboot stop working. BUT I rebooted my phone and the ROM at&t works until now. Is it normal? Or must I re-install the RUU? Thank you for your reply.
rvaaness said:
I was very afraid to do the update by RUU because I had already brick my htc one m8. But finally, I done it. Everything was working but at the step 5/7, my computer said that the fastboot stop working. BUT I rebooted my phone and the ROM at&t works until now. Is it normal? Or must I re-install the RUU? Thank you for your reply.
Click to expand...
Click to collapse
Since it seems the RUU didn't run to completion, I'd run it again. Its not uncommon for this to happen.
If you check the hboot number, main version, etc. I have a feeling these have not changed, and that the steps executed successfully involved just pushing the files to the phone (and not actually installing them). But that is just a guess, as I don't know off had what step is what.
Ok. I understand now. But... Now, when I am checking the software update, there is no upadate available however my android version is 4.4.2.
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
Ok. I understand now. But... Now, when I am checking the software update, there is no upadate available however my android version is 4.4.2.
Click to expand...
Click to collapse
You typically won't get OTA updates on the AT&T version M8 unless you are connected to the AT&T network. This is a AT&T specific requirement (other versions will update fine regardless of carrier).
Did you get the original OTA (Post #1) over the network; or did you put the file on the phone yourself manually?
In any case, you can RUU to update all the way up to the latest version Android 5.0, no need to mess with OTAs at all.
I received the OTA by network, and can't put it on my phone manually as I said I can't access to a custom recovery.
I fear to use RUU, in case all steps will be not finished, and I think that maybe last time it was just a chance. Am I wrong?
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
I fear to use RUU, in case all steps will be not finished, and I think that maybe last time it was just a chance. Am I wrong?
Click to expand...
Click to collapse
I already mentioned, that the RUU not running fully the first time is fairly common.
Anything has a small chance to brick the phone (so be aware of the risks and consequences). But this is the official RUU meant for your device. Its one of the safest things around.
Ok. Thank you. But now, I have another problem. A big problem!
My phone was fallen, the screen is not broken, but the phone doesn't turn on. When I plug the charger, the LED is red and there is a picture of charging empty battery. Already try:
1- Push the Power + Volume Up
2- Push the Power + Volume Down
3- Push the Power + Volume Up + Volume Down during 1-2 minutes
Everything is not working. The LED just turn to green and after the same screen battery charging.
Do you think that it is the motherboard? Thank you for the reply.
rvaaness said:
My phone was fallen, the screen is not broken, but the phone doesn't turn on. When I plug the charger, the LED is red and there is a picture of charging empty battery. Already try:
1- Push the Power + Volume Up
2- Push the Power + Volume Down
3- Push the Power + Volume Up + Volume Down during 1-2 minutes
Everything is not working. The LED just turn to green and after the same screen battery charging.
Do you think that it is the motherboard? Thank you for the reply.
Click to expand...
Click to collapse
Try holding combo 1 for a minute or so.
Also, try combo 1 and 2 with and without the charger plugged.
Combo 3 is not a valid combo on this phone, that I am aware. No point in trying it.
Mobo? Maybe. Can be any number of things since you dropped it.
Related
The basic problem I have is that the software won't apply to my phone correctly.
Software number: 1.02.605.6. Should show 2.01.605.11
Any help would be awesome.
Here is more information that I think could be useful. Please request any additional information or clarification.
I delocked, then I ran the new RUU, then unlocked it back up. I got to the point of basically having everything stock, and it showed the new 2.01.605.11 software number, but obviously I wanted everything back, so I flashed my nand backup using amon ra. I must have missed something because I'm basically back to the same spot I used to be which was that the update would randomly shut my phone down and end on this error "E:Error in /cache/fumo/OTAPkg.zip" in the recovery screen and i'd have to battery pull to make things restart..
I'm not sure if it's different now, but my baseband version shows:
0.95.00.1118r, 0.95.00.1223r
i know the first one is the new baseband. I do not have the 5 signal bars though, although I did when everything was stock for a minute before i started messing with things again.
ON the bootloader screen it shows hboot v2.11
So I think i'm really close just missing something. Is it not cool to just flash my old recovery file that i made before starting this stuff? Did I include too much information when I created it(check too many boxes).. I'm not even sure how to ask this question to be honest.
When I try to do the update itself at this point, it will download and start to apply, and then give me the same error like this one.
'E:Error in /cache/fumo/OTAPkg.zip'
Since doing everything I currently cannot use wifi, it shows "error" in the settings menu which I know is similiar to other errors people have gotten.
I would greatly appreciate any help and explanation!
Have you tried relocking your phone and doing a factory reset via the bootloader? The OTA will pop up once factory reset. This is how to applied the OTA with ease, hope this helps!
I actually did a factory reset before any of this. I should have included that in the OP. Honestly I think it was still locked when I factory reset, but I know it worked in some form because I no longer had amon-ra recovery. I'm like right on the verge of understanding all this kernal stuff on another level but obviously not there yet since I can't figure this OTA out.
So you were rooted debloated but otherwise stock, and you just relocked *which means its still rooted right?* and then factory reset, then the update will apply.. then you unlock it again.. and then you can flash back to your debloated nand backup?
Maybe i'm not understanding flash and recover.. can i not use those interchangeably?
Could my problem be that I did the factory reset before locking it back up? I thought with some methods factory reset wasn't necessary (RUU resets things regardless)..
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
You might as well run the RUU for 2.01.605.11. It is the update and will probably fix everything for you. It will get you back to stock, you will just have to unlock the phone after you run the RUU and then reinstall Amon Ra to get root back.
thurst0n said:
I delocked, then I ran the new RUU
Click to expand...
Click to collapse
I've already run the new RUU.
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
richii0207 said:
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
Click to expand...
Click to collapse
Ok Im going to sort of "Start over soon" if I can't finnegal a way here shortly.
But I swear it showed 'relocked' in bootloader, and i was still rooted. Relocking it forces everything back to stock, but it sitll shows the updated radio, and hboot2.11
I really don't think I ever flashed a kernal unless you count amon-ra as being a kernal. Again i'm new to this and some of the terminology confuses, me so explanation to the steps helps too.
EmerikL said:
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
Click to expand...
Click to collapse
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
thurst0n said:
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
Click to expand...
Click to collapse
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
Click to expand...
Click to collapse
Getvar All shows this
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.01.605.11
(bootloader) serialno: 000000
(bootloader) imei: 000000000
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bc948b45
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done.
Click to expand...
Click to collapse
Same here.
thurst0n said:
Getvar All shows this
Code:
< waiting for device >
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-main: 2.01.605.11
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
Click to expand...
Click to collapse
First of all, I would edit your post and delete your serial number and imei as I believe that is sensitive info.
So you are updated based on what you posted, did you check your baseband in settings? That will confirm your radio update. I would try wiping your cache and dalvik cache in recovery. I do think there's some trace of that update and your phone is trying to update but that file isn't there so it errors out.
After you wipe power down, pull battery and then reboot. Hopefully that fixes it.
Then go into settings and see if it shows any updates available for you.
Sent from my ADR6425LVW using Tapatalk
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
demayod said:
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
Click to expand...
Click to collapse
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Thanks so much for the response! I appreciate the help. Very informative. I'll read through & hopefully I report back with good news tomorrow morning. :cyclops:
Yay! All done!
Thanks so much for the guide! and the help!
-Dan
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
demayod said:
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
Click to expand...
Click to collapse
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
clsA said:
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
Click to expand...
Click to collapse
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
demayod said:
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
Click to expand...
Click to collapse
This is the instructions posted by Scotty85
I'm just re-posting it for you
http://androidforums.com/t-one-all-things-root/723061-t-ruu-1-26-502-12-a.html#post5864243
Click to expand...
Click to collapse
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
here are some directions to flash "rom.zip"
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
clsA said:
This is the instructions posted by Scotty85
I'm just re-posting it for you
Click to expand...
Click to collapse
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
demayod said:
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
Click to expand...
Click to collapse
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
My mid is PN0712000. I think that was always my mid. Don't recall changing it.
My cid is currently CW__001
I've tried: RUU_M7_UL_JB_50_Cingular_1.26.502.12.exe
also tried: RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
I'm currently S-On (could that be an issue?)
I'm unlocked.
clsA said:
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
Click to expand...
Click to collapse
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Yep that should do it
Sent from my HTC One using Tapatalk 4
It did! I'm completely back to stock. I decided to update to the latest RUU that AT&T has released. Just to avoid AT&T wanting me to update to see if it fixes the problem. I know for a fact that it wouldn't fix the problem anyway.
Oddly, my phone told me I was up to date while on the .12 RUU even though I knew the .15 RUU exists. I downloaded the RUU for .15 and it ran fine once I went back to stock after running the .12 rom.zip.
In summary, you saved me from a huge headache! Thanks so much for all the help & kindness.
demayod said:
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Click to expand...
Click to collapse
How did you change our CID if you were S-On?
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
larrydadz said:
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
Click to expand...
Click to collapse
Comments: Sprint
modelid:
cid: SPCS_001
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Whoareyou said:
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Click to expand...
Click to collapse
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
krook6023 said:
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111)...
Click to expand...
Click to collapse
Maybe an issue with SuperCID...
You should read this thread: http://forum.xda-developers.com/showthread.php?t=2753631
People had a similar problem and a few were able to get back into hboot by plugging the phone to computer and persistently pressing power and volume down and/or volume up in different combinations. If you can get back to the boot loader flash a know working firmware. It's worth a shot... Here are some relevant comments from that thread...
streather said:
Same problem here, bricked the phone.
I have managed to get it to turn back on and got to the silver HTC logo but I sent the wrong command over fastboot and it turned off again
Click to expand...
Click to collapse
BanBoo said:
How do you managed it?!
Click to expand...
Click to collapse
simaka said:
OK, I got back to the bootloader.
Guys, be persistent in pressing power+vol buttons while usb connected to PC, it took me about 10-15 minutes but now I am back to fastboot!
Any ideas what would be the best course of action now?
Click to expand...
Click to collapse
simaka said:
Not sure if it was power + vol down or + vol up... But I definitely waited each time about 20 secs before switching to the other possibility. And the phone was usb connected to my pc.
Click to expand...
Click to collapse
simaka said:
Yes, each time. I also tried pressing both + and - at the same time, but that was not the winning combination.
Click to expand...
Click to collapse
yoshi8 said:
how did you recognized that you are in fastboot again? did your screen turn on again?
Click to expand...
Click to collapse
simaka said:
Yes, it has booted and screen is lit and I am in fastboot. Now wondering what is the best next step... Which firmware should I upgrade with...
Click to expand...
Click to collapse
simaka said:
Here is what I did the last time:
1. winclock showing seconds in front of me.
2. hold power + vol down.
3. Count 3 seconds
4. release.
5. Go to 1 and add 1 second on step 3 . In about 20 minutes (when I surpassed 20 secs I started from 3 seconds on step 3 again) I woke it up.
good luck!
Click to expand...
Click to collapse
Sent from my HTC One_M8 using Tapatalk
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
NxNW said:
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
you know what i mean, it was all 1s also holding the buttons didnt work
Whoareyou said:
you know what i mean, it was all 1s also holding the buttons didnt work
Click to expand...
Click to collapse
Just checking- someone said it could be an issue with the CID, and that would definitely be "an issue" ; )
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Click to expand...
Click to collapse
That right there is what bricked your phone. I honestly don't know why people care so much about the red message on boot to flash a modded Hboot. Most devs on the One international forum are starting to pull of their modded Hboots as people usually don't know flashing a modded one can brick phones on future updates or so.
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Jorakal said:
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
That is a good way however we should point if one has a moded hboot and applies the official RUU will brick the phone. Just pointing that out.
Sent from my HTC One using Tapatalk
Firmware Update
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Tewessarino said:
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Click to expand...
Click to collapse
Take a look @Behold_this thread TMOUS Firmware Packages - Release Builds for the correct firmware to return you to stock hboot.
factory reset
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
matador1510 said:
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
Click to expand...
Click to collapse
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
factory reset
majmoz said:
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
Click to expand...
Click to collapse
thanx i will try this will let you what happens
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
lordtopher said:
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Click to expand...
Click to collapse
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
majmoz said:
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
Click to expand...
Click to collapse
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
lordtopher said:
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
Click to expand...
Click to collapse
Can you connect the phone to a computer and is it recognized?
If yes, then I would recommend flashing the firmware. It contains hboot and you may have an issue with hboot.
Here is the procedure for flashing the firmware. If your phone is already in bootloader/FASTBOOT USB you can skip the first line.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Hi everyone. New to the forum and new to flashing etc. I have been playing with my phone for a couple of nights now but finally gave in and think I need to ask for help.
Here is a bit of background info so far. The last few weeks my One X+ has been suffering from getting stuck coming out of airplane mode. I am currently using an old Desire HD so thought I have nothing to lose by trying to fix the +.
I have managed so far to unlock the bootloader and root the phone. I have flashed TWRP and created a backup.
I have tried to load Android Revolution 8 which complete successfully along with the boot image but when the phone starts I get the HTC splash screen (quietly Brilliant & One X Beats Audio) but it then goes to just HTC then the phone turns itself off.
Have tried a couple of time but end up having to flash my recovery to revert back to how it was.
I feel I may be missing something and would appreciate it if someone could help me out.
Many Thanks :good:
Battery empty?
Sent from my Find 5 using Tapatalk
Lloir said:
Battery empty?
Sent from my Find 5 using Tapatalk
Click to expand...
Click to collapse
No I don't think so. Like I say I have had a few goes at it now and from reading some of the guides on here which say it is important to make sure it has plenty of charge, I have made sure it is well charged before starting.
If it helps, here is some info phone the phone:
HTC One X+
CID-HTC__001
ENRC2B
HBOOT-1.72.0000
Model ID-PM3511000
Have you tried doing a full wipe before or during flashing ARHD? Can you still get into the bootloader or recovery? I had similar problem, changed the cable then flashed the boot image again.
qasimrb said:
Have you tried doing a full wipe before or during flashing ARHD? Can you still get into the bootloader or recovery? I had similar problem, changed the cable then flashed the boot image again.
Click to expand...
Click to collapse
I have done a wipe yes. I have been picking my way through these guides which all have small differences.
http://forum.xda-developers.com/showthread.php?t=2066390
http://forum.xda-developers.com/showthread.php?t=1987885
http://forum.xda-developers.com/showthread.php?t=1995685
Yes I can still access the bootloader and TWRP recovery. The phone is currently restored back to how it was originally.
Are you flashing the boot image before or after you install the rom? With the ARHD he recommends flashing his firmware.zip before flashing the rom.
But from what I remember when my phone was stuck on the splash screen I went back into the bootloader, used another cable and flashed the firmware.zip again, restarted it and it was fine.
Info when I'm in bootloader is:
***UNLOCKED***
ENRC2B_U S-ON
HBOOT-1.30
CPLD- None
MICROP- None
RADIO- None
(Don't know why it says "none" next to radio, network etc is fine, Vodafone UK)
qasimrb said:
Are you flashing the boot image before or after you install the rom? With the ARHD he recommends flashing his firmware.zip before flashing the rom.
But from what I remember when my phone was stuck on the splash screen I went back into the bootloader, used another cable and flashed the firmware.zip again, restarted it and it was fine.
Info when I'm in bootloader is:
***UNLOCKED***
ENRC2B_U S-ON
HBOOT-1.30
CPLD- None
MICROP- None
RADIO- None
(Don't know why it says "none" next to radio, network etc is fine, Vodafone UK)
Click to expand...
Click to collapse
I have tried both ways. Flashing the boot image before and after the installing the ROM and both ways reproduce the same effect.
I have read the page where it mentions loading the firmware but as I have just set out about learning the in's and out's of loading ROMS I wasn't sure what this was. I now understand what the boot image is and what the ROM is but take it the firmware is something different. Should loading the firmware be the first step before falshing the boot image and ROM?
I have been over to his download page with the two 401 firmwares which I believe are the ones I require. The only issue I have is, it seems these are earlier versions so wasn't sure they would be correct to use. I cannot check currently as I'm at work but I think I am running firmware version 2.18.401.3.
So which one should I load?
Also here is the info from my bootloader screen:
HTC One X+
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-boomode: disabled
HW Secure Path: enabled
MODEM PATH: OFF
Model ID-PM3511000
Software Number - 2.18.401.3
CID-HTC__001
Hello there.
I have been trying at this for a while now but simply cannot figure out how to get around this issue. I have successfully rooted my M8 but now I am trying to install OTA updates. I looked up a guide on how to do this and came to this video:
Everything was going swimmingly until about minute 7 in the video where the step is to and go ahead with the OTA updates. When my phone restarts to install the updates the progress bar loads to about 1/5 and then stops for a few moments before giving me the triangle red exclamation mark icon.
How do I get around this? I'm fairly certain I have the right stock recovery. All I want to do is install the OTA updates without losing any of my current apps/settings. If an easier process is to unroot my phone and leave it that way then so be it.
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Any help pointing me in the right direction would be swell. I apologize in advance for the tall order. Thanks.
blinkdagger said:
Hello there.
I have been trying at this for a while now but simply cannot figure out how to get around this issue. I have successfully rooted my M8 but now I am trying to install OTA updates. I looked up a guide on how to do this and came to this video:
Everything was going swimmingly until about minute 7 in the video where the step is to and go ahead with the OTA updates. When my phone restarts to install the updates the progress bar loads to about 1/5 and then stops for a few moments before giving me the triangle red exclamation mark icon.
How do I get around this? I'm fairly certain I have the right stock recovery. All I want to do is install the OTA updates without losing any of my current apps/settings. If an easier process is to unroot my phone and leave it that way then so be it.
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Any help pointing me in the right direction would be swell. I apologize in advance for the tall order. Thanks.
Click to expand...
Click to collapse
If I remember correctly, you can't be rooted doing official ota updates. Finish updates, then root
BR7fan said:
If I remember correctly, you can't be rooted doing official ota updates.
Click to expand...
Click to collapse
Ok, do you think it's worthwhile to manually do the updates?
blinkdagger said:
Ok, do you think it's worthwhile to manually do the updates?
Click to expand...
Click to collapse
Yeah I found them to be those guys get the latest up very quick. Make sure your s-off
BR7fan said:
Yeah I found them to be those guys get the latest up very quick. Make sure your s-off
Click to expand...
Click to collapse
Ok thanks a lot. I will try to manually install the updates.
BR7fan said:
If I remember correctly, you can't be rooted doing official ota updates. Finish updates, then root
Click to expand...
Click to collapse
You would be remembering incorrectly. Root has no impact itself on whether an OTA will install. As long as no system files have been altered by the user (using root permissions), and stock recovery is installed. Root and unlocked bootloader are both okay. Although you will most likely lose root after the update.
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
blinkdagger said:
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Click to expand...
Click to collapse
Is your phone the T-Mob version, or an AT&T version converted to T-Mob? Because this is the AT&T version specific forum section.
Another option to update would be to just run the T-Mobile Lollipop RUU. Relock the bootloader if you are s-on. Biggest downside, is that RUU will wipe the phone; and keeping user data may be your reason for seeking the OTA route.
redpoint73 said:
You would be remembering incorrectly. Root has no impact itself on whether an OTA will install. As long as no system files have been altered by the user (using root permissions), and stock recovery is installed. Root and unlocked bootloader are both okay. Although you will most likely lose root after the update.
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
Is your phone the T-Mob version, or an AT&T version converted to T-Mob? Because this is the AT&T version specific forum section.
Another option to update would be to just run the T-Mobile Lollipop RUU. Relock the bootloader if you are s-on. Biggest downside, is that RUU will wipe the phone; and keeping user data may be your reason for seeking the OTA route.
Click to expand...
Click to collapse
I think I may have posted in the wrong forum. My phone is simply the T-Mobile version as far as I know. I think I may have changed some system files around. Do you know of a way to reset them to default that way I can proceed with the OTA updates? I do want to keep all the apps and user settings. My plan was to re root the phone after the OTA updates were done. Thanks for your help.
blinkdagger said:
I think I may have posted in the wrong forum. My phone is simply the T-Mobile version as far as I know.
Click to expand...
Click to collapse
T-Mobile has its own section, so yes this is the wrong forum section. But I'll try to help anyway, as your issues aren't that carrier specific.
blinkdagger said:
I think I may have changed some system files around. Do you know of a way to reset them to default that way I can proceed with the OTA updates?
Click to expand...
Click to collapse
Few different options.
1) Just restore the nandroid backup you made before messing with system files. And you did this, like you should before making any such mods, RIGHT? Well if not:
2) You can manually change them all back. Probably the most tedious method, especially since you don't seem sure of what you changed.
3) Find the right stock nandroid and flash it. Find corresponding stock recovery, and flash it.
4) Relock the bootloader and RUU to stock, and since you can just RUU to the current OS version, no need to OTA. After that, just unlock the bootloader again via HTCDev.com (of if you want to avoid that, sunshine) in preparation for installing custom recovery (and root) again. Yes, RUU will wipe that phone, but that brings us to the next point:
blinkdagger said:
I do want to keep all the apps and user settings. My plan was to re root the phone after the OTA updates were done. .
Click to expand...
Click to collapse
You are rooted, so back up your apps and app data with Titanium Backup (or similar root app). Then you can just restore all the apps and app data after you RUU. You should be backing them up anyway. Saying you want to keep your app data; then not having them backed up is a contradiction. If you data is important to you, back it up. And that advice goes for whether you decide to RUU or not.
Backing up setting with Titanium across ROM versions is not recommended. But unless you have a really large amount of settings customizations, it usually doesn't take that much time to set these up again manually, anyway (as long as your apps and app data are already restorable).
Option 4 above is what I would consider. Its really up to you whether options 3 or 4 are best for you. But the reason I like RUU, even though it has the extra steps of relocking/unlocking the bootloader, and backing up your data; what it saves you is from finding the right stock nandroid and stock recovery, and putting them to the correct location on the phone to then Restore with TWRP. And these steps are ones with potential for mistakes that can make them exhaust a lot more time than you would think. RUU is a complete factory image, so everything is sure to play well together, no guesswork or potential for mistakes.
redpoint73 said:
T-Mobile has its own section, so yes this is the wrong forum section. But I'll try to help anyway, as your issues aren't that carrier specific.
Few different options.
1) Just restore the nandroid backup you made before messing with system files. And you did this, like you should before making any such mods, RIGHT? Well if not:
2) You can manually change them all back. Probably the most tedious method, especially since you don't seem sure of what you changed.
3) Find the right stock nandroid and flash it. Find corresponding stock recovery, and flash it.
4) Relock the bootloader and RUU to stock, and since you can just RUU to the current OS version, no need to OTA. After that, just unlock the bootloader again via HTCDev.com (of if you want to avoid that, sunshine) in preparation for installing custom recovery (and root) again. Yes, RUU will wipe that phone, but that brings us to the next point:
You are rooted, so back up your apps and app data with Titanium Backup (or similar root app). Then you can just restore all the apps and app data after you RUU. You should be backing them up anyway. Saying you want to keep your app data; then not having them backed up is a contradiction. If you data is important to you, back it up. And that advice goes for whether you decide to RUU or not.
Backing up setting with Titanium across ROM versions is not recommended. But unless you have a really large amount of settings customizations, it usually doesn't take that much time to set these up again manually, anyway (as long as your apps and app data are already restorable).
Option 4 above is what I would consider. Its really up to you whether options 3 or 4 are best for you. But the reason I like RUU, even though it has the extra steps of relocking/unlocking the bootloader, and backing up your data; what it saves you is from finding the right stock nandroid and stock recovery, and putting them to the correct location on the phone to then Restore with TWRP. And these steps are ones with potential for mistakes that can make them exhaust a lot more time than you would think. RUU is a complete factory image, so everything is sure to play well together, no guesswork or potential for mistakes.
Click to expand...
Click to collapse
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
blinkdagger said:
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
Click to expand...
Click to collapse
Yes. As of this date, Sunshine is the only way to gain S-Off for the M8. Firewater is discontinued.
blinkdagger said:
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
Click to expand...
Click to collapse
The s-off statement in the thread you linked was specific to firmware packages. S-off is required to flash a firmware.zip, not an RUU. Those are 2 very different things.
RUU will run fine with s-on, as long as you relock the bootloader; and also you can only run an RUU that is equal or greater than the software version you rooted (looks like Android 4.4.4). So what you want is a T-Mobiel RUU for either Android 4.4.4 (software 3.xx) than OTA to Android 5.0; or RUU right to Android 5.0 (software 4.xx).
redpoint73 said:
The s-off statement in the thread you linked was specific to firmware packages. S-off is required to flash a firmware.zip, not an RUU. Those are 2 very different things.
RUU will run fine with s-on, as long as you relock the bootloader; and also you can only run an RUU that is equal or greater than the software version you rooted (looks like Android 4.4.4). So what you want is a T-Mobiel RUU for either Android 4.4.4 (software 3.xx) than OTA to Android 5.0; or RUU right to Android 5.0 (software 4.xx).
Click to expand...
Click to collapse
Hey I know it has been a while but I just got around to taking care of this. I want to use an RUU to reset everything like you mentioned. The trouble I am now having is with the re-locking procedure.
I am trying to to relock the bootloader using the "fastboot oem lock" command. When I enter the command I get this message.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.194s
I have done this about 5 times now and the lock status remains "UNLOCKED". Thank you for all your help thus far. I will continue to try to search for a solution.