Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
might be your hardware, i am soff with 651.8
Sent from my 831C using XDA Free mobile app
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
You could try it multiple times. Reboot the phone, computer, change USB ports, etc.. Who knows, maybe it'll work.
I know the M8 I got S-Off on took the 1.54.651.8 OTA before I even bothered to actually mess with it (unlock bootloader, root, and S-Off) and it was perfectly able to do all of those things.
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
If Firewater says it won't work on your device, then you can't get S-OFF for the time being. There's nothing you can do about that.
Don't flash anything above 1.54.651.8 without being S-Off
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
I'm running into the same problem and I need it badly.
If you do flash .13 without S-off you basically will have no way to flash the firmware and could be without audio from the stock music app.
Wow it's been a long night. This is a learning process for me. I've never come to a new phone so quickly so I'm getting used to the fact that development takes time and I need to be patient. I pretty much soft bricked my phone last night. Ended up deleting my system partition and had to pull some tricks to even get back into a bootable rom. I took one of the TWRP stock restores and reverted all the way back to 1.12.651.17. Then I fastboot flashed the stock recovery from 1.54.651.8 and took the OTA update so now I am completely back to stock....FEW...avoided a trip to the sprint store. I now understand that since I don't have S-OFF yet, I should flash any software versions over .8. In order to have a fully working .13, I'm sure the firmware is required as well (most likely the reason why my audio wasn't working for some of the ROMs). However, I'm still stuck with the issue in the picture below. I need to get S-OFF so I can flash the firmware 1.54.651.8, including the Hboot, Is it possible to flash an Hboot.img without being S-OFF?
#firewater is the IRC channel for the S-OFF by the way.
Also why is my radio and open dsp showing invalid-ver-info?
Anybody please help?
And something is really messed up because now my vibration won't work. No idea what is going on I just badly need s-off.
@mhuffer
So what is your current issue? It sounds like you have a working 1.54.651.8 setup, which, without S-OFF, is the most up-to-date. You might not be able to run the Harman Kardon ROM, as that may require the HK firmware, but besides that is everything working (outside of the invalid entries showing in HBOOT)?
Captain_Throwback said:
@mhuffer
So what is your current issue? It sounds like you have a working 1.54.651.8 setup, which, without S-OFF, is the most up-to-date. You might not be able to run the Harman Kardon ROM, as that may require the HK firmware, but besides that is everything working (outside of the invalid entries showing in HBOOT)?
Click to expand...
Click to collapse
Well it seems like my Hboot isn't recognizing my radios and somthing tells me the firmware is borked somehow because my vibration feedback isn't working. I am currently on 1.54.651.8, rooted, dev unlocked, fully stock. You can see from the picture my Hboot doesn't look right. My vibration was working fine yesterday but i cannot pin point when it stopped working. I'm guessing when I accidentally deleted the system partition through TWRP 2.7.0.7. I am currently running your version of TWRP (2.7.0.7). I'm also in the firewater IRC asking for help. I think my best bet would be to get s-off somehow and hboot the framework from 1.54.651.8 with unmodified hboot so I can get back to stock (if this is possible). At some point in all my confusion last night I did change my CID version to 11111111 and try to run the RUU for the HK version (.13) this might be where it all went wrong. I have my phone up and running and everything is working except for vibration and the Hboot looks out of whack.
mjhuffer said:
Well it seems like my Hboot isn't recognizing my radios and somthing tells me the firmware is borked somehow because my vibration feedback isn't working. I am currently on 1.54.651.8, rooted, dev unlocked, fully stock. You can see from the picture my Hboot doesn't look right. My vibration was working fine yesterday but i cannot pin point when it stopped working. I'm guessing when I accidentally deleted the system partition through TWRP 2.7.0.7. I am currently running your version of TWRP (2.7.0.7). I'm also in the firewater IRC asking for help. I think my best bet would be to get s-off somehow and hboot the framework from 1.54.651.8 with unmodified hboot so I can get back to stock (if this is possible). At some point in all my confusion last night I did change my CID version to 11111111 and try to run the RUU for the HK version (.13) this might be where it all went wrong. I have my phone up and running and everything is working except for vibration and the Hboot looks out of whack.
Click to expand...
Click to collapse
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Captain_Throwback said:
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Click to expand...
Click to collapse
How do I flash it without being S-off? Can I run it with S-On? I think I really just need a way to revert my Hboot to stock. I was hoping somebody had an RUU available that would just wipe everything and start from scratch.
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
Captain_Throwback said:
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Click to expand...
Click to collapse
I need someway to revert my Hboot while being S-ON. I was hoping somebody that had some knowledge could make and RUU with the proper CID to revert EVERYTHING back to stock. I mean I want to start from the bottom up. I don't know if this is possible without HTC releasing anything.
mjhuffer said:
How do I flash it without being S-off? Can I run it with S-On? I think I really just need a way to revert my Hboot to stock. I was hoping somebody had an RUU available that would just wipe everything and start from scratch.
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
I need someway to revert my Hboot while being S-ON. I was hoping somebody that had some knowledge could make and RUU with the proper CID to revert EVERYTHING back to stock. I mean I want to start from the bottom up. I don't know if this is possible without HTC releasing anything.
Click to expand...
Click to collapse
No one can make a RUU it has to be leaked from HTC.
Sent from my 831C using Tapatalk
Konfuzion said:
No one can make a RUU it has to be leaked from HTC.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
I figured that, is there any way to create a flashable zip with signed everything except for the recovery so I can possibly push it through TWRP. You have to understand I want to try everything possibly before returning this phone to sprint. I have a feeling they will want to ship it off to HTC if the vibration doesn't work.
mjhuffer said:
I figured that, is there any way to create a flashable zip with signed everything except for the recovery so I can possibly push it through TWRP. You have to understand I want to try everything possibly before returning this phone to sprint. I have a feeling they will want to ship it off to HTC if the vibration doesn't work.
Click to expand...
Click to collapse
You don't need to be S-OFF to flash the signed firmware.zip through HBOOT, which is why I suggested it.
---------- Post added at 01:54 PM ---------- Previous post was at 01:40 PM ----------
https://www.dropbox.com/s/cm6m61o78r0poe6/firmware.zip
Relock Bootloader, then fastboot oem rebootRUU, then fastboot flash zip firmware.zip.
Then you can unlock again if you want and flash custom recovery. But you can at least see if the firmware zip gets everything working properly again.
skizzled said:
You could try it multiple times. Reboot the phone, computer, change USB ports, etc.. Who knows, maybe it'll work.
I know the M8 I got S-Off on took the 1.54.651.8 OTA before I even bothered to actually mess with it (unlock bootloader, root, and S-Off) and it was perfectly able to do all of those things.
Click to expand...
Click to collapse
I never got a message of "You are out of luck" on my failed attempts. But....
First phone took me like 3 tries. Windows 7 x64
Second phone took like 4 failed attempts Windows 8.1 x64 (same computer) (timing out with over 2 minutes of dots......) using the exact same version of firewater as previous phone.
I was not sure if it was a Windows 8 issue.
Then I tried downloading the latest firewater and it was different from what I downloaded a month ago and worked the first time.
I agree. Try multiple times. Try with phone on WIFI vs Mobile Data. SO that Data is available quickly after adb reboot.
Try rebooting computer and try even another computer another USB port. Some computers have internal "USB Hubs". Try front vs Back etc.
I was able to do it on Windows 8.1 x64. I install latest HTC Sync. Then uninstall everything but the drivers.
I also had flashed Bad Boys 1.1 (Unlocked with S-ON) to get my rooted OS instead of manually rooting it. Then Factory Reset it. Turned on WIFI then did S-OFF.
Most rooted ROMs remove a lot of baggage that might interfere with rooting.
I'm still running all stock firmware though except for Recovery.
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
It doesn't matter how many times you try. It won't work. Read the message.
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
Ouch, pretty blunt message.
You don't need S-OFF to get wifi tether. All you need is HTC Unlock and Root.
S-OFF mainly allows you to flash firmware. You can only flash complete and signed firmware without S-OFF.
And each time you do, you'll have to reflash recovery.
I believe you can install several ROMs with S-ON that support Wifi Tether.
I ran "Wifi Tether Router" from Google Play ($1.99) with S-ON (HTC Unlock/Root) before S-OFF was available.
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
The Captain is right. I got on the IRC this morning and talked to the firewater guys. They didn't really say why but they were at least a good amount of help. I can't say I blame them for not releasing any information on why. I just wish I knew about bootloader exploits.
Also, I'm on windows 7 pro 64-bit. I have a laptop with win 8 64-bit, but am afraid to try on that PC due to ALL its USB ports are 3.0 (and firewater says to avoid 3.0 ports).
Captain_Throwback said:
You don't need to be S-OFF to flash the signed firmware.zip through HBOOT, which is why I suggested it.
---------- Post added at 01:54 PM ---------- Previous post was at 01:40 PM ----------
https://www.dropbox.com/s/cm6m61o78r0poe6/firmware.zip
Relock Bootloader, then fastboot oem rebootRUU, then fastboot flash zip firmware.zip.
Then you can unlock again if you want and flash custom recovery. But you can at least see if the firmware zip gets everything working properly again.
Click to expand...
Click to collapse
Does this firmware.zip possibly have the hboot and boot.img included? If not could you please make me one with it. It worked but the Hboot still says Tampered Relocked and my Radio and Open DSP say Invalid_Ver_Info and I still don't have vibration.
mjhuffer said:
Does this firmware.zip possibly have the hboot and boot.img included?
Click to expand...
Click to collapse
Yes.
Related
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
winwiz said:
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
Click to expand...
Click to collapse
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
htc one m7 said:
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
Click to expand...
Click to collapse
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
winwiz said:
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
Click to expand...
Click to collapse
me i have my stuck rom running also nandroid pulled by cmd
but no chance for me
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
thanks next time when i need a root i will get s-off before that .now my chance is getting s-off wich is not available now
if u dint tell me dont search i would search for ever XD
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
i just want to get updates from htc
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
htc one m7 said:
i just want to get updates from htc
Click to expand...
Click to collapse
Then you should've left the phone stock
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. If you used the revone method to root, it should take care of it. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Click to expand...
Click to collapse
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
winwiz said:
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
Click to expand...
Click to collapse
You could run the all in one toolkit and remove the tampered and relocked flags.
---------- Post added at 02:06 AM ---------- Previous post was at 01:17 AM ----------
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
This thread is open for questions like these. Flame on elsewhere.
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
Click to expand...
Click to collapse
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
htc one m7 said:
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
Click to expand...
Click to collapse
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
kibmikey1 said:
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
Click to expand...
Click to collapse
Who's flaming and complaining, and I did help ... I wouldn't help you now but that's another story. As for noobs, If you can't be bothered to read and search then that says something about you. For starters, even though you were wrong (and not the OP) I did help, I have also spent more time helping on here than I have posting anything else, so if you don't like it, you know what you can do.
You might want to give correct advice aswell, if he's on Hboot 1.54 then he'd need S-Off to flash an older Hboot, which he cannot do. Thanks
iElvis said:
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
Click to expand...
Click to collapse
when i red your reply it seemed too easy but no
stuck recovery when you mean that ''fastboot flash recovery recovery.img'' pulled from nandroid back up ? yes ur right i manged to do that it was succesful but no change even a systim rom is not available getting signature failure 'seems promising yah
i know my thing is hard but it shouldnt be like that right im runing a rom now 4.3 im fine with it but i really want to F*** htcdev members :v
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
iElvis said:
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
Click to expand...
Click to collapse
if you want to help me help me now
i have my reovery.img and it flashes perfectly
how to get stuck rom ?
you mean the file with date it is bout 1.8GB named 2013-08-27.19.58.35 that i should put it in supfic folder do i can flash it with recovery cwm ?
since i have my back up and since it is S-on i wont mind flashing any thing
There is no ruu for my phone (02___001) so now I have s off I was going to run a stock ruu and update to the latest firmware. If I send the phone back for repair and change my cid to HTC_001 would HTC know I have changed my cid even if I s on?
Anyone help me at all?
stovie_steve said:
Anyone help me at all?
Click to expand...
Click to collapse
Two things:
1- I dont know if they keep a record of IMEI (or s/n) <--> carrier, but I think they have to and do.
2- the CID is stored in several partitions, not only the one you change with fastboot writecid.
HOWEVER, it really depends on how far they're going to dig into this, if they are going to check their IMEI database or check the different partitions on the phone, just to "prove you wrong", I guess they could.
But then again, would it be worth all that hassle for them?
I dont have any experience with repair centers or how far they would go to prove that you changed something on your phone, and it's really quite country (and HTC people) dependent; for some they have no problem with an unlocked or relocked phone, and other even have a problem with S-Off (though they can't prove the phone didn't ship that way in the first place)
Better have someone from your region (O2 so UK?) post their experience(s)
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
stovie_steve said:
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
Click to expand...
Click to collapse
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
nkk71 said:
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
Click to expand...
Click to collapse
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
stovie_steve said:
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
Click to expand...
Click to collapse
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
nkk71 said:
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
Click to expand...
Click to collapse
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
stovie_steve said:
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
Click to expand...
Click to collapse
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
stovie_steve said:
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
Click to expand...
Click to collapse
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
stovie_steve said:
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
Click to expand...
Click to collapse
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
nkk71 said:
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
Click to expand...
Click to collapse
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
stovie_steve said:
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
Click to expand...
Click to collapse
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
nkk71 said:
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
Click to expand...
Click to collapse
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
stovie_steve said:
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
Click to expand...
Click to collapse
Ok, my thoughts, in a nutshell
1. Unlock bootloader via HTC dev <- YES
2----- try rumrunner 3.62
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off <- Ok, try, if it fails use above rumrunner 3.62
Once S-Off:
--- remove tampered: revone or http://forum.xda-developers.com/showthread.php?t=2477792
5. Restore nandroid backup for my 02 version 1.28.206.7
--- set phone to LOCKED, using revone (or http://forum.xda-developers.com/showthread.php?t=2475914)
------- you will need to have SU privileges which you can get using revone or flashing SuperSU; if you do flash SuperSU, uninstall it after getting LOCKED
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match) <- Yep
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Once you have your bootloader "LOCKED", no TAMPERED, no red text on bootup, do "fastboot oem writesecureflag 3"
reboot three times and see if everything sticks, and don't take any other OTAs.
Hit me with a thanks if this was useful
So you think I shouldn't upgrade to the latest OTA once I get s on?
stovie_steve said:
So you think I shouldn't upgrade to the latest OTA once I get s on?
Click to expand...
Click to collapse
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
nkk71 said:
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
Click to expand...
Click to collapse
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
nkk71 said:
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
Click to expand...
Click to collapse
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
stovie_steve said:
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
Click to expand...
Click to collapse
the touchscreen drivers were part of the 2.xx firmware package, not hboot, so if you don't use a full RUU, it will break the touchscreen drivers, but you can use an OTG cable + mouse.
stovie_steve said:
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
Click to expand...
Click to collapse
Unfortunately you can't (anymore), but this one should be close enough: http://d-h.st/users/guich/?fld_id=25920#files, or the best thing is to get a hold of the OTA 3.62.206.1 file and extract it from it.
Anyway, in my humble opinion, first things first: unlock using HTCdev and see if you can get rumrunner to S-Off on 3.62.
I just got a new laptop with 8.1 loaded on it... tried to flash a rom and it didnt go well.. bootlooping at the bootloader. computer wont recognize the phone, doesnt say fastboot usb. ive downloaded every possible driver i could find for 2 days and nothing...
basically ive narrowed it down to needing the amd usb host drivers for win 8.1 and i cant find em or a solution anywhere.
No i cant use another computer.
please please help, im totally screwed.
You can try this http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
Or use a pc that is not Win 8.1
The good news is if you can get your hboot updated to 1.55 your phone will be recognized in fastboot.
BD619 said:
You can try this http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
Or use a pc that is not Win 8.1
The good news is if you can get your hboot updated to 1.55 your phone will be recognized in fastboot.
Click to expand...
Click to collapse
thanks.. havent checked the link yet... wouldnt i need fastboot to get the hboot? haha catch 22
edit... checked that link.... must have seen it 10 times now... i dont understand, can i somehow use the intel drivers with my amd?
think im gunna dual boot ubuntu and see where that takes me... ugh
Use option 2 a Windows machine that is not running 8.1
BD619 said:
Use option 2 a Windows machine that is not running 8.1
Click to expand...
Click to collapse
thatd be great but i live on a tiny island in the caribbean.. theres no one around me with a computer, honestly... theres not even a sprint store on the island!
Lol I forgot about Ubuntu that should get ya going
blacksantron said:
thatd be great but i live on a tiny island in the caribbean.. theres no one around me with a computer, honestly... theres not even a sprint store on the island!
Click to expand...
Click to collapse
never thought I would feel bad for someone on a Caribbean island, haha. hope you get it running, I just installed 8.1 and used the rumrunner modified 1.55 hboot and everything is fine, good luck!
jblaze10 said:
never thought I would feel bad for someone on a Caribbean island, haha. hope you get it running, I just installed 8.1 and used the rumrunner modified 1.55 hboot and everything is fine, good luck!
Click to expand...
Click to collapse
yeah yeah... paradise and all...except it sucks when i cant communicate with anyone.. OK SO UPDATE
after totally crashing my boot partitions trying to dual boot 8.1 & linux, I atttained dual boot... ugh was rough.. came to me in the middle of the night and i just hit 3 keys and bam, dual boot... ok
YES thanks to linux i was able to push a new recovery on as well as a new ROM!! yayyyyyyy not so much.
NOW.. i have a rom running but i have no firmware, radio, nothing.. In my quest to put a firmware on i have achieved S-OFF.. (I also used rumrunner, but my hboot remains 1.44?) and flashed what looked like working radio stuff, but nope. Should i be trying all this with a Sense ROM? Im on SlimKat atm. Thats my only idea now.. i've flashed firmwares out the wazoo and nothing gives me those lovely service bars... just an empty triangle... Any Thoughts? really dont want to download a 900meg rom.
thanks!!!
U may have to ruu. Also rumrunner is for 1.55 hboot so I really don't know if it would work. Revone and moonshine are for 1.44 check bd19 faq thread or pm him if he isn't busy he will gst u on the right path!:thumbup:
Use OMJ's stock rooted ROM. But if you just need firmware and you have S-off, flash the firmware set from OMJ's RUU thread in fastboot . Instructions are there in the thread.
If you need help, just ask. That should get you going. Also, you can flash the firmware package that does not include hboot, recovery and boot. It's on the thread as well.
OMJ thread:
http://forum.xda-developers.com/showthread.php?t=2576995
tdhite said:
Use OMJ's stock rooted ROM. But if you just need firmware and you have S-off, flash the firmware set from OMJ's RUU thread in fastboot . Instructions are there in the thread.
If you need help, just ask. That should get you going. Also, you can flash the firmware package that does not include hboot, recovery and boot. It's on the thread as well.
OMJ thread:
http://forum.xda-developers.com/showthread.php?t=2576995
Click to expand...
Click to collapse
thanks for the tip...
i tried it, as per the instructions.. it went along as though is was working, but upon reboot, still an empty triangle.... baseband "unknown"
could it be something as mundane as me using an aosp rom and not a sense? looks like im facing the 1 gig RUU download... ugh
The ROM has nothing to do with the firmware. You are not getting flashed if your radio shows unknown.
Are you entering fastboot oem and then flashing the firmware set?
tdhite said:
The ROM has nothing to do with the firmware. You are not getting flashed if your radio shows unknown.
Are you entering fastboot oem and then flashing the firmware set?
Click to expand...
Click to collapse
oh yes, absolutely.
fastboot oem rebootRUU
wait should i still lock the bootloader before trying this?
fastboot oem lock?
No. No need to lock. You should be getting a radio version if you followed the few instructions in the thread for 'flashing modified firmware.' If you are really S-off, that should work.
tdhite said:
No. No need to lock. You should be getting a radio version if you followed the few instructions in the thread for 'flashing modified firmware.' If you are really S-off, that should work.
Click to expand...
Click to collapse
well rumrunner says i am s-off.. but these radio/firmware flashes dont take.... bootloader says, tampered, unlocked, s-off, hboot 1.44.
i just dont get it... well cheers to my impending 2 day download... UGH!
blacksantron said:
well rumrunner says i am s-off.. but these radio/firmware flashes dont take.... bootloader says, tampered, unlocked, s-off, hboot 1.44.
i just dont get it... well cheers to my impending 2 day download... UGH!
Click to expand...
Click to collapse
Which firmware are you trying to flash? Give us a link.
I would suggest flashing the Full Firmware 3.04.651.2 found HERE
It should give you a fresh flash of the firmware as well as update your hboot to 1.55 which in turn will make your device recognized in fastboot with Windows 8.1
ok now im going crazy
i downloaded the RUU from that thread above and ran it... says that usb is not connected. I verified that it is by running adb devices and it lists my phone... fastboot reboot works,,, for some reason the RUU thinks its not connected?!?!?!
im pulling my hair out
I believe you are on Windows 8.x, from previous notes. You need to upgrade hboot as BD noted above, which means flash the full firmware package from the links we gave so you get hboot upgraded. I'd use your Ubuntu install for that, but no matter, your choice if you know Windows is working.
But if that works, I seriously think you can blow off the RUU and load a ROM at that point. I would also look at checking things out with the LTE app from the play store once your radio is up, but be very careful with that app and only change the cdma/gsm/whatever selection option.
tdhite said:
I believe you are on Windows 8.x, from previous notes. You need to upgrade hboot as BD noted above, which means flash the full firmware package from the links we gave so you get hboot upgraded. I'd use your Ubuntu install for that, but no matter, your choice if you know Windows is working.
But if that works, I seriously think you can blow off the RUU and load a ROM at that point. I would also look at checking things out with the LTE app from the play store once your radio is up, but be very careful with that app and only change the cdma/gsm/whatever selection option.
Click to expand...
Click to collapse
right on, thanks... yeah im at hboot 1.55 now. So yeah im gunna grab a sense rom. wish me luck, havent had a phone for 4 days now
NOWWWW the sense rom im installing (Android Revolution 41.0) bootloops during the animation..
tried to reinstall the rom i was on that was working just no radio (SlimBean) and now that almost boots up then bootloops.... I swear this is torture.
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
ianthomas said:
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Devilish_Angel said:
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Click to expand...
Click to collapse
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
ianthomas said:
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
Click to expand...
Click to collapse
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
S-OFF - do it!
Devilish_Angel said:
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
Click to expand...
Click to collapse
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
... well buddy you quoted the wrong guy . never mind. this is exactly what i was telling him to get s-off to make things easier. appreciate your help though ...
ianthomas said:
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
It's my understanding that the OTA only works on bone stock phones.
slyest12 said:
It's my understanding that the OTA only works on bone stock phones.
Click to expand...
Click to collapse
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Little story to tell:
A day or two ago I got a notification of an ota*.9* to be exact, I tried installing it knowing it wouldn't cause I was rooted. I like to flash back to my stock Rom and update the apps and stuff so I get get the stock feel back without losing much from my daily driver Roms.
Anyways, there is a thread in the forums about installing this update, I tried it and wiped my phone minus the stock Rom, everything was gone even backups. The thread suggested to me to download this app sort of like flashify to flash stock recovery. After flashing stock recovery, well I had or think I had stock recovery cause I had to reinstall twrp, that's when I found out I wiped the heck out of my phone.
I had to start from scratch without a stock Rom cause what ever I did, my stock Rom was borked somehow, everything was gone, I couldn't "repair" missing stuff* like the weather/widget couldn't stick on the home screen. I had to make a sense six Rom my "stock" Rom while gathering more info on RUU and being s-off.
What I thought was this, I'd have to relock boot loader to do a RUU, which I didn't want to do, cause I am thinking I will lose root and have to htcdev again. But I'm s-off'd and now knowing that I won't need to relock bootloader, I have a question.
How do I EXACTLY go about RUU with s-off if I don't have to "oem lock"?
I s-off'd mainly to change boot splash and use a modded hboot to show its "not" rooted, I knew I don't have to htcdev again while s-off, but I was hoping to not come to that point, then this ota thing happened.
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Lol, nice hijack buddy, but it just so happens I have the same question
I got frustrated about a continuous brick while on S-ON, so I decided to S-OFF on my Hboot 1.56, and turns out, only Firewater was able to give me S-OFF. The process was very simple!!!
http://firewater-soff.com/
But even with S-OFF, I still soft brick or get into a bootloader bootloop while trying to install any non stock ROMS:
[Q] Bootloader Bootlopp soft brick on Viper 5.8.0 and other ROMS
I stopped trying more crazy things... I learned no to use TWRP 2.7 in my case, and use older versions, or PhilzTouch, but I still can't figure out how to either OTA update to .9, or install the Viper ROM correctly.
My guess is the same as yours... I shouldn't push a Stock odex ROM through fastboot, or ADB sideload through recovery. Having S-OFF means being able to use the RUU tool WITHIN a stock ROM itself, BUT BEFORE doing so, maybe it's best to flash a stock recovery, or this firmware file:
[Guide][How-to] Run 4.06.651.4 RUU on any windows without any problem..!!
That I guess it's the same found here (MD5 match "Full Firmware from RUU (fastboot flashable)"):
[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM
Anyways, before trying to do any of that, I will try to simply run the RUU from within the stock ROM, and hope the RUU flashes a firmware that contains a stock recovery as well (and maybe more?), so that maybe that's all I need to install the .9 OTA properly through the stock ROM, and after that, try and get the Viper ROM installed properly.
Will report back whatever I can find.
More useful posts:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
[ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | KitKat | Deodexed | myHUB | Updated 2/23/14
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
[Tutorial][Resource][Root]Unlock-Recovery-SuperSU for HTC One(M7)-Sprint-m7wls The all in one folder put togheter by BD619 in this post is pretty handy.
EDIT: Actually I will report back in my other question too, since this thread was supposed to be about RUU, and S-OFF, which I resolved through Firewater under Hboot 1.56.
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
v1ral said:
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
Click to expand...
Click to collapse
... There is a way to bypass hfa if you don't know yet ...
Devilish_Angel said:
... There is a way to bypass hfa if you don't know yet ...
Click to expand...
Click to collapse
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
v1ral said:
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
Click to expand...
Click to collapse
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
I forgot to thank you for your advise, which I took, and I don't regret There is a tiny little fine print about this though: " you don't have to relock the bootloader to flash an RUU"... That is not mentioned in the guides I read, and I will try to clarify in my noob post.
v1ral said:
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Click to expand...
Click to collapse
It is confusing for me too, but one of my theories was right, and I felt like a dunce once I figured it out, and I think you figured it out too...
Anyways, the HTC one will be for my brother, so I had limited access to it, and finally did more tests on it to figure things out.
I will try and answer your questions to my best of knowledge, but please keep in mind this is a noob/guinea pig point of view that is still asking questions, and I may be wrong on some things, so bear with me, but this has worked for me:
===========================================================================
Being on a Sprint HTC ONE with Hboot 1.56, originally on stock 4.06.651.4 , and S-OFF thanks to Firewater (other methods failed for me). I would recommend getting S-OFF now (to whoever else this may help).
OK v1ral, as far as I know, the ability to flash the 4.06.651.4 RUU WITHOUT having to relock the bootloader is from WITHIN the stock ROM itself, NOT from fastboot or anywhere else.
TIP: When unlocking the bootloader, simply save the .BIN file HTCDEV sends you, and save the command used to unlock for quick unlocking and relocking, just in case.
However you have to flash stock recovery first if s-on, how about with s-off?
You don't have to flash a stock recovery, because the RUU itself does that for you, regardless of S-ON or S-OFF. The only condition is having to relock the bootloader if S-ON BEFORE running the 4.06.651.4 RUU from WITHIN the stock ROM you're in, but obviously that is not necessary if S-OFF.
Can I RUU without relocking bootloader with s-off?
As far as I know, yes. that is the perk of having S-OFF.
Can I install an ota update without flashing stock recovery with s-off?
As far as I know (please correct me), the RUU itself flashes a stock recovery anyways, or at least that's one of the messages it gives while working. Keep reading for the info on how to install the OTA properly in my case.
Last thing, what are the steps to update my stock Rom, while being s-off?
OK, here we go, there is a very important, and easy missing detail nobody mentions in the guides I read, and the reason I was soft bricking with any rom.
How to OTA update from 4.06.651.4 to 4.06.651.9 properly, regardless of being S-ON, or S-OFF, and avoid bootloader bootloop for noobs
First off, If you're already in trouble, and can't install a stock rom, in a bootloop, or don't know how to adb sideload a rom into your device, etc... PM me to try and help you out of it, and start off in a stock room. That may take more time.
Moving on, assuming you're already in a stock rom, or any 'working' rom for that matter, meet these requierements first:
Make sure you never installed HTC Sync before, EVER. Have proper drivers installed, and a correct ADB online connection to your phone is important. I'm just assuming you didn't lazy out, and know how to research the drivers in here already. I just need you to run the command
ADB devices
Click to expand...
Click to collapse
and get a correct online connection between your phone, and PC. Another thing is not to use usb 3.0, or the frontal usb inputs on your PC, and use the back inputs just in case...
And even MORE important tip, is to never... EVER... use cheap low quality or damaged usb cables. I learned this the hard way hard bricking 2 phones in my old LG LGNPST days (LGNPST is another type of flashing tool for LG devices).
Having a damaged usb cable may be really dangerous, specially if your'e S-OFF
Having an al in one folder with the tools to work is pretty convenient, and user BD619 gathered one in his thread
He may not always have the latest version of the TWRP or CWM/PhilzTouch recoveries in it, but you can easily get them in this forum obviously.
TIP: TWRP is the recommended recovery on this device, version 2.7.0.3 didn't work for me, but the new 2.7.0.4 seems better for me, but I still can't mount an OTG drive to it, so you may have to learn how to push/adb sideload ROMs or files into it like this.
OK, from WITHIN your stock ROM, run this 4.06.651.4 RUU first (you only need to relock bootloader prior to running it if you're S-ON):
http://forum.xda-developers.com/showthread.php?t=2658910
It doesn't matter if you're already on firmware 4.06.651.4, run it anyways (it will flash a stock recovery, and more), reboot, and
THEN relock your bootloader, regardless of being S-ON or S-OFF
That was the little detail I was missing, and should've figured out before...
After relocking the bootloader, reboot back in, and THEN, and only then, you can download and install the 4.06.651.9 update from within the Software Update option.
After updating properly to 4.06.651.9, it is then that you can unlock the bootloader back again, flash TWRP, and root with it, or get ROMS already rooted without hiccups.
Finally, if I'm wrong on any of the small details in this, please correct me, but it was what worked for me at least.
Devilish_Angel said:
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
Click to expand...
Click to collapse
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
v1ral said:
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
Click to expand...
Click to collapse
... It should. Moreover it is far more easy to flash a simple zip than mounting the file system, finding files and then deleting some and renaming some ? ...
My HTC One has all the necessary prerequisites for flashing Roms. I'm not sure how to check s-off though, but I think that's the case. I can flash Roms that do not use Aroma, but if the ROM contains Aroma there is no use. They all freeze at a certain point, I believe around some part that has to do with the System. For example, Maximus HD freezes at 1% when formatting something. Any help would be appreciated. I have looked a lot for the last few days, and can't seem to find an answer.
ronii1123 said:
My HTC One has all the necessary prerequisites for flashing Roms. I'm not sure how to check s-off though, but I think that's the case. I can flash Roms that do not use Aroma, but if the ROM contains Aroma there is no use. They all freeze at a certain point, I believe around some part that has to do with the System. For example, Maximus HD freezes at 1% when formatting something. Any help would be appreciated. I have looked a lot for the last few days, and can't seem to find an answer.
Click to expand...
Click to collapse
Okay so I'm assuming that you're flashing a kk rom here. Are you on the latest recovery and also on a kk base with the latest radios and hboot already on the device? Also make sure you're flashing the right rom for you're device. What device do you have? And also send the link to the rom you're trying to flash just so I can double check that it's correct as if it's freezing at 1% then all I can think that is the problem is you're either trying to flash a kk custom rom on a jb rom without updated firmware and radios or your recovery is out of date or the 3rd reason could simply be you're trying to flash the wrong rom for your phone.
dc959 said:
Okay so I'm assuming that you're flashing a kk rom here. Are you on the latest recovery and also on a kk base with the latest radios and hboot already on the device? Also make sure you're flashing the right rom for you're device. What device do you have? And also send the link to the rom you're trying to flash just so I can double check that it's correct as if it's freezing at 1% then all I can think that is the problem is you're either trying to flash a kk custom rom on a jb rom without updated firmware and radios or your recovery is out of date or the 3rd reason could simply be you're trying to flash the wrong rom for your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2189373
That is the rom, It's Maximus HD. My hboot is 1.54, I'm not sure if my phone has the latest radios, but I have the latest TWRP recovery. 2.8.0.2 I think? I have the HTC One M7 for AT&T., but it says HTC One UL in the same screen I found the hboot. I believe the phone was converted to the GPE edition since it says GOOGL1 on the hboot screen. (I bought this second hand)
EDIT: I just want to add that Android Revolution HD yields the same results, but at 10%. And my phone is currently on a stock build of Sens 6 4.4.3, but the rom before it was GPE.
ronii1123 said:
http://forum.xda-developers.com/showthread.php?t=2189373
That is the rom, It's Maximus HD. My hboot is 1.54, I'm not sure if my phone has the latest radios, but I have the latest TWRP recovery. 2.8.0.2 I think? I have the HTC One M7 for AT&T., but it says HTC One UL in the same screen I found the hboot. I believe the phone was converted to the GPE edition since it says GOOGL1 on the hboot screen. (I bought this second hand)
EDIT: I just want to add that Android Revolution HD yields the same results, but at 10%. And my phone is currently on a stock build of Sens 6 4.4.3, but the rom before it was GPE.
Click to expand...
Click to collapse
If you go into your bootloader you'll see under the **unlocked** message you'll see something that has the phone model and then ship and after ship it will say either s-on or s-off and for the ROM you're trying to flash you have to be s-off thankfully you're on hboot 1.54 so you can use rumrunner to gain s-off if you're not so check that
dc959 said:
If you go into your bootloader you'll see under the **unlocked** message you'll see something that has the phone model and then ship and after ship it will say either s-on or s-off and for the ROM you're trying to flash you have to be s-off thankfully you're on hboot 1.54 so you can use rumrunner to gain s-off if you're not so check that
Click to expand...
Click to collapse
Looks like I am S-Off already. This is strange. It's the only device that has reacted this way to Aroma. I will say that I decide to flash Elemental X today, and that uses Aroma. That worked no problem.
ronii1123 said:
Looks like I am S-Off already. This is strange. It's the only device that has reacted this way to Aroma. I will say that I decide to flash Elemental X today, and that uses Aroma. That worked no problem.
Click to expand...
Click to collapse
Have you checked the md5 of the ROM to make sure that it isn't just a bad download or something which you would just need to re download it again?
dc959 said:
Have you checked the md5 of the ROM to make sure that it isn't just a bad download or something which you would just need to re download it again?
Click to expand...
Click to collapse
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
After every attempt, when I restore a backup, I see the text "E: Unable to mount ' /cache' " in red
ronii1123 said:
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
Click to expand...
Click to collapse
Yea that's actually what I was just about to say haha I just had to grab the links to the CID's so you can find the one for your phone as it's a converted gpe phone not a factory one which means you simply just need to go to the link I'll post here and find the RUU that is for at&t and the CID will be listed under the download link then you just need to change it.
Link for CID: http://www.htc1guru.com/downloads/ruu-file-downloads/
Once you've found your CID listed in the link which I'll have a look myself to see if I can find it for you but you need to then go into terminal or cmd and type in:
adb reboot bootloader
adb oem writecid CWS__001
fastboot erase cache
fastboot reboot
I changed the code so that it has the correct CID for you so just type in what I've typed there and you'll be back to normal and it should all flash fine
---------- Post added at 05:00 PM ---------- Previous post was at 04:39 PM ----------
ronii1123 said:
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
After every attempt, when I restore a backup, I see the text "E: Unable to mount ' /cache' " in red
Click to expand...
Click to collapse
I always receive the red text saying it can't mount cache so don't worry it's not going to stop you from flashing that's just an issue that I have no idea what's causing it but cache is a temporary file anyway so it isn't going to affect installing a ROM well at least it hasn't for me
dc959 said:
Yea that's actually what I was just about to say haha I just had to grab the links to the CID's so you can find the one for your phone as it's a converted gpe phone not a factory one which means you simply just need to go to the link I'll post here and find the RUU that is for at&t and the CID will be listed under the download link then you just need to change it.
Link for CID: http://www.htc1guru.com/downloads/ruu-file-downloads/
Once you've found your CID listed in the link which I'll have a look myself to see if I can find it for you but you need to then go into terminal or cmd and type in:
adb reboot bootloader
adb oem writecid CWS__001
fastboot erase cache
fastboot reboot
I changed the code so that it has the correct CID for you so just type in what I've typed there and you'll be back to normal and it should all flash fine
---------- Post added at 05:00 PM ---------- Previous post was at 04:39 PM ----------
I always receive the red text saying it can't mount cache so don't worry it's not going to stop you from flashing that's just an issue that I have no idea what's causing it but cache is a temporary file anyway so it isn't going to affect installing a ROM well at least it hasn't for me
Click to expand...
Click to collapse
Alright I'll give that a shot, thanks! I'll let you know of my results.