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
Related
Hi Guys,
I really need some help this one........ I rooted my phone sometime ago now and recently in my stupid idiot mind decided to unroot (Yeah stupid i know). Firstly i flashed the RUU:
RUU_PYRAMID_ICS_HTC_Europe_3.12.401.2_Radio_11.65.3504.00U_11.19.3504.29_2_test_233440.exe
Then i went through the s-on process when i finished and rebooted the phone it just kept going to htc logo then blank screen then off and just repeats this process. I've gone into Hboot screen and get this image in the attachment.
Any advice or help would really help I've come over from the Darkside of iPhone so I'm fairly new to all this.
With S-On, you cannot flash a rom from a different region. And your bootloader has changed to 1.23 which i dont think revolutionary is compatible with (the tool to s-off your phone). try flashing the original rom of your phone.
Try flashing an older RUU so u can downgrade hboot version and try running revolutionary again. If not try using official HTC boot unlocker
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
Thanks for the reply's I'm sure I've tried to downgrade but I've no clue what version was on the phone before root, i know it was the latest gingerbread at the time 3.4 ???????? Oh and I'm in the UK if that helps?????
http://www.filefactory.com/f/c87a2330449af512/
Here you can find all the shipped ROMs for Sensation. There are 4 there, if u search for the word "UK", T-Mobile, Vodafone, Orange and H3G. Pickup the one according to your operator.
But please dont use any of those in case your phone is not bound to any operator. Then you'll have to figure out something else. Update here if that is the case and will try to find a ROM for you.
andyshep1974 said:
Hi Guys,
I really need some help this one........ I rooted my phone sometime ago now and recently in my stupid idiot mind decided to unroot (Yeah stupid i know). Firstly i flashed the RUU:
RUU_PYRAMID_ICS_HTC_Europe_3.12.401.2_Radio_11.65.3504.00U_11.19.3504.29_2_test_233440.exe
Then i went through the s-on process when i finished and rebooted the phone it just kept going to htc logo then blank screen then off and just repeats this process. I've gone into Hboot screen and get this image in the attachment.
Any advice or help would really help I've come over from the Darkside of iPhone so I'm fairly new to all this.
Click to expand...
Click to collapse
DAMN man! You decided to go S-ON on a ICS LEAK???..... Pretty silly mate
Since you are in the UK, I would go for a STOCK unbranded RUU, to be on the safe side. Search the forum to try and find the stock 1.18.000 hboot.img and flash via PG58IMG in recovery, as the newer hboot's like you now have dont support fastboot commands.
I really dont know otherwise mate....You may have to use htcdev.com to unlock bootloader.
When i purchased the phone it was unlocked but i use Orange uk. I'm not bothered if it was unlocked as I'm only going to use Orange uk anyway so thats not an issue.
I've tried most of the RUU for Europe but just keep getting errors i really do think its a dead end..........
Yeah I'm stupid !!!!!!!!!!!!!!!! I've tried loads of RUU off there and just keep getting errors I've unlocked using htc.dev software, I'll put up another picture of the current state of the device.
andyshep1974 said:
When i purchased the phone it was unlocked but i use Orange uk. I'm not bothered if it was unlocked as I'm only going to use Orange uk anyway so thats not an issue.
I've tried most of the RUU for Europe but just keep getting errors i really do think its a dead end..........
Click to expand...
Click to collapse
Ok.... Try follow this guide http://forum.xda-developers.com/showthread.php?t=1228648 to get stock recovery. Use the 'GET STOCK RECOVERY MANUALLY' and only follow it to step 5.
Get the recovery_signed.img from an RUU like it says... preferably this one http://www.filefactory.com/file/c0a...00U_10.15.9035.02_2_release_228602_signed.exe
Once you got it zip it up using 7zip file manager or winzip etc... and rename it to PG58IMG.zip
Place on your SD card and boot into bootloader and when it asks to update click yes and see if it changes your boot loader back to stock 1.18.000. If it does..then s-off again using revolutionary then FLASH an OFFICIAL RUU not a LEAK!!
If that dont work HTCDEV.com it is mate
I hope this helps.. I not at all experienced much either, but know enough to watch my arse and be careful. You may need an experienced dev from xda to give you some advise
ajay83 said:
Ok.... Try follow this guide http://forum.xda-developers.com/showthread.php?t=1228648 to get stock recovery. Use the 'GET STOCK RECOVERY MANUALLY' and only follow it to step 5.
Get the recovery_signed.img from an RUU like it says... preferably this one http://www.filefactory.com/file/c0a...00U_10.15.9035.02_2_release_228602_signed.exe
Once you got it zip it up using 7zip file manager or winzip etc... and rename it to PG58IMG.zip
Place on your SD card and boot into bootloader and when it asks to update click yes and see if it changes your boot loader back to stock 1.18.000. If it does..then s-off again using revolutionary then FLASH an OFFICIAL RUU not a LEAK!!
If that dont work HTCDEV.com it is mate
I hope this helps.. I not at all experienced much either, but know enough to watch my arse and be careful. You may need an experienced dev from xda to give you some advise
Click to expand...
Click to collapse
Mate thanks for the advice and info I'll give it a go and let you know.
Thanks again!!!!!!!!!!!!
andyshep1974 said:
Mate thanks for the advice and info I'll give it a go and let you know.
Thanks again!!!!!!!!!!!!
Click to expand...
Click to collapse
No worries. I HOPE it works..... it's a long shot in all honesty as you've have also gone back to s-on. If you was still s-off then a previous hboot can be flashed no probs.
Worth a try
Install Stock Unbranded RUU for UK
I've placed the Image file onto sd card and zipped it but no good just cheeps saying no image all the way down the screen (In green writing). The phone is unlocked with htc.dev already. I've really just gotta face facts and bite the bullet so to speak.
jasminthoria said:
Install Stock Unbranded RUU for UK
Click to expand...
Click to collapse
Tried loads of them but none seem to work.
Thanks
andyshep1974 said:
I've placed the Image file onto sd card and zipped it but no good just cheeps saying no image all the way down the screen (In green writing). The phone is unlocked with htc.dev already. I've really just gotta face facts and bite the bullet so to speak.
Click to expand...
Click to collapse
You zip the image 1st, so it's PG58IMG.zip THEN put into SDCARD and boot into bootloader 'power & vol-' together
It's 'already' unlocked via htc? damn man.... I really dont know then bud. You going s-on on a phone which is already s-off'd by htcdev.com was a waste of time really, because they already know it been unlocked whether you went back to s-on or not.
I've attached a signed recovery, place in sd card and boot into bootloader and see if it worksView attachment PG58IMG.zip
ajay83 said:
You zip the image 1st, so it's PG58IMG.zip THEN put into SDCARD and boot into bootloader 'power & vol-' together
It's 'already' unlocked via htc? damn man.... I really dont know then bud. You going s-on on a phone which is already s-off'd by htcdev.com was a waste of time really, because they already know it been unlocked whether you went back to s-on or not.
Click to expand...
Click to collapse
I made the image file a zip thats right ??????
Yeah I'm really stuck cause if i send it away to htc they will know its been unlocked/locked so I'm sort of screwed. Guess i could play dumb and say it was like it when i got it. Thanks for the help though bud.
Try the .zip file I put up in previous post and let me know.
If it dont work, then Im sorry bud. Worth a shot tho.
If you do go through HTC, keep me informed and let me know what they say.
ajay83 said:
Try the .zip file I put up in previous post and let me know.
If it dont work, then Im sorry bud. Worth a shot tho.
If you do go through HTC, keep me informed and let me know what they say.
Click to expand...
Click to collapse
Tried your zip file and got parsing zip then went back to white screen i pressed recovery it went to phone with green circle thingy then went to phone with red triangle is that any help ???????????
andyshep1974 said:
Tried your zip file and got parsing zip then went back to white screen i pressed recovery it went to phone with green circle thingy then went to phone with red triangle is that any help ???????????
Click to expand...
Click to collapse
Right, turn off the phone, now take the .zip file off the sd card and boot into bootloader again but DONT press anything. just tell me what it says now at the top. What hboot number does it say?
You have a stock recovery now, so clicking on recovery inside boot loader takes you to that screen.
ajay83 said:
Right, turn off the phone, now take the .zip file off the sd card and boot into bootloader again but DONT press anything. just tell me what it says now at the top. What hboot number does it say?
You have a stock recovery now, so clicking on recovery inside boot loader takes you to that screen.
Click to expand...
Click to collapse
hboot 1.23.0000
Same as before guess I'm doomed then.
Alright, so we all know it's confusing to differentiate the One XL from the One X, especially since Rogers and AT&T insist on calling it the One X.
IF YOU HAVE A "ONE X" FROM ROGERS/AT&T, YOU HAVE THE ONE XL. DON'T EVEN BOTHER VISITING THE ONE X FORUMS.
Now, you've gone and downloaded CWM from the One X forums and flashed it to your One XL, and you're semi-bricked. Let's get you out of that pickle. Please note that I have not done any of this to my own One XL, as there's no ROMs or custom recovery images or kernels for our phone yet. However, just this morning I performed a similar operation on my Jetstream, and the steps will be identical. I take no responsibility for any problems you experience.
First, you'll need to download the leaked RUU that can be found here: http://forum.xda-developers.com/showthread.php?t=1550930
EDIT: designgears has offered a newer recovery image. I'm not sure what advantages it would bring, but at least there's a second option: http://www.gigashare.in/53885
Please note that this is marked as the AT&T RUU, so there's no guarantee this will work for Rogers. However, your recovery mode is screwed anyway, so in my opinion, it couldn't hurt to try.
Once you've downloaded the RUU, run it. You don't need to install the RUU itself, we just have to have the application running. Once running, it'll create a "rom.zip" file in a temp folder somewhere in your user profile. While the RUU is open, just search for "rom.zip" and you should find it. Open this file and extract "recovery_signed.img" to your computer, into the same folder as your "fastboot" application. Once you've done this, close the zip file and exit the RUU.
Now, boot your device into fastboot mode
Code:
adb reboot bootloader
Once in bootloader mode, you may need to select "fastboot" from the menu.
Now that you're in fastboot mode, you can flash the recovery we extracted from the RUU:
Code:
fastboot flash recovery recovery_signed.img
Your screen will go through a couple brief steps, something like "sending recovery_signed.img" then "writing recovery_signed.img" and then "OK."
Try to boot into recovery now, and you should see the standard HTC recovery mode!
I really hope this helps everyone out. I'll iterate again that I have no tried this with my One XL, so I have no actual proof that this will work. But, if you've already flashed the wrong recovery image, you should be somewhat familiar with these steps already.
EDIT: Please post your success with this method. As I haven't tested, I'd like to know if everything's kosher, and I can change the instructions accordingly if something's wrong.
Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
1.61.502.1 CL49502
designgears said:
Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
Click to expand...
Click to collapse
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?
craig0r said:
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?
Click to expand...
Click to collapse
It's AT&T recovery.
Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?
For myself I will leave it for now and wait until an official rogers RUU or custom recovery to make sure I don't break it again
Sent from my HTC One X
bongd said:
Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?
Click to expand...
Click to collapse
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium
craig0r said:
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol
I feel your pain!
bongd said:
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol
Click to expand...
Click to collapse
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!
krepler said:
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!
Click to expand...
Click to collapse
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!
bongd said:
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!
Click to expand...
Click to collapse
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img
krepler said:
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img
Click to expand...
Click to collapse
and the latest:
http://www.gigashare.in/0029e = Cingular 1.68.502.1 Radio 0.16.32.09.01 boot_signed.img
http://www.gigashare.in/03695 = Cingular 1.68.502.1 Radio 0.16.32.09.01 recovery_signed.img
Should've just waited and posted these ones... buuuuuuut, I have no patience.
Hopefully the boot.img works for you! Let me know how she goes.
bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
---------- Post added at 07:25 AM ---------- Previous post was at 07:22 AM ----------
krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
Krepler, Can you tell me how did you solve your recovery? I am in your sisutation as well, flash the wrong recovery and once I boot to recovery and it will occur the boot loop, however I am still able to use the One X (Semi-bricked). Did you flash the stock recovery from Rogers or the one that you just posted from AT&T?
Elin28 said:
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
Click to expand...
Click to collapse
One does not interfere with the other. Recovery is pretty much its own operating system, completely segregated from the rest of the phone. It can neither hinder nor enhance the booting of your phone in normal mode. You could theoretically flash a random sequence of ones and zeros to the recovery partition, and the phone would continue to boot just fine. Until you try and go into recovery mode that is. Flashing the recovery_signed.img as per my instructions is safe in regards to the phone's normal operation. I can't promise that it's a working recovery, however, as I've not tried it myself.
Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!
Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
bongd said:
Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!
Click to expand...
Click to collapse
@bongd
Awesome bro!!!! Glad you got your hox up and running.
Sent from wherever I am!
yoohoohoo said:
Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
Click to expand...
Click to collapse
Have you tried running "fastboot erase cache"?
What other steps have you done as well? The killer for me was the boot.img file that Leedroid created as part of his ROM installation. The AT&T recovery is what I had used. For a moment I thought I might need to try flashing the system.img file like redwreck had to, but I didn't need to.
Perhaps someone could upload that as well, please? If you need to flash that, it's "fastboot flash system system.img" and it'll flash that too. I always do "fastboot reboot" after as well.
I trust that these should work. Hopefully there'll be a full Rogers RUU so we can flash that just to be on the safe side. Best of luck! I'll keep an eye on this thread as well.
Since I posted earlier I've been setting things up and it's working like a damn charm. Tried exhausting every weird and quirky feature I thought might screw up, but I can't find anything that's not working.
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.
Okay so i was having wifi issues on Trickdroid 7.0.0 TMOUS.. so i did a little searching and what not and found out i had to flash 2.3.5 parts/radio to get it working. before hand i was getting full bars/4g. After i flashed both 2.3.5 extra partitions, and the 2.3.5 radio i reboot to find out my wifi finally works, then i notice i have no signal.. i tried rebooting, etc didnt work. tried restoring the backup i made through clockwork before i flashed the radio; didnt work. tried taking out my SIM card and putting it back in, didnt work. ive tried flashing miui, trickdroid 8.x.x, a nandroid posted from stock 2.3.5, nothing will bring back my signal. so i thought maybe my SIM card is messed up, i put it in my backup go phone and i get full bars.
also, i tried RUU both 1.5.x and 1.8.x and both give me RUU error 155 after its done "sending files"..
any help would be awesome. could i flash a older radio or something??
edit: im on hboot 1.09 btw
Okay looks like no one knows how to fix this?
tried flashing a older radio and no go, and just flashed RUU 1.84 and no go as well. i flashed the international trickdroid and upon first boot i had signal (no 4g) and i was able to send a text to myself and received it. then i restarted my phone and.. gone that was before i flashed the RUU.
stratax said:
Okay looks like no one knows how to fix this?
tried flashing a older radio and no go, and just flashed RUU 1.84 and no go as well. i flashed the international trickdroid and upon first boot i had signal (no 4g) and i was able to send a text to myself and received it. then i restarted my phone and.. gone that was before i flashed the RUU.
Click to expand...
Click to collapse
Try this.
Originally Posted by ckpv5 View Post
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One S after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img / unlocked bootloader
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
---------- Post added at 09:54 PM ---------- Previous post was at 09:41 PM ----------
stratax said:
Okay so i was having wifi issues on Trickdroid 7.0.0 TMOUS.. so i did a little searching and what not and found out i had to flash 2.3.5 parts/radio to get it working. before hand i was getting full bars/4g. After i flashed both 2.3.5 extra partitions, and the 2.3.5 radio i reboot to find out my wifi finally works, then i notice i have no signal.. i tried rebooting, etc didnt work. tried restoring the backup i made through clockwork before i flashed the radio; didnt work. tried taking out my SIM card and putting it back in, didnt work. ive tried flashing miui, trickdroid 8.x.x, a nandroid posted from stock 2.3.5, nothing will bring back my signal. so i thought maybe my SIM card is messed up, i put it in my backup go phone and i get full bars.
also, i tried RUU both 1.5.x and 1.8.x and both give me RUU error 155 after its done "sending files"..
any help would be awesome. could i flash a older radio or something??
edit: im on hboot 1.09 btw
Click to expand...
Click to collapse
So can you post the link to where you got the "2.3.5 extra partitions" and the radio from. And how did you flash them on your phone?
dc211 said:
Try this.
---------- Post added at 09:54 PM ---------- Previous post was at 09:41 PM ----------
So can you post the link to where you got the "2.3.5 extra partitions" and the radio from. And how did you flash them on your phone?
Click to expand...
Click to collapse
thank you for your reply. this is where i got it. http://forum.xda-developers.com/showthread.php?p=32170653 from "Rsotbiemrptson" i also got the radio update from him, what he posted.. http://forum.xda-developers.com/showthread.php?t=1657831&page=285 look at my quote at the bottom.
stratax said:
thank you for your reply. this is where i got it. http://forum.xda-developers.com/showthread.php?p=32170653 from "Rsotbiemrptson" i also got the radio update from him, what he posted.. http://forum.xda-developers.com/showthread.php?t=1657831&page=285 look at my quote at the bottom.
Click to expand...
Click to collapse
This is a tricky one but I got a few ideas. Need a little bit more info. What version of hboot do you have?
---------- Post added at 11:10 PM ---------- Previous post was at 11:02 PM ----------
dc211 said:
This is a tricky one but I got a few ideas. Need a little bit more info. What version of hboot do you have?
Click to expand...
Click to collapse
Oh i see 1.09 now. I understand why the updated adsp wcnss would fix your wifi but I can't really figure out what broke your radio. You flashed a bunch of different roms so you ruled that out. I would go ahead and try flashing the 2.35 radio again and see if that helps. If not flash an older radio and see.
I know how to undo all the changes you made but lets see what a new radio flash does first. Don't just flash the one you have but re-download it fresh and flash with that.
dc211 said:
This is a tricky one but I got a few ideas. Need a little bit more info. What version of hboot do you have?
---------- Post added at 11:10 PM ---------- Previous post was at 11:02 PM ----------
Oh i see 1.09 now. I understand why the updated adsp wcnss would fix your wifi but I can't really figure out what broke your radio. You flashed a bunch of different roms so you ruled that out. I would go ahead and try flashing the 2.35 radio again and see if that helps. If not flash an older radio and see.
I know how to undo all the changes you made but lets see what a new radio flash does first. Don't just flash the one you have but re-download it fresh and flash with that.
Click to expand...
Click to collapse
okay thank you. i will try a few more things. i really hope its not blacklisted, i really dont think it is though since it happened RIGHT afterwards.
oh other details is i didnt wipe or anything i just flashed both, partition parts/radio then rebooted and wifi worked then had no service.
stratax said:
okay thank you. i will try a few more things. i really hope its not blacklisted, i really dont think it is though since it happened RIGHT afterwards.
oh other details is i didnt wipe or anything i just flashed both, partition parts/radio then rebooted and wifi worked then had no service.
Click to expand...
Click to collapse
Since it just happened after you flashed new stuff that leads me to believe that was the cause. I'm pretty sure I know how to fix. But if it were me I'd start with re-flashing the radio.
I just installed the OTA 2.3.5 update over 1.84 RUU and still no go, im going to try to install the radio through recovery and see if that fixes it.
edit: well that was dumb.. now i have the updated hboot :l
stratax said:
I just installed the OTA 2.3.5 update over 1.84 RUU and still no go, im going to try to install the radio through recovery and see if that fixes it.
edit: well that was dumb.. now i have the updated hboot :l
Click to expand...
Click to collapse
Sorry to hear that! I didn't expect you to try that route. However, it should have resolved your issue the OTA would have overwritten everything you did. You couldn't get a cell signal after the RUU or OTA?
dc211 said:
Sorry to hear that! I didn't expect you to try that route. However, it should have resolved your issue the OTA would have overwritten everything you did. You couldn't get a cell signal after the RUU or OTA?
Click to expand...
Click to collapse
Still a no go.. D: im going to try and install trickdroid 7.0.0 and re-install that radio just to double check.
stratax said:
Still a no go.. D: im going to try and install trickdroid 7.0.0 and re-install that radio just to double check.
Click to expand...
Click to collapse
You can't reinstall the radio, those days are over for you. Sorry to be the bearer of bad news. You're stuck with 2.x RUU's only from now on to change radios.
Since your in this spot you might try the latest CM10 nightly they have implemented the radio firmware into the rom itself. That might allow you to sidestep your problem. Also check under about -> phone and see if your imei matches whats on the box that came with the phone.
Okay, i now know its not blacklisted. I just unlocked it with the unlock .exe and put a extra AT&T SIM card laying around and put in the AT&T APN and everything and still says "disconnected because service is unavailable". sooooo, thats good news! i guess..
im going to try to flash a nightly and see if that works. my brother just told me they are probably working on the 4g towers here and maybe thats why it isnt working on this phone and a few other people.. that would be cool, but frustrating that ive done all this.
edit: with the at&t SIM card it just says "no service" in the notifications bar. With the T-Mobile SIM card it says "Emergency calls only". weird
edit2: Still doesnt work with cyanogenmod 10.
stratax said:
Okay, i now know its not blacklisted. I just unlocked it with the unlock .exe and put a extra AT&T SIM card laying around and put in the AT&T APN and everything and still says "disconnected because service is unavailable". sooooo, thats good news! i guess..
im going to try to flash a nightly and see if that works. my brother just told me they are probably working on the 4g towers here and maybe thats why it isnt working on this phone and a few other people.. that would be cool, but frustrating that ive done all this.
edit: with the at&t SIM card it just says "no service" in the notifications bar. With the T-Mobile SIM card it says "Emergency calls only". weird
edit2: Still doesnt work with cyanogenmod 10.
Click to expand...
Click to collapse
im suck in the same place man i hope someone finds out
Yeah I thought today it might be fixed but its not. It finally finds T-Mobile if I search for it but it won't connect to it. It won't connect to att either when I put my att sim in. So I think its the phone having issues.. I've been seeing a lot of other people having them as well.
When I select any network or even automatic registration it says "can't connect right now. Try again later."
I uploaded two screen shots. It won't even let me call T-Mobile..
Sent from my HTC One S using xda app-developers app
stratax said:
Yeah I thought today it might be fixed but its not. It finally finds T-Mobile if I search for it but it won't connect to it. It won't connect to att either when I put my att sim in. So I think its the phone having issues.. I've been seeing a lot of other people having them as well.
When I select any network or even automatic registration it says "can't connect right now. Try again later."
I uploaded two screen shots. It won't even let me call T-Mobile..
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
yep dude same here that sucks man it happened after i put a rom on too
I'm glad I'm not the only one.. this is probably the last htc I will get. I hear it is happening on the one x as well. Tomorrow I'll call T-Mobile and ask about it.
Sent from my HTC One S using xda app-developers app
Can you check under about -> phone and see if your imei matches whats on the box that came with the phone. If you do can you give me the first 4 or 5 digits
stratax said:
I'm glad I'm not the only one.. this is probably the last htc I will get. I hear it is happening on the one x as well. Tomorrow I'll call T-Mobile and ask about it.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
same here man this sucks now i have to start all over but i didnt get it from t mobile but i went in there to get a sim card to see if that was it and they said they cant do nothing so i guess we are suck with a $600 ipod touch with ICS lol
dc211 said:
Can you check under about -> phone and see if your imei matches whats on the box that came with the phone. If you do can you give me the first 4 or 5 digits
Click to expand...
Click to collapse
I don't have the box, and the sticker on the back is mostly worn since I used the phone for a while without the sim cover (I bought it new without it). but I just looked in my google dashboard, and typed *#06# and it matched and I can see the last three digits on the sticker clearly and they match with both as well. the first 5 digits are: 35990
thanks.
ragin69 said:
same here man this sucks now i have to start all over but i didnt get it from t mobile but i went in there to get a sim card to see if that was it and they said they cant do nothing so i guess we are suck with a $600 ipod touch with ICS lol
Click to expand...
Click to collapse
I didn't get it from tmobile either, I bought it new from somebody. had the stickers and everything on it. I swear, every HTC phone I have ever had, has had at least 1 major issue. well, the g1 didn't.
edit: even people on the one v are having the issues:http://forum.xda-developers.com/showthread.php?t=1679461 serious HTC wtf
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.