Bootloader error - cannot RUU or anything - One (M7) Q&A, Help & Troubleshooting

Successfully gained S-Off and Unlock via Revone. Needed to revert to return phone. Successfully locked and gained S-On, although "tampered" appeared on the b/l screen...
Problem now is WiFi no longer works. I cannot flash a complete ROM via RUU, it fails at updating signature. I cannot flash an OTA zip for the same reason. I cannot enter recovery - all I get is the red triangle.
I cannot regain S-Off, or Unlock (via Revone). Error 2.
I've tried firmware.zip - many parts fail. Although my ROM version is now dated April 12th not May 3rd.
Other than WiFi and tampered, the phone works.
I'm stuck!

You should have done s on only when everything else is stock, your lucky your phone even turns on.
I would try to re unlock it, flash a custom recovery and flash a rom get it working again. Then s off and try the whole going stock procedure again.
Sent from my Tricked out HTC One

It won't unlock from Revone

Unlock by flashing the unlock token from htc dev
Sent from my Tricked out HTC One

Done that. However, if the bootloader's knackered, or partly so, a Custom ROM won't flash a new bootloader. Not sure why I need the interim step. My idea was to S-off now unlocked a try RUU again

LenAsh said:
Done that. However, if the bootloader's knackered, or partly so, a Custom ROM won't flash a new bootloader. Not sure why I need the interim step. My idea was to S-off now unlocked a try RUU again
Click to expand...
Click to collapse
Let us know what happens after you run an ruu and try to s off again
Sent from my Tricked out HTC One

Flashed Cwm Ok. Relocked bl. Flashed odex stock 4.2.2 Ok. WiFi now works. Flashed 4.2.2 recovery. Still not getting in to stock recovery. Tampered still showing. RUU dies as before.
Sent from my GT-I9300 using xda premium

Related

Vivid will not reboot after flash or Juopunut S-off

I was trying to obtain S-off through Juopunut Bear, but after it finds my device and tries to reboot it into its program, it simply doesn't reboot. The phone then will not start at all unless I pull the battery and boot into Hboot. From there I flashed my backup img through fastboot and I was good. I found this thread that said I need to ICS 3.32 firmware. On my phone I noticed I am on Software number 3.26.502.56, so I tried to flash the provided download of 3.32 using fastboot. And it did the same exact thing! Would not reboot, and had to battery-pull and re-flash my backup to get it to work.
What is my problem here?
I am on a unlocked and rooted HTC Vivid running stock ICS and stock Kernel.
I really hope I am not committing a stupid error and wasting everyone's time, but it is possible. Thanks in advance for any help!
lonehunter65 said:
I was trying to obtain S-off through Juopunut Bear, but after it finds my device and tries to reboot it into its program, it simply doesn't reboot. The phone then will not start at all unless I pull the battery and boot into Hboot. From there I flashed my backup img through fastboot and I was good. I found this thread that said I need to ICS 3.32 firmware. On my phone I noticed I am on Software number 3.26.502.56, so I tried to flash the provided download of 3.32 using fastboot. And it did the same exact thing! Would not reboot, and had to battery-pull and re-flash my backup to get it to work.
What is my problem here?
I am on a unlocked and rooted HTC Vivid running stock ICS and stock Kernel.
I really hope I am not committing a stupid error and wasting everyone's time, but it is possible. Thanks in advance for any help!
Click to expand...
Click to collapse
If you can get hboot relock the bootloader and run the stock ruu file seems to work for ant errors I've ever gotten , then just go back and redo every thing but s off it should stay off .
Bigtjmc said:
If you can get hboot relock the bootloader and run the stock ruu file seems to work for ant errors I've ever gotten , then just go back and redo every thing but s off it should stay off .
Click to expand...
Click to collapse
Not sure I'm completely understanding you. I need to relock and run stock ruu, then redo everything except s-off? That kind of defeats the purpose, I am trying to s-off
lonehunter65 said:
Not sure I'm completely understanding you. I need to relock and run stock ruu, then redo everything except s-off? That kind of defeats the purpose, I am trying to s-off
Click to expand...
Click to collapse
Yes if you are having problems after any mod to the os just relock the bootloader and run the stock ruu file and it will fix the issue , then go back after you got the phone working right and then unlock the bootloader , flash recovery , root , ect .
But the s-off should stay off and you won't have to redo that step .
So basically you will be on a stock ics with s-off
Then just redo the process to get it where you want it .
Bigtjmc said:
Yes if you are having problems after any mod to the os just relock the bootloader and run the stock ruu file and it will fix the issue , then go back after you got the phone working right and then unlock the bootloader , flash recovery , root , ect .
But the s-off should stay off and you won't have to redo that step .
So basically you will be on a stock ics with s-off
Then just redo the process to get it where you want it .
Click to expand...
Click to collapse
I'm sorry but this just doesn't make sense, the phone is automatically S-On not S-Off, so it won't 'stay s-off'. You understand what I mean?
lonehunter65 said:
I'm sorry but this just doesn't make sense, the phone is automatically S-On not S-Off, so it won't 'stay s-off'. You understand what I mean?
Click to expand...
Click to collapse
did you succeed s-off ?
if you did the s-off procedure via " wire trick " was successful the relocking the boot loader will not change the s-off it will stay off ,
Then relock. Run ruu now you are stock ics with the s-off still , and all the errors should be fixed .
Then just re unlock bl , flash recovery , root , flash New custom Rom / kernel, ect.
All I'm saying is if you have s-off then your good ,
To fix all the errors run the ruu , only reason you need to relock bl is the ruu will reject the install if you are unlocked .
Bigtjmc said:
did you succeed s-off ?
if you did the s-off procedure via " wire trick " was successful the relocking the boot loader will not change the s-off it will stay off ,
Then relock. Run ruu now you are stock ics with the s-off still , and all the errors should be fixed .
Then just re unlock bl , flash recovery , root , flash New custom Rom / kernel, ect.
All I'm saying is if you have s-off then your good ,
To fix all the errors run the ruu , only reason you need to relock bl is the ruu will reject the install if you are unlocked .
Click to expand...
Click to collapse
Oh, we are talking past each other. I did not succeed s-off, when it reboots my phone via Control Bear it does not boot into the Juopunut program, and I have never had a chance to do the wire trick! Thanks for the help though.
lonehunter65 said:
Oh, we are talking past each other. I did not succeed s-off, when it reboots my phone via Control Bear it does not boot into the Juopunut program, and I have never had a chance to do the wire trick! Thanks for the help though.
Click to expand...
Click to collapse
I had trouble on my first S-OFF attempt. I had made a mistake (I missed one of the S-OFF prep steps in section 2 of the SuperGuide, which is at http://forum.xda-developers.com/showthread.php?t=1416836 ).
If you want to try again?
-If you have relocked your bootloader, flash your phone stock using your appropriate RUU while phone is in Fastboot mode.
*** If you haven't relocked bootloader yet, you can do it first via fastboot ("fastboot oem lock")
-Start at section 1 of the superguide (unlocking the bootloader, yeah it sucks to do the process again but thankfully htc makes it easy!)
-And then you can try S-OFF process again (section 2 in superguide)
I know this is for the Vivid but I have the same problem with my EVO 3D. And Can get any help from anyone over there. I just relocked the evo but dont know the next step. Can anybody help me here?
gaarak54 said:
I know this is for the Vivid but I have the same problem with my EVO 3D. And Can get any help from anyone over there. I just relocked the evo but dont know the next step. Can anybody help me here?
Click to expand...
Click to collapse
Download the ruu from HTC or you should be able to download it from the EVO 3d forum while in fastboot mode hook you phone up to your computer fastboot should change to fastbootusb then double click on the ruu and let it do its thing do not unplug till it is finished then you will be out of box stock
Sent from my HTC PH39100 using Tapatalk 2

[Q] S-On Htc First?

So I've run into a problem with my new Htc First phone, the wifi doesnt locate any access points.
Its unlocked,rooted and S-off-ed.
I can unroot and lock the bootloader but does anyone know how to S-on it?
Yea, you just have to ruu first and then follow this guide.
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Kendosis said:
Yea, you just have to ruu first and then follow this guide.
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Click to expand...
Click to collapse
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
dramon said:
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
Click to expand...
Click to collapse
You usually have to run a factory reset, cache/dalvik cache wipe before you flash roms. I get that wifi problem sometimes when trying to flash a rom before wiping.
dramon said:
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
Click to expand...
Click to collapse
DUDE QUICK THING ! you can't flash any roms in till you RELOCK THE BOOTLOADER ! I know it sounds weird but trust me you will keep the S-off status (assuming you have s-off) and everything works fine, I couldn't flash any roms in till I relocked and I heard others have this problem too.
Now the WiFi problem, if factory resetting doesn't work, try flashing the stock rooted ROM around these threads, if that doesn't work try JMZ's kernel, and if that doesn't work then you have a hardware problem, good luck.
Sent from my HTC first
If he just RUU's it he won't have to worry about relocking his boot loader, he should just use titainium backup and ruu to save time.
Kendosis said:
If he just RUU's it he won't have to worry about relocking his boot loader, he should just use titainium backup and ruu to save time.
Click to expand...
Click to collapse
Trust me I've tried RUU and even that didn't work for me, in till I relocked , it was weird but its worth a shot since relocking keeps the s-off anyways
Sent from my HTC first
SneakyGuyDavid said:
Trust me I've tried RUU and even that didn't work for me, in till I relocked , it was weird but its worth a shot since relocking keeps the s-off anyways
Sent from my HTC first
Click to expand...
Click to collapse
I've tried it many times already it works, after you ruu it you just have to turn s-on before you try to unlock the boot loader again otherwise you'll get bootloop.
Kendosis said:
I've tried it many times already it works, after you ruu it you just have to turn s-on before you try to unlock the boot loader again otherwise you'll get bootloop.
Click to expand...
Click to collapse
guys guys, you've lost me.
All I need to do is wipe away all traces of my rooting and bootloader unlocking etc as I'm returning it for warranty.
Now my First is rooted, custom recovery and s-off and unlocked .
I want it unrooted, s-on and boot loader locked.
Someone please guide me through the steps :/
btw im not a n00b, but this is my first HTC phone so I'm not too familiar with these ruu's and s-offs
dramon said:
guys guys, you've lost me.
All I need to do is wipe away all traces of my rooting and bootloader unlocking etc as I'm returning it for warranty.
Now my First is rooted, custom recovery and s-off and unlocked .
I want it unrooted, s-on and boot loader locked.
Someone please guide me through the steps :/
btw im not a n00b, but this is my first HTC phone so I'm not too familiar with these ruu's and s-offs
Click to expand...
Click to collapse
Step 1. RUU your device
Step 2. After it reboots when it's done ruu'ing just start it and go through the set up.
Step 3. Turn on USB debugging mode.
Step 4. Turn on CMD on your PC then just follow the commands below
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writecid xxxxxxxx (where xxxxxxxx is your stock CID.) Mines is CWS__001 on the HTC first I'm not sure if it's the same on all devices just check to see if yours it the same, if it is just use fastboot oem writecid CWS__001
fastboot reboot-bootloader
fastboot getvar cid (It should say CWS__001 if that is your cid.)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
And that's it, it is a extremely simple process lol, I've done it at least 20 times since I tend to ruu my device a lot off of S-OFF, when messing around with different roms.
http://forum.xda-developers.com/showthread.php?t=841890
So its okay if I flash the ruu by the second method as in this thread?
And will custom recovery be overwritten with stock recovery?
OK Update!
I was well on my way to relock,s-on my phone etc and here's what happened
 @Kendosis
 @SneakyGuyDavid
1) Sucessfully RUU'd
As it happened I didnt have my sim inserted and when I rebooted, the wifi was working! When I inserted the sim the wifi stopped working. I did some bit of research and it turns out it has something to do with wifi country codes. Apparently it can be fixed by this app
https://play.google.com/store/apps/details?id=com.fardjad.android.wifixmanager
2) Since the app required root, I was going to get root again.
(Flashing RUU gave me bootloader locked)
I unlocked and then flashed CWM
3) Since I had no roms on my phone storage and the CWM doesnt mount storage, I had to sideload the ROMS.
4) No matter which roms I flashed, I was stuck in a bootloop. I relocked and tried flashing again but I was again stuck in a bootloop. CWM works fine though.
Current status: Bootloader Locked, S-off.
What do I do to fix this bootloop :/
@dramon
I told you to s-on after you ruu first otherwise you get boot loop lol.
Now RUU again and right after don't install nothing just start up the phone and turn usb debugging on and follow the steps to S-ON.
Kendosis said:
@dramon
I told you to s-on after you ruu first otherwise you get boot loop lol.
Now RUU again and right after don't install nothing just start up the phone and turn usb debugging on and follow the steps to S-ON.
Click to expand...
Click to collapse
also sideload sucks ass, if you flash TWRP then you can run adb from it and use adb push, so in cmd you would run " adb push
ROMZIPNAME.ZIP /sdcard "
Thanks guys, I now have an idea of how the rooting and unlocking works for HTC (Y)

What Can I Do With S-ON?

Sorry for this n00b question, but I have never dealt with s-on before. I acquired s-off and was running custom roms no problem, Then, I had to send the phone in to HTC to fix the purple tint camera issue. So, I went full stock and made the mistake of putting it back s-on. Apparently, I can no longer s-off anymore (please correct me if I am wrong!)
So, now I am stuck with s-on and I have already htcdev unlocked my bootloader (in an attempt to s-off which I only later found out I can't do anymore).
How can I still run custom roms and gain root?
Also, if I do those things, will I still be able to go back and get OTA if I wanted to? Like, will I be able to go back to stock to run an OTA update for kitkat if it comes?
Thanks for the help!
SnapplerX said:
Sorry for this n00b question, but I have never dealt with s-on before. I acquired s-off and was running custom roms no problem, Then, I had to send the phone in to HTC to fix the purple tint camera issue. So, I went full stock and made the mistake of putting it back s-on. Apparently, I can no longer s-off anymore (please correct me if I am wrong!)
So, now I am stuck with s-on and I have already htcdev unlocked my bootloader (in an attempt to s-off which I only later found out I can't do anymore).
How can I still run custom roms and gain root?
Also, if I do those things, will I still be able to go back and get OTA if I wanted to? Like, will I be able to go back to stock to run an OTA update for kitkat if it comes?
Thanks for the help!
Click to expand...
Click to collapse
Hi, why can't you S-OFF? Is it due to your updated hboot?
It should be no problem getting S-OFF using rumrunner.
You can get root either by flashing a custom recovery like TWRP which helps you gain root.
Or flash a custom rom like Android Revolution which provides root access after flashing.
If you wan get OTA later on, I believe you have to create a nandroid backup using a custom recovery of your stock
or flash a RUU which requires S-OFF.
Check out the warning in this thread http://forum.xda-developers.com/showthread.php?t=2431515
Also, I confirmed I can't do it because I unlocked the bootloader but rumrunner keeps giving me an error something like "you need insecure bootloader or root su or fu"
That's why I think I can't s-off anymore.
So I'm just looking for steps to run a custom Rom and gain root access with s-on and also what are my limitations with s-on?
Lastly if I needed to, would I be able to get back stock enough to flash ota?
Please delete this post. Accidental double post.
DarkZacky said:
Hi, why can't you S-OFF? Is it due to your updated hboot?
It should be no problem getting S-OFF using rumrunner.
You can get root either by flashing a custom recovery like TWRP which helps you gain root.
Or flash a custom rom like Android Revolution which provides root access after flashing.
If you wan get OTA later on, I believe you have to create a nandroid backup using a custom recovery of your stock
or flash a RUU which requires S-OFF.
Click to expand...
Click to collapse
Nevermind, I just successfully gained S-OFF using rumrunner! I had to htcdev unlock the bootloader AND gain root access and I tried it and it took a while, but it worked!!
In case anyone else has this problem, I had s-off before then i went back s-on and fully stock to get a warranty fix for my camera. When I got it back, I tried to get s-off again by rumrunner, but I kept encountering an error that said "ERROR: looks like device is not rooted AND lacks an unsecure kernel. SU or FU!!"
I did have an unlocked bootloader, so I didn't know why I was getting that. I assumed that my device was no longer able to achieve s-off because according to a post (see post above this) it warned that going back s-on after s-off will result in an non-s-offable device and I didn't encounter this error when I did it the first time.
But, I thought I might as well root it and try again.
I flashed a custom recovery and flashed a superSU zip file to gain root access.
I tried rumrunner again and after a little while, it worked!!

Failed: Return to stock and unrooted (Verizon)

I posted in the Verizon forums a day ago, but have received little to no help. Now I hope that someone can help me here.
Original post http://forum.xda-developers.com/showthread.php?t=2599610
I used this thread to unroot and return to stock http://forum.xda-developers.com/show...highlight=s-on
I had done this before with one of CM 10 and I kept the files used in this thread.
I switched to AOKP kitkat 12-30-13. I wanted to return to stock and unrooted.
I got to the oem ruu and kept receiving this message. FAILED (remote: 90 hboot pre-update! please flush image again immediately)
I did this repeatedly as followed. It went over 5 times. I figured this was a problem. Now I am stuck in the bootloader where my phone is locked and S-on. I tried to flash it again and now I get remote: 12 signature verify failed.
It also says ***TAMPERED*** at the top of bootloader, above ***LOCKED***
Edit: I wanted to mention that I do have a backup of my kitkat state at the beginning of all of this. It is in twrp, but I can't flash install the twrp.img, signature verify failed.
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
sweetnsour said:
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
Click to expand...
Click to collapse
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
geeibara said:
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
Click to expand...
Click to collapse
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
sweetnsour said:
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
Click to expand...
Click to collapse
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
geeibara said:
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
Click to expand...
Click to collapse
to be able to reflash twrp you need to unlock your bootloader that is why you are getting signature fail error

[q] at&t m7 relocked, s-on, tempered, security warning

My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
ajr901 said:
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
Click to expand...
Click to collapse
Post a fastboot getvar all except for the imei and serialno! I hope you restored the MID!
majmoz said:
Post a fastboot getvar all except for the imei and serialno! I hope you restored the MID!
Click to expand...
Click to collapse
LOL @ randomly clicking and ending up with S-On and locked bootloader. That's a great way to mess up your phone .
Deepening on your fastboot output, you are probably SOL.
oh no,
locked bootloader + GPE =
http://forum.xda-developers.com/showthread.php?t=2547894
alray said:
oh no,
locked bootloader + GPE =
http://forum.xda-developers.com/showthread.php?t=2547894
Click to expand...
Click to collapse
Yup. Shows how easy it is to mess up . maybe hope depending on fastboot output
SaHiLzZ said:
maybe hope depending on fastboot output
Click to expand...
Click to collapse
yep we will see.
I also heard of someone lucky here who had a rep from HTC helping him. That guy from HTC compiled a custom firmware package signed with HTC private key (which will allow it to be flashed with s-on and locked bootloader). Once the firmware is flashed, it will unlock the bootloader. That was the only time I heard about this kind of thing and i'm not sure its approved by HTC and will probably not happen soon again.
Similar situation, but haven't gone backwards yet
I just bought a AT&T-locked HTC One M7 and mistakenly thought that rooting and s-off would unlock the SIM. I've also requested an unlock code from AT&T, but if what he's saying is true, I'm going to have to revert to a stock AT&T phone as well.
So my question is, How do I go backward without screwing up the same way? I have made some recovery backups of the original ROM but the bootloader was unlocked already. Took me a long time to figure out how to go forward in the process and I wasn't really concerned about having to re-lock anything because it's beyond the warranty period.
I'm running the following:
Bootloader unlocked
CWM Touch Recovery backups along the way
Firewater for S-Off
Venom ViperOne ROM installed
Bulletproof kernel
Firmware upgraded to 6.09.401.5
I'd really like to un-do as little of this as possible. I'm wondering what part of the modification is detected by the SIM unlock code process.
I'm kind of a noob, but this is my second Android phone that I've rooted and modded in the past couple of weeks, so I'm getting better. I'm very frustrated that unlocking the SIM is such a big deal. Any help you can offer is appreciated.
lamonster26 said:
I just bought a AT&T-locked HTC One M7 and mistakenly thought that rooting and s-off would unlock the SIM. I've also requested an unlock code from AT&T, but if what he's saying is true, I'm going to have to revert to a stock AT&T phone as well.
So my question is, How do I go backward without screwing up the same way? I have made some recovery backups of the original ROM but the bootloader was unlocked already. Took me a long time to figure out how to go forward in the process and I wasn't really concerned about having to re-lock anything because it's beyond the warranty period.
I'm running the following:
Bootloader unlocked
CWM Touch Recovery backups along the way
Firewater for S-Off
Venom ViperOne ROM installed
Bulletproof kernel
Firmware upgraded to 6.09.401.5
I'd really like to un-do as little of this as possible. I'm wondering what part of the modification is detected by the SIM unlock code process.
I'm kind of a noob, but this is my second Android phone that I've rooted and modded in the past couple of weeks, so I'm getting better. I'm very frustrated that unlocking the SIM is such a big deal. Any help you can offer is appreciated.
Click to expand...
Click to collapse
your situation isnt really comparable to OP's situation.
You just have to use the sim unlock code on a stock rom or "close-to-stock" rom like arhd (might also work on venom idk)
If you have to return stock to use the sim unlock code, you can use the stock odexed rom of 6.09.401.5 on available arhd blog download section. just make a nandroid backup of your current setup, flash the stock odexed rom, sim unlock using the code and then revert back to your venom rom using your nandroid backup.
or with s-off, simply ruu your phone, use the unlock code then flash the rom you want to use.
Got it working
alray said:
your situation isnt really comparable to OP's situation.
You just have to use the sim unlock code on a stock rom or "close-to-stock" rom like arhd (might also work on venom idk)
If you have to return stock to use the sim unlock code, you can use the stock odexed rom of 6.09.401.5 on available arhd blog download section. just make a nandroid backup of your current setup, flash the stock odexed rom, sim unlock using the code and then revert back to your venom rom using your nandroid backup.
or with s-off, simply ruu your phone, use the unlock code then flash the rom you want to use.
Click to expand...
Click to collapse
Thanks again. Just bought an unlock code for $5 off one of those sites and it worked without doing any changes to the ROMs and other mods. Thanks for the tip about going back to stock easily though. Might want to set that up just as a backup.

Categories

Resources