Related
Hi, i am new here and after some help. Have just had my htc one repaired for the 2nd time (blown top speaker ee didn't repair properly so had to go to htc) so now want to go to stock htc_001.
I am on orange and been waiting for the 1.29 update (never going to come) so i carried out s-off on my phone this morning and changed the cid to htc_001. That all went okay and i relocked the phone and put it back to s-on. When i check the cid on the phone and with revone it says htc_001, so that all worked okay.
I downloaded the htc ruu 1.28 from xda and installed it, it when through the checking and installed it all (took about 15mins), i got no error messages it said update successful. The phone rebooted and was wiped clean and had to go through all the settings when you first get your phone. When i go to software version its still running 1.28.61.7 (the orange software) and when i check for updates it says none available. I have tried twice to install the ruu and both times it says successful but won't write over the orange software.
I am not sure what i have done wrong but some help to get my phone onto stock htc so i get timely updates and not having to wait for rubbish orange.
Any help would be greatly appriciated
Thanks Ashley
CID is HTC__001 (capital letters, double underscore). If you're not using that it might not work...can't see why not tho
EddyOS said:
CID is HTC__001 (capital letters, double underscore). If you're not using that it might not work...can't see why not tho
Click to expand...
Click to collapse
Thanks for the quick reply, I have just double checked it is HTC-001 the only thing i can think of is its because the orange version is a higher number to the htc. Would i have to install a ruu for a different area (asia maybe) and then put it back to HTC_001 and try to update to the 1.28 htc version? I wouldnt want it to be stuck on the wrong country version if it still wont update to the europe version.
HTC__001, not HTC_001 - you HAVE to use TWO underscores...
EddyOS said:
HTC__001, not HTC_001 - you HAVE to use TWO underscores...
Click to expand...
Click to collapse
Thanks for replying again, I looked and I did only have 1 underscore. So I s-off it again and changed it to HTC__001 and ran the ruu again, it still not overwriting the orange software even though it says its completed and phone is ready to use.
I am not sure what to do now to get it to overwrite it, you anyone has any answers or things for me to try that would be great.
Ashley
I'm also having the same problem. Changed my CID to HTC__001 (confirmed in bootloader), the RUU runs all the way through successfully (takes about 10 minutes) but the update is not applied.
Not sure what I am doing wrong?
saquib said:
I'm also having the same problem. Changed my CID to HTC__001 (confirmed in bootloader), the RUU runs all the way through successfully (takes about 10 minutes) but the update is not applied.
Not sure what I am doing wrong?
Click to expand...
Click to collapse
Looks like I'm having the same issue - did either of you find a solution?
I ended up applying a nandriod backup to get 1.28.
Change cid to super cid 11111111.
saquib said:
I ended up applying a nandriod backup to get 1.28.
Click to expand...
Click to collapse
Cheers - guess I'll go that way too - don't suppose you have a link to the backup - unfortunately the BugsyLawson site is down
Sorry don't have a copy to hand, I also downloaded it from that site.
Ashes20vt said:
Thanks for replying again, I looked and I did only have 1 underscore. So I s-off it again and changed it to HTC__001 and ran the ruu again, it still not overwriting the orange software even though it says its completed and phone is ready to use.
I am not sure what to do now to get it to overwrite it, you anyone has any answers or things for me to try that would be great.
Ashley
Click to expand...
Click to collapse
I had this very similar issue yesterday, What I was trying to do was restore my other HTC One back to stock before giving it to my nephew. It made me panic a little bit because after restoring my nandroid backup I proceeded to change the CID, lock the bootloader and have S-ON. But after doing that I just remembered that I forgot to change the MID back to the original and also I have the "Tampered" flag..
So I got S-OFF again and unlocked the bootlaoder and ran the 1.28.401.7 RUU just to start fresh before I change the MID back and get rid of the "Tampered" flag. Anyway even after I ran the RUU the the original ROM was still there and the "Tampered" flag was still present. I didn't get any errors at all when running the RUU.
So in the end after erasing the cache and dalvik cache I managed to successfully get the 1.28.401.7 on the HTC One and flashed the 1.29.401.12 OTA. I then locked the bootloader and put S-ON back. I didn't bother changing the MID back because I had enough of flashing for the day.
Up to now I still don't have any clue what I did or happened why the RUU won't overwrite the original ROM (nandroid restore). I'm just glad thatit is back to stock. It may have a different stock ROM but I'm sure my nephew won't even care what he has.
Rex2369 said:
I had this very similar issue yesterday, What I was trying to do was restore my other HTC One back to stock before giving it to my nephew. It made me panic a little bit because after restoring my nandroid backup I proceeded to change the CID, lock the bootloader and have S-ON. But after doing that I just remembered that I forgot to change the MID back to the original and also I have the "Tampered" flag..
So I got S-OFF again and unlocked the bootlaoder and ran the 1.28.401.7 RUU just to start fresh before I change the MID back and get rid of the "Tampered" flag. Anyway even after I ran the RUU the the original ROM was still there and the "Tampered" flag was still present. I didn't get any errors at all when running the RUU.
So in the end after erasing the cache and dalvik cache I managed to successfully get the 1.28.401.7 on the HTC One and flashed the 1.29.401.12 OTA. I then locked the bootloader and put S-ON back. I didn't bother changing the MID back because I had enough of flashing for the day.
Up to now I still don't have any clue what I did or happened why the RUU won't overwrite the original ROM (nandroid restore). I'm just glad thatit is back to stock. It may have a different stock ROM but I'm sure my nephew won't even care what he has.
Click to expand...
Click to collapse
I managed to sort it out, not sure how I did it really. I tried to flash it manually which it didn't do as it was playing games with me. I tried the ruu with supercid which it didn't work. I put it back to HTC__001 and relocked it then tried flashing manually again, it didn't work so tried afew times but no luck. So I tried the ruu one more time and it worked, I got the 1.29.401.12 ota straight away too. I think trying to manually flash it corrupted something so the ruu was able to overwrite orange. The phone nearly broke me and was about to give in but glad I kept at it though as orange updates are ridiculous.
Thanks to all that helped me with my error of not putting 2 underscores in the cid.
I am just hoping the 4.2.2 updates on my phone okay when it's released soon.
So today I turned on my phone and I have noticed that there is about an inch in depth line across the screen which isn't picking up touches anymore, so I rung HTC and it's going in for an in warranty repair on Monday. Of course, I need to convert it completely back to stock, but the only problem is I converted it to a Google Edition, changing the CID and, more importantly, the MID. I followed this thread when doing it originally, but I wanted to know if anyone knows if I can flash the same ENG HBOOT onto my GE phone and not have it brick on me? Then I can change my MID and CID back and flash the EU RUU for my phone and send it in on Monday with no issues...hopefully.
Or is there an easier way? Will they check the MID? I changed it to PN0712000 from PN0710000 and CID to GOOGL001 from HTC__001. If I just changed the CID and left the MID, would it matter? Would I still get OTA's on the stock Sense ROM on that MID?
Thanks in advance.
EDIT: So of course I've tried flashing an RUU in the meantime, but I can't. I've tried 2 of those .exe ones but they both fail, I'm assuming because of my changed model ID. I can't find an unencrypted one either that I can change the headers of so I can flash it...ugh. This is becoming a massive pain the bumholey.
RUU's fail because of MID? I thought if you have s-off any RUU would work? I need to know this too cause I might have to RUU and send in for warranty.
I don't know. But I've gone back to complete stock now, great! Of course, there's another problem FFS.
WiFi now doesn't work at all, it just says error. Fabulous. This only happened once it did a system update to the 1.29 update. Now it's asking me to update to 2.24, but I don't have enough data left on my usage to download it to see if it'll fix it, so now I don't know what to do. I've tried Googling this issue, and it appears as though some people might have had it, but I can't find a solution or anything. HALP!
EDIT: I reflashed the RUU and the WiFi is working again. I'm going to try the update again and see if it causes WiFi to not work again, if so then...I don't know what I'll do. Flash OTA's through CWM and see if it fixes it...?
EDIT2: And this time the WiFi works fine. Something must have happened the first time...but all's working fine now. Hooray! Apart from the screen, which is why I'm sending it back to HTC...
May I ask You how did You manage to go back to stock ROM? I'm on stock 4.3 GE Now. I've got S-OFF and bootloader locked. When I go to the fastboot mode and start the RUU (exe file) goes fine, but half way through (when It's moving the ROM to the internal memory) error shows up saying there are some (no specific details) problems that I can fix, but when I do all 4 fixing steps it doesn't help.
I've taken the stock Sense RUU from here
http://www.androidruu.com/index.php?developer=M7
M7/RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I'd love to know how you accomplished this, I've got the same issue going on so I need to revert back to stock using an RUU, but it keeps failing.
can you give us the breakdown of how you did it?
Needing some help if you anyone can help at all. I was trying unroot my Sprint M8. Something went wrong when I flashed stock recover wrong, I don't know what but the issues started after that, and now it keeps booting into bootloder mode and won't go pass that. I have contacted HTC Premium Support to see if they have any advice still waiting to hear back. I have contacted Sprint and they have told me to take into a store to see if it can be repaired. Does anyone have any tips or advice on how to fix this? Or do you know if it can be fixed by Sprint of if that is wasting a trip. Any help would be much appreciated. Don't know if this is the right forum or not. If not I'm sorry. Thanks for anyone in advance who has any advice tips or whatever it may be..
You can fix your issue with a RUU. Hit the second link in my sig and scroll down to the RUU section. Find the RUU that matches your current software/firmware version and follow the instructions in my thread to run the RUU on your device.
Magnum_Enforcer said:
You can fix your issue with a RUU. Hit the second link in my sig and scroll down to the RUU section. Find the RUU that matches your current software/firmware version and follow the instructions in my thread to run the RUU on your device.
Click to expand...
Click to collapse
Even though I can't boot past the bootloader mode screen?
Download the latest RUU, and make sure that the appropriate drivers are on your computer.
Also, make sure that you lock your bootloader (fastboot oem lock) before running the RUU if you are S-On. If you're S-Off, just run the RUU as is.
If that doesn't work, come back here.
Edit: Magnum responded while I was still typing. Listen to him.
And to respond your question, the RUU is run from the bootloader screen, so you're exactly where you need to be.
AarSyl said:
Download the latest RUU, and make sure that the appropriate drivers are on your computer.
Also, make sure that you lock your bootloader (fastboot oem lock) before running the RUU if you are S-On. If you're S-Off, just run the RUU as is.
If that doesn't work, come back here.
Edit: Magnum responded while I was still typing. Listen to him.
And to respond your question, the RUU is run from the bootloader screen, so you're exactly where you need to be.
Click to expand...
Click to collapse
Okay my bootloader is locked. The issues started some time between flashing stock recover and relocking the bootloader. It says Tampered Relocked Security Warning if that means anything.
Now I tried fastboot oem rebootRUU and fastboot flash zip firmware.zip when it is flashing the zip in RUU it says
targeted reported max download size
sending zip
OKAY
Writing zip
(bootloader) signature checking
FAILED
Is there anything to be done from here or should I just take it to the carrier store to see if they can fix it or should I just send it in for repiar to HTC?
Which RUU are you trying to install?
Magnum_Enforcer said:
Which RUU are you trying to install?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=23610159112652841
This one.
Download the RUU that matches the software/firmware version you already have installed. Connect your phone & computer via Fastboot USB mode, then double-click the RUU file to start the install process (if the directions to the RUU differ, use the ones posted for the particular RUU).
Magnum_Enforcer said:
Download the RUU that matches the software/firmware version you already have installed. Connect your phone & computer via Fastboot USB mode, then double-click the RUU file to start the install process (if the directions to the RUU differ, use the ones posted for the particular RUU).
Click to expand...
Click to collapse
Thats what I did. That is the RUU that matched my software/firmware. And like I said this is what it says it command prompt
targeted reported max download size
sending zip
OKAY
Writing zip
(bootloader) signature checking
FAILED
Is your phone the HK or non-HK version? Go to the link below and download the RUU again. Follow the directions for the manual update.
http://www.htc.com/us/support/htc-one-m8-sprint/news/
I also suggest reading through the thread below:
http://forum.xda-developers.com/showthread.php?t=2729173
Magnum_Enforcer said:
Is your phone the HK or non-HK version? Go to the link below and download the RUU again. Follow the directions for the manual update.
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Click to expand...
Click to collapse
Non HK.
Magnum_Enforcer said:
Is your phone the HK or non-HK version? Go to the link below and download the RUU again. Follow the directions for the manual update.
http://www.htc.com/us/support/htc-one-m8-sprint/news/
I also suggest reading through the thread below:
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Okay I will do. I am going to give it another shot if that doesn't work I guess I will just make a trip to the Sprint store in the morning. If I can't get the RUU to work do you think Sprint will be able to do anything? Or should I just pay the fee and have it repaired by HTC?
cordawgfrito said:
Okay I will do. I am going to give it another shot if that doesn't work I guess I will just make a trip to the Sprint store in the morning. If I can't get the RUU to work do you think Sprint will be able to do anything? Or should I just pay the fee and have it repaired by HTC?
Click to expand...
Click to collapse
Sprint should be able to fix it. Having said that, you don't need to try and run the RUU from a command line. Double-click the RUU file from your desktop to start the installer, then follow the prompts on your computer as they appear.
Magnum_Enforcer said:
Sprint should be able to fix it. Having said that, you don't need to try and run the RUU from a command line. Double-click the RUU file from your desktop to start the installer, then follow the prompts on your computer as they appear.
Click to expand...
Click to collapse
Cheers mate. Did that and it is now online again. Again cheers, You are a life saver mate.
cordawgfrito said:
Cheers mate. Did that and it is now online again. Again cheers, You are a life saver mate.
Click to expand...
Click to collapse
Glad to help:thumbup:
Magnum_Enforcer said:
Glad to help:thumbup:
Click to expand...
Click to collapse
I have a question im on a stock rooted rom with no system changes except for the boot up sound which i restored. I flashed the stock recovery and then tried to take the OTA but it failed about a quarter of the way through. would my best bet be to just flash the firmware and flash a 4.4.4 stock rom with the eye feature when available or do I just do a RUU? Im just trying to keep phone up to date with stock rom. any suggestions?
gscarborough said:
I have a question im on a stock rooted rom with no system changes except for the boot up sound which i restored. I flashed the stock recovery and then tried to take the OTA but it failed about a quarter of the way through. would my best bet be to just flash the firmware and flash a 4.4.4 stock rom with the eye feature when available or do I just do a RUU? Im just trying to keep phone up to date with stock rom. any suggestions?
Click to expand...
Click to collapse
Edit: See post #19.
Magnum_Enforcer said:
Currently there is no stock rooted ROM for 4.4.4. You can update your firmware if you'd like and then wait for someone to publish a stock rooted ROM. Otherwise you can troubleshoot the reason you can't install the OTA and go from there.
Click to expand...
Click to collapse
Thanks since I'm S- off can I just RUU to the current.version
Sent from my 831C using XDA Free mobile app
gscarborough said:
Thanks since I'm S- off can I just RUU to the current.version
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
My apologies. The latest stock rooted ROM can be found in the link below:
http://themikmik.com/showthread.php...L-Stock-Rooted-Base-3-30-651-2-(Android-4-4-4)
Magnum_Enforcer said:
My apologies. The latest stock rooted ROM can be found in the link below:
http://themikmik.com/showthread.php...L-Stock-Rooted-Base-3-30-651-2-(Android-4-4-4)
Click to expand...
Click to collapse
Thanks again
Sent from my 831C using XDA Free mobile app
im trying to go back to stock using an ruu. i have a tmobile m7 but whenever i use the ruu it says error. can someone post the most recent ruu so i can restore from it?
wiswis said:
im trying to go back to stock using an ruu. i have a tmobile m7 but whenever i use the ruu it says error. can someone post the most recent ruu so i can restore from it?
Click to expand...
Click to collapse
im not going to get deep into another fix tonight, but can you tell us what error your getting and everyone who can help you will need your fastboot getvar all, remove imei and serial number before posting it though
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
jwalters1123 said:
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
Click to expand...
Click to collapse
You say the RUU failed...
Any error message?
As much info as you can give would be better.
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
jwalters1123 said:
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
Click to expand...
Click to collapse
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
BD619 said:
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
jwalters1123 said:
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
Click to expand...
Click to collapse
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
BD619 said:
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
Click to expand...
Click to collapse
ok so hboot version says 3.19.0.0000, i am on a usb 2.0 port, i am not sure how to paste my copied text from the cmd prompt into this box so i just pasted it to a .txt file and attached that and it has all the getvar all info. thanks for the help.
Everything is current according to the getvar...go ahead and remove it as it contains the imei #
The latest RUU should work.
Maybe try downloading Sync Manager to update the drivers or try a different PC/usb port.
Low and behold i was in a 3.0 port lmao... smh... so you just saved me beating my head against the wall for god knows how much longer, thanks for the help, the ruu is working fine now:fingers-crossed: