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.
Related
I have HTC One from Three UK, I got S-off, Super CID 11111111, currently on viper One, wondering if anyone tried changing there MID and CID and work out way to get taiwanees 2.24 update, now I dont want people saying do this do that, please I want to know who actually done this successfully. If Yes, Can you please share your experience.
I have a question...why? Why would you want to go through the trouble just to get an ota when were very shortly going to have stock rooted roms..I just can't get why people get so upsy to get the ota
a box of kittens said:
I have a question...why? Why would you want to go through the trouble just to get an ota when were very shortly going to have stock rooted roms..I just can't get why people get so upsy to get the ota
Click to expand...
Click to collapse
I agree with you, Just wanted to get earliest updates, one more thing with that update HTC has already taking out all the reasons of custom rom for me!!
and one more thing it will flash the firmware, and there would be stability, i am becoming more of flashoholic with the phone all the time in recovery!!:laugh::laugh:
I have done it so I could get ota from dev edition, changing the cid is easy however changing the mid is not. You must flash engineering hboot and add some changes using android sdk command prompt. If your interested let me know, however you can easily update your firmware and Rom pretty easy and most developers are only a couple days behind an update, plus they are much improved from what HTC original Rom. I would wait the couple day and flash the Rom and if your concerned about firmware there are many threads on xda that are pretty much noob proof! Good luck
handman29 said:
I have done it so I could get ota from dev edition, changing the cid is easy however changing the mid is not. You must flash engineering hboot and add some changes using android sdk command prompt. If your interested let me know, however you can easily update your firmware and Rom pretty easy and most developers are only a couple days behind an update, plus they are much improved from what HTC original Rom. I would wait the couple day and flash the Rom and if your concerned about firmware there are many threads on xda that are pretty much noob proof! Good luck
Click to expand...
Click to collapse
Thanks for the Info. Did you follow this guide.
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
3alaawi said:
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
Click to expand...
Click to collapse
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
LibertyMarine said:
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
Click to expand...
Click to collapse
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Ok.. I flashed the zip.. but this really shouldn't be an issue
But with "excluding other firmware parts" I meant.. if you try another ROM and there it works, you should definitely know that the issue is caused by the system and not by hardware or bootloader etc...
Try another ROM and if it works fine, you can try another RUU.. maybe the zip.. and then you can re-unroot your HTC One and then they won't have any chance finding out what you'd done
3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Did it work? Or can I provide more help?
LibertyMarine said:
Did it work? Or can I provide more help?
Click to expand...
Click to collapse
I actually just booted into the bootloader and turned the phone on again. Then I could lock my device again and it seemed stable though I didn't have much time to test it. I just sent it in for repairs earlier today (for another issue, I have the camera tint problem with my device).
I'm guessing the previous times I reset it, it had that option in the power menu on (fast boot or something like that) maybe thats why the problems didn't go away?
Anyway, thanks for your help
Dont't buy HTC. They Thef's .
This is Problem.... Producer send fake updates to destroy all firmware stock too. I Have Desire 626 from ORANGE PL and my phone get update with this same problems. One idea. Dont't buy HTC. They Thef's .
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
Delete.
dakota123456789 said:
Okay, a little backstory here first. So I recently got a Note 4 and switched from Sprint to TMobile. I now want to give my M8 HK Edition to my mom who still has Sprint and is using an S3. I had my M8 Rooted, S-OFF, and unlocked. Since then, and I have been trying to figure this out for about a week, I have returned my device to S-ON, relocked, and unrooted. My device in bootloader now says "Software Status - Modified, Relocked, and S-ON." Which I believe to be all normal. Now here is my problem, I am in no way able to factory reset the device. I can't run an RUU, run any system updates, anything to get it closer to new than it is.
I am on Software Version: 1.54.654.13
Android Version: 4.4.2
Is there anything I can do? It is really bothering me.
I've been trying to figure this out for days. Searching on google and XDA, and keep running into the same stuff. All I want to do is factory reset this device.
Click to expand...
Click to collapse
Find the latest ruu
I feel so dumb. After reading the directions in the M8 RUU Section, I thought that you had to pick the RUU that related to your model and firmware version. I guess the version I was selecting was an older one and not actually the matching firmware RUU. Thanks gstanke.
I messed up this phone big time, and I accept all responsibility. However, I would just want to know if it can be salvaged in any way at all possible.
Here is what happened:
I bought the phone on ebay. It was rebooting just after booting up. I read somewhere it had to do with the radio. I flashed the radios for the version yet no improvement. When Lollipop RUU came out I used it to update and it stopped rebooting, but no radio. I flashed it to a CDMA network here, as I usually do, yet no service. I paid for Sunshine and unlocked bootloader. I installed CWM and flashed CM11. No radio as well. I now went into adventure mode: What if I changed CID and install a Verizon RUU, maybe it could help. I changed CID to 11111111 and tried flashing a Verizon M7 RUU. It failed and asked for Model ID compatibilty. I went further and changed Model ID to Verizon (PN0731000) from Sprint Model ID (PN0720000) and there the problem started. The RUU failed again and the phone got stuck in this mode (see attached pictures). Fastboot still works but I think there's a mixup in the CID/MID so it can't take any RUU.
Is this phone recoverable? If yes, how? I will be very happy to try anything, even if it means spending extra to get it done. I would want to fix this and learn from the process.
Thanks in advance.
ezeuba said:
I messed up this phone big time, and I accept all responsibility. However, I would just want to know if it can be salvaged in any way at all possible.
Here is what happened:
I bought the phone on ebay. It was rebooting just after booting up. I read somewhere it had to do with the radio. I flashed the radios for the version yet no improvement. When Lollipop RUU came out I used it to update and it stopped rebooting, but no radio. I flashed it to a CDMA network here, as I usually do, yet no service. I paid for Sunshine and unlocked bootloader. I installed CWM and flashed CM11. No radio as well. I now went into adventure mode: What if I changed CID and install a Verizon RUU, maybe it could help. I changed CID to 11111111 and tried flashing a Verizon M7 RUU. It failed and asked for Model ID compatibilty. I went further and changed Model ID to Verizon (PN0731000) from Sprint Model ID (PN0720000) and there the problem started. The RUU failed again and the phone got stuck in this mode (see attached pictures). Fastboot still works but I think there's a mixup in the CID/MID so it can't take any RUU.
Is this phone recoverable? If yes, how? I will be very happy to try anything, even if it means spending extra to get it done. I would want to fix this and learn from the process.
Thanks in advance.
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showthread.php?t=2490792
Problem solved. I had to try so many things, but the good thing is that this phone (once you're S-OFF and can get into fastboot) is virtually unbrickable. At last everything works now, even the GSM unlock. I will try and outline the steps I went through in case someone someday needs it.
Of course no way to install Verizon ruu some hardware differences have been found