Ok, so I installed Cleanrom 6 and flashed Elemental 6.0(I know it's experimental, I should have been prepared for something like this). I went into recovery(CWM) for something and instead of getting into recovery it just showed cwm logo and immediately rebooted to the splash screen and stayed there. I then tried to reboot several times into recovery and the rom, only resulting in the same thing. SOO while in bootloader I decide "hey I'll just run the 2.20 ruu and everything will be ok.". Well, I ran fastboot oem lock and it said it failed but now the bootloader says RELOCKED. Now, having relocked, the RUU program STILL can't detect my phone. Then I realize, I don't have the Unlock_code.bin anymore. So now I'm stuck in bootloader, (somewhat)relocked, and have absolutely no idea what to do next. Oh and I have S-OFF if that helps.
Thanks for taking the time to read that wall of text(hopefully), Does ANYONE have an idea of what I can do next? I sincerely appreciate any help I can get.
Thanks
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
iElvis said:
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
Click to expand...
Click to collapse
Thanks so much for the reply, Yeah I'm still SuperCID and I'll try that. I am supposed to be in bootloader for the RUU to detect my phone, right? and when it "relocked" it said
Code:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.938s
Again, sorry. I know this was REALLY dumb. I just panicked. Thanks for taking the time to help.
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
If you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
iElvis said:
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
if you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
Click to expand...
Click to collapse
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
jacobas92 said:
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
Click to expand...
Click to collapse
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
iElvis said:
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
Click to expand...
Click to collapse
Ok, thanks guys. I REALLY appreciate the help. It's booting fine now. I guess the only problem now is why it won't get past the first 3 seconds into booting to recovery or the rom. I had also flashed multiple versions of TWRP but still had the same problems. I'll just shut it down for an hour or 2 and try again later.
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
iElvis said:
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
Click to expand...
Click to collapse
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
jacobas92 said:
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
Click to expand...
Click to collapse
My phone doesn't like undervolting at all. Bulletproof is a great way to go.
Sent from my HTC One XL
area51avenger said:
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
majortaylor said:
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
Its all good now they helped me. But to answer your question, I do know that even with s-off there are a few if not all fastboot commands that write to certain partitions that require an unlocked bootloader (at least from my experience).
Related
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
very simple to fix. The fact that you got to the "ready to unlock?" screen means the unlock token works.
go into settings on the phone go to power. Turn OFF fastboot.
Power off the phone completely.
Boot to bootloader
send the unlock.bin again
this time it will stick.
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
Sometimes the phone can get confused about its locked state.
To fix:
-Force reboot the phone. Hold the power button for 10+ seconds until bottom lights flash and then stop.
-Boot in to bootloader
Now force the phone to lock even if you think it is locked already.
-fastboot oem lock
-fastboot flash unlocktoken Unlock_code.bin
Sending "fastboot oem lock" tends to get the phone back on the right track so it doesn't just keep rebooting in to a relocked state.
get into bootloader manually volume down + power.
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
yes root will happen.
unlock bootloader. Install twrp recovery. Flash the root package found here http://forum.xda-developers.com/showthread.php?t=1673935
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Ethere said:
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Click to expand...
Click to collapse
I think you may have to use fastboot flash recovery recovery.img because of the new limitations of the new HBOOT. It might be only for boot.imgs though
That worked rohan32 Thanks so much to both of you. Now I have an unlocked bootloader and TWRP installed. Going for root now. Thank you thank you thank you! You guys have saved me from wanting another phone!
[EDIT]Rooted as well. Again, thank you both so much!
thanks everyone i solved my problem.dint except quick replies from you guys.
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
If you stay away from the AT&T cid you will be fine.
In theory things could change but at the moment so long as you have super cid prior to RUU flashing you will be fine.
OK I just got my AT&T HOX today and from what I've read hear there is no way to root it? Since I have 2.20.502.7 710RD but if I use super cid I can flash roms?
Without root you can't get super Cid
Please update the title and add "Resolved"
Sent from my HTC One XL using xda premium
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Bump
Sent from my One S using XDA Premium 4 mobile app
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
bump
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.
Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.
pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!
So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks
pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755
[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.
Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
mikel.canovas said:
Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
Click to expand...
Click to collapse
Can you get to bootloader? Fastboot access? You were soff previously correct?
Sent from my One Xl using Tapatalk 2
jrior001 said:
Can you get to bootloader?
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
mikel.canovas said:
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/evita
From twrp's site grap the 2.6.3 recovery.IMG and with phone in bootloader where you see "fastboot usb" type in cmd promt fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
And the fastboot reboot-bootloader
Then navigate and try to get to recovery again
If you get that far flash ROM again, just that for now and relax for a bit
Sent from my One Xl using Tapatalk 2
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
mikel.canovas said:
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
Click to expand...
Click to collapse
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
jrior001 said:
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
No bootloader is "relocked". I was in fastboot when I ran the RUU since ADB is not being recognized when in bootloader. RUU was successful, didn't seem like anything went wrong
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
redpoint73 said:
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
Click to expand...
Click to collapse
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
mikel.canovas said:
Bootloader says relocked.
Click to expand...
Click to collapse
You need to unlock bootloader again to flash TWRP.
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
Click to expand...
Click to collapse
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Click to expand...
Click to collapse
Using the unlock token is known to sometimes fail and require repeated attempts, just keep trying.
Not sure why the RUU didn't work, that is weird.
jrior001 said:
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
I've done the RUU twice now. Same results. Was s-off with 2.14 hboot
mikel.canovas said:
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
Click to expand...
Click to collapse
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
timmaaa said:
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
mikel.canovas said:
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
Click to expand...
Click to collapse
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
timmaaa said:
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
Click to expand...
Click to collapse
Then why has it failed 3 times? RUU is reporting successful. So what's the error?
Which error code is it giving you?
Sent from my Evita
timmaaa said:
Which error code is it giving you?
Sent from my Evita
Click to expand...
Click to collapse
RUU gives no error. It shows that it's successful
hello XDA. I appologize if i am breaking rules but i dont know what else to do with my phone.
I recently bought an AT&T X. it had the 2.20 at&t firmware installed. i managed to root it and supercid it and unlock bootloader. however, ever since then, i cannot update thru RUU. i was updating to 2.14 hboot to get facepalm s-off.
writing zip ...
<bootloader> adopting the signature contained in this image...
<bootloader> zip header checking...
<bootloader> zip info parsing...
FAILED <remote: 99 unknown fail>
i tried downloading the OTA and made sure its AT&T software as i do not have s-off yet. I have flashed stock recovery (i had twrp installed after i rooted and supercid) and navigate to OTA files but i get this.
mount SDCARD failed 1 times
mount SDCARD failed 2 times
mount SDCARD failed 3 times
mount SDCARD failed 4 times
mount SDCARD failed 5 times
i chose apply from phone storage and i get:
invalid operation
rebooting...
also i ran JET and successfully downgraded hboot to 1.09 cuz i read it not all parts of s-on were implemented, so i thought i could obtain s-off that way.
i have searched all over xda and google. i do as much research as i can first.
Whoa, where are you getting your information? Stop what you're doing. Running the jb RUU while s-on and SuperCID is going to brick your phone. You're lucky it's failing.
What makes you think you need to update it to get s-off? Have you attempted the Facepalm procedure yet?
Sent from my Evita
timmaaa said:
Whoa, where are you getting your information? Stop what you're doing. Running the jb RUU while s-on and SuperCID is going to brick your phone. You're lucky it's failing.
What makes you think you need to update it to get s-off? Have you attempted the Facepalm procedure yet?
Sent from my Evita
Click to expand...
Click to collapse
My bad. Wat happened was i successfully rooted while on 2.20 and proceeded to flash the zip indicated by facepalm s-off thread. thats when i started getting the error 99. i checked cid and made sure it was 11111111, which is required by facepalm s-off. now no RUU's work.. i setting the cid back to its original CWS__001 and ran updated RUU but still got the same errors.
i forgot to mention that in the first post. i know RUU while s-off and scid bricks it.
How many times did you try Facepalm, and got error 99? It seems some folks have gotten error 99, and just ran it again.
Bootloader needs to be relocked to run RUU with s-on. Did you relock the bootloader?
redpoint73 said:
How many times did you try Facepalm, and got error 99? It seems some folks have gotten error 99, and just ran it again.
Bootloader needs to be relocked to run RUU with s-on. Did you relock the bootloader?
Click to expand...
Click to collapse
i ran it multiple times. i saw a thread i forgot where to find it. i looked thru pages of different threads and i found one that says if u get error 99 just run it again till it flashes. it never flashed for me. i grew a bit impatient and stopped trying. :cyclops:
i tried relocking once but didnt work. i didnt try too much while relocked ill try again when i get the chance.
hijodedios51206 said:
i ran it multiple times. i saw a thread i forgot where to find it. i looked thru pages of different threads and i found one that says if u get error 99 just run it again till it flashes. it never flashed for me. i grew a bit impatient and stopped trying. :cyclops:
i tried relocking once but didnt work. i didnt try too much while relocked ill try again when i get the chance.
Click to expand...
Click to collapse
There are a couple of solutions to the error 99 problem strewn throughout the Facepalm thread, you can't go through more than a few pages without seeing me mention the solutions. Plus there's another s-off method called Rumrunner that you could have tried. You've kinda taken a step backwards by changing your CID back to stock.
Anyway...
What do you mean you tried relocking but it didn't work? Exactly what didn't work?
timmaaa said:
There are a couple of solutions to the error 99 problem strewn throughout the Facepalm thread, you can't go through more than a few pages without seeing me mention the solutions. Plus there's another s-off method called Rumrunner that you could have tried. You've kinda taken a step backwards by changing your CID back to stock.
Anyway...
What do you mean you tried relocking but it didn't work? Exactly what didn't work?
Click to expand...
Click to collapse
i mean i tried relocking to run RUU but still got error 99. i still have supercid currently. it got to the point i cannot write cid anymore. bootloader simply freezes when i send command to write cid. im not at my computer so ill post cmd's output when i get home. i tried both s-off methods.
hijodedios51206 said:
i tried relocking once but didnt work.
Click to expand...
Click to collapse
The RUU will never run with an unlocked bootloader and S-on. So there is your answer right there.
redpoint73 said:
The RUU will never run with an unlocked bootloader and S-on. So there is your answer right there.
Click to expand...
Click to collapse
alrite ill try it again. ill post the results when i do. thanks.
hijodedios51206 said:
alrite ill try it again. ill post the results when i do. thanks.
Click to expand...
Click to collapse
just be careful of your steps. like the usual supercid + s-on + ruu = brick combo lol
pandasa123 said:
just be careful of your steps. like the usual supercid + s-on + ruu = brick combo lol
Click to expand...
Click to collapse
ill do my best thank u.
hijodedios51206 said:
i mean i tried relocking to run RUU but still got error 99. i still have supercid currently. it got to the point i cannot write cid anymore. bootloader simply freezes when i send command to write cid. im not at my computer so ill post cmd's output when i get home. i tried both s-off methods.
Click to expand...
Click to collapse
hijodedios51206 said:
alrite ill try it again. ill post the results when i do. thanks.
Click to expand...
Click to collapse
You said earlier that you had set the CID
back to stock didn't you? If that isn't the case I'm not sure why you wrote that, you need to provide accurate information otherwise it's almost impossible to help you.
Forget about relocking the bootloader, just find the solution for the error 99 problem in the Facepalm thread and get s-off. It's the easiest solution.
Sent from my Evita
Ok i relocked bootloader and ran RUU and it worked thanks. Facepalm s-off did not work for me again same error 99 so i ran rumrunner's s-off. it worked. as i type i am flashing ruu again to clear the tampered flag. thanks for the help.
Do i have to go from s-off to s-on when i want to go back to stock?
If yes, how to do it?
Or will the part when running RUU make me back to s-on & unroot?
hunabku said:
Do i have to go from s-off to s-on when i want to go back to stock?
If yes, how to do it?
Or will the part when running RUU make me back to s-on & unroot?
Click to expand...
Click to collapse
No, S -Off will not go away unless you enter a certain command in fastboot.
You can return to stock by relocking your bootloader & running your RUU and you will be good to go. Even if I were selling the phone I wouldn't return it to S-ON. I mean anyone with any knowledge would appreciate it, and if the others simply wouldn't know what s-on/s-off is.
But If you are dead set on it, make sure it is the last thing you do after you have ran the RUU and all seems good. (I think you would have to unlock the boot loader again and S-On, then relock it)
****** WARNING******** Do not type this willy nilly to anyone reading this......This should only be done once everything is okay and you are selling/returning a phone... okay I warned you.
fastboot oem writesecureflag 3
^^^^^DANGEROUS COMMAND^^^^^^^ I hate even posting that because some noob will type it.
In fact here is a guide.
http://androidforums.com/one-s-all-...-get-back-stock-moonshine-facepalm-s-off.html
tivofool said:
No, S -Off will not go away unless you enter a certain command in fastboot.
You can return to stock by relocking your bootloader & running your RUU and you will be good to go. Even if I were selling the phone I wouldn't return it to S-ON. I mean anyone with any knowledge would appreciate it, and if the others simply wouldn't know what s-on/s-off is.
But If you are dead set on it, make sure it is the last thing you do after you have ran the RUU and all seems good. (I think you would have to unlock the boot loader again and S-On, then relock it)
****** WARNING******** Do not type this willy nilly to anyone reading this......This should only be done once everything is okay and you are selling/returning a phone... okay I warned you.
fastboot oem writesecureflag 3
^^^^^DANGEROUS COMMAND^^^^^^^ I hate even posting that because some noob will type it.
In fact here is a guide.
http://androidforums.com/one-s-all-...-get-back-stock-moonshine-facepalm-s-off.html
Click to expand...
Click to collapse
Thanks. Just one more question. in this topic http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
They say nothing about flashing stock recovery or anything, is it really not needed?
hunabku said:
Thanks. Just one more question. in this topic http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
They say nothing about flashing stock recovery or anything, is it really not needed?
Click to expand...
Click to collapse
I have read on here that you don't have to. That when running the RUU it puts stock recovery on.
I've also read that if you are getting errors trying to run the RUU you needed to put stock recovery on before running the RUU.
I don't know. The times I have run an RUU I always flashed the stock recovery first.