So I've searched this forum and other forums numerous times before I posted this. Androidcentral, amongst other forums, and i still can't find a solution to my many RUU problems.
Basically AT&T is making me send my phone back, I rooted it, S-Off, And my bootloader is currently unlocked. Every time I try and used RUU, I get errors ranging from Error 155, to Error 170. Sometimes RUU will begin to flash my phone back to stock. But then my phone hangs at the HTC One silver logo, and I have to restart the phone because it won't go any further.
I have tried to lock my bootloader, as well as unlock it, and S-Offed my phone and tried it with S-On and I am still getting numerous errors. It managed to start flashing once, and put me back on HBOOT 1.44, from HBOOT 1.55, and it seems like it doing that has made my problems worse.
I DO have the correct RUU exe for my phone, I'm certain of it, and now whenever I go to manually push the .ZIP file through ADB, it hangs on the screen that says waiting for device, or when I try and getvar as well.
Any solutions would be greatly appreciated. I'm usually very very very very knowledgeable about rooting and unrooting and going back to factory stock on numerous phones. But this is my first HTC.
S-Off
HBOOT 1.44 from 1.55
modelid: PN0712000
cid: CWS__001
EasyTiger6x13 said:
So I've searched this forum and other forums numerous times before I posted this. Androidcentral, amongst other forums, and i still can't find a solution to my many RUU problems.
Basically AT&T is making me send my phone back, I rooted it, S-Off, And my bootloader is currently unlocked. Every time I try and used RUU, I get errors ranging from Error 155, to Error 170. Sometimes RUU will begin to flash my phone back to stock. But then my phone hangs at the HTC One silver logo, and I have to restart the phone because it won't go any further.
I have tried to lock my bootloader, as well as unlock it, and S-Offed my phone and tried it with S-On and I am still getting numerous errors. It managed to start flashing once, and put me back on HBOOT 1.44, from HBOOT 1.55, and it seems like it doing that has made my problems worse.
I DO have the correct RUU exe for my phone, I'm certain of it, and now whenever I go to manually push the .ZIP file through ADB, it hangs on the screen that says waiting for device, or when I try and getvar as well.
Any solutions would be greatly appreciated. I'm usually very very very very knowledgeable about rooting and unrooting and going back to factory stock on numerous phones. But this is my first HTC.
S-Off
HBOOT 1.44 from 1.55
modelid: PN0712000
cid: CWS__001
Click to expand...
Click to collapse
Are you on Win8.1? hboot 1.44 doesn't play nice with Win 8.1
take a look at my guide (also the FAQs!!!), http://forum.xda-developers.com/showthread.php?t=2541082
and use the RUU.ZIP method using: http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-12-zip/
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.
Ok so long story short,, I think I messed my htc one pretty bad today.
1)I installed 1.28.401.7 update from this thread:http://forum.xda-developers.com/showthread.php?t=2305490 <----I changed the CID of the phone to 11111 when doing this
2)After that I installed the custom rom from trickdroid.
3)Then I installed the 30 steps volume or something and my phone would just freeze with the htc boot logo. After several on and off and still being freezed, I think I erased the current rom.
4)Then with NO rom on the phone , I changed the Model ID and basically here's my info from the txt that I filled in:
modelid: PN07120
cidnum:HTC__Y13 VZW__001
mainver: 1.28.401.7
btype:1
aareport:1
hbootpreupdate:12
I followed this guide to do the above steps
http://forum.xda-developers.com/showthread.php?t=2322820
Only after flashing that PN07120(model id found in the back of the phone) that I read on fastboot that the model number was PN0712000.
But still everything went fine and my phone was already unlocked and s-off before I changed CID and MID. My phone was now displaying HTC_001 and PN071000 as model.
After trying to reflash the 1.28.401.7 firmware, I had no luck...tried the:
RUU_M7_UL_JB_50_Cingular_1.26.502.12
RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3 but still no luck.
when I do adb devices, it doesn't find any device...after that I tried a fastboot command to relock the bootloader and it DID work. So fastboot is working. But nothing can be mounted while i'm in recovery e.g can't mound /sd card....etc
So I'm basically left with a phone with no rom, just bootloader(relocked) and recovery(cwm). Any help would be really appreciated. I'm quite stressed right now for having damaged my phone permanently and being such a noob .
About to go to bed, I'll try to flash via RUU.zip and will post tomorrow. if i get any success
Dude, you're messing around with incredibly sensitive partitions and parameters in a really haphazard way, I'm surprised your device isn't already bricked. However if you can use fastboot then you're phone is likely salvageable. You could try following this guide to push a ROM to your phone and flash that to get it running again. Is your phone now s-off?
Hello everyone!
I have an AT&T HTC One that is S-Off, relocked, SuperCID, black HBoot 1.54, currently on ViperOne 2.7 with stock kernel. I've been trying for the past day and a half to get the 3.22.1540.1 Brightstar WWE to run so I could have it back to stock with the most current OS. I also want to fully convert it to a Developer's Edition phone as well. I thought that with SuperCID you could run any RUU but so far every single time it ends in an error. I also tried changing the CID to the Developer's Edition CID (BS_US001) and still came back with the same error. So here I am on the greatest place in the world for Android phone assistance and advice asking for help in getting my phone converted to a Developer's Edition and/or on the 3.22 RUU. Thanks in advance for any help.
P.S. I already did try to search like crazy for the answers to my questions.!
Well you may need a stock recovery to run an ruu.exe. And I'd recommend going back to super-cid and then running the ruu as well. Be sure you back up all your information that you do then wish to lose, as the ruu will format the entire phone.
Sent from my HTC One using Tapatalk 4
Willieumm said:
Hello everyone!
I have an AT&T HTC One that is S-Off, relocked, SuperCID, black HBoot 1.54, currently on ViperOne 2.7 with stock kernel. I've been trying for the past day and a half to get the 3.22.1540.1 Brightstar WWE to run so I could have it back to stock with the most current OS. I also want to fully convert it to a Developer's Edition phone as well. I thought that with SuperCID you could run any RUU but so far every single time it ends in an error. I also tried changing the CID to the Developer's Edition CID (BS_US001) and still came back with the same error. So here I am on the greatest place in the world for Android phone assistance and advice asking for help in getting my phone converted to a Developer's Edition and/or on the 3.22 RUU. Thanks in advance for any help.
P.S. I already did try to search like crazy for the answers to my questions.!
Click to expand...
Click to collapse
No need to relock boot loader because the developer edition comes by default unlocked. Unlock it to continue. You need to change your CID to 11111111 (super CID) and you need to flash the 1.44 hboot (I believe) the black hboot may be causing the problem.
Downgrade to the lowest firmware you can find for the Developers edition.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
(Yes, twice.)
Check to be sure everything was successful.
fastboot reboot-bootloader
Make sure the bootloader is locked.
Run the ruu.
Let it do its thing.
Boot the phone and set it up.
Go to settings - about phone - software information - system update.
Allow it to download and update.
Repeatedly check for update until you reach 4.3
Sent from my HTC One using XDA Premium 4 mobile app
Hi there,
Did you get it work 3.22.1540.1 dev edition on your phone?, im still stuck in the same problem, got an HTC One AT&T, i got working the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe (dev edition), when i check for updates, there's an update of 17mb, after updating that one, i check again and found the 3.22.1540.1 OTA (around 550mb), i downloaded and agree to install it, but when reboot the phone, it got stuck in the HTC logo screen, did not go further, even trying to get into recovery, same thing, got stuck in HTC logo screen.
Another test i did, was installing RUU_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe and even the zip version, both of them install correctly but same problem, got stuck in HTC Logo screen, right now my phone is Unlocked bootloader, S-off with supercid (also tried the BS_US001 CID, same problem), hboot 1.55, is there any chance someone can help me with it? thanks a lot
leca27 said:
Hi there,
Did you get it work 3.22.1540.1 dev edition on your phone?, im still stuck in the same problem, got an HTC One AT&T, i got working the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe (dev edition), when i check for updates, there's an update of 17mb, after updating that one, i check again and found the 3.22.1540.1 OTA (around 550mb), i downloaded and agree to install it, but when reboot the phone, it got stuck in the HTC logo screen, did not go further, even trying to get into recovery, same thing, got stuck in HTC logo screen.
Another test i did, was installing RUU_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe and even the zip version, both of them install correctly but same problem, got stuck in HTC Logo screen, right now my phone is Unlocked bootloader, S-off with supercid (also tried the BS_US001 CID, same problem), hboot 1.55, is there any chance someone can help me with it? thanks a lot
Click to expand...
Click to collapse
go into stock recovery and do a factory reset ..it should boot then
Let me start off with I think I got lucky. Try this at your own risk. I locked my bootloader and turned my security back on for a TMOUS warranty exchange for the dreaded purple tint in camera. I received my replacement only to find out that in fluorescent lighting the replacement HTC ONE M7 had a greenish tint but only under fluorescent lighting. So I am getting another replacement sent for free. This is where my troubles begin. I decided to unlock my bootloader for my original phone again and root it so I can set everything up again for daily use. I got through all those steps fairly easy. FYI: original phone is on newest TMOUS OTA_M7_UL_K44_SENSE60_MR_TMOUS_5.14.531.1_R-4.19.531.10_release_373019xng22l97gj5szmwv. I then relocked the phone and tried to flash RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.zip in order to achieve s-off again but to no success. Hboot 1.57.000 with S-ON wasn't having any of it I guess.
I unlocked bootloader and relocked bootloader several times trying several different methods to no success. Oh, my recovery was TWRP 2.7.0.0. At some point I realized that if I was going to return this phone I needed to get s-off again to remove tampered flag and actually lock phone instead of relock. I happened to come across a stock rom that I decided to install in hopes of accomplishing S-off. Stock 3.24.531.3 T-Mobile.zip was the rom. Long story. I know. So here is what I did;
Unlocked bootloader
Flashed TWRP and gained root using WinDroid Universal HTC Toolkit
Installed Stock 3.24.531.3 T-Mobile.zip ROM via TWRP
Phone would not fully boot past HTC ONE Animation screen
powered down and powered back on into bootloader
relocked bootloader and rebooted bootloader
unlocked bootloader again
Phone now booted completely into the stock rom I flashed
Proceeded to use firewater for S-off
Didn't work first time
Powered down phone by holding power button and rebooted normally
Tried firewater again and to my luck the SOB worked and I am S-Off again on newest HTC One TMOUS with an older Stock 3.24.531.3 T-Mobile rom
I'm sorry if I have no links to anything I mentioned but I am new to this so I don't really know how to link to other stuff I found on the site. Thanks to all the great people whose tools and rom I used to achieve S-off again.
Prior to doing those steps firewater would not get past the first chugging stage.
If you got the chugging message you were always going to be able to s off it. Firewater isn't worried about the hboot so much as the version of your cpu as to whether the exploit will work on it
Sent from my HTC One using XDA Premium 4 mobile app
It would get to the chugging and sit there for bit then kick the phone back to root command. It didn't matter how many times I tried it would always do the same thing at the same spot. I would then have to reboot the phone and try again but no success. I'm just sharing what I did and worked for me. Clearly the exploit didn't want to work before I did the steps I took. I wouldn't have spent almost 30 hours of reading and trying to fix the problem I caused otherwise. Maybe it was a fluke or dumb luck. I don't know.
Where can I find this stock rom?
Nevermind this did not work.
So my current setup is this:
Tampered
Relocked
SecurityWarning
M7_MLS PVT SHIP S-ON RH
HBOOT 1.57.0000
Radio 1.01.20.0904_2
Open DSPv32.120.274.0909
OS-3.04.651.2o (the little o at the end of this line is highlighted)
eMMC-boot 2048MB
I'm just trying to get this phone back in working condition so I can give it to my daughter. But nothing I do is working. Currently phone boots into some old version, not sure what. But I can't do over the air updates because it just reboots into the bootloader and won't finish.
I've refreshed back to stock from the bootloader, and started down the path found in this thread:
http://forum.xda-developers.com/showthread.php?t=2618524
to get S-OFF (NOTE: I'm on hboot 1.57 and it's for 1.55, but I have no idea how to get back to 1.55)
I got through the first step (tricking it into thinking it's on version 3.04.651.2) and now when I do an adb devices, it isn't seeing my phone anymore. Also, I seem to have lost recovery? I had TRWP on there and now if I try to select 'recovery' it just returns to the bootloader screen and won't go into recovery any more.
Help. It literally just want to wipe the thing and put something useable on it. Stock, rooted or not, whatever. If I try to update the software on the phone from within the phone settings, it reboots into the bootloader and gets stuck.
Thanks in advance!
Probably the easiest thing to do then is to flash the full firmware first. Then run the RUU. You probably can get by with just the RUU, but it sometimes errors out if the firmware is not flashed first. You can get the firmware and the RUU (along with basic instructions on how to use them) from here: http://forum.xda-developers.com/showthread.php?t=2795856
coal686 said:
Probably the easiest thing to do then is to flash the full firmware first. Then run the RUU. You probably can get by with just the RUU, but it sometimes errors out if the firmware is not flashed first. You can get the firmware and the RUU (along with basic instructions on how to use them) from here: http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
That worked! Thank you so much!!