So I was trying to restore my HTC one back to normal stocks, with both tampered gone and for it to say Locked again. I haven't used the phone in a few months (switched to a Nexus 5). All I had done with it was unlock the bootloader, install TWRP, and use some random ROMs, with the last one on there being a pretty old version of the Insert Coin Rom, which was based on one of the leaked 4.2.2 OTAs prior to its release.
So what I had read that I needed to do was use revone to get S-OFF. At first I was having issues, repeatedly getting error code = -1. I was able to do the " ./revone -P " command, which would say success and then waiting for device reboot. After this, when trying to run any command I would get that error code. Somehow I got it to work, but on the wrong command (at least I think): " ./revone -l " which then relocked my bootloader. From my limited knowledge, I believe that you need to be complete stock so that it will work. Well as I said, I'm not, so I now have "security warning" with both S-On and the bootloader being Locked (not relocked) and Tampered.
I can't get fastboot to detect the phone, nor does an RUU detect it. I'm just stuck in the bootloader.
I'm on hboot 1.44 and got the phone around June I believe although I'm not sure. It's an AT&T variant, so perhaps I had a patched hboot?
Anyways, any help is much appreciated!
SniperofFear said:
So I was trying to restore my HTC one back to normal stocks, with both tampered gone and for it to say Locked again. I haven't used the phone in a few months (switched to a Nexus 5). All I had done with it was unlock the bootloader, install TWRP, and use some random ROMs, with the last one on there being a pretty old version of the Insert Coin Rom, which was based on one of the leaked 4.2.2 OTAs prior to its release.
So what I had read that I needed to do was use revone to get S-OFF. At first I was having issues, repeatedly getting error code = -1. I was able to do the " ./revone -P " command, which would say success and then waiting for device reboot. After this, when trying to run any command I would get that error code. Somehow I got it to work, but on the wrong command (at least I think): " ./revone -l " which then relocked my bootloader. From my limited knowledge, I believe that you need to be complete stock so that it will work. Well as I said, I'm not, so I now have "security warning" with both S-On and the bootloader being Locked (not relocked) and Tampered.
I can't get fastboot to detect the phone, nor does an RUU detect it. I'm just stuck in the bootloader.
I'm on hboot 1.44 and got the phone around June I believe although I'm not sure. It's an AT&T variant, so perhaps I had a patched hboot?
Anyways, any help is much appreciated!
Click to expand...
Click to collapse
Uninstall Htc sync, driver htc, reinstall Driver htc. reset computer . Go to bootloader on device, connect USB.
hoangvanchung said:
Uninstall Htc sync, driver htc, reinstall Driver htc. reset computer . Go to bootloader on device, connect USB.
Click to expand...
Click to collapse
It still shows up as an unrecognized usb device.
Edit: of course the issue is windows 8. testing on win 7 laptop currently...
SniperofFear said:
It still shows up as an unrecognized usb device.
Edit: of course the issue is windows 8. testing on win 7 laptop currently...
Click to expand...
Click to collapse
did you ever figure this one out? I am stuck here
Related
Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?
i wanted to get stock Rom from custom Rom with image version 3.04.651.2 . So I downloaded latest ruu. Which is also 3.04.651.I re-locked boot loader and started ruu
It cleaned user data till 3% then got stuck at sending file.
Then returned error that it can't upgrade this version of ruu.
Now I'm at stuck at the white screen with boot loader , fastboot modes etc option. Custom recovery is gone. I can't unlock it again
I don't have s-off enable.
While erasing data it's on HTC black screen with logo.
Then it says sending . And then it gives error saying it can't update using this ruu. Try another version. I'm lost.:crying:
Please help me please.
What Winver? Alongside what FW version are you on while attempting to go to 3.04?
EPayne123 said:
What Winver? Alongside what FW version are you on while attempting to go to 3.04?
Click to expand...
Click to collapse
Tried running RUU two more times and it worked.
Now I want to figure how to Unlock relocked Bootloader. I think its only possible via S-off.
Now the problem is that ADB is offline mode.. how Do I adb and push the needed files for s-off
I am on windows xp
aashishbhargav said:
Tried running RUU two more times and it worked.
Now I want to figure how to Unlock relocked Bootloader. I think its only possible via S-off.
Now the problem is that ADB is offline mode.. how Do I adb and push the needed files for s-off
I am on windows xp
Click to expand...
Click to collapse
Update you android sdk/platform tools folder that will fix the offline status
There are no files needing to be pushed to get s-off
bigdaddy619 said:
Update you android sdk/platform tools folder that will fix the offline status
There are no files needing to be pushed to get s-off
Click to expand...
Click to collapse
Thanks, I got the online status.
Now I am with "Relocked" Bootloader, Hboot 1.55, 4.3 Android.
I read that I cannot get S-off on this built. Therefore I tried Rumrunner. But that is failing too after few reboots.
So what is the way to get Bootloader unlocked. Cannot Unlock via HTC DEV Since its Relocked.
My purpose here to unlock bootloader is ROOT the phone and unlock Sim Lock.
how to unlock Re-locked bootloader without ROOT access
aashishbhargav said:
Thanks, I got the online status.
Now I am with "Relocked" Bootloader, Hboot 1.55, 4.3 Android.
I read that I cannot get S-off on this built. Therefore I tried Rumrunner. But that is failing too after few reboots.
So what is the way to get Bootloader unlocked. Cannot Unlock via HTC DEV Since its Relocked.
My purpose here to unlock bootloader is ROOT the phone and unlock Sim Lock.
Click to expand...
Click to collapse
So in other words,
how to unlock Re-locked bootloader without ROOT access if you are on 4.3 and Hboot 1.55
aashishbhargav said:
So in other words,
how to unlock Re-locked bootloader without ROOT access if you are on 4.3 and Hboot 1.55
Click to expand...
Click to collapse
You can use your unlock token if you still have it. If not you can use HTC-Dev again
bigdaddy619 said:
You can use your unlock token if you still have it. If not you can use HTC-Dev again
Click to expand...
Click to collapse
thanks a ton. I swear I tried it thrice before. But I think because of drivers I got error message saying "too Many links"
I tried dev token again and it worked.
Now I have to figure out way to unlock SIM. So far all methods are proving useless after Sprint has decided to screw people with blocking s off and removing api that allowed SIM unlock
aashishbhargav said:
thanks a ton. I swear I tried it thrice before. But I think because of drivers I got error message saying "too Many links"
I tried dev token again and it worked.
Now I have to figure out way to unlock SIM. So far all methods are proving useless after Sprint has decided to screw people with blocking s off and removing api that allowed SIM unlock
Click to expand...
Click to collapse
You can use rumrunner to s-off then ruu back to 1.29 and get sim unlock
bigdaddy619 said:
You can use rumrunner to s-off then ruu back to 1.29 and get sim unlock
Click to expand...
Click to collapse
thanks followed your lead and got the SIM unlock. Will dashing sense 5.5 android 4.3 Rom again lock me ?
I'm kinda in a bad situation here.
I am very familiar with adb, fastboot, flashing and all that jazz but ran into a problem here:
I was trying to return back to stock rom and locked device to return it for warranty (bad top speaker and mic) and in the process I re-locked the bootloader and switched the s-off to s-on.
But when I went to flash the RUU via fastboot I kept getting a error message of signature failure.
Then after trying more RUU's that were most similar to my device I still was getting the same error.
I then tried an .exe RUU but kept getting errors during the process.
If I reboot it, it just returns to the bootloader and recovery goes to the bootloader as well.
Here are some pics:
sarktheshark said:
I'm kinda in a bad situation here.
I am very familiar with adb, fastboot, flashing and all that jazz but ran into a problem here:
I was trying to return back to stock rom and locked device to return it for warranty (bad top speaker and mic) and in the process I re-locked the bootloader and switched the s-off to s-on.
But when I went to flash the RUU via fastboot I kept getting a error message of signature failure.
Then after trying more RUU's that were most similar to my device I still was getting the same error.
I then tried an .exe RUU but kept getting errors during the process.
Click to expand...
Click to collapse
post a fastboot getvar all (excluding IMEI and s/n)
ruu.zip are usually already decrypted, so would fail the signature check.
nkk71 said:
post a fastboot getvar all (excluding IMEI and s/n)
ruu.zip are usually already decrypted, so would fail the signature check.
Click to expand...
Click to collapse
Would really appreciate any help, quite desperate here, I'm actually expecting some important calls and can't even access my phone.
sarktheshark said:
Would really appreciate any help, quite desperate here, I'm actually expecting some important calls and can't even access my phone.
Click to expand...
Click to collapse
let's see the getvar output
nkk71 said:
let's see the getvar output
Click to expand...
Click to collapse
Its already in the image attachments.
sarktheshark said:
Its already in the image attachments.
Click to expand...
Click to collapse
my bad didn't see the screenshots, I always prefer copy/paste
RUU.EXE for you is on androidruu.com or htc1guru.com
androidruu.com RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8
or
htc1guru.com RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8
this will upgrade you to 4.19.661.8 and since you are already S-ON, only use this if:
1- no TAMPERED
2- LOCKED not RELOCKED
.
My bootloader screen shows:
TAMPERED
RELOCKED
SECURITY WARNING
will this RUU still work?
sarktheshark said:
My bootloader screen shows:
TAMPERED
RELOCKED
SECURITY WARNING
will this RUU still work?
Click to expand...
Click to collapse
it may get rid of tampered and security warning, but it will DEFINITELY NOT get you LOCKED, which is usually needed for warranty!!
time to unlock, get S-Off again, and follow the guide properly.
So will it install without error and get me stock ROM for now?
Cause after that, I can get S-OFF later, I'm just desperate for something to run now.
nkk71 said:
it may get rid of tampered and security warning, but it will DEFINITELY NOT get you LOCKED, which is usually needed for warranty!!
time to unlock, get S-Off again, and follow the guide properly.
Click to expand...
Click to collapse
Ya it did not work: (see attachment)
sarktheshark said:
Ya it did not work: (see attachment)
Click to expand...
Click to collapse
don't know what error 158 is... but the ruu should work fine; possibly USB3 problems??
HOWEVER, I highly recommend you get S-Off before upgrading to 4.4 !! (because there is a possibility S-Off won't work!!)
so unlock, s-off, then install any ROM, until you have time to do this properly!
how can I even get s-off again without a rom even installed ?
nkk71 said:
don't know what error 158 is... but the ruu should work fine; possibly USB3 problems??
HOWEVER, I highly recommend you get S-Off before upgrading to 4.4 !! (because there is a possibility S-Off won't work!!)
so unlock, s-off, then install any ROM, until you have time to do this properly!
Click to expand...
Click to collapse
Im using usb 2.0 directly from the rear of my PC, its Windows 7 64bit ultimate
sarktheshark said:
how can I even get s-off again without a rom even installed ?
Click to expand...
Click to collapse
You need a ROM installed, no way around that, hence the (yeah made a little mistake): unlock, put a ROM on it, then S-Off
sarktheshark said:
Im using usb 2.0 directly from the rear of my PC, its Windows 7 64bit ultimate
Click to expand...
Click to collapse
Win7 + USB2 port should be okay.... but this guy also had a problem with the ruu
http://forum.xda-developers.com/showthread.php?t=2707246
and even though it was a USB2 port, the "internal" usb hub showed as a "USB3 hub", a different PC, and it worked.
my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh. I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
my Hboot is version 1.57 and my OS is 6. 10.531.9
I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
kage_outram said:
my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh.
I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
my Hboot is version 1.57 and my OS is 6. 10.531.9
I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
Click to expand...
Click to collapse
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
majmoz said:
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
Click to expand...
Click to collapse
What commands do I put in to add the RUU
kage_outram said:
What commands do I put in to add the RUU
Click to expand...
Click to collapse
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
majmoz said:
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
Click to expand...
Click to collapse
what should happen next
Hey guys, so I tried to unlock my phone to switch over to T-mobile and in the process, I believe I bricked my phone. I followed some very misleading guide, and due to this, my phone is stuck on the RUU screen with the four triangles. To make things worse, my computer (running win 8.1) stopped being able to recognize my phone, so adb and fastboot won't recognize it either (I feel like this happened due to me trying to flash a RUU). I tried several times to re-install drivers to no avail. I don't think I can get to the recovery screen either. Is there any hope in saving this or is it a goner? Thanks.
What I've done so far before this state:
S-OFF
Rooted
changed the CID and MID to T-mobile relevant IDs
kiweewee said:
Hey guys, so I tried to unlock my phone to switch over to T-mobile and in the process, I believe I bricked my phone. I followed some very misleading guide, and due to this, my phone is stuck on the RUU screen with the four triangles. To make things worse, my computer (running win 8.1) stopped being able to recognize my phone, so adb and fastboot won't recognize it either (I feel like this happened due to me trying to flash a RUU). I tried several times to re-install drivers to no avail. I don't think I can get to the recovery screen either. Is there any hope in saving this or is it a goner? Thanks.
What I've done so far before this state:
S-OFF
Rooted
changed the CID and MID to T-mobile relevant IDs
Click to expand...
Click to collapse
if you have used a 1.xx.xxx.x RUU with windows 8.1, thats the problem. When flashing a 1.xx.xxx.x ruu, your bootloader will downgrade to version 1.44. This bootloader version isn't compatible with windows 8.1 (fastboot won't work).
The ruu screen with 4 triangles = incomplete ruu flash. Most likely caused by the computer not being able to flash the entire RUU after hboot 1.44 was flashed.
If using a ruu.exe, you'll need to find a winXP or 7 pc. If using a ruu.zip, you can either use winXP, win7, Linux (recommand ubuntu 12.04 32 bits version) or MacOS.
Btw why did you flashed a ruu to unlock your phone? You know that sim-unlock can be done simply by using a paid code? Or if you have s-off you can sim-unlock for free using the sieempi method.
can you post all the information you can see on the bootloader screen here?
Uh I don't think I can get to the bootloader screen as it is stuck on the RUU screen. Would connecting my phone on linux get some response?
kiweewee said:
Uh I don't think I can get to the bootloader screen as it is stuck on the RUU screen. Would connecting my phone on linux get some response?
Click to expand...
Click to collapse
hold volume down and power until the phone reboot in bootloader mode. can you confirm the ruu version used?
I've done that and the screen just turns off and on with the RUU screen with the four triangles still there.
I've also tried connecting my phone on linux, after installing adb and fastboot, but it has given me a "HTC unknown usb device( device failed enumeration) " warning.
I used this ruu after hearing my phone should be using this ruu, I changed the cid to 11111111 and mid to tmobile on the android.info file so it would work
RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted
After flashing this once it gave me the hboot error thing to boot again, but that is when my phone stopped responding to fastboot.
kiweewee said:
I used this ruu after hearing my phone should be using this ruu, I changed the cid to 11111111 and mid to tmobile on the android.info file so it would work
RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted
After flashing this once it gave me the hboot error thing to boot again, but that is when my phone stopped responding to fastboot.
Click to expand...
Click to collapse
I'm pretty sure your totally wasting your time you can't turn a CDMA Verizon phone into a GSM t-mobile phone by flashing a RUU
your going to end up with a bunch of screwed up partitions
this is how you get fastboot working on windows 8.1 hboot 1.44
http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337