Related
HI everyone. i have started this thread as i didnt know what to do when i first had to send my wildfire back for repairs. first download the attatched zip. unzip to desktop and make sure u have got the drivers for your bootloader interface already installed. to do this you will need just two things. the zip you have just downloaded and the HBOOT which i included inside the ziped file. once extracted run the java file named S-ON.jar and plug your phone in and turn on fastboot. once connected make sure you click on check connection. once you have done that you should see your serial number appear. okay your ready to go. look for the first tab and click on it. then click on HBOOT/SPL. locate the HBOOT file you inzipped with the S-ON tool and then click it. once done just click on flash HBOOT/SPL. once done you will see it says FLASH HBOOT/SPL/SUCCESS. thanks for takuing time to look at my GUIDE and i hope it helps you. just remember one thing only flash the new HBOOT after you have installed the RUU which is android 2.1 update 1 so you can root again.
thanks for posting this, gonna try it now since I have to send my wildfire in for repair..
no problem if you have any trouble let me know and ill help you gain s-on
Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular
kaefert said:
Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular
Click to expand...
Click to collapse
this will not work with xtc clip i have 1 other way tho. please try this.
go into you start menu click RUN the type cmd in the dialog box. when you have the cmd up type C:\fastboot>fastboot oem mb 9C068490 1 30 then it will say okay. then open the s-on tool then try to flash the HBOOT. let me know if you have anymore problems. but this way shud work for you
they will not accept it as they just have to go into the HBOOT menu and they will be able to see it is s-off. and they will send it back as it is and wont carrie out any sort of repairs on it as you have hacked the phone and comprimised the security software
hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed
kaefert said:
hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed
Click to expand...
Click to collapse
okay no worries. if they wont repair it. then get back to me and ill cook somthing up and get you back to s-on. this is the trouble when gaining s-off with a xtc clip. its a pain to get back to s-on again lol but good luck anyways
Thanks for the moral support, I hope they will repair it...
Well back then I had no chance, my Wildfire was delivered to me with hboot 1.01.001 back in the time where there was no software S-OFF method for 1.01.001 and up, so I found myself a shop that had an XTC-Clip and invested 10€ on him
Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again
kaefert said:
Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again
Click to expand...
Click to collapse
Great news for you mate im glad they sorted it out for you. and your very lucky as they sent mine back twice for being s-off lol.
lol, where are you from? and where did they send your device? Im from austria and they sent my device to slovakia and they gave me a slovenian report of what they did so I had to use google translate to understand it
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
schnidex said:
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
Click to expand...
Click to collapse
Go to shippedroms and download the RUU for your phone. Although why you'd want to return to stock is beyond me?
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
schnidex said:
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
Click to expand...
Click to collapse
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
olyloh6696 said:
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
Click to expand...
Click to collapse
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
kartkk said:
do a nandroid backup & also set up your adb beforehand
setting up adb saved me from possibly bricking my device a few times
try this guide
Click to expand...
Click to collapse
ben_pyett said:
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
Click to expand...
Click to collapse
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Sent from my HTC Desire S using XDA Premium App
olyloh6696 said:
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Click to expand...
Click to collapse
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
ben_pyett said:
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
Click to expand...
Click to collapse
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
olyloh6696 said:
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
Click to expand...
Click to collapse
If the ruu runs successfully to competition I believe that it will return the device do that it's identical to stock
Swyped from HTC Desire S using XDA Premium
After many, many hours of trying to figure out what the hell half the terminology about Android actually means and wondering whether or not I would brick my phone..
..I'm now back to S-ON. It's been a pretty horrible experience all in all. Yes, it's easy when you know how but knowing how has been through trial and fortunately not much error.
From being on 6.98.1002, I used the Jorgen method in Ben's link above to get to 0.98.0000. I should note that when my phone was first supplied, I was on 0.98.0002 and very worried that the earlier software wouldn't work - but I tried it anyway, and it did. However, I was still S-OFF.
I then re-installed my stock network ROM using the RUU. This kept me on 0.98.0000 but put the phone to S-ON. I flashed the branded ROM that the phone was shipped with thinking that this would take me to 0.98.0002 but to my surprise it didn't. Otherwise though, the phone is now stock condition again.
So I then tried to update OTA to the problematic software which caused me all this grief in the first place - and it appears my network have withdrawn it. And rightly so, pending a fix.
schnidex said:
Ben, I've seen elsewhere you've said:
"If you load the latest RUU you may end up updating the HBOOT so that it can't be downgraded."
..in which case, Houston, we may have a problem. The latest HTC non-branded ROM (1.47...) gives you HBOOT 6.98.1002.
Click to expand...
Click to collapse
You're right, I'm afriad that this is an area where I'm no expert, But HBOOT = 6.98.1002. = Alpharevx = so you've not upgraded it simply failed to downgrade (which is slightly better- I think )
I notice that there are a couple of guides, allow I've obviously not tried either of them both are in the [GUIDE] A Complete Tutorial for the Beginners and Others sticky
The second guide looks quite complex and not for beginners...
Although I've just spotted a note within the second guide which says says
Note 2: RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs.
So Opps....a full nights sleep may shed some more light on this.....and hopefully so sound advice from someone who has already performed this task.
Good luck. (I'll back online in the morning) - but, only really able to answer easier questions and not unfortunately not provide you with a solution.....but I'll do what I can!
Alternate way to restore your phone to S-ON and stock
If your attempts are unsuccessful, there's another potential way to go S-ON.
http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2
Maarten
HI guys,
Had a quick search on my phone and couldn't find anything in this section, do forgive me if there's already a thread that explains this.
Basically, my phone keeps randomly rebooting, and sometimes only boots to them shut itself down again, no matter what rom, radio or hboot it's on, so I decided that I'm going to have to take it back to o2 as it's still under warranty.
The only problem is, I'm rooted and want to return to s-on. I've Google'd how to do this on the Sensation and found that you can do it via the ruu, but this can sometimes brick your device, is there any easy way to do this with clockwork installed etc?
If it helps, I'm running 4.03, latest radio and latest hboot, the baseband version states this: 11.76A_3504.00P.11.24A.3504.11_M
Thanks in advanced,
Dan
DanielF50 said:
HI guys,
Had a quick search on my phone and couldn't find anything in this section, do forgive me if there's already a thread that explains this.
Basically, my phone keeps randomly rebooting, and sometimes only boots to them shut itself down again, no matter what rom, radio or hboot it's on, so I decided that I'm going to have to take it back to o2 as it's still under warranty.
The only problem is, I'm rooted and want to return to s-on. I've Google'd how to do this on the Sensation and found that you can do it via the ruu, but this can sometimes brick your device, is there any easy way to do this with clockwork installed etc?
If it helps, I'm running 4.03, latest radio and latest hboot, the baseband version states this: 11.76A_3504.00P.11.24A.3504.11_M
Thanks in advanced,
Dan
Click to expand...
Click to collapse
Follow these steps:
1. Flash an RUU - It doesnt matter which one but I would recommend the latest 3.33.401.6 RUU - WARNING: THIS STEP MUST BE DONE, FAILURE TO DO THIS STEP WILL RESULT IN A BRICKED DEVICE!
2. Once the RUU has done its thing, boot into bootloader, connect to pc, go to fastboot usb mode and type the following command:
fastboot oem writesecureflag 3
All done
To add on the post above me, if the RUU.exe is unable to find your device, install the "Universal_Naked_Driver_0.7" drivers. Worked for me.
Jonny said:
Follow these steps:
1. Flash an RUU - It doesnt matter which one but I would recommend the latest 3.33.401.6 RUU - WARNING: THIS STEP MUST BE DONE, FAILURE TO DO THIS STEP WILL RESULT IN A BRICKED DEVICE!
2. Once the RUU has done its thing, boot into bootloader, connect to pc, go to fastboot usb mode and type the following command:
fastboot oem writesecureflag 3
All done
Click to expand...
Click to collapse
1.RUU corresponding to his device must be chosen for rma purposes.. Otherwise they won't accept it.. They will check the main-version too which varies for each RUU
Also running RUU as a exe ( not manually flashing) will never result in a brick.. In case something is failed.. It's completely reverted
DanielF50 find the exact RUU as per your Cid and mid
The below guide is the best one.. Which will help you in finding the right RUU and flashing instructions
http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
1.RUU corresponding to his device must be chosen for rma purposes.. Otherwise they won't accept it.. They will check the main-version too which varies for each RUU
Also running RUU as a exe ( not manually flashing) will never result in a brick.. In case something is failed.. It's completely reverted
DanielF50 find the exact RUU as per your Cid and mid
The below guide is the best one.. Which will help you in finding the right RUU and flashing instructions
http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I have the same problem, my phone keeps on rebooting every time. Where did you find the original HTC rom?
anielk77 said:
I have the same problem, my phone keeps on rebooting every time. Where did you find the original HTC rom?
Click to expand...
Click to collapse
where??
ive given a link already ..which will help you in finding the right RUU ..just read read read the guide
Hi guys, thanks for all the replies!
I flashed the RRU but flashed one of the latests ones, and now I can't root to restore my settings etc with Titanium Backup
Anyone know of a temporary root on 1.27, without having to use HTC dev, so that I don't void my warranty?
DanielF50 said:
Hi guys, thanks for all the replies!
I flashed the RRU but flashed one of the latests ones, and now I can't root to restore my settings etc with Titanium Backup
Anyone know of a temporary root on 1.27, without having to use HTC dev, so that I don't void my warranty?
Click to expand...
Click to collapse
arent you going to RMA it?
anyways if you are already SOFF ..you can use my one click root tool from my soff guide (link in my signature)
ganeshp said:
arent you going to RMA it?
anyways if you are already SOFF ..you can use my one click root tool from my soff guide (link in my signature)
Click to expand...
Click to collapse
I am, but I wanted to restore my settings so I can use it for a few days before I take it in, as work has got in the way lol.
I S-On'd after restoring the RUU as I didn't know revolutionary didn't work n 1.27, obviously not up to speed with this stuff anymore :silly:
DanielF50 said:
I am, but I wanted to restore my settings so I can use it for a few days before I take it in, as work has got in the way lol.
I S-On'd after restoring the RUU as I didn't know revolutionary didn't work n 1.27, obviously not up to speed with this stuff anymore :silly:
Click to expand...
Click to collapse
If SON Then rooting process is difficult. If you want to avoid htc-dev. As you need to soff again.. That too juopunutbear (wire trick)... You should have done SON just when you return the device..
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
If SON Then rooting process is difficult. If you want to avoid htc-dev. As you need to soff again.. That too juopunutbear (wire trick)... You should have done SON just when you return the device..
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I've tried the wire trick too, can't seem to get it to work, so completely given up, whenever the wire trick supposedly works my phone actually turns itself off
DanielF50 said:
I've tried the wire trick too, can't seem to get it to work, so completely given up, whenever the wire trick supposedly works my phone actually turns itself off
Click to expand...
Click to collapse
Wire trick for soff without htc-dev is but hard.. Check the troubleshoot point #3 for tips, tricks
Also the phone switching off means.. The pause you gave is too high..
Try this
0.5 sec tap - 1.5 sec pause - 0.5 sec tap
Sent from my pyramid.. Through blazing fast sonic waves
Thanks mate, got it rooted and s-off'd now
Any way to S-ON and Unroot again without wiping now!? lol.
Was thinking, flashing certain images through fastboot should do that shouldn't they?
hi all,
i HAD a sensation running Android Revolution HD 6.8.0. and without checking properly, i installed AOKP-42-20130118.zip and gapps-jb-20121212-signed.zip. the phone won't boot or charge. i then realised this is not a sensation rom, it's a HTC ONE rom, i think!! . i've followed the HTC Unbricking Project and get "device not found...check connections" in ubuntu. phone shows up on windows as other device labeled QHSUSB_DLOAD. is my phone toast? sorry if all this sounds amateurish as im completely new to all this. thanks all.
thats some dangerous thing happened there ..if HTC UNBRICKING not doing any help ..then service center only
Try flashing the official RUU suitable to your device. It may recover your device
Sent from my HTC Sensation using xda app-developers app
Alsager said:
Try flashing the official RUU suitable to your device. It may recover your device
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
cant seem to connect to device to flash anything. not looking good. any ideas?
Only service center :/
miticogirl said:
Only service center :/
Click to expand...
Click to collapse
thanks all for your help. it seems i live in a country where nobody can fix my phone. i've called nearly every service center in New Zealand. it may be my only option to send this phone to my brother in the USA and get it fixed there. can anyone recommend a repair center anywhere that can fix this? Thanks again.
bensod said:
thanks all for your help. it seems i live in a country where nobody can fix my phone. i've called nearly every service center in New Zealand. it may be my only option to send this phone to my brother in the USA and get it fixed there. can anyone recommend a repair center anywhere that can fix this? Thanks again.
Click to expand...
Click to collapse
have you:
1. installed the HTC drivers
2. put the device in "bootloader mode" when trying to flash the RUU,
3.uninstalled the HTC sync program,
4. used the original USB cable
sorry for very late response.
Alsager said:
have you:
1. installed the HTC drivers
2. put the device in "bootloader mode" when trying to flash the RUU,
3.uninstalled the HTC sync program,
4. used the original USB cable
sorry for very late response.
Click to expand...
Click to collapse
no worries, thanks for answering.
yes tried all of the above, several times. tried newest drivers, and 3.0.0.007, messed around with several usb cables, changed computers. device not found error every time. i think the phone is stuffed. will send it to mobiletechvideos in Texas. it's a 50 dollar repair. will be a bit more careful next time.
bensod said:
no worries, thanks for answering.
yes tried all of the above, several times. tried newest drivers, and 3.0.0.007, messed around with several usb cables, changed computers. device not found error every time. i think the phone is stuffed. will send it to mobiletechvideos in Texas. it's a 50 dollar repair. will be a bit more careful next time.
Click to expand...
Click to collapse
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
ganeshp said:
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
no, can not boot phone. phone is dead boot bricked.
found a place to fix it but it's not cheap. thanks all for your help.
ganeshp said:
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
hi, my phone has been recovered and back working. service centre returned the phone with locked bootloader, s-off and hboot 1.29.
i'd like to get back to Android Revolution HD 6.8.0, can i just root and flash a recovery, or have i to unlock the bootloader again on htv dev? can i use the backups i made earlier on hboot 1.27?
thanks again.
bensod said:
hi, my phone has been recovered and back working. service centre returned the phone with locked bootloader, s-off and hboot 1.29.
i'd like to get back to Android Revolution HD 6.8.0, can i just root and flash a recovery, or have i to unlock the bootloader again on htv dev? can i use the backups i made earlier on hboot 1.27?
thanks again.
Click to expand...
Click to collapse
you received the phone with LOCKED bootloader and SOFF ?
then before doing anything ..i would suggest you to ..check whether the phone is soff or not (I've seen 3 cases at-least where the phone showed soff (after the phone got back from service center) but its not actually soff and people bricked their phone again trying to flash stuff) ... to check soff status go to my soff guide (link in my signature)..try the controlbear soff NO HTC_DEV unlock one ..if the phone is properly soff then the controlbear says soff and exits ..otherwise your phone is not soff ..
also you cant do HTC-DEV unlock (motherboard got replaced so IMEI changed) as IMEI changed and the unlock procedure fails ..the only way is JB SOFF
ganeshp said:
you received the phone with LOCKED bootloader and SOFF ?
then before doing anything ..i would suggest you to ..check whether the phone is soff or not (I've seen 3 cases at-least where the phone showed soff (after the phone got back from service center) but its not actually soff and people bricked their phone again trying to flash stuff) ... to check soff status go to my soff guide (link in my signature)..try the controlbear soff NO HTC_DEV unlock one ..if the phone is properly soff then the controlbear says soff and exits ..otherwise your phone is not soff ..
also you cant do HTC-DEV unlock (motherboard got replaced so IMEI changed) as IMEI changed and the unlock procedure fails ..the only way is JB SOFF
Click to expand...
Click to collapse
hi again, thanks for the heads up. i've run controlbear and confirmed the phone is s-off. during the process it asked to install modified juopunutbear hboot, which i said no. should i have? also phone imei is same as before (no motherboard replacement) so whats my next move, i'm a little cautious as I've bricked phone already once!! thanks ganeshp.
bensod said:
hi again, thanks for the heads up. i've run controlbear and confirmed the phone is s-off. during the process it asked to install modified juopunutbear hboot, which i said no. should i have? also phone imei is same as before (no motherboard replacement) so whats my next move, i'm a little cautious as I've bricked phone already once!! thanks ganeshp.
Click to expand...
Click to collapse
yes install juopunutbear hboot via controlbear and if that didnt went successfully ..install patched revoultionary hboot (at the end of first post i think) from kohr-ah firmware thread present in sensation development section.
then you cna continue with custom recovery flashing and then custom rom (if you want you can backup your current stock rom too from the custom recovery before trying the new rom )
ganeshp said:
yes install juopunutbear hboot via controlbear and if that didnt went successfully ..install patched revoultionary hboot (at the end of first post i think) from kohr-ah firmware thread present in sensation development section.
then you cna continue with custom recovery flashing and then custom rom (if you want you can backup your current stock rom too from the custom recovery before trying the new rom )
Click to expand...
Click to collapse
hey thanks for all your help. i'm back to where i was before all the drama. one last thing, is there a rom out there that's pure android? no sense? one you would recommend? thanks again for your help.
bensod said:
hey thanks for all your help. i'm back to where i was before all the drama. one last thing, is there a rom out there that's pure android? no sense? one you would recommend? thanks again for your help.
Click to expand...
Click to collapse
cm 10.1 of albioman ?
the latest one is pretty stable
ok like the title says ive been messing with this thing for a week now and im getting to the point im about to smash it with a hammer
its stuck in a boot loop and i have no backup to load apparently. it was rooted when i got it and my roomate messed it up while i was at work im not sure how or what was done but no matter what i try to do i cant get it out of this loop. im not familiar with android at all ive been reading and searching but i cant find anything helpful ive tried to ruu a few times not really knowing which files to use i finally found out that the radio needed to be the same found a matching file but still no luck i know im gonna get flamed for being so uneducated in this matter but i have indeed searched and i feel im left with no other option then to ask for assistance here
i can get to the boot loader and im just going to type down exactly what i see on it although i dont really know what any of it means
***tampered***
***unlocked***
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1..0.45.0622
emmc-boot
jun 11 2012,14:36:28
fastboot usb
vol up
vol down
power
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
im in need of a thourough stepo by step instruction on how to fix this thing i dont care if its by means of a custom rom stock rom whatevers easiest. i know how to utilize fastboot with instruction and ive changed back and forth between cwm and twrp but no matter how many tuts i follow i always end up in a loop and im not sure why again i apologize for being such a noob but ive come to realize that this forum is the best at fixing stupid problems like mine fairly quickly
thanks in advance for your help....
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Edit: Also, I'm assuming you have no knowledge of adb and fastboot commands? Because you might need to learn. And did you try this ruu? It's for your firmware version. http://forum.xda-developers.com/showthread.php?t=1814217
RollTribe said:
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Click to expand...
Click to collapse
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
frankthebunny said:
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
Click to expand...
Click to collapse
frankthebunny said:
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
Click to expand...
Click to collapse
Alright, so I'm assuming the problem is there is no ROM on the phone or someone did factory reset in bootloader. So if the ruu helps, great (it should). If not, then I'm sure we'll figure it out.
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
frankthebunny said:
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
Click to expand...
Click to collapse
Yup. Since you're on an older hboot there's no preparation needed. I'm assuming you don't really want to get into all this rooting stuff and just want a working phone? If you want help with rooting, come back here when the ruu is done, but if you like it stock, then you should be good to go :beer:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
actually i would like to root it after i get it all fixed and put a custom rom on it and what not. like i said earlier i can follow instructions this was just a difficult spot to start from ya know.
twistedddx said:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
right on ill do that. is there anything else i should be downloding now to prepare for what ever it is i need to do to protect my phone from messing up again?
exad said:
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
Click to expand...
Click to collapse
yeah it is an at&t phone. at least it says on the top of it however im using straight talk t-mobile i believe.
will i need to root it again in order to utilize the t-mobile carrier?
No need to root for your carrier.
But you will need to root again to install other roms.
So is this phone back up and running again yet?
Sent from my HTC One XL using xda app-developers app
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
frankthebunny said:
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
Click to expand...
Click to collapse
What ruu?
Did you relock the bootloader?
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
heres the name of the file
htc_one_x_RUU_2.20.502.7_att_us_08022012
frankthebunny said:
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
Click to expand...
Click to collapse
First do :
fastboot oem readcid and tell me what it says
if it's CWS__001 then do:
fastboot oem lock
And chill, your phone will work when I'm done with you.
it say
cid: 11111111
frankthebunny said:
it say
cid: 11111111
Click to expand...
Click to collapse
ok hopefully since it didn't say CWS__001 you didn't use the lock command.
do:
fastboot oem writecid CWS__001 (be sure to note there are two "_")
then do
fastboot oem readcid
It should now say CWS__001
please confirm
nice ok ive changed it now to CWS__001