I've been running ViperXL (Bulletprrof 1.3 kernel) just fine fine for a few weeks. It's been nearly flawless. Just now, though, the backlight went out and nothing I do seems to bring it back on. I've rebooted, plugged into AC, and tried booting into recovery. In the sunlight I can see just enough to know the device is on. I've managed to get into settings, which thankfully has a white background, and verified that brightness is at max.
There is no backlight even through the reboot process.
ctennenh said:
I've been running ViperXL (Bulletprrof 1.3 kernel) just fine fine for a few weeks. It's been nearly flawless. Just now, though, the backlight went out and nothing I do seems to bring it back on. I've rebooted, plugged into AC, and tried booting into recovery. In the sunlight I can see just enough to know the device is on. I've managed to get into settings, which thankfully has a white background, and verified that brightness is at max.
There is no backlight even through the reboot process.
Click to expand...
Click to collapse
When you reboot the phone, does the boot image (Default HTC Screen) also have no backlight? Or in recovery is there a backlight? If not, it's a hardware failure. Screen would need to be replaced. If the backlight comes on when in recovery or during first boot image, then it's something software related which is easier to fix.
There's no backlight anywhere. I know it's not kernel since I was able to fastboot flash the default kernel for ViperXL over USB.
If I bought this through AT&T less than a year ago does anyone know if it's under warranty? I'd hate to pay to get the screen replaced. I'd rather try to get it back to stock and take it in.
That's assuming, of course, someone can point me to instructions for getting back to stock! I've looked but haven't seen any in the forum.
It's hardware. You need a new screen. You would need to s-off if you're not already and then run the appropriate ruu for your carrier. I believe at&t will warrant it np.
S-off directions are stickied in original android dev section and ruu's can be found in the resource compilation thread linked in my signature.
Make sure to download an executable Ile and not a zip. Easier to return to stock with exe
Sent from my HTC One X using xda app-developers app
exad said:
It's hardware. You need a new screen. You would need to s-off if you're not already and then run the appropriate ruu for your carrier. I believe at&t will warrant it np.
S-off directions are stickied in original android dev section and ruu's can be found in the resource compilation thread linked in my signature.
Make sure to download an executable Ile and not a zip. Easier to return to stock with exe
Click to expand...
Click to collapse
Thanks a ton. I'm already S-Off. I spoke with customer service and they're going to send me a replacement device (same model, though I asked if it was possible to change). Should I be using the one labeled [ruu] [stock] att 2.20 ota? There are a few whose names look like what I might want.
No you'll want one that is ruu and not ota. Doesn't matter what version so long as it's at&t. The filename will end with exe
Sent from my HTC One X using xda app-developers app
exad said:
No you'll want one that is ruu and not ota. Doesn't matter what version so long as it's at&t. The filename will end with exe
Click to expand...
Click to collapse
Ok, so like [STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 ? And the RUU will wipe anything that's not stock, right? Thanks.
It will return your phone to stock but your bootloader will still be unlocked and you will still have s-off. You can spoof it like it's never been unlocked and return it to s-on though I doubt that would be worth the trouble.
Sent from my HTC One X using xda app-developers app
exad said:
It will return your phone to stock but your bootloader will still be unlocked and you will still have s-off. You can spoof it like it's never been unlocked and return it to s-on though I doubt that would be worth the trouble.
Click to expand...
Click to collapse
I see. So you don't think they'd bother digging too deeply to notice it's s-off and unlocked? I'll run the RUU tonight and check in later.
I really appreciate your help this evening.
Since it's a hardware issue, I doubt they'll care to dig That far into it. From what I see on here AT&T is pretty lenient about unlocked phones, especially when it's a hardware issue.
Sent from my Sony Tablet S using xda app-developers app
I'm having difficulty running the RUU. I've rebooted and connected my device to my computer and run the RUU utility. It says it can't find the device and to check the connection. I can't see the screen well enough to turn debug mode on or off on the device. What can I do to run the RUU?
Try running while in bootloader/fastboot?
Sent from my Sony Tablet S using xda app-developers app
That did it, thanks. Now to wait until the sun is bright enough out today to wipe the SD card through settings.
I'm going to miss being rooted.
Related
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
dalton42503 said:
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
Click to expand...
Click to collapse
YOUR PHONE IS NOT BRICKED. The term bricked means that your phone is a useful as a brick, i.e. if you can get into HBOOT, it's not bricked.
Gotta ask though, why did you not use the Hack Kit as its the only reliable method to root, my advice to you sir is when this gets cleared up READ AND EDUCATE YOURSELF before you really do brick your phone.
If you have a SDcard reader, pop out the SDcard and place one of the PD98IMG stock ROMs on your SDcard. From here you can reboot into HBOOT with the sdcard in your phone and HBOOT should pick up the PD98IMG and flash a working stock ROM. From here, you can root with the Hack Kit...
This will help you, read it and do what the stock ROM option...if you can get into HBOOT
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
dalton42503 said:
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
Click to expand...
Click to collapse
is the file named exactly "PD98IMG.zip"..you may also want to check the hide extension option to be sure its not hiding the .zip because if it is and you renamed it to "PD98IMG.zip" with the hide extension on, the phone will read it as "PD98IMG.zip.zip" and you would get that error.
haha and yeah man, we've all been there...I don't want to discourage you man, rooting is such an awesome experience and the hack kit is a pretty straight forward process, if you do the research and take the time to understand what you're doing, but lets see if we can help you out here first. I had the same issue you're having when I tried to flash a radio (same PD98IMG method you're trying to use) and it turned out to be the hide extension issue.
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
dalton42503 said:
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
Click to expand...
Click to collapse
hmm, so its named PD98IMG.zip caps and everything? If its not working you m ay have to get a stock RUU and run it through fastboot..
This is why you should educate yourself first. You do not need to unlock the bootloader from the HTC dev site. Now you could flash the the stock ruu from the PC and then use the hack kit. Check the stickies in the Inspire general section for more help.
Sent from my HTC Inspire 4G using Tapatalk
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
dalton42503 said:
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
Click to expand...
Click to collapse
Dalton, lock your bootloader again. Boot into fastboot and plug the phone. You will see fastboot usb at the top. Then plug your phone and open cmd session. Once there type fastboot oem relock. Once that is done, try flashing the .exe file in the HTC site (original GB update), making sure that you have HTC Sync installed.
If that fails, then I would try using the HACK Kit to gain S-OFF and root. You will then be able to revert to stock or flash a custom rom...
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
willm98G97B said:
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
Click to expand...
Click to collapse
He won´t be able to use the Kit if the bootloader is unlocked. HE MUST RELOCK Bootloader...then run the Kit...It´s worth mentioning that...
True, never ran htc s unlock option.
Sent from my Inspire 4G using XDA Premium HD app
Thanks A MILLION!!!
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Glad you have it back....yeah you'd better read and make sure what are about to do it and of course what risks are involved before making a move....
Dalton,
I would suggest following glevitan's and willm's assertion of getting s-off and root to use custom roms. Custom roms are WAY better than anything HTC has to offer, and much easier to install, if you have an issue warranty wise, you can always return to stock. Just make sure you know how to flash correctly, search for it and you will find easy instructions, and if memory serves, a youtube video which helped me greatly.
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Can you tell me the which firmware or send me a link.I have a same problem
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
glevitan said:
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
I am having a bootloader error with stock ro.(error 140)
How can i fix it
ydnbngl said:
I am having a bootloader error with stock ro.(error 140)
How can i fix it
Click to expand...
Click to collapse
if you have unlocked the bootloader then relock it...then run it again.
glevitan said:
if you have unlocked the bootloader then relock it...then run it again.
Click to expand...
Click to collapse
It is relocked and ship s-on
Hey guys, I just picked up a Inspire as a play toy since my cousin upgraded.. What in looking for is a RUU for the latest update if there is any.. 2.3.5, firmware 3.20 if I'm not mistaken. (Its not in front of me at the moment).. I've tried numerous sites and it seems as though they don't exist anymore..
Quick history, phone worked fine. Bone stock, never rooted or unlocked. So she took the latest update, and ever since then it has problems... Main thing is when the screen goes black, it reboots. EVERY SINGLE TIME. So I decided to unlock via htcdev, fastbooted twrp 2.4.4.0, and flashed a rom to see if it fixed it. Flashed jellytime and respective gapps, no dice. Phone is still rebooting upon locking. Last resort is a ruu... I've tried over clocking, overvolting, etc... No go. I'm not ruling out hardware 100%, but bc it didn't do this before the update makes it last on my list... Any advice?
Sent from my One X using Tapatalk 2
Test it without the sd card.
Reflash the ruu.
Sent from a dream.
I don't have the ruu lol. That's why I posted here... It seems like every site has it taken down...
Sent from my One X using Tapatalk 2
InflatedTitan said:
I don't have the ruu lol. That's why I posted here... It seems like every site has it taken down...
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
https://www.google.com/#hl=en&output=search&sclient=psy-ab&q=htc_inspire4g_att_RUU_3.20.502.52_US&oq=htc_inspire4g_att_RUU_3.20.502.52_US&gs_l=hp.3...3147.3147.0.4546.1.1.0.0.0.0.204.204.2-1.1.0.les%3B..0.0...1c.2.6.psy-ab.m3erFIGkS8Q&pbx=1&bav=on.2,or.r_cp.r_qf.&bvm=bv.43828540,d.eWU&fp=c539a620ba7dec8b&biw=1366&bih=641
There seems to be a link with the files, haven't checked if it's in it. As well, I have a copy of the last inspire update but no where to upload it and in case you can't find it via the provided link.
Hey thanks man. I'll give that a shot .
One more question, if I flash the stock lower firmware zip, would that be enough to run the aahk to s-off? Or is there more to it than that? Last time I tried it said the firmware was not supported up to that version
Sent from my One X using Tapatalk 2
InflatedTitan said:
Hey thanks man. I'll give that a shot .
One more question, if I flash the stock lower firmware zip, would that be enough to run the aahk to s-off? Or is there more to it than that? Last time I tried it said the firmware was not supported up to that version
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I wouldn't recommend flashing a lower firmware.... Not sure if anything bad will happen but it does not seem like a good idea. Besides, aahk has been retired. There is no support for it and it is only for advanced users.
You can try glevitans tool in the development section to unlock your bootloader but he two has left these forums due to too many self rightious (or however you spell that) noobs.
Sent from a dream.
Right... I'm already unlocked and rooted.. So there's no way to s-off without jumping through hoops? Lol... I can throw out some fastboot and adb commands... But as far as DD'ing blck partitions I'll just give up on s-offing
Sent from my One X using Tapatalk 2
Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file..
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file..
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I can't give you any other advice to the first problems you had but yes when you boot into hboot. It automatically searches for a pd98img.zip.. That is completely normal
Sent from my Inspire 4G using xda premium
Ok, I have never been more tempted to throw a phone in all my life. This has me VERY irritated.
I got this htc one x on a hunch, was a good deal, seen great roms on here, thought it was a good idea. I've had nothing but trouble. Heres my deal:
I went to the htcdev site to get the boot loader unlocked. Im no dummy, I've gotten into LOTS of phones. This thing is crazy. I've watched 20 videos, used 3 different computers, NOTHING works. ALWAYS says Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Now this isn't my first rodeo, I read, searched, paused videos made sure I was getting the same info selected, spaces, EVERYTHING that were showing between my screen and the youtube screens. This phone has taken the latest att update. Is this the problem? Has getting into the phone been cut out? Is there another way to get in and load roms? Should I ditch it for a galaxy?
You have supercid, right? The One XL can't have bootloader unlock without it. AT&T Doesn't like for people to use phones the way they're intended to be used
There is a new method for unlocking on the latest update over in general.
Sent from my HTC One XL using xda premium
I've never owned a phone so hard to deal with... Everything I read says I need to be rooted, I need to have bootloader unlocked to root, different direction loops I cant seem to break... The noobproof all require bootloader unlocked... there is SO much info, it all points in different directions, and I cant make heads or tails out of it to be honest. I've been reading for 2 days and am about to pitch this thing as far as I can.
I cant find the directions for supercid, just what it does. I normally don't require hand holding... I have an upgrade coming in September.....
Part of my issues is I don't have a charge only mode...
what carrier did the phone come from and what software version are you on?
klloyd said:
Part of my issues is I don't have a charge only mode...
Click to expand...
Click to collapse
Newest update doesn't have this option. There's a root method in dev section, however you need linux to run the script. But that's easy to make a bootable CD just to run the script. After you root then dev unlock. Then you can proceed to either fastboot a recovery or use goo manager to install the latest. Then flash away...
I recommend you follow the S-off thread too... That way you don't need fastboot to flash boot.img. then if it came with 3.18 firmware, you'll also need to follow the touchscreen downgrade thread if you plan on using Aosp roms.
It's really not hard to do the last 2 steps, but I have to agree you need to go through an a$$load of steps to get the desired effect. But this phone is great with custom roms. Some call me crazy, but if I run carbon Rom tweaked it'll rival my buddies S4 no problem
Sent from my HTC One XL using Tapatalk 2
Its a true blue att phone. Running 4.1.1, software 3.18.
I actually run Linux on about everything... I am using my wifes computer to do all this, cause it seemed windows was easier. (insert shame here)
Im just use to the one clicks, the easy additions of clockwork in a single flash on the galaxy phones. Im not giving up, but believe you me, there is an note2 or and s4 in my future.
klloyd said:
Its a true blue att phone. Running 4.1.1, software 3.18.
I actually run Linux on about everything... I am using my wifes computer to do all this, cause it seemed windows was easier. (insert shame here)
Im just use to the one clicks, the easy additions of clockwork in a single flash on the galaxy phones. Im not giving up, but believe you me, there is an note2 or and s4 in my future.
Click to expand...
Click to collapse
*Gags a little* lol. Good luck man
Sent from my HTC One XL using Tapatalk 2
The reason info conflicts is AT&T phones cant use htcdev unlock by AT&T request.
All other evita's can use htcdev fine.
So AT&T phones need root to change cid to pretend to not be an AT&T phone before they can unlock.
Sent from my HTC One XL using xda app-developers app
As normal, wonderful help! Im on the right track this time! Thanks!
klloyd said:
Its a true blue att phone. Running 4.1.1, software 3.18.
Click to expand...
Click to collapse
If that's the case, you need to go here:
http://forum.xda-developers.com/showthread.php?t=2283760
That will change you Cid so it no longer identifies your phone as an AT&T model. Then, and only then will you be able to use htcdev to unlock your phone.
Sent from my HTC One X using xda app-developers app
I am currently stuck in the bootloader. To make matters worse, I relocked to RUU and am stuck at Sending with that. I am Super CID which I think is the problem. To make matters even worse, I no longer have my unlock_code.bin file.
Is there any hope for my phone? Also, the RUU process has completely wiped my phone. Thanks for any input in advance. I have searched and searched for an answer but haven't found anything useful.
Sent from my HTC One XL using XDA Premium 4 mobile app
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
timmaaa said:
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
Click to expand...
Click to collapse
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Sent from my Evita
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
//JavaJ said:
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have a locked bootloader and the correct CID there should be no harm in running the RUU. The unlock process (from memory, I could be wrong) doesn't require the phone to be booted into an os, it's all taken care of while the phone is in bootloader. That's kinda irrelevant now anyway as it isn't possible anymore.
Are you using the usb cable that came with the phone? You can try using a different usb port, usually the ones on the back of the pc tower are the best.
May I ask, how exactly do you think the s-off process screwed up the phone? It either succeeds or fails, and there should be no serious repercussions from either.
Sent from my Evita
Click to expand...
Click to collapse
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
timmaaa said:
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
Click to expand...
Click to collapse
Took your advice about the usb port. Switched it to the back and the ruu worked. Will I be able to run the root exploit again? Yes, this definitely has been a learning experience. Coupled with my lack of sleep and overall frustration I made some bad moves. Thanks for your patience and help though. Much appreciated.
And no, I could not get back into recovery after I relocked it. It would send me right back to the bootloader. Also, I did do a factory reset from the bootloader. Believe me, taking mental notes all the way here.
Sent from my HTC One XL using XDA Premium 4 mobile app
Now that you have a working os, you could be able to use the exploit again to unlock the bootloader etc. Just take it slowly though, do some reading so you gain a bit of knowledge. And if you have any questions, don't be afraid to ask.
Sent from my Evita
Unlocked and rooted. Again. Thanks for your help. Leary of trying to s off again though
Sent from my HTC One XL using XDA Premium 4 mobile app
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
timmaaa said:
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
Click to expand...
Click to collapse
Yes, I have done it before, on my One X. Not quite sure what went wrong. Maybe the issue with my wife's phone was preexisting and reared it's ugly head in the process. I have been rooting and nodding phones for years. I am not a complete noob. I am experienced in java programming and have created many interesting applications for my phone. Perhaps I should take my java knowledge and automate my s off experience.
Sent from my HTC One XL using XDA Premium 4 mobile app
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Very nice found Tim.....:thumbup:
Swyped From BlueICESense_JBE
timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
timmaaa said:
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
Click to expand...
Click to collapse
Just wanted to let you know that I went through s off and all went well. Only thing I can think was the problem was that either there was a pre existing corruption on the phone, or the usb port I was using.
Sent from my HTC One XL using XDA Premium 4 mobile app
It could have been anything. It's becoming more and more apparent that different things halt the process for different users. It makes it really difficult to troubleshoot when helping someone through the process. In the end you got it though which is great.
Sent from my Evita
Hi all,
I am attempting to S-off the wife's ATT HTC One X, so that I can install a Kit Kat Rom in it. Her phone is unlocked and running CM10.2, but she's S-on.
I've tried several toolkits, but they get stuck and time out waiting for the device once it reboots into the bootloader. In debugging mode, adb devices identified the phone just fine, but the computer (running Windows 8.1) says doesn't recognize the phone when in bootloader. I've got Koush's Universal ADB driver installed, installed HTC Sync for the drivers, then uninstalled the program. The drivers are still there when I navigate to them.
If this isn't the appropriate forum, then I apologize.
Many thanks in advance!
What method are you trying to use?
Sent from my HTC One X using xda premium
magnetboard said:
What method are you trying to use?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Rumrunner is one. It reboots into bootloader post the warnings then runs its 120 seconds and times out waiting for the device.
Ah, windows 8 and newer have problems with fastboot. That's why. Do you have access to a computer with windows 7 or lower?
Sent from my HTC One X using xda premium
magnetboard said:
Ah, windows 8 and newer have problems with fastboot. That's why. Do you have access to a computer with windows 7 or lower?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I can put an old HD back in with W7. I take it there is no workaround with 8.1?
Windows 8 is fine with fastboot but 8.1 is where the problems begin. No workaround yet. What see the bootloader details though? Depending on your current setup you might not even need s-off yet. S-off isn't required to flash the ROMs, but it's required to update your firmware (via an RUU). If your firmware is up to date you can just flash.
Sent from my Evita
timmaaa said:
Windows 8 is fine with fastboot but 8.1 is where the problems begin. No workaround yet. What see the bootloader details though? Depending on your current setup you might not even need s-off yet. S-off isn't required to flash the ROMs, but it's required to update your firmware (via an RUU). If your firmware is up to date you can just flash.
Sent from my Evita
Click to expand...
Click to collapse
What all do you need to know? She has her phone with her today.
She has 2.18. I don't know other details off the top of my head and walking her through to boot to bootloader would be an utter disaster, lol.
The reason for trying to get S-off was that both the KitKat versions of CM and PA stated that S-off was required.
Thanks for your help.
If your cousin can't get to the bootloader by herself, then she has absolutely no business having a modified phone. Handing a modified device to someone who has no idea about what they're doing is a bad idea. The device has root privileges, access to areas that see not normally accessible. This means it's easy top screw up the device if you don't know what you're doing. Also, if something goes wrong she's not gonna know what to do, will probably panic and screw it up even more. Return it to stock.
Sent from my Evita
timmaaa said:
If your cousin can't get to the bootloader by herself, then she has absolutely no business having a modified phone. Handing a modified device to someone who has no idea about what they're doing is a bad idea. The device has root privileges, access to areas that see not normally accessible. This means it's easy top screw up the device if you don't know what you're doing. Also, if something goes wrong she's not gonna know what to do, will probably panic and screw it up even more. Return it to stock.
Sent from my Evita
Click to expand...
Click to collapse
Appreciate the concern. This is my wife's phone, and she's handled CM10.2 just fine for the last 6 months. She's informed enough to not do something stupid, but let's me handle rooting and flashing.