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.
Related
I guess I will start by saying that I have been a long time 'lurker.' I started coming around XDA back when the original Dash was new and have used all the information pumping out since then.
I tried looking around as best as I could to see if there were any other threads regarding a full root with the HTCdev bootloader but could only find discussion and debates around it.
I mostly am just confirming that it can be done. Not sure if I am a lucky one or if it was even a very risky process, but it took me all of about 15 minutes so I'm not complaining.
All I did was follow the instructions from HTCdev to unlock my sensation. After that I followed this guide from Step 2.
I currently have S-OFF, superuser access, installed a new rom, and reverted to my original rom. Everything seems to be properly working without a hitch.
Also, for clarity on this part in HTCdev FAQ:
What does this mean for me?
Unlocking the bootloader means that you now have the ability to customize software on your device. Please note that changing your bootloader can cause significant issues with your device and once you have unlocked your device, you have agreed to the disclaimer that states a change in warranty status such that in the event you render your device unusable, you are responsible for the recovery of your device, whether by repair or by other means.
Click to expand...
Click to collapse
All that means is that if you brick your device through unlocking or flashing new roms that HTC will not warranty your device. If everything works properly but you end up with other issues, i.e. touch screen no longer is responsive, then you are covered. I actually spoke to an HTC rep about it and that is what I got. Now they may try to say that unlocking may have caused it, but that isn't anything new.
Hmmm -_-
Sent from my HTC Sensation 4G using XDA App
hmmmm hmmmm cough choke cough
kleanblade said:
I guess I will start by saying that I have been a long time 'lurker.' I started coming around XDA back when the original Dash was new and have used all the information pumping out since then.
I tried looking around as best as I could to see if there were any other threads regarding a full root with the HTCdev bootloader but could only find discussion and debates around it.
I mostly am just confirming that it can be done. Not sure if I am a lucky one or if it was even a very risky process, but it took me all of about 15 minutes so I'm not complaining.
All I did was follow the instructions from HTCdev to unlock my sensation. After that I followed this guide from Step 2.
I currently have S-OFF, superuser access, installed a new rom, and reverted to my original rom. Everything seems to be properly working without a hitch.
Also, for clarity on this part in HTCdev FAQ:
All that means is that if you brick your device through unlocking or flashing new roms that HTC will not warranty your device. If everything works properly but you end up with other issues, i.e. touch screen no longer is responsive, then you are covered. I actually spoke to an HTC rep about it and that is what I got. Now they may try to say that unlocking may have caused it, but that isn't anything new.
Click to expand...
Click to collapse
Not trying to antagonize here but can you supply us with some screen shots of your "About" section and kernel and ROM part...??? No disrespect meant but if you say this is true then I would like to visualize the outcome. Thanks!
I understand anyone's skepticism. So I will provide, as best I can, whatever information I can. Have a couple screens attached. Soon as I can find a camera or get my hands on someone's phone I will take a picture of the HBOOT screen.
I'm not trying to do anything other than a "Hey, this actually worked for me." HTC's method just gave me the unlock and S-OFF. I understand it hasn't been the case for everyone. In fact I even had issues with HTC's method once I got the prompt to actually unlock the device. It wouldn't accept my input the first few tries (choosing yes or no yielded nothing).
Very legitimate. You should do a tutorial video on youtube and post it here.
kleanblade said:
I understand anyone's skepticism. So I will provide, as best I can, whatever information I can. Have a couple screens attached. Soon as I can find a camera or get my hands on someone's phone I will take a picture of the HBOOT screen.
I'm not trying to do anything other than a "Hey, this actually worked for me." HTC's method just gave me the unlock and S-OFF. I understand it hasn't been the case for everyone. In fact I even had issues with HTC's method once I got the prompt to actually unlock the device. It wouldn't accept my input the first few tries (choosing yes or no yielded nothing).
Click to expand...
Click to collapse
Sent from my HTC Sensation 4G using XDA App
hmmm
why use this and not the alpharev solution?
my question exactly...
reddoni said:
why use this and not the alpharev solution?
Click to expand...
Click to collapse
What is the difference between the two unlocking methods? Does one let you go back to S-on should you want to revert back? Are more internals accessible with one over the other (like radio's)? Just curious. When I do root I want to make sure I am using the best one with optimal features. Thanks in advance.
I personally have not seen a distinct advantage with using either method. If the phone bricks with either method you are out in the cold no matter what. Both are relatively easy to do. With HTC's method your warranty will at least be intact for any issues they deem not responsible from being rooted w/o having to 'hide' that you rooted your device. HTC's method may be easier to 'relock' your device as well. After I locked my device and rebooted, I locked it again and it was as simple as a short command. Any deeper than that I will say it's beyond my ability to know.
I feel like its as simple as an apples and oranges approach or an OEM vs after market. HTC has tested and checked their method and put their stamp of approval on it. For some 'consumers' it gives them a better sense of security. AlphaRev method works just as well but will never have the clout a large corporation, such as HTC, has.
If there is an interest for Snipes' request I could try to put a guide together. I know I don't command much credibility yet. So I don't want to do something know one would trust. However, it really isn't much different then the current guide available.
Also, HBOOT picture attached. As far as locking up your device again, with the HTC method it puts **** RELOCKED **** as the header and S-ON. I believe (not sure since I haven't done it) with the revolutionary method it simply replaces the hboot screen to the original.
How did you S-OFF? Using the same adb command as those with the Nexus One did?
I simply followed HTC's method to unlock the boot loader and it gave me S-OFF.
This gist of HTC's process is that you use go through fastboot, get your device token code, submit your token code to HTC, they email you an unlock_code.bin file, and you finish up with flashing your device with the unlock code. It is not difficult and took me about 3 minutes, maybe. The only extra thing that I am not even sure you need, is to have htcsync installed (it was listed as a requirement by htc).
Also,
The only two commands you use in the process are:
fastboot oem get_identifier_token (to get the token you need to submit)
fastboot flash unlocktoken Unlock_code.bin (flash your unlock code on the device)
If you want to relock your device you simply use:
fastboot oem lock
I just tried the HTCdev way, and I did get unlock, but did not get S-OFF
Billyvnilly said:
I just tried the HTCdev way, and I did get unlock, but did not get S-OFF
Click to expand...
Click to collapse
same here, it says unlocked but still s-on... and i get an error when trying to flash recovery (step 2) what to do?
I'll get my hands on another Sensation and see what results I get.
Odd that I would be the only one with a sensation that has s-off.
miroxlava said:
same here, it says unlocked but still s-on... and i get an error when trying to flash recovery (step 2) what to do?
Click to expand...
Click to collapse
Just start with step one then. I was able to follow all steps (except i dont need supercid) after doing htcdev. took maybe 45 minutes from start to finish, including downloads, restarts, and getting new ROM installed. Which btw, the CM7 alpha is out... trying it out soon.
Ok the HTCdev site says this. Not to mention they know you S-offed cause you did it via their website and tools.
Please understand that you will not be able to return your device to the original state
Click to expand...
Click to collapse
And in the [Guide] to Installing S-off, ClockWork, Root, SuperCID & S-on [03/AUG/11](noobproof) thread it says.
For Warranty Purposes/Returns:Follow Step 4 below for removing Clockwork and Root FOLLOW STEP 5 TO CHANGE BACK TO S-ON - CONFIRMED TO BE WORKING- USE WITH CAUTION
Click to expand...
Click to collapse
Now my question is this, if you S-off your Sensation via the HTCdev site and then S-on your Sensation via the method mentioned in the guide. Does your Unlit go back like it was originally, and not say " **** RELOCKED ****" at the top of the screen. Or is the to methods of S-offing your Sensation compatible with one another. I mean will combining the two brick the device. I would like some feed back from some devs that know more about what is actually going on when you switch from S-on to S-off, or from S-off to S-on.
Edit: Also the HTCdev site says this.
going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
Click to expand...
Click to collapse
So this is at the OP, just cause you use the HTCdev site to S-off your bootloader. It does not mean it does not void your warranty. And it does not mean HTC will fix your device if things go wrong and your device is rendered usless. You have to remember it is HTCdev, key word being dev not HTC.
Hi folks.
You'll have to excuse me, as I know next to nothing about putting roms and whatnot into my phone - but I am super excited about being able to learn how, etc.
I'm currently using a totally stock and normal HTC Sensation 4G and have been since roughly the time it came out with my carrier. The phone has started being... weird, so I'm looking to change things around with it.
Anyways - I've been looking around the site and trying to find what exactly is the best starting point for somebody with absolutely no experience.
I've seen some noob threads here and there, but I'm not sure if they're leading me to readying my phone to throw no a new rom. Is there just some sort of state to put my phone into and then be able to flash whatever rom is available for it?
This is what I started looking at but I'm not sure if this a good jump off or not to ready my phone for fun changes.
Thanks for being patient with me on this.
Read this guide: http://forum.xda-developers.com/showthread.php?t=1192300
Basically, you need to S-OFF your phone, and install a new recovery. Then you can flash new roms from your new recovery.
Use the Revolutionary method in the guide to unlock your phone. Install the Clockworkmod Recovery, and Super CID if you want. That just means that you'll be able to flash a rom meant for *any* carrier, not just your own.
That's it.
59seconds said:
Read this guide: http://forum.xda-developers.com/showthread.php?t=1192300
Basically, you need to S-OFF your phone, and install a new recovery. Then you can flash new roms from your new recovery.
Use the Revolutionary method in the guide to unlock your phone. Install the Clockworkmod Recovery, and Super CID if you want. That just means that you'll be able to flash a rom meant for *any* carrier, not just your own.
That's it.
Click to expand...
Click to collapse
Thanks!
That's exactly what I needed. I plan on digging around when I get home.
Good luck. Just remember to read everything all the way through before you do anything, and make sure that you understand all of the steps. Most of the problems that people have is because they just don't read the information/guides.
59seconds said:
Good luck. Just remember to read everything all the way through before you do anything, and make sure that you understand all of the steps. Most of the problems that people have is because they just don't read the information/guides.
Click to expand...
Click to collapse
Fair advice for nearly anything!
Question about doing all this...
Do I have to have my phone connected to my computer? Or is this done primarily through the phone?
You'll need to transfer over some files. Super CID requires you to run commands to your phone from your computer, but that's it. It's definitely worth it to have fastboot and adb running on your computer in case you need it.
59seconds said:
You'll need to transfer over some files. Super CID requires you to run commands to your phone from your computer, but that's it. It's definitely worth it to have fastboot and adb running on your computer in case you need it.
Click to expand...
Click to collapse
Great! I will keep that in mind for when I'm there!
Is this generally a long winded process?
Nah The first time is a bit of work since you have to S-OFF your phone and install a recovery. But it's a breeze after that. So many people have done it and the xda forums are very helpful. I followed that guide the first time and had zero problems.
So, hopefully somebody will have a bit of an idea what to do here...
First things first. I'm doing this all through a bootcamp-esque program from my Macbook - and currently on Windows 7, as there's only Windows and Linux available for the Revolutionary method.
I've downloaded the program. Opened it into a folder, etc. Turned on USB debugging and done everything else the tutorial has mentioned.
Has anybody had similar issues before?
speps said:
Hi folks.
You'll have to excuse me, as I know next to nothing about putting roms and whatnot into my phone - but I am super excited about being able to learn how, etc.
I'm currently using a totally stock and normal HTC Sensation 4G and have been since roughly the time it came out with my carrier. The phone has started being... weird, so I'm looking to change things around with it.
Anyways - I've been looking around the site and trying to find what exactly is the best starting point for somebody with absolutely no experience.
I've seen some noob threads here and there, but I'm not sure if they're leading me to readying my phone to throw no a new rom. Is there just some sort of state to put my phone into and then be able to flash whatever rom is available for it?
This is what I started looking at but I'm not sure if this a good jump off or not to ready my phone for fun changes.
Thanks for being patient with me on this.
Click to expand...
Click to collapse
You mentioned the phone being "weird", in what way is it weird? If this turns out to be a hardware issue or something that requires you to send the phone back to the manufacturer, rooting the phone can void your warranty (if you have any warranty left).
Please keep this in mind prior to rooting your phone. There is a way to flash your phone back to stock and return S-ON but from what I hear it is a little risky and there is a chance of bricking your phone while doing it (as with any part of the rooting process).
When following directions for rooting, I would advise you to read the whole instructions list first to ensure you have an understanding of the whole process, so you don't get stuck at any steps. Make sure you follow the guides exactly as well.
Never heard of anyone doing this through bootcamp on a MAC, but as with any compatability issues, if you have any strange issues with any of the steps it is best to use a native Windows or Linux machine to perform the rooting process.
I have never had any issues with any rooting process, for my SGS and Sensation XE using a Windows 7 64bit computer.
rickadlee said:
You mentioned the phone being "weird", in what way is it weird? If this turns out to be a hardware issue or something that requires you to send the phone back to the manufacturer, rooting the phone can void your warranty (if you have any warranty left).
Please keep this in mind prior to rooting your phone. There is a way to flash your phone back to stock and return S-ON but from what I hear it is a little risky and there is a chance of bricking your phone while doing it (as with any part of the rooting process).
When following directions for rooting, I would advise you to read the whole instructions list first to ensure you have an understanding of the whole process, so you don't get stuck at any steps. Make sure you follow the guides exactly as well.
Never heard of anyone doing this through bootcamp on a MAC, but as with any compatability issues, if you have any strange issues with any of the steps it is best to use a native Windows or Linux machine to perform the rooting process.
I have never had any issues with any rooting process, for my SGS and Sensation XE using a Windows 7 64bit computer.
Click to expand...
Click to collapse
It's been doing a lot of the issues listed here - plus, the battery life is just absolute crap. I've ordered new batteries for it (the 1900mAh Anker ones people here discussed before) and taken a few other steps to try and make it work in my favour a bit more.
I was able to almost complete the S-Off process last night, although I hit a brick wall as it just continued on the "Zerging root" while using Revolutionary. Damn.
I may try again when I get home.
One thing NO ONE ever points you to do but is, in my mind, the most important thing is to try a make sure there is an RUU available for your current ROM.
An RUU (ROM Upgrade Utility) is a complete ROM from HTC which will restore your phone to stock should you need to send it back for a warranty claim.
To check for an RUU, you first need to know your current ROM version that your phone came with. Go to Settings>About phone>Software information and make a note of the 'Software version' e.g. 1.50.401.3
Once you have that, go here and try to find a file name matching the version:
http://forum.xda-developers.com/showthread.php?t=1074559
If you find one, download it and keep it safe
EddyOS said:
One thing NO ONE ever points you to do but is, in my mind, the most important thing is to try a make sure there is an RUU available for your current ROM.
An RUU (ROM Upgrade Utility) is a complete ROM from HTC which will restore your phone to stock should you need to send it back for a warranty claim.
To check for an RUU, you first need to know your current ROM version that your phone came with. Go to Settings>About phone>Software information and make a note of the 'Software version' e.g. 1.50.401.3
Once you have that, go here and try to find a file name matching the version:
http://forum.xda-developers.com/showthread.php?t=1074559
If you find one, download it and keep it safe
Click to expand...
Click to collapse
I'll be sure to do that. Thanks!
Would anybody know why I keep getting stuck at the "zerging root.." portion?
Unless it usually takes a few minutes, it seems to just... hang.
As far as I can tell, everything else is set up correctly for this to work.
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.
Hi Guys,
I'm trying to get a 'stable' rom for a phone I've given to my daughter (Evita / Telstra one XL).
I've tried a heap of things, tried to s-off, change radio files etc... Anyway, current status is that it's been unlocked, s-on, and I have twrp.. I'm using KickDroid XL v4.0.0 ROM, looks great, but the phone keeps on rebooting... Also loosing 3G signal, so have to reboot it quite a few times a day to resolve. (tired another rom, same problem, loss of 3g signal and multiple reboots during the day)
I'm sure it's got to do with the radio file, but can't seem to fix that. I've read 'so much!' information, but really confused now. I've tried to supercid it, unsuccessfully, tried to find the all-in-one toolking (bt it looks like its been removed)..
So, this is what I have when I boot it:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.23a.32.09.29
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
TWRP recovery
2.6.3.0
htc one xl
Evita
Any help in how to (or if I should) get the radio/hboot up to hopefully resolve the loss of 3G?
I'm no expert, but not that dumb either. I follow instructions from the start, but most of the time it gets stuck half way (ie, when doing supercid, boots to the HTC logo, but won't go any further)..
Any help really appreciated.
The problem is not that the ROM is unstable, the ROM is perfectly stable if you meet the requirements. The problem is your current firmware version. You need to update to the 2.15 firmware package. It does state that very clearly in the "You Need" section in the beginning of the Kickdroid thread. Please search/research properly before posting in future, it's part of the XDA rules. This issue has been discussed extensively in every single Sense 5 ROM thread, plus this is probably the 100th thread like this in our Q&A section.
Sent from my Evita
Why are you even giving your daughter a rooted/modded phone at all? Unless she has an understanding of what root means, its not a good idea. Does she even need anything except a bone stock phone?
thanks timmaaa, I appreciate you taking the time out to reply.
I'll do some more checking on firmware 2.15... I've honestly read about 5 hours last weekend on various threads... some lead to dead ends (it toolbox), some I can't get to work (supercid)... I tried this a couple of months ago, and almost bricked it, but managed to get twrp working...
Redpoint73, are you asking why give her a phone, or why a rooted phone? The answer to the first one is that she is 11, and catches the bus to and from school. The phone is used in an emergency. I've rooted it to give her some new features, and because it was locked with Telstra and that is not the carrier we are using anymore (much cheaper options here than Telstra), so I needed to get rid of the firmware...
Overall, I appreciate any help. I actually run 5 forums (car related), and I fully understand noob's coming on and asking the same question week after week. Our forums have a lot less posts than this one (< 200,000), but we still have members, week in-week out, answering the same questions because they like to help, and because sometimes there is too much information out there to sift through, especially when somebody is willing to point you in the right direction with a friendly smile
duplicate post, (sorry, hit save twice!)
jnrdavo said:
Redpoint73, are you asking why give her a phone, or why a rooted phone? The answer to the first one is that she is 11, and catches the bus to and from school. The phone is used in an emergency. I've rooted it to give her some new features, and because it was locked with Telstra and that is not the carrier we are using anymore (much cheaper options here than Telstra), so I needed to get rid of the firmware...
Click to expand...
Click to collapse
Its pretty clear from my post that it was root/mod that I was referring to. Root has nothing to do with Subsidy (SIM) Lock, and the firmware has little to do with the carrier you are on (I've been using the German T-Mobile stock ROM for a while now, despite being on AT&T).
Of course its up to you to decide what you do with the phone. But you should consider (if you haven't already) the security risk of giving a rooted device to a user that knows little or nothing about such things. Even more so for s-off, which is necessary for the solution that timmaaa suggested.
My question has less to do with exactly "who" the phone is for. But more to the point, when people come on here saying they are modding the phone for "someone else" (be it mom, third cousin, or whatever), if that person isn't doing it for themselves, its pretty questionable whether they need such mods at all.
ok, thanks redpoint73..
I understand where you are coming from, and appreciate your comments.
Now, anybody else like to point me in the right direction (to a link to get the latest firmware, or a compatible one working)?
jnrdavo said:
Now, anybody else like to point me in the right direction (to a link to get the latest firmware, or a compatible one working)?
Click to expand...
Click to collapse
You serious? timmaaa already told you where to find it.
Since I'm feeling charitable right now, here it is, complete with step-by-step instructions (only need to follow Posts #2 and 4): http://forum.xda-developers.com/showthread.php?t=2485865
The original thread where Turge posted his firmware package (see under "OPTIONAL", s-off is required before doing this): http://forum.xda-developers.com/showpost.php?p=45072132&postcount=1
Or just install the Beastmode kernel (S-off not required): http://forum.xda-developers.com/showthread.php?t=2165880
thanks mate. I appreciate the charity, I really do I'm trying not to be a nob.. I'm actually having another go this morning... I've got win 8.1 (yeah, I know) so trying to get the latest driver to work is a pain.... Just trying x_factory windows, backups up twice, but then doesn't run the next command (to change CID)...
Anyway, thanks again. I'll persist on...
Background:
My wife migrated from the (US AT&T) One X to the One on day one. Her One X has been sitting in her bedside drawer for almost a year. (She wanted to keep it as a backup.) Her One recently suffered irreparable physical damage; need to get her up and running on the One X.
Before the One X's temporary retirement, we:
Gained SuperCID
Unlocked Bootloader
Flashed custom recovery
Flashed a (Android 4.1 based) AOKP nightly
Did not achieve S-OFF
When the One X came back out of retirement, it had some major stability issues. Coming from the Nexus world, and (admittedly) not doing thorough enough research, I thought I could quickly re-ROM her phone and have her up and running.
Long-story short, I've somehow seemed to corrupt the recovery partition and the boot partition. And I'm not sure where to go next...
I can access the bootloader and fastboot. In fact, the bootloader is immediately loaded on boot.
I cannot achieve S-OFF. Every method I've seen requires some combination of fastboot and adb commands. I can do the fastboot portion, but without a working Android partition, I cannot perform the adb commands.
Every attempt to flash a custom recover via fastboot fails:
FAILED (remote: 12 signature verify fail)
From the research I've done, it seems like I need S-OFF to flash a recovery and ROM, but I need a ROM to achieve S-OFF.
Is that the case? Is there anything else I can try?
Run the 2.20 RUU, it's the only option you have, it should fix your partitions. Do not run the 3.18 RUU while s-on though or you'll brick.
How did the phone end up with borked partitions?
Sent from my Evita<br>
timmaaa said:
Run the 2.20 RUU, it's the only option you have, it should fix your partitions.
Click to expand...
Click to collapse
Found and downloaded 2.20 RUU; was nervous as hell running this with S-ON. The process never errored out, and the application never hung, I never saw a progress bar on the HOX either. (RUU quoted ~10 minutes. I waited 40.) I hard-bounced the phone and tried again... Success!
Thanks for the recommendation!
timmaaa said:
How did the phone end up with borked partitions?
Click to expand...
Click to collapse
I pushed the stock T-Mobile ROM to the phone from the older recovery that was already on the HOX, then rebooted. It hung at boot; was never able to boot back into Android. I was still able to access the bootloader and fastboot, so I tried pushing TWRP to the HOX using the WinDroid Toolkit. After that, I wasn't able to access Android or TWRP, and the phone booted directly to the bootloader.
The biggest mistakes: cockiness and lack of research. (Statement of frustration: this S-ON/S-OFF nonsense is for the birds!)
I'd strongly suggest you get s-off now, and discontinue your use of toolkits in favour of manual fastboot commands.
Sent from my Evita
timmaaa said:
I'd strongly suggest you get s-off now, and discontinue your use of toolkits in favour of manual fastboot commands.
Click to expand...
Click to collapse
Noted. Thanks...
The whole situation was frustrating because it was self-inflicted and I knew better than rush into trying to re-ROMing on hardware I wasn't familiar with.
I usually don't use toolkits; was just on a system that hadn't been prepped with adb yet. I re-learned a valuable lesson: take the time to set that up!
What's most frustrating is that I did try to use adb (after hosing the filesystem). I just kept running into issues with S-ON while trying to push boot.img's and recoverys. Coming from my Nexus world, I'm not accustomed to that.
Cool cool. It might be worth taking a quick look at my Evita FAQ and How-To Guide For Beginners threads in my signature. I'm not insinuating that you're a beginner, but they contain some vital information specific to this device which you might find useful.
Sent from my Evita
timmaaa said:
It might be worth taking a quick look at my Evita FAQ and How-To Guide For Beginners threads in my signature. I'm not insinuating that you're a beginner, but they contain some vital information specific to this device which you might find useful.
Click to expand...
Click to collapse
Yeah... that -- among many, many others threads -- was one of the threads I checked out after killing it.
I was so convinced that S-ON was my problem that I spent most of my time trying to get S-OFF and repair my recovery via fastboot. Had I been able to let go of that notion, I might have gotten somewhere without having to ask for help.
I only-ever mess with the wife's hardware when there's a problem, so I'm not incredibly familiar with it. I'll definitely re-review your guide before I take on any other tasks!
Thanks again!