SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
you are lucky to have white screen
You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium
xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.
vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...
xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.
can anyone please help
Where can I get stock recovery, stock boot for the phone?
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^
thanks for the reply, however ur link is broken.
And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??
Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though
xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up
I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app
Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.
Related
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!
bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.
bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.
iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked
gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.
Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.
You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS
Hi the girlfriend has well and truely messed up her phone so any help anyone could give would help.
Ok first off she has a htc sensation hboot 1.27 not sure if it's gb or ics but it's 3.32 so would expect it to be ics.
Is stuck s-on not rooted and had USB disabled before the issue started.
Ok the thing is its stuck at the hboot screen I can get to fastboot (USB and ac). But that's as far as it goes.
It's a stock Vodafone rom and is CID locked to uk voda.
I can't access it with adb believe me I've tried or controlbear.
I have located the correct ruu to try and reflash the phone but I get error 170 or 171 USB errors.
So I tried extracting the rom and loading it via the sd which it finds checks and then goes back to the hboot screen without any
Error message so I'm stumped as to what to do now.
Thanks in advance if anyone can help
paradox1985 said:
Hi the girlfriend has well and truely messed up her phone so any help anyone could give would help.
Ok first off she has a htc sensation hboot 1.27 not sure if it's gb or ics but it's 3.32 so would expect it to be ics.
Is stuck s-on not rooted and had USB disabled before the issue started.
Ok the thing is its stuck at the hboot screen I can get to fastboot (USB and ac). But that's as far as it goes.
It's a stock Vodafone rom and is CID locked to uk voda.
I can't access it with adb believe me I've tried or controlbear.
I have located the correct ruu to try and reflash the phone but I get error 170 or 171 USB errors.
So I tried extracting the rom and loading it via the sd which it finds checks and then goes back to the hboot screen without any
Error message so I'm stumped as to what to do now.
Thanks in advance if anyone can help
Click to expand...
Click to collapse
Hi,
Try following THIS GUIDE
malybru said:
Hi,
Try following THIS GUIDE
Click to expand...
Click to collapse
Already tried but adb won't find the device ive tried using it on both linx and windows both fresh installs so no driver conflicts. I will point out that controlbear can reboot the phone but can't root into it. I'm stumped. Thanks anyway
paradox1985 said:
Already tried but adb won't find the device ive tried using it on both linx and windows both fresh installs so no driver conflicts. I will point out that controlbear can reboot the phone but can't root into it. I'm stumped. Thanks anyway
Click to expand...
Click to collapse
no ..read the guide again ..the process doesn't require ADB ..you just need fastboot ..so read it again .try the method ..if you still facing problems come back here
ganeshp said:
no ..read the guide again ..the process doesn't require ADB ..you just need fastboot ..so read it again .try the method ..if you still facing problems come back here
Click to expand...
Click to collapse
No joy with fastboot either. Every time it tries to write anything it fails. I'm losing the will to live with this phone. May just buy her another one
paradox1985 said:
No joy with fastboot either. Every time it tries to write anything it fails. I'm losing the will to live with this phone. May just buy her another one
Click to expand...
Click to collapse
give me ..the exact error you are getting i can guess the reason better
as for the fails ..i assume it is "REMOTE NOT ALLOWED" ..which happens because you have LOCKED bootloader and thus you need to unlock the bootloader first
Stil no joy can't get the unlock.bin to take. Will continue to fidle with it but have bought her a st27i for now to keep the lady happy lol
ok ive uploaded the unlock token recieved my unlock bin used fastboot flash unlocktoken Unlock_code.bin. and all is fine the pc side but im not getting any disclaimer coming up asking if i accept and thus it isnt unlocking
paradox1985 said:
ok ive uploaded the unlock token recieved my unlock bin used fastboot flash unlocktoken Unlock_code.bin. and all is fine the pc side but im not getting any disclaimer coming up asking if i accept and thus it isnt unlocking
Click to expand...
Click to collapse
Try using this tool.
I was having problems with the other guides but this worked straight away:
http://kgs1992.com/redirect?linker=tool
So I've read a few things on the forum about signal drops and have tried a few solutions but I wanted to get some additional feedback before I go the ATT:
Just in the past few days, I have had increasingly frequent signal drops. This has become really annoying for me, as it always seems to happen when I am using mobile data or sending a text message. The signal drop is transient and only lasts about 30 seconds before it re-connects to my network. I haven't noticed much correlation with when it actually happens but I have attached a picture just so you all can see how frequent these signal drops are. Happens when phone is asleep or in use. These are the things I have tried:
1) Originally was running KingCobra 1.5 and thought it may have been the ROM so I flashed CM10
2) Flashed radio 2.09 for ATT - this showed no improvement / did not make it worse
3) Wiped cache / Dalvik - no improvement
My next course of action was to go to ATT and get a new SIM card. Is it possible that a faulty SIM over time could cause this? And would replacing the SIM likely help in the experience of this community?
Thanks a lot for the input, and if there is something else I can do that I haven't already tried please let me know!
Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.
redpoint73 said:
Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.
Click to expand...
Click to collapse
Can this sort of thing spontaneously happen? One day the SIM just starts getting derpy?
I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app
area51avenger said:
I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Well I got a new SIM from AT&T and I'm still dropping signal. They did say that they just put up LTE towers here where I'm at 2 days ago, which, coincidentally is when I started getting signal drops. I suppose all that is left is for me to RUU? I don't know how to so it should be fun reading up lol
Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Edit: Could someone enlighten me a little bit on the process of the RUU -- The only thing that is cloudy here is that I am currently running CM10, would I be able to run the executable RUU if I was running a stock odexed/deodexed ROM after re-locking the bootloader? I have looked at this (http://forum.xda-developers.com/showthread.php?t=1814217&highlight=ruu) and the associated guide but this all assumes that I'm already on a stock image right? I've tried doing some reading but I am drawing a blank on the RUU process
TheEmpyre said:
Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Click to expand...
Click to collapse
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2
superchilpil said:
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?
TheEmpyre said:
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?
Click to expand...
Click to collapse
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2
superchilpil said:
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Edit: Forgot that when you unlock bootloader you do it through fastboot with "fastboot flash unlocktoken Unlock_code.bin so ultimately I would be able to re-flash my recovery etc
TheEmpyre said:
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Click to expand...
Click to collapse
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token, flash twrp, and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2
superchilpil said:
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file
TheEmpyre said:
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file
Click to expand...
Click to collapse
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2
superchilpil said:
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen
TheEmpyre said:
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen
Click to expand...
Click to collapse
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2
superchilpil said:
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?
What my screen looks like here before and after selecting bootloader with the power button
Sent from my Nexus 10 using Tapatalk 2
TheEmpyre said:
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?
Click to expand...
Click to collapse
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
alright, in fastboot run fastboot oem rebootRUU
then run the ruu.exe
superchilpil said:
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
Click to expand...
Click to collapse
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected
TheEmpyre said:
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected
Click to expand...
Click to collapse
try my method above, ive tried it with fastboot... the ruu just ignores it
That method should work, the ruu should pick it up and wipe it clean
I changed my CID back to CID__001 from superCID and re-locked phone. Now when I go back to unlock with unlock_code.bin it does not work.
So I regenerate a token identifier....
C:\Users\M\HOX>fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO639E7B248BDCAB6CBEA0577A98CD11AD
INFO0B20640D8180AB31F0B0DC2DDC62EB6A
INFO2524B5D27105D40678D5CC2C0E492220
INFO6A98F11162989E19E5F326B78E38D72E
INFO31E8D7A04B433C18C204D007D4B58689
INFO693ABAC1650EB10FC962312231F9E548
INFOF8D103A3EE4DD17F2D807751D006C739
INFO6254FA142E08F7DDBDF777300D8C8BE5
INFO4A6BA0CE58FFAAF25646B8B8A21CF068
INFO50F67F9A30A6DD984D50E497AF32485D
INFOFF19DBAB976D7F81CDC9E8320BD25E9D
INFOA56BB0B240AB81E35CD9742922C28320
INFOC02CF3A74B8589948155024DA23D31EC
INFO7620755FE9B5CA879B4968E79E239B39
INFOBFC9203AD5ED5373F568492B61B20700
INFO0C5B33DEA9E101B475EAF0E3CD4076F7
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Users\M\HOX>
On HTC site I get error code 160 mid not allowed when I try to generate a a new .bin
My Token identifier prior to the change was
<<<< Identifier Token Start >>>>
1A5036DDFCC755FA08619C55D40C47D0
A6FB8A57A0F9482C9174A6FA83921F0A
8D639270F2DCA79AD36FFB093D79F319
B9A66170322959FC5A93C12CB3500DF5
C6D42B624710F209FF4A4B70F5EAA9F3
B1947CFA26A96C7969F2788CAA631583
1C643ED6FEA902F1349AC5219AB8648C
C405010F564F16D1F63E3EA5DE089BE6
02D0CC3CBBFDDBBC74B8844144333E0E
BB70889A1F45259AE20ADCE88E7A201A
CF4BEB1A6F44E3162C63959FB800CF99
1E081824821F45DD2BEC4420A29A8F06
F4271D50F0F124EF324F5E41A34CE420
10572E09220654655A467B7AE1EAFB51
1D52CB57BA7154FB9CAC9F782494AF35
D76D2762018B42BEA736906581D9D1BE
<<<<< Identifier Token End >>>>>
The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.
redpoint73 said:
The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.
Click to expand...
Click to collapse
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.
ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).
Palmetto_X said:
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.
Click to expand...
Click to collapse
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Sent from my HTC One XL using Tapatalk 2
sizemore2000 said:
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Click to expand...
Click to collapse
OP stated in another thread he bought his bootloader unlocked too.
But yes, I agree, there was not point in him relocking it. He wanted to return to stock. I suggested he flash a stock rooted ROM, but he either didn't listen, or was already too far down the relocking path (removed TWRP).
redpoint73 said:
ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).
Click to expand...
Click to collapse
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me
I think you should PILOT the closest vehicle over the phone to end this misery for everyone
954wrecker said:
I think you should PILOT the closest vehicle over the phone to end this misery for everyone
Click to expand...
Click to collapse
Aren't you supposed to be in school?
Palmetto_X said:
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me
Click to expand...
Click to collapse
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?
redpoint73 said:
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?
Click to expand...
Click to collapse
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
In attempting to fix the RUU problem I have I would flash stock recovery, stock boot.img, relock, try to RUU......my last genius move was rename cid , stock recovery, boot.img, relock...........now I am dead in the water
Palmetto_X said:
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
Click to expand...
Click to collapse
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?
redpoint73 said:
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?
Click to expand...
Click to collapse
I just tried it on another PC and got RUU 2.2 to work. Thank you very much for your persistence.
Ouch. 2.20 RUU means you are now stuck with the 1.14 hboot. Fine if you want to stay stock, but a bit of a pain for flashing custom ROMs, as you now have to flash boot.img separately from fastboot. You also can't flash radios now.
1.73 or 1.85 would have been better. Did you try to run those RUUs on this other PC first?
He deserves hboot 1.14 after talking trash earlier. Hopefully he didn't even try the earlier ruu's
Sent from my HTC One XL
Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.
iElvis said:
Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.
Click to expand...
Click to collapse
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.
so... theres a way to permanently brick your CID to the point where it cant be changed/unlocked again? :/ now i'm REALLY going to read up on how to relock and get my phone back to the 2.20 RUU (came on that, no sense trying to get an earlier one) for selling it....
redpoint73 said:
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.
Click to expand...
Click to collapse
I'd like him to root his phone and brick it. Then he can come back here to whine about how crappy the phone is when he's the retard.
But wait, there's more.
I just exchanged an Xperia S for this HTC One S in excellent condition. It was already bootloader unloked, has TWRP only that it was sim locked. I tried the unlock.sh script (both from terminal emulator, and root explorer) then manually getting the UN_lock_code and subtracting the reversed 7 digits from the IMEI (with the added one), and even the automated app. The script kept running and never show the unlock code, and the one I got using this method wasn't accepted.
Then I thought I should to a factory reset and try again. So I reboot to bootloader, chose factory reset and now everything is wiped. No OS installed so I can't boot, TWRP won't mount USB storage so I can' flash any other rom.
Please help.
Is this a ville or the ville C2?
From your hbot, it seems like C2
42freelancer said:
Is this a ville or the ville C2?
From your hbot, it seems like C2
Click to expand...
Click to collapse
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?
cars ontols
zgomot said:
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?
Click to expand...
Click to collapse
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want. As far as SIM unlocking, shouldn't you be S-Off first?
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.
42freelancer said:
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want.
Click to expand...
Click to collapse
How about ViperSC2? Will that do?
42freelancer said:
As far as SIM unlocking, shouldn't you be S-Off first?
Click to expand...
Click to collapse
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
42freelancer said:
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.
Click to expand...
Click to collapse
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.
For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
zgomot said:
How about ViperSC2? Will that do?
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.
Click to expand...
Click to collapse
Not sure if you saw my last post before this one, I forgot to reply with your quote.
42freelancer said:
For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
Not sure if you saw my last post before this one, I forgot to reply with your quote.
Click to expand...
Click to collapse
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.
That seems to be an issue with Windows 8.1. It also seems to be the only OS affecting fastboot. There is a file I used to get all of my drivers working properly, with ADB and fastboot. Fastboot is required with any S-Off attempt. I'll go scope out the file and return here.
---------- Post added at 08:04 PM ---------- Previous post was at 07:59 PM ----------
zgomot said:
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.
Click to expand...
Click to collapse
Try this! This should work: http://forum.xda-developers.com/showthread.php?t=2588979
This is what I used last night to reinstall my drivers with working ADB and Fastboot. It also comes with a picture guide on how to fix the device detection. It's fast, easy, lightweight, and best of all, it works!
Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.
Tried that and I still can't get fastboot devices to enumerate my device. Pfffft.
zgomot said:
Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.
Click to expand...
Click to collapse
No sweat. I've got nothing going on later, so I'll do some research for ya! Night
OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?
zgomot said:
OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?
Click to expand...
Click to collapse
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601
42freelancer said:
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601
Click to expand...
Click to collapse
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.
zgomot said:
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.
Click to expand...
Click to collapse
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?
42freelancer said:
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?
Click to expand...
Click to collapse
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.
zgomot said:
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.
Click to expand...
Click to collapse
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess
42freelancer said:
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess
Click to expand...
Click to collapse
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.
zgomot said:
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.
Click to expand...
Click to collapse
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] http://forum.xda-developers.com/showthread.php?t=2644607 TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.
42freelancer said:
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.
Click to expand...
Click to collapse
PROGRESS!
I managed to get S-OFF. Do I try sim-unlocking now, or is there anything else I have to do first?