Thanks in advance for any help... I've searched and come up empty in terms of up-to-date stuff. I'm super-cid, unlocked bootloader, s-off (phone came that way off a private sale) with a RUU conversion to GPE. I want to take advantage of the sense 6 update especially the new battery saving mode. Really wondering weather:
1- downgrading firmware is still a thing coming from GPE and going to the latest Sense 6 roms
2- Weather I should use an RUU or try flashing a custom recovery and a wrong
3- Weather there's any other watch-outs I should know
Change your CID/MID accordingly for Dev edition and run the http://www.androidruu.com/getdownlo...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
This will get you going all the way to Sense 6 with a few updates. Do not LOCK boot loader or turn S-ON
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Without further details can't help
komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Based on the google searches I've done, this is normal. The HTC RUU installation never actually finishes. You just need to wait until the progress bar stops moving, make a coffee, then reboot and hope you haven't just bricked the phone.
SaHiLzZ said:
Without further details can't help
Click to expand...
Click to collapse
See above--what happened to him is normal.
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
komienski said:
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
Click to expand...
Click to collapse
Change cid to BS_US001 and make sure mid is PN0712000
Sent from my HTC One using XDA Free mobile app
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.
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
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
MacSkizzle said:
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
Click to expand...
Click to collapse
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can I get s-off? All I can access is my bootloader.
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded, extracted, and ran the correct soju but I get an error. It says to run rumrunner again and READ... I don't know what I did wrong. I did this with my phone in fastboot usb mode, is that right?
MacSkizzle said:
Can I get s-off? All I can access is my bootloader.
Click to expand...
Click to collapse
I'm pretty sure that's all you need. But I could be wrong.
TriBeard said:
I'm pretty sure that's all you need. But I could be wrong.
Click to expand...
Click to collapse
When I run the rumrunner program, I type 'Yes' twice then I get an error telling me to run rumrunner again and READ. What did I do wrong?
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
I'll try this tonight when I get home from work, thanks for the input.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
This didn't do it either. PLEASE SOMEONE HELP ME
I don't know if you can flash OMJ's firmware if your bootloader is set to "Relocked". I could be wrong but I think what you need to do is unlock it again first and install a recovery. Then flash OMJ's stock firmware from recovery. From there you can probably do the S-OFF process and RUU back to stock.
You do need to be able to boot into your ROM for S-OFF to work, as you start the S-OFF process while the phone is booted up and running.
MacSkizzle said:
This didn't do it either. PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
Look HERE
So my problem is the further, I had a fully working HTC first with the latest Hboot update previously moonshined with the old one. So I had S-off, root, JMZ's custom kernel and an unlocked bootloader but then after a while I've done alot of flashes, zip installs tweaks and modifications that created pesky problems that wouldn't go away with a simple wipe in CWM. That's okay though I could just do a complete restore with the RUU. And i did, no I didn't re-lock the bootloader because I had S-off anyways. Everything came out great. But then I went ahead and the problems started to happen.. After unlocking the bootloader I had an eternal bootloop that wouldn't go away, but did a simple re-lock and booted up just fine.
My question is what the hell am I doing wrong? does it have to do with the version of RUU im using?
abrahammmmmmm_ said:
So my problem is the further, I had a fully working HTC first with the latest Hboot update previously moonshined with the old one. So I had S-off, root, JMZ's custom kernel and an unlocked bootloader but then after a while I've done alot of flashes, zip installs tweaks and modifications that created pesky problems that wouldn't go away with a simple wipe in CWM. That's okay though I could just do a complete restore with the RUU. And i did, no I didn't re-lock the bootloader because I had S-off anyways. Everything came out great. But then I went ahead and the problems started to happen.. After unlocking the bootloader I had an eternal bootloop that wouldn't go away, but did a simple re-lock and booted up just fine.
My question is what the hell am I doing wrong? does it have to do with the version of RUU im using?
Click to expand...
Click to collapse
You got to turn S-ON after you RUU a previously S-OFF'd device.
Kendosis said:
You got to turn S-ON after you RUU a previously S-OFF'd device.
Click to expand...
Click to collapse
Wow, well I was completely unaware of that. Sorry for the noob question but how would i go about in doing that?
abrahammmmmmm_ said:
Wow, well I was completely unaware of that. Sorry for the noob question but how would i go about in doing that?
Click to expand...
Click to collapse
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Kendosis said:
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Click to expand...
Click to collapse
Thanks! One question: what's the stock cid number for the RUU the first has? I now have S-on but when I tried to run the RUU again to see if everything was working I got error 131 which shows when there's a CID mismatch. The CID I used was cws__001. I have the first with a t-mobile simcard by the way if that changes anything
abrahammmmmmm_ said:
Thanks! One question: what's the stock cid number for the RUU the first has? I now have S-on but when I tried to run the RUU again to see if everything was working I got error 131 which shows when there's a CID mismatch. The CID I used was cws__001. I have the first with a t-mobile simcard by the way if that changes anything
Click to expand...
Click to collapse
Try a different version of the ruu, there's two iirc. Try version 1.08.502.1 if that doesn't work try the next version.
Kendosis said:
Try a different version of the ruu, there's two iirc. Try version 1.08.502.1 if that doesn't work try the next version.
Click to expand...
Click to collapse
I tried both and it's a no go. Pretty sure it has to do with me changing the cid number on without knowing to the one I said earlier. But I guess if I would ever want to run the ruu I'd have to s-off it first and do it the long way then but at least I can successfully unlock the boot loader now with no problems, or at least I think. (Haven't tried it yet)
Edit:
Problem solved I unlocked the bootloader once more moonshined and set a supercid on the phone
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: