Related
Well I decided to jump the hoop and go for rooting my mt4g slide. Was doing great and unlocked it using the lovely All-In-One tool kit and couldn't get the phone to show S-off. I figured I needed to get this done before installing a rom's as I tried 2 different ones and neither would work. Tried a few different things and still wouldn't work to get S-off. Long story short, now I'm in a boot loop where the phone automatically goes into the boot loader. It will start up and show the mytouch splash screen before going into the loader. It will scan the sdcard for files and say there isn't a image etc and go back to the main boot loader screen. I can't do anything beyond that. I hit recovery, factory reset, and nothing. Tried putting roms and see if it would out of the blue read one.
It's my fault for taking the risk but adding a bit of insult to my injury is my back up phone, G1, won't even turn on now. So now I'm kind of phone less. Any suggestions on how to restore hboot?
1st of all WRONG FORUM!!!!!! This is for Development, not questions. That's what general is for. Second, there's a couple threads in General about this. Just hit search.
Magical Mods, may we please have this moved. Thanks.
Sent from my MIUI V4
take out your sdcard and use an adapter to put a stock PG59IMG.zip on your sdcard (make sure its named PG59IMG.zip) and go back into the bootloader. It will confirm if you want to install the zip and in 10 mins you'll be back on stock. Oh and ^ plus one please next time post in general as this has nothing to do with developing.
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
Thread reported just for the use of "take a chill pill."
blackknightavalon said:
Thread reported just for the use of "take a chill pill."
Click to expand...
Click to collapse
Yes, the correct terminology is 'Take a chill pill, Bill.
Can't get chill without the Bill.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
Sorry I wasn't "helpful". I'll do better to assist you next time....or just ignore it
I can't help you and I expect you to get a satisfactory answer.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
XMC, a Dev. He helped you, we where all noobs once. You should check out the "Welcome to XDA Video". Just follow the Rules. That's all, follow the rules.
Sent from my MIUI V4
To supplement what Agent said the appropriate section for this would be the General section.
Additionally the development area is where devs post new roms, tools and hacks. Users can add observations to these threads to further development.
Hastily spouted for your befuddlement
fsured said:
Well I decided to jump the hoop and go for rooting my mt4g slide. Was doing great and unlocked it using the lovely All-In-One tool kit and couldn't get the phone to show S-off. I figured I needed to get this done before installing a rom's as I tried 2 different ones and neither would work. Tried a few different things and still wouldn't work to get S-off. Long story short, now I'm in a boot loop where the phone automatically goes into the boot loader. It will start up and show the mytouch splash screen before going into the loader. It will scan the sdcard for files and say there isn't a image etc and go back to the main boot loader screen. I can't do anything beyond that. I hit recovery, factory reset, and nothing. Tried putting roms and see if it would out of the blue read one.
It's my fault for taking the risk but adding a bit of insult to my injury is my back up phone, G1, won't even turn on now. So now I'm kind of phone less. Any suggestions on how to restore hboot?
Click to expand...
Click to collapse
"tried a few different things" to get S-Off?
There are two ways of getting S-off. One is done with Revolution if your HBOOT is earlier than 1.45. The other is juopunutbear if your HBOOT is 1.45. Did you check your HBOOT version before "trying a few things"?
Did you read the instructions for the all-in-one toolkit? Or possibly just follow the steps in order in the program? It's specifically designed so you don't need s-off.
I'm assuming you must have flashed CWM recovery since you said you did a factory reset. Did you do Juopunutbear or revolution, or are you planning on leaving S-ON? If S-ON, Did you flash a kernel(boot.img) using the toolkit? If you can get into HBOOT and get into recovery, there's no reason you should need to revert to stock. However, if your plan is to continue doing steps before reading the instructions, you should probably revert to stock anyway before you really do brick your device.
This link will provide you everything you need to get your device running. Just follow the spteps from the beginning. If your bootloader is already unlocked from HTCDev, then start at the step directly after unlocking the bootloader.
http://forum.xda-developers.com/showthread.php?t=1532809
The toolkit worked well for me (even though it was my first attempt at anything), so I guess I'd echo that. It also matched with the step-by-step guides on stuff I found elsewhere in the forum. BUT there is a real difference in the method and order of things for the two hboots, hence KarriOn's questions.
However, having rooted and S-Offed, I then got a bit cocky and managed to end up in a not dissimilar position to you! Total panic, but I managed to get out by thinking through what I'd done, researching, and the cause and hence solution became clear. Took a night sleeping on it, and 2 hours.
what HBOOT?
Did you unlock the boot loader?
Did you get recovery on
Did you do a backup before going any further?
Sent from my myTouch_4G_Slide using xda premium
I followed the all in one tool for everything. I've finally been able to get into cwm recovery. For awhile it wouldn't and I gave up for the night. Came back yesterday morning to tinker with it more and it worked. I've tried flashing the superSu.zip file in cwm and after it reboots it still reads s-on. But either way I can't get the phone to do anything other than boot into the bootloader screen. I'm going to check out the link about 2 posts up and tinker with it after work. Thanks for the replies!
http://forum.xda-developers.com/showthread.php?t=1532809[/QUOTE]
Oh yeah, that is the tread I used and the tool. After getting unlocked from HTC I tried flashing a rom and it wouldn't work. Figured I needed to get s-off for roms also. That is where my error started.
fsured said:
http://forum.xda-developers.com/showthread.php?t=1532809
Oh yeah, that is the tread I used and the tool. After getting unlocked from HTC I tried flashing a rom and it wouldn't work. Figured I needed to get s-off for roms also. That is where my error started.
Click to expand...
Click to collapse
You don't need S-Off for ROMs to work. It sounds like you didn't flash a kernel after installing a ROM. The instructions on doing this are listed in the all-in one tool thread, the "flash ics roms with s-on" thread, and even on the all-in one tool interface itself.
fsured said:
I followed the all in one tool for everything. I've finally been able to get into cwm recovery. For awhile it wouldn't and I gave up for the night. Came back yesterday morning to tinker with it more and it worked. I've tried flashing the superSu.zip file in cwm and after it reboots it still reads s-on. But either way I can't get the phone to do anything other than boot into the bootloader screen. I'm going to check out the link about 2 posts up and tinker with it after work. Thanks for the replies!
Click to expand...
Click to collapse
Flashing SuperUser won't get you to S-Off. Hasoon2000 has two different toolkits. One that will guide you through the rooting process and the other on how to gain S-Off using the Juopunutbear method. Having S-Off isn't necessary to root but it will take a few extra steps to flash a different ROM with S-ON. I was too much of a chicken to try the S-Off method since there is some risk involved but several have reported that it worked successfully for them.
First of all, sorry if I'm just being stupid and daft, but I've been reading here for the past two days now and either I'm missing something crucial here or maybe it just can't work for some reason (and believe me: being stupid myself is far preferable to the alternative).
So I own a Desire S as you may have guessed, and hey it was even rooted. Had a nice Android 2.3.5 with HTC Sence 3 on it. So ignoring my own best advice (never change a running system) I decided to try the new HTC ICS update. After being quite unsuccessful for almost two days because the HTC Update Utility stubbornly refused to update with an Error 155 message - informing me that I was using the wrong utility - today's breakthrough made me realise I had no choice but to use the HTCdev to relock my phone. Before that of course I had made a backup of the whole system via 4EXT and via Titanium Backup. So all my stuff is safe and sound on my SD-Card. So the update went well today and my Desire S now has Android 4.0.4 and Sense 3.6, hurray.
Now I first used the HTCDev tool to unlock the bootloader - worked like charm, and then tried to S-Off and root my phone again and install a Recovery tool and thus get my contacts and all the other stuff back. BUT here I encountered minor difficulties since Revolutionary tells me my phone (HBoot 2.02.0002) is not supported (?!). Consequently Gingerbreak or SuperOneClick are useless to me. So now I got a working blank phone with a beautiful new UI but with no contacts, calendar and apps.
Could anyone please point me in the right direction and tell me what I'm doing wrong? Is there another way to get S-OFF? My phone had the same HBoot Version prior to the update, why was it no problem to S-OFF and root it then? Am I just to tired to see and obvious solution? Do I have to downgrade before I can update?
If you got this far reading my rambling, I hope it made some sense to you and I'd like to thank you for your patience and of course for your help in advance.
Best regards
Archer
Archer74 said:
...
Click to expand...
Click to collapse
tl;dr ... but I read enough of it. Read the stickies. Read the recent threads concerning the ICS ROM. All the answers are already there - you've been a member of the forum for long enough to know how it works.
SimonTS said:
tl;dr ... but I read enough of it. Read the stickies. Read the recent threads concerning the ICS ROM. All the answers are already there - you've been a member of the forum for long enough to know how it works.
Click to expand...
Click to collapse
Yeah ... I know why you feel that way. I've been around in several other forums and simply got crazy because people always asked the same bloody questions. Thanks for keeping me motivated to continue searching
Believe me if I HADN'T been sitting in front of the damn screen for that long without success I wouldn't have asked. But to be honest: I simply can't find the solution. I'm rather sure it might be quite easy and must've overlooked it before, but ... well ... needle and haystack ... forest and trees ... you get my drift ... Well, I guess I'd better go to bed. It's past midnight, and just maybe there'll be some kind of divine intervention in my sleep In any case tomorrow I might be more awake.
Thanks and good night.
Archer
As you're now S-Off, install 4Ext recovery via ADB then flash superuser. If you need precise steps they are detailed clearly in many of the other threads.
Archer74 said:
So now I got a working blank phone with a beautiful new UI but with no contacts, calendar and apps.
Click to expand...
Click to collapse
a bit out of topic:
for your contacts and calendars, why don't you just sign in to your google account and you'll get them back in no time... i never restore my google contacts and calendars with titanium, don't want to mess with google sync.
SimonTS said:
As you're now S-Off, install 4Ext recovery via ADB then flash superuser. If you need precise steps they are detailed clearly in many of the other threads.
Click to expand...
Click to collapse
Well strictly speaking I'm not S-OFF, only the bootloader is unlocked. And that was bugging me all the time. But your're right: today I re-read the second guide thread above and found what I was searching:
How to: Root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
http://forum.xda-developers.com/showthread.php?t=1525100
There I found out, that with this HBoot version I did not have to S-OFF the phone but could install Recovery only with the bootloader unlocked.
toxic-hero said:
a bit out of topic:
for your contacts and calendars, why don't you just sign in to your google account and you'll get them back in no time... i never restore my google contacts and calendars with titanium, don't want to mess with google sync.
Click to expand...
Click to collapse
I use Google Calendar only for my work phone, and see no reason to upload all private stuff to the internet. We're all doing too much of that already anyway. But yeah that would work too. Thx
Ok before I get skewered by the tenured members of this esteemed site, I just wanted to say that I did my research as many of you suggested, and I feel like I've read every thread about the following topic to no avail, my phone is in the same state, I digress;
Like many on here before me, I have been handed the "white screen of death" on my HTC Inspire 4G. Some call it a soft brick, even though that's a frowned upon term. Either way, I have it and I'd really like to get rid of it. I can access my Hboot no problem, my phone is S-OFF, so that's not an issue. I tried running an RUU on here to update the image, but when it rebooted, the HTC white screen of death reappeared. Tried running the PD98IMG.ZIP image and reflashing a custom pre-rooted stock rom, didn't work.
Threads I've tried:
http://forum.xda-developers.com/showthread.php?t=1286832
http://forum.xda-developers.com/showthread.php?t=1390677
http://forum.xda-developers.com/showthread.php?t=1396229
These were the three that ware most similar to the problem I had I felt like, yet neither had the solution I was looking for. Clearly, the phone isn't bricked since I can get into the HBoot, but besides that, I'm stuck. For all I know, I'm a complete idiot and missing a vital step, but I'm almost at my wits end and I really just need my smartphone back. Any assistance, regardless of how condescending it may be, will be received with immense gratification if it indeed helps my problem. Thank you, and please help me .
And little more info, please. Can you get into recovery from hboot? If so, is it a stock or custom recovery? What version of hboot are you running?
This thread will probably be moved to Q&A. Stick with it and we will try to help.
Sent using the power of the dark side.
fballplyr92 said:
Ok before I get skewered by the tenured members of this esteemed site, I just wanted to say that I did my research as many of you suggested, and I feel like I've read every thread about the following topic to no avail, my phone is in the same state, I digress;
Like many on here before me, I have been handed the "white screen of death" on my HTC Inspire 4G. Some call it a soft brick, even though that's a frowned upon term. Either way, I have it and I'd really like to get rid of it. I can access my Hboot no problem, my phone is S-OFF, so that's not an issue. I tried running an RUU on here to update the image, but when it rebooted, the HTC white screen of death reappeared. Tried running the PD98IMG.ZIP image and reflashing a custom pre-rooted stock rom, didn't work.
Threads I've tried:
http://forum.xda-developers.com/showthread.php?t=1286832
http://forum.xda-developers.com/showthread.php?t=1390677
http://forum.xda-developers.com/showthread.php?t=1396229
These were the three that ware most similar to the problem I had I felt like, yet neither had the solution I was looking for. Clearly, the phone isn't bricked since I can get into the HBoot, but besides that, I'm stuck. For all I know, I'm a complete idiot and missing a vital step, but I'm almost at my wits end and I really just need my smartphone back. Any assistance, regardless of how condescending it may be, will be received with immense gratification if it indeed helps my problem. Thank you, and please help me .
Click to expand...
Click to collapse
Can you get into recovery? If not, follow the Ace Think Tank guide on post #7 starting on the bottom of page 9, the section "S-OFF no recovery," to get a recovery back; then use that recovery to flash a ROM. If so, just flash a ROM from recovery.
bananagranola said:
Can you get into recovery? If not, follow the Ace Think Tank guide on post #7 starting on the bottom of page 9, the section S-OFF no recovery, to get a recovery back; then use that recovery to flash a ROM. If so, just flash a ROM from recovery.
Click to expand...
Click to collapse
This
Sent from my Inspire 4G using xda premium
Please post all questions in the Q & A section. Thanks. Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
I tried an S-off as per the procedure everything went well
Supercid 11111111
and Finally A bootloader with S-Off
but when The device booted,it showed the home screen with the unlock screen and as soon as the screen unlocks its gives and error "Process system failed" (somethng almost similar) and gave an option to wait or close the program, choosing either of the two would result in a continuous bootloop
Attempts Made So far
-reflashed the kernals,ROMs, with Factory reset, Wipes Via fastboot commands
-Did A factory reset from Bootloader to clear all the Corrupt files
-Re-locked the bootloader to Install a fresh RUU
Attempted the S-Off from Win8 PC, but later RUUs were also tried Via Win7
Thannks to beaups and jcase so far for all the Help, Appreciated:good:
All the above steps couldnt bring back the cell to normal.Therefore,would Appreciate any help
#Latest attempt was Installing a Recovery via fastboot, it showed 'failed" Error
Thank You
Don't factory reset from bootloader, that corrupts the SD card. Have you tried flashing stock recovery? If your SD card is corrupted, that's the only way to fix it. Also, keep in mind next time that you should post questions in Q&A, people tend to get a little upset when they show up here.
C'mon man, wrong section.... Use Q&A.... :facepalm:
trathiang said:
Don't factory reset from bootloader, that corrupts the SD card. Have you tried flashing stock recovery? If your SD card is corrupted, that's the only way to fix it. Also, keep in mind next time that you should post questions in Q&A, people tend to get a little upset when they show up here.
Click to expand...
Click to collapse
You shouldnt help people that dont follow rules. I have already reported this post. Reasons like this I just want to kill a kitten.
droidkevlar said:
You shouldnt help people that dont follow rules. I have already reported this post. Reasons like this I just want to kill a kitten.
Click to expand...
Click to collapse
but.. I like kittens
Sent from my One S using xda premium
rufh_s said:
I tried an S-off as per the procedure everything went well
Supercid 11111111
and Finally A bootloader with S-Off
but when The device booted,it showed the home screen with the unlock screen and as soon as the screen unlocks its gives and error "Process system failed" (somethng almost similar) and gave an option to wait or close the program, choosing either of the two would result in a continuous bootloop...
...Error
Thank You
Click to expand...
Click to collapse
You obtained S-Off but corrupted phone's internal card b/c perhaps you did not wait enough time when did the last step (adb shell su -c "/data/local/tmp/soffbin3" before reboot) when did S-Off.
1. Now, Re-lock your bootloader and then reboot into RUU flash mode: fastboot oem rebootRUU
2. Flash either HTC RUU or OTA Update from here
3. Reboot - you will have stock ROM
4. Now unlock bootloader, flash custom recovery, root, do backup, (you still have Super CID) and then do S-Off (if you really need)
P.S. Q should be in General Thread
droidkevlar said:
kill a kitten.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=uvqJ1mTkEuY
To be fair, if he hadn't posted in QA, he probably wouldn't have got the response. All the good people are here. QA is mostly full of 'how to I get into my bootloader' crowd.
(I follow the rules though )
ipit said:
To be fair, if he hadn't posted in QA, he probably wouldn't have got the response. All the good people are here. QA is mostly full of 'how to I get into my bootloader' crowd.
(I follow the rules though )
Click to expand...
Click to collapse
My thoughts exactly. If you want less Q&A posts here, go to Q&A and help some noobs out.
dr_rick13 said:
but.. I like kittens
Sent from my One S using xda premium
Click to expand...
Click to collapse
Lmao...
WOW look at this right in developing (shakes head) always try q&a first if a few days go by and no response then maybe try in the rom but don't start a question here.
P. S. Next time you loop your phone Google it first then read till your blue in the face if no luck that way then come here, please.
Sent from my HTC one s running rootbox 4.2.2 unofficial, bubba kernel v3.5 fix oc using XDA app
good to see the noobs are the harshest critics.
#iamatroll
Sent from my HTC One S using xda app-developers app
droidkevlar said:
You shouldnt help people that dont follow rules. I have already reported this post. Reasons like this I just want to kill a kitten.
Click to expand...
Click to collapse
Em why not? So what its in the wrong section its a bit late to ***** about it so why not help and just let him know he did wrong like trathiang did and he only has 17 posts so shame on you.
I've factory reset from bootloader and stepped on other land mines as well. Don't worry, as long as you don't mess up your bootloader I think it is pretty hard to brick this phone.
I would suggest you flash TWRP recovery if you don't already use that, wipe everything including internal SD card, mount it and copy over the ROM and flash it again. Maybe it's something wrong with the ROM you are using?! Perhaps try a different one and of course make sure it's for an HTC One S (ville) phone.
If you try mount the internal SDcard and Winbloz says the sdcard needs to be formatted then do that using all defaults (fat32).
mustardman29 said:
I've factory reset from bootloader and stepped on other land mines as well. Don't worry, as long as you don't mess up your bootloader I think it is pretty hard to brick this phone.
I would suggest you flash TWRP recovery if you don't already use that, wipe everything including internal SD card, mount it and copy over the ROM and flash it again. Maybe it's something wrong with the ROM you are using?! Perhaps try a different one and of course make sure it's for an HTC One S (ville) phone.
If you try mount the internal SDcard and Winbloz says the sdcard needs to be formatted then do that using all defaults (fat32).
Click to expand...
Click to collapse
I apologize for posting in the wrong section, but in the past had an experience that my questions remained un-answered in Q &A Section so had to post it here to attract the best minds to comment
As far as i remember there was no issues with S-Off.. as i waited for some time then did an Adb reboot and later it showed S-Off in Bootloader
I also Googled alot before posting it here .. In case Someone missed out the procedures i followed to get it back, its a long list of tries
I Already tried the RUU process ( will give it one more try now)
I also tried with different ROMs but the same issue
Sorry for the wrong section
rufh_s said:
I apologize for posting in the wrong section, but in the past had an experience that my questions remained un-answered in Q &A Section so had to post it here to attract the best minds to comment
As far as i remember there was no issues with S-Off.. as i waited for some time then did an Adb reboot and later it showed S-Off in Bootloader
I also Googled alot before posting it here .. In case Someone missed out the procedures i followed to get it back, its a long list of tries
I Already tried the RUU process ( will give it one more try now)
I also tried with different ROMs but the same issue
Sorry for the wrong section
Click to expand...
Click to collapse
Which RUU are you trying? If it's 2.35, try something older, like 1.84. I could never get 2.35 to work.
Darknites said:
Em why not? So what its in the wrong section its a bit late to ***** about it so why not help and just let him know he did wrong like trathiang did and he only has 17 posts so shame on you.
Click to expand...
Click to collapse
why not? i guess rules arent needed, r they? he isnt the first, and wont be the last, but there is a reason for rules. if ppl continue to help them, they wont listen to the rules and continue to post in the wrong sections and clog up dev and general with crap. i help on here and irc and been around for quiet some time. tired of ppl just feeling entitled. i always check in q&a as i try to help when i can. but when ppl refuse to follow the rules, i will not help and will report the post.
droidkevlar said:
why not? i guess rules arent needed, r they? he isnt the first, and wont be the last, but there is a reason for rules. if ppl continue to help them, they wont listen to the rules and continue to post in the wrong sections and clog up dev and general with crap. i help on here and irc and been around for quiet some time. tired of ppl just feeling entitled. i always check in q&a as i try to help when i can. but when ppl refuse to follow the rules, i will not help and will report the post.
Click to expand...
Click to collapse
The way I see it, this guy is not asking how to change his wallpaper or install a Hello Kitty theme. His phone won't boot. The night I got my phone, I did a factory reset from the bootloader and spent 4 hours having a panic attack trying to fix it. It's a ****ty feeling, we've all been there, and when we were there, all we wanted was to figure out how to save our phones. Helping people while reminding them to post in the right section will make people have a more positive experience with xda. Telling them wrong section and refusing to answer them is petty and alienating.
The way I see it, this guy is not asking how to change his wallpaper or install a Hello Kitty theme. His phone won't boot. The night I got my phone, I did a factory reset from the bootloader and spent 4 hours having a panic attack trying to fix it. It's a ****ty feeling, we've all been there, and when we were there, all we wanted was to figure out how to save our phones. Helping people while reminding them to post in the right section will make people have a more positive experience with xda. Telling them wrong section and refusing to answer them is petty and alienating.
Click to expand...
Click to collapse
Thank you for the Support, believe that's the same feeling I am going through, I would Generally follow All the Rules, this time had to take different path as it was a bit severe
Which RUU are you trying? If it's 2.35, try something older, like 1.84. I could never get 2.35 to work.
Click to expand...
Click to collapse
I did a 2.35, Ill go for something else now, As I am Using a US t-mobile, but I am from India, will the country specific RUU matter? like can I us Europe's version as well?
Downloading 1.84 now, will get back as soon as its done
I have scoured the internet for a solution, but my phone is from Hell. Every single thing I have ever done has ended in errors, ranging from trying to flash the rom zip and getting a "data length is too large" to errors while my phone did still have an OS and flashing through fastboot or double clicking in an exe would give me errors regarding the version or whatever other bs. I have been actively trying to fix this phone for well over a year! When I first started, it was still under warranty, and now it's just a paperweight that continues to waste days of my time at a time.
I am by no means a noob to electronics, but it seems I must be missing something I didn't learn, as I must be a noob in rooting/unrooting/flashing phones. I hope to God nobody suggests that I should have posted this in another thread, as I have searched all similar threads (all over the internet, different phones, any website that Google could find) and tried every single method anybody suggested. Most methods would be completely useless as I wouldn't meet the prerequisites, but I tried even those methods once I exhausted all serious methods.
I have officially gone mad and am about to say goodbye to all technology and go live in a Amish community for the rest of my life. I became so desperate and crazy that I managed to mess up my phone further than it was to begin with. PLEASE HELP! I am at your humble service, and I await any and all instruction.
A little background:
I got the phone from a family member once they cracked their screen, as I am much more of a hardware techie and I got the phone as a present to fix and use for myself. My family member is trigger happy and likes to root everything he could get his hands on. I am much happier with the stock versions of things as they give the best performance for my needs, not to mention the much less hassles and headaches with updates and reception and so on and so forth. I got the phone when it had 1.73.502.1 software on it. I wanted to upgrade to the 3.18.502.6 software version that was available, unroot the phone, and take everything back to dead stock. Since then, 5.18.502.1 has become available. (Side story about this: when double clicking the 5.18.502.6 RUU exe to go into my temp folder and extract the ROM zip, this version doesn't execute for some reason when downloaded from the "HTC OTA and RUU collection" thread (http://forum.xda-developers.com/showthread.php?t=2119610), and the previous version mentioned does execute and show up in my temp folder in Windows, but there are two roms (rom 1 and rom 2), and when extracting them, I get errors, so I had to download and extract 2.20.502.7, which executed and extracted without any problems)). I tried unlocking the bootloader through HTC's website (yes, I believe I relocked it about a year ago in a stupid move because I read that in order to execute an RUU you have to be relocked), but I guess AT&T is a big douche, so I had to superCID (cid 11111111) before doing so, but simply doing "fastboot oem writecid 11111111" wouldn't work, so I literally tried a million different tools I found until magically (literally, I don't know what happened or what I did), I got to superCID, in which case I unlocked with no problem. I then tried every method possible of updating, flashing, everything, but when things got to the actual rom zip part or executing RUU or basically the last steps, I would always be presented with errors and fails. In an angry move, I went to TWRP and erased everything I could get my hands on (I know, I messed up, kill me), and so I deleted the OS and whatever else was on the phone. Since then, I also managed to relock the bootloader (which I locked and unlocked multiple times with no problem and had the unlock code, so I figured I'm safe forever), and take my CID back to cws__001 (which I thought might be the cause of all of my errors, but found that now I can no longer unlock my bootloader).....
I now have an HTC One X from AT&T that is relocked, CID is cws__001,stock recovery, no operating system to boot into adb, and not able to flash anything on it to get into TWRP at least to try and adb sideload or some other things to take back the screw-ups I did since last night.
Info on bootloader:
TAMPERED
RELOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Nov 26 2012, 18:37:14:-1
I apologize beforehand for even touching the phone's software and trying to mess with it and maybe learn a thing or two in the process. Again, I thank you greatly beforehand for all your input, and I hope to hear back soon!
Erik
You can run the 3.18 att ruu to fix the phone to the point of it booting. If you want to learn a few things (such as custom ROMs and the like) you can visit threads on how to root, unlock the bootloader, get supercid, and then s-off.
Sent from my One XL using XDA Premium 4 mobile app
Thanks for the prompt response
I tried what you suggested just now (downloaded the 3.18.502.6 RUU exe from the thread http://forum.xda-developers.com/showthread.php?t=2119610, went into fastboot, right-clicked the exe and chose to run as administrator), and I got "ERROR [158]: Image Error"
I had tried that numerous times in the past as well, with either the same error or various other errors, through fastboot and through the phone being on and fully operable.
On a side note: for some reason it's recognizing my current image version as 3.18.502.6, but there is no operating system on there now, and when there was, it was definitely 1.73.502.1
Any other suggestions?
edit: also, please don't tell me that I should have changed my CID to CWS__001 instead of cws__001....does it make a difference if the CID is lowercase or uppercase?
Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita
timmaaa said:
Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
You're correct about me having rushed the process. Well, I didn't at first, but after the first few days, I began to just try anything I could get my hands on, and believe it or not, that was a year ago, so every once in a while I'll grab the phone and try searching some new things, but it's not like there are an infinite number of ways to go about things :\ Thanks for the help so far though, really
edit after seeing your edit: hahaha! yeah, you caught yourself perfectly! Also, in response to your question: I've tried flashing the unlock token through multiple different programs, but to no avail. As you said, I royally screwed myself in thinking that I could put back my CID (but my stupid self didn't put uppercase letters), and I thought I'd still be able to use my unlock token since I had gotten the code beforehand and it worked multiple times before, but I was mistaken
To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita
timmaaa said:
To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita
Click to expand...
Click to collapse
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time
Ruu while in fastboot mode.no?
Edit my bad just noticed the part about lower case cid
Sent from my One XL using xda app-developers app
EsoteRIcalfreaK said:
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time
Click to expand...
Click to collapse
Unfortunately for you there is no differing view. You've gotten the phone to a point where it cannot be resurrected via traditional means. Jtag is indeed your only option, and yes it's a repair service. They hook your motherboard up to a riffbox and push the partitions to it, you can even request things like s-off. There's a user here on XDA called zarboz who does jtag repairs, and I believe he's the cheapest you'll find. He's based out of Ohio I think. Contact him via PM for details.
Sent from my Evita
Great, I have an awesome paperweight that I made myself, and the person that I could talk to so that I could get help doesn't accept private messages from someone who has less than ten posts, hahaha
I'm so hoping that the head of HTC's development department somehow joins the forum and tells me that I just need to fastboot some crying smiley face symbol and the phone will start dancing for me until everything goes back to it's original factory settings...why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!
The RUU is HTC's version of software reset. The problem isn't a lack of reset program from the manufacturer, the problem is the fact that you changed the CID incorrectly.
Sent from my Evita
I can't believe uppercase and lowercase make a difference though
Also, I tried executing the RUU in multiple different ways, even when the OS was operable, in the last year, multiple times, with multiple different versions, but I was always presented with an error of some sort and the RUU setup would cancel and close. The first thing I tried after every exploit that I did was to run the RUU, so I really don't know what else I could have done differently to have gotten the RUU to run without errors, or else I wouldn't have gone this far and tried unorthodox measures to try and revive the poor guy
Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Sent from my Evita
EsoteRIcalfreaK said:
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
Click to expand...
Click to collapse
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
EsoteRIcalfreaK said:
I have scoured the internet for a solution, but my phone is from Hell.
Click to expand...
Click to collapse
EsoteRIcalfreaK said:
why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!
Click to expand...
Click to collapse
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
EsoteRIcalfreaK said:
I can't believe uppercase and lowercase make a difference though
Click to expand...
Click to collapse
How is that so unbelievable? As timmaaa mentioned, case is often crucial when it comes to computers. Since when is syntax not important when typing computer commands?
For the CID in particular, its obviously all hinging on a handful of crucial characters. So it needs to be typed exactly right.
redpoint73 said:
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
Click to expand...
Click to collapse
adb works in recovery or while the phone is stuck at loading screen but not in bootloader. Ofcourse, without an OS there's nothing to grant su. Though, he MAY be able to rewrite his CID using the 3.18 method anyway since I imagine the recovery must have SU or equal permissions..
I am less inclined to want to help after all his whining though :/
exad said:
I am less inclined to want to help after all his whining though :/
Click to expand...
Click to collapse
timmaaa said:
Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Click to expand...
Click to collapse
redpoint73 said:
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
Click to expand...
Click to collapse
Guys, guys, please do understand that I did many many hours of research before attempting anything. It wasn't until just recently that I began to just go plain crazy and just throw whatever I could get my hands on into commands and such (and that was all done in the matter of one frustrating night actually, so for almost two years I researched and learned things from mostly this board and tried different methods I found useful). You should see the bookmarks I have created on my browser (I deleted a bunch of useless ones recently, but I have 24 as of right now just explaining One X things)!
If you read closely (I know, I have written a lot, because I have seen people get completely flamed for not writing enough information), I mentioned that I have been trying to revive this phone for over a year now (two years this month). The reason I didn't ask for help earlier, which I wanted to do from day one, is for respect to exactly you guys...
1. I was about to make an account on here and post the very first day I got the phone, but after watching the introduction/noob video on YouTube for this website that explains the rules and what to do before EVER posting ANYthing, I decided to do a little more research and do my best to listen and learn from all the tutorials and great help you guys have given to others.
2. I wanted to make sure, as the video and as many of you mention on this forum, to try every avenue and method before coming for help. I did so precisely for the reason of not wanting to look as though I'm "whining". I might have exaggerated a bit in saying that I threw everything I found at the phone, because I did not just blindly do things without the proper research.
The OS I "accidentally" deleted in hoping to get rid of whatever software was on there that really was not changing or allowing me to RUU or anything. I thought that if I deleted it, it would be easier to put a fresh genuine stock copy on it. I was mistaken, and by the time I realized, I had done the damage to the phone. The biggest mistake that caused this irreversible damage was MY OWN unfortunate way of thought of thinking that uppercase and lowercase wouldn't make a difference (actually the truth is, I thought the original CID was lowercase, but seeing as how I had spent almost two years on this project, and I had had a very long day, I didn't double check to make sure, and I figured that I would be able to go back and change it worst case scenario...this my MY mistake, and I am by no means whining or complaining for MY OWN MISTAKE).
All that being said, please gentleman, if there is anything I could do to revive this phone and reverse my wrong-doings, I would appreciate it greatly and be forever grateful. I assure you, I will not perform a single step without confirming that I am doing the right thing. I am definitely wanting your help, and I definitely do seek to leave behind something that other people who make similar mistakes to mine can look back on for future reference.
Long story short, I messed up, it's my fault, I'm not complaining or whining, my Crapple and Samsuck comments were just to poke fun at those companies, and I would really appreciate it if anyone could help me in any shape way or form. Thank you beforehand
Erik
Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086
exad said:
Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086
Click to expand...
Click to collapse
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand
To be honest I think this was dubious at best, it was worth a try but I didn't hold much hope for it actually working. The only place it might have worked would have been in TWRP, even then your system was wiped so the structure required for the commands doesn't even exist in the partition. Someone else chime in here if I'm wrong, but I still believe jtag is the only option out of this.
Sent from my Evita
EsoteRIcalfreaK said:
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand
Click to expand...
Click to collapse
You have stock recovery!? -_- I think timaaa is right then -_- I will flash stock recovery and test ADB just to be sure, just for you homeboy. I will post an update shortly.
---------- Post added at 03:21 PM ---------- Previous post was at 03:05 PM ----------
Yeah, sorry man, Jtag only.