I Recently Bought an Htc one (M7) {running android 4.3} from an electronics shop well 4.4 Kitkat Just came out so I was all excited to update to check out all the changes... sadly I was mistaken. The previous owner had tried to root the phone so im stuck with a phone that is "Tampered" "Unlocked"
with "s-on" not to bad right? well the recovery on the phone is Team win project recovery... and the phone is not rooted
I want to return the phone to stock or at least beable to get normal ota updates
Can some one give me a detailed step by step walkthrough of how to switch the phones recovery back to stock im not very tech savy in this field
Smerfurdt92 said:
I Recently Bought an Htc one (M7) {running android 4.3} from an electronics shop well 4.4 Kitkat Just came out so I was all excited to update to check out all the changes... sadly I was mistaken. The previous owner had tried to root the phone so im stuck with a phone that is "Tampered" "Unlocked"
with "s-on" not to bad right? well the recovery on the phone is Team win project recovery... and the phone is not rooted
I want to return the phone to stock or at least beable to get normal ota updates
Can some one give me a detailed step by step walkthrough of how to switch the phones recovery back to stock im not very tech savy in this field
Click to expand...
Click to collapse
you have to flash a RUU
Boachti said:
you have to flash a RUU
Click to expand...
Click to collapse
Its a Tmobile phone is there one for tmobile?
and doesnt that require s-off?
well the ruu I tried wouldnt even run on my Laptop
There are some T-Mobile RUU's. Check the T-Mobile forum. Specifically this thread: http://forum.xda-developers.com/showthread.php?t=2496074
Me personally I would check to see what HBOOT version is on there and if it's lower than 1.57, go S-OFF before doing anything else. Then just use TWRP to flash a stock or stock-ish 4.4 ROM and never mind OTA's.
Sent from my HTC One using xda app-developers app
NxNW said:
There are some T-Mobile RUU's. Check the T-Mobile forum. Specifically this thread: http://forum.xda-developers.com/showthread.php?t=2496074
Me personally I would check to see what HBOOT version is on there and if it's lower than 1.57, go S-OFF before doing anything else. Then just use TWRP to flash a stock or stock-ish 4.4 ROM and never mind OTA's.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thank you guys im looking further into it. Does the phone need to be rooted to flash a rom or just have the bootloader unlocked?
For kit Kat it needs to be s-OFF. Let's get that out of the way first.
And some s-OFF methods require a rooted ROM to work as I recall. So it's already getting complicated.
But a typical custom Rom doesn't *need* root, in fact after flashing you will discover it *gives* you root.
Going that route requires work and some reading. Then again, getting an RUU to run successfully does too.
Basically the situation you''re in is not horrible, but to go all the way forward (S-OFF Kit Kat with ability to do anything you want in the future) or all the way back (totally locked down stock system capable only of accepting OTA's ) will require work either way.
Sent from my HTC One using xda app-developers app
So basicaly it may be simpler if I...
1 s-off
2 download rom
2.5 put on phone memory
3 go to team win recovery
4 Click install and choose said rom?
is that the basics of it?
if I want the least amount of trouble?
Also I guess what makes this most confusing for me is the non stock recovery
and to use fire water for the s-off I need to remove htc sync from the phone?
I feel im doing more work and stressing than i should be?
Yes Im quite Noobish..
Pretty much yes.
There could be adventures along the way, but I think this outcome would position you well for the future.
The biggest question is how old is your HBOOT.
There is no S-OFF for 1.57 and existing exploits for 1.56 don't always work.
If you can get S-OFF, you can do anything, including a) destroying your phone by mistake; b) changing your mind later and going back to S-ON; and, my personal favorite, c) destroying your phone in the act of trying to go back to S-ON (due to modified/ damaged HBOOT partition).
If you can't get S-ON, well, see if you can get back to stock.
Occasionally you are truly stuck and can neither go forward nor backward.
Which in your case is not so bad. 4.3 works great. Honestly plenty of people here are trying to go *back* to 4.3 after trying 4.4.
With S-OFF you can always do that. S-ON, not so much..
Sent from my HTC One using xda app-developers app
Yeah.. now i have a pretty blue screen that once every 10 minutes or so will flash the google logo so yup bricked...
That would qualify as an "adventure". Still, it sounds like something less than "bricked".
See if you can enter HBOOT (hold down volume-down and power buttons for a few seconds or if you're in a boot loop , just hold down volume-down as phone is booting up).
If so, you can select fastboot and you should have the option to power down. That should give the battery a rest and give you time to think.
At some point you need to have the android tools fastboot and adb set up on your computer.
When you do, enter HBOOT, select fastboot (with phone plugged into computer via USB) and run the command fastboot getvar all.
Post the results here.
The first post of this thread doesn't really contain enough detail for others to help you otherwise.
Sent from my HTC One using xda app-developers app
Related
Before you guys jump on me, I would like to apologize for just being dumb. Even though that is the truth, may I have some help?
I didn't read the guide on turning the S-Off on my Vivid, I thought all I had to do was run the hason s-off and it would automatically do everything for me. Yeah, I didn't even know about a wire trick (I've already admitted the obvious). My Vivid just boots to the JoupunutBear screen and reboots after about 3 minutes to the same screen. I guess I've bricked my device!:crying:
Is it possible for HTC to remotely restore my Vivid, or do I have to take it to an authorized dealer that repair phones? If so, how much am I looking at? I wished I had left my phone alone, but doing some of the crazy wild and exciting stuff for phones is so cool! I wish I had read that I needed to pin mod something, or else I would not have tried to do S-Off! I just got my phone a few days ago in a trade for my HTC Shift.
I guess this will be an expensive lesson and hopefully I'll read and not think every procedure for different phones are the same.
I miss my Vivid!:crying:
Use flashtool and flash stock rom .....
Sent from my E15 using Tapatalk 2
bandarigoda123 said:
Use flashtool and flash stock rom .....
Sent from my E15 using Tapatalk 2
Click to expand...
Click to collapse
I thought as long as I had reovery image on my device, I had nothing to worry about. Boy was I wrong!
Any tips on which recovery I should use? Preferably with guide, my nerves are a bit tweaked right now.
OK, I just relocked...now what?
Downloaded AT&T stock ROM, downloaded AT&T PH39img. I guess now I'm suppose to place both files on SD card and use HBOOT?
Follow the guide in my signature titled "back to stock" (I think its step 6). Then if you want to re root or whatever follow the guide in my signature steps 1-4.
Sent from my HTC PH39100 using xda premium
Double post
slapshot30 said:
Follow the guide in my signature titled "back to stock" (I think its step 6). Then if you want to re root or whatever follow the guide in my signature steps 1-4.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Following your guide now, I'll let you know how it goes.
I have to download the RUU and not use the AT&Tzip I've already have downloaded. Seems straight forward, I'll reply back, thanks!
Since I have some time before the RUU finishes downloading, I tried to reflash factory rom using the second method. When I reboot into recovery, it does load the PG file, but it doesn't give me an option to flash anything?
Just a heads up...for me ruu never worked with a unlocked bootloader so if it doesn't work relock your bootloader with the super tool thing in he dev section...just boot into fastboot from hboot and click relock bootloader, then boot back to fastboot and run the ruu
Sent from my HTC PH39100 using xda app-developers app
mg2195 said:
Just a heads up...for me ruu never worked with a unlocked bootloader so if it doesn't work relock your bootloader with the super tool thing in he dev section...just boot into fastboot from hboot and click relock bootloader, then boot back to fastboot and run the ruu
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
thats the easiest way to do it
kobe_24 said:
Since I have some time before the RUU finishes downloading, I tried to reflash factory rom using the second method. When I reboot into recovery, it does load the PG file, but it doesn't give me an option to flash anything?
Click to expand...
Click to collapse
The beginning of step 6 requires you to relock the bootloader. Otherwise, the RUU or PH zip will not work.
Sent from my HTC PH39100 using xda premium
Man this download is taking long, I still have 15 percent to go (6 minutes)!
I guess I have to have the RUU for any of this to work, so I'll stop playing around with it before I render the device useless. So I'll be patient since I have 5 minutes to go, then I should be able to perform any of the two methods found in the guide. I'm so glad there are so many here to help me, I love you guys! Don't be too flattered, I love my Vivid more! Once this is done, I'll thank each and every one of you!
OK all, I have to leave for right now. I started the RRU utility, but it stops at checking signatures.
ERROR (155) Unknown error
The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I have an AT&T Vivid, I thought the one for Holiday Cingular was the correct one? On the phone it says RUU update failed. So I'll look into it when I get back and try then. For some reason I can't update the HBOOT?
Bye for now!
I bet you can't update the bootloader while it is locked, LOL!
As said...I'll look into it when I get back.
kobe_24 said:
OK all, I have to leave for right now. I started the RRU utility, but it stops at checking signatures.
ERROR (155) Unknown error
The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I have an AT&T Vivid, I thought the one for Holiday Cingular was the correct one? On the phone it says RUU update failed. So I'll look into it when I get back and try then. For some reason I can't update the HBOOT?
Bye for now!
I bet you can't update the bootloader while it is locked, LOL!
As said...I'll look into it when I get back.
Click to expand...
Click to collapse
It should work if you re-locked your bootloader... So that isn't the problem. Maybe somewhere during you trying to S-OFF you still managed to change the HBOOT to the unofficial one. If so, then the RUU or PH zip will both probably not work. Somehow you need to get back to the stock HBOOT. You might need to ask in the Juoponut bear thread or contact them directly.
slapshot30 said:
It should work if you re-locked your bootloader... So that isn't the problem. Maybe somewhere during you trying to S-OFF you still managed to change the HBOOT to the unofficial one. If so, then the RUU or PH zip will both probably not work. Somehow you need to get back to the stock HBOOT. You might need to ask in the Juoponut bear thread or contact them directly.
Click to expand...
Click to collapse
It says I have HBOOT-1.85.0025. I'm back now, so I'll just keep trying.
Congratulations!
Your ROM update has been completed. Your Android phone is now ready for use.
Yup guys, just had to get the right RRU which is the htc_vivid_att_RUU_3.26.502.56_US.exe
Phone is back up and running and everyone is thanked!
Big thank you for all who stood by me during my time of sorrow.
really sorry for starting a new thread but i've been searching like crazy and i have not found anything like what i have to deal with.
So the phone WAS a stock rogers Raider, sim unlocked when i bought it. Everything was okay until i started messing around with it.
What has happened to the phone:
I used hasoon's kit to unlock the bootloader and gain root access, along with rom manager and cwm because i wanted to download an ics rom for my phone. well the VERY NEXT DAY the stock ota update for ics came out for my phone, and when i tried to update it the official way it would get stuck on the htc screen until my battery completely died beyond repair, so 2 weeks later when the new battery came in the mail, i was still rooted and on 2.3. I learned after that the ota updates do not work on my rooted phone for some reason, so i tried to install an ics rom through clockworkmod recovery, and now when i try to boot my phone it gets stuck at the htc screen and doesnt do anything more, but using power and vol. UP i can still access hboot, which says "unlocked with s-on" ive tried to hit "factory reset" but it still wont boot.
If possible, what i would like to do to the phone:
Completely restore the phone to stock, locked bootloader, unrooted, and to a stock gingerbread so i can install the ota ice cream sandwich update.
I know i'm asking for a ton of help but please hear me out, im honestly getting depressed because of this darn phone.
Also, please use words as simple as you can because im really not the type of person who shouldve even started with all this stuff!
jperta said:
really sorry for starting a new thread but i've been searching like crazy and i have not found anything like what i have to deal with.
So the phone WAS a stock rogers Raider, sim unlocked when i bought it. Everything was okay until i started messing around with it.
What has happened to the phone:
I used hasoon's kit to unlock the bootloader and gain root access, along with rom manager and cwm because i wanted to download an ics rom for my phone. well the VERY NEXT DAY the stock ota update for ics came out for my phone, and when i tried to update it the official way it would get stuck on the htc screen until my battery completely died beyond repair, so 2 weeks later when the new battery came in the mail, i was still rooted and on 2.3. I learned after that the ota updates do not work on my rooted phone for some reason, so i tried to install an ics rom through clockworkmod recovery, and now when i try to boot my phone it gets stuck at the htc screen and doesnt do anything more, but using power and vol. UP i can still access hboot, which says "unlocked with s-on" ive tried to hit "factory reset" but it still wont boot.
If possible, what i would like to do to the phone:
Completely restore the phone to stock, locked bootloader, unrooted, and to a stock gingerbread so i can install the ota ice cream sandwich update.
I know i'm asking for a ton of help but please hear me out, im honestly getting depressed because of this darn phone.
Also, please use words as simple as you can because im really not the type of person who shouldve even started with all this stuff!
Click to expand...
Click to collapse
Use the guide in my signature. It's step 6. Basically what it entails is relocking the bootloader (an OTA, RUU, PH zip all won't work with an unlocked bootloader), then running the Rogers ICS RUU for your device (the link for that is in the guide). The RUU does the same thing as the OTA. That's the easiest way to do it. No need to mess around with going back to stock GB and all that. You can go straight to stock ICS if you re-lock your bootloader and run the ICS RUU.
jperta said:
really sorry for starting a new thread but i've been searching like crazy and i have not found anything like what i have to deal with.
So the phone WAS a stock rogers Raider, sim unlocked when i bought it. Everything was okay until i started messing around with it.
What has happened to the phone:
I used hasoon's kit to unlock the bootloader and gain root access, along with rom manager and cwm because i wanted to download an ics rom for my phone. well the VERY NEXT DAY the stock ota update for ics came out for my phone, and when i tried to update it the official way it would get stuck on the htc screen until my battery completely died beyond repair, so 2 weeks later when the new battery came in the mail, i was still rooted and on 2.3. I learned after that the ota updates do not work on my rooted phone for some reason, so i tried to install an ics rom through clockworkmod recovery, and now when i try to boot my phone it gets stuck at the htc screen and doesnt do anything more, but using power and vol. UP i can still access hboot, which says "unlocked with s-on" ive tried to hit "factory reset" but it still wont boot.
If possible, what i would like to do to the phone:
Completely restore the phone to stock, locked bootloader, unrooted, and to a stock gingerbread so i can install the ota ice cream sandwich update.
I know i'm asking for a ton of help but please hear me out, im honestly getting depressed because of this darn phone.
Also, please use words as simple as you can because im really not the type of person who shouldve even started with all this stuff!
Click to expand...
Click to collapse
You need to read before you jump the gun and mess around
First of all you can't be rooted and you can't have an unlocked bootloader for official updates/ruus
Second you can't flash ics unless you are s off and get an ics hboot
Here's the fix,
1) download the ruu from HTC website...I can try and find a link later
2) boot into hboot then fastboot
3) run the tool kit and use the relock bootloader option
4) if your phone reboots just go back to fastboot
5) if your bootloader now says relocked then just run the ruu
Ruu is official update done through a computer
Sent from my HTC PH39100 using Tapatalk 2
resuldsd (Simonds)
mg2195 said:
You need to read before you jump the gun and mess around
First of all you can't be rooted and you can't have an unlocked bootloader for official updates/ruus
Second you can't flash ics unless you are s off and get an ics hboot
Here's the fix,
1) download the ruu from HTC website...I can try and find a link later
2) boot into hboot then fastboot
3) run the tool kit and use the relock bootloader option
4) if your phone reboots just go back to fastboot
5) if your bootloader now says relocked then just run the ruu
Ruu is official update done through a computer
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Thank you both for your replies, i absolutely agree i really regret doing this, a link would be greatly appreciated too. and i just relocked my bootloader and it says "relocked security warning" so i guess its relocked, and finally how would i run the ruu? Im really sorry for being so clueless
The ICS Rogers RUU is here. Just boot into hboot and run it on your computer.
psmpar traditional
slapshot30 said:
The ICS Rogers RUU is Just boot into hboot and run it on your computer.
Click to expand...
Click to collapse
okay thanks so much, it always says "All free download slots are in use" which is strange because it only says that when i try to download the rogers ruu. i guess i just have to wait.
*update*
okay one more annoying question i promise. if i download gingerbread ruu from hotfile, i cant post the link but from another thread it works, and by doing what you said, hboot, plugin to computer and run the .exe, can i then upgrade to 4.0 by using the ota?
When i re-locked my bootloader, to confirm i went into h-boot, and it should say "Re locked bootloader".
But follow slapshot guide to the tee and you'll be good.
Sent from my HTC-X710a using xda app-developers app
Hi There,
After just recently switching to Android I have been having great fun customising my phone in ways I could never with my iPhone.
I currently running the latest release of TWRP Recovery and Using the Android Revolution HD ROM.
While there is currently nothing wrong with my phone I was just wondering what my options are in terms of going as far back to stock as I can.
Being 1.54 I understand I will always have re-locked on my device until an exploit is found or if I fancied shelling out for a Java Card.
In the popular RUU, OTA, etc thread under the Nandroid section is a recovery which would be compatible with my CID.
M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x
If I was to flash CVM and then proceed to restore this back and then flash the included recovery.img to my device 1. Would it work in the first place and 2. Would I be able to remove the Tampered warning.
Tbh I'm not overly worried about the warrenty. Espically being in the UK and our law covering things like this. But none the less I like being able to go down the simple root (See what I did there ) if I have to return the device.
Many Thanks and sorry for the noob question.
Syther101
1. Yes it should work
2. No it won't
You might also run into issues as you have 4.2.2 FW and will end up with a 4.1.2 ROM which might lead to touchscreen problems
Thanks for the reply Eddy. Yeah I was afraid of the touchscreen issue. Will have to have a tinker around when I get time.
From what I have read I was under the impression when you put the stock recovery abd stock ROM back on the device abd relocked the bootloader the tampered message would go.
Guess not then. Best just hope I don't have to return the device or wait for a new s-off
Thanks again
Syther101
Sent from my HTC One using XDA Premium 4 mobile app
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
I rooted my phone thinking it would benefit me, like it did on my EVO 3D, however i cannot have been more wrong. First off all the ROMS i tried (CM11, viper, insert coin,) had either a buzzing noise from the top speaker, or the WIFI didn't work. Second i cannot update the firmware using the OTA update. I download it then try to install and all that happens is it boots into TWRP. I just want to know if there is a way to get it back to normal like i just got the phone. I tried finding my Cid and doing the unlocker method, but i didn't find any Cid labeled spcs_004. Is there just an RUU i can run that will get my phone back on track with sprint? I have the Harmon Kardon model of the M8 BTW. Also i never updated my phone since i got it, so i'm on firmware no 1.54.xxx.xx (i don't know the rest of the numbers off hand).
Go to the thread in the link below. Download the 3.31.654.2 RUU to your computer. Connect your phone and computer via USB cable and boot your phone into Fastboot USB mode. Open up a command terminal with your ADB/Fastboot folder, then re-lock your bootloader using the command fastboot oem lock (unless you're S-off). Leave your phone and computer connected and from either Fastboot USB mode or while booted to the Android OS double-click the RUU to start the installer. Follow the prompts on your computer screen to install the RUU. For more info hit the second link in my sig and read the RUU section of that guide.
http://forum.xda-developers.com/showthread.php?t=2729173
Thank you. It worked and my phone is working like i just got it. Big thanks for the quick reply.
D3TH5150 said:
Thank you. It worked and my phone is working like i just got it. Big thanks for the quick reply.
Click to expand...
Click to collapse
Anytime, glad to help :thumbup:
I had the same problem just got my hk m8 rooted it and flashed nocturnal night vision ... had problems with WiFi and the Rom booting up as well as recovery so I ran the 3.31.654.2 RUU and got it running again, problem is I can't get a good signal my calls drop after like 30 seconds all the time... any help would be greatly appreciated I'll donate too
Magnum_Enforcer said:
Anytime, glad to help :thumbup:
Click to expand...
Click to collapse
Oh my gosh. If this helps get me back....
I screwed up and tried to flash ARHD v32 without being s-off and I've been without my M8 for 24 hours. And freaking out for the last nine. I knew it couldn't be that difficult to get back to reality.
BOOM shaka lakka!
I was just getting ready to call Sprint and go into a repair facility with some crazy story about how this all happened.
Thank you!:good::good::good:
Time to do some serious reading before I attempt that again.
Original Sprint CID number?
Magnum_Enforcer said:
Anytime, glad to help :thumbup:
Click to expand...
Click to collapse
Okay so I did originally mess up rooting and flashing my HTC One m8 sprint edition. Since that day I succesfully (After 8 hours of horrible things) got it back to factory reset with the exception of S-off and the super cid. The thing is I dont want the super Cid because i DO want the OTA Update. The problem is I was a noob and forgot to save the original sprint CID number. So long story short. Does anyone have the Sprint CID number. Unless the Super CID number gets OTA updates for Stock. PLease and Thanks
cboy1234 said:
Okay so I did originally mess up rooting and flashing my HTC One m8 sprint edition. Since that day I succesfully (After 8 hours of horrible things) got it back to factory reset with the exception of S-off and the super cid. The thing is I dont want the super Cid because i DO want the OTA Update. The problem is I was a noob and forgot to save the original sprint CID number. So long story short. Does anyone have the Sprint CID number. Unless the Super CID number gets OTA updates for Stock. PLease and Thanks
Click to expand...
Click to collapse
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I have SuperCID and still receive OTA notifications.
Update to reset stock htc one m8
So after doing more research I found that the image that I grabbed for stock android came from a H/K Edition. In fact the phone identifies itself as the as the Harmon edition ( I got the RUU from here http://forum.xda-developers.com/showthread.php?t=2729173) I was curious as you said that you yourself got OTA updates. Aside from lollipop, which updates did you receive. I only ask because I have heard of phones bricking up after doing an update and then something going wrong because they tampered with their tech. I DO want lollipop, but if it means losing my phone, then it is obviously not worth it.
ALSO looking at that website, I have verified that I got the NON-H/K edition....I am at a loss, I can try flashing it again, but honestly, I hate even looking at fastboot or any bootloader for the time being. Push comes to shove I will go down the rabbit hole again, but I do not want to risk a brick like before.
SIDENOTE: Not sure if its significant, but after flashing that RUU, I lost the weather widget at the top of blinkfeed, It only shows something such as "HIGHLIGHTS" If you would like I can post screen shots.
I am sorry to be such a noob and/or burden, and if you can help i would very much appreciate that if not, could you please direct me to a place where I could figure it out. Possibly a link or a person.
PLEASE AND THANKS!!!
cboy1234 said:
So after doing more research I found that the image that I grabbed for stock android came from a H/K Edition. In fact the phone identifies itself as the as the Harmon edition ( I got the RUU from here http://forum.xda-developers.com/showthread.php?t=2729173) I was curious as you said that you yourself got OTA updates. Aside from lollipop, which updates did you receive. I only ask because I have heard of phones bricking up after doing an update and then something going wrong because they tampered with their tech. I DO want lollipop, but if it means losing my phone, then it is obviously not worth it.
ALSO looking at that website, I have verified that I got the NON-H/K edition....I am at a loss, I can try flashing it again, but honestly, I hate even looking at fastboot or any bootloader for the time being. Push comes to shove I will go down the rabbit hole again, but I do not want to risk a brick like before.
SIDENOTE: Not sure if its significant, but after flashing that RUU, I lost the weather widget at the top of blinkfeed, It only shows something such as "HIGHLIGHTS" If you would like I can post screen shots.
I am sorry to be such a noob and/or burden, and if you can help i would very much appreciate that if not, could you please direct me to a place where I could figure it out. Possibly a link or a person.
PLEASE AND THANKS!!!
Click to expand...
Click to collapse
I don't actually install the OTA I flash the previous version stock rom and download the OTA, then pull it from my phone so the devs can use it to build roms and pull the firmware.
It's pretty hard to brick these devices unless you do something really crazy. As long as you can get to recovery or bootloader it's only soft bricked meaning it can be saved.
I would suggest changing your CID back to stock
Code:
fastboot oem writecid SPCS_001
Then run the latest RUU that will put you where you need to be to take the OTA when it comes.