Related
I'm trying to get to S-OFF using Facepalm S-OFF, however when I connect my One X in bootloader to my PC (I have 2 laptops & 1 desktop) it pops up that the USB device that you connected has malfunctioned and windows does not recognize it it does the same thing on all 3 PC's.I originally posted in the Facepalm thread and am now posting here as per thedailyl3af recomendation that I post here since he could not help me. When I connect my One X to the PC the phone is recognized by both the PC & HTC Sync manager (yes I shut down the Sync manager) but soon as I go to bootloader the PC no longer recognizes it. The main reason I want S-OFF is so that I can flash different kerrnals and radio's to try and clear up the One X clearity problem, when I am talking to people most of the I am saying "what" or "could you repeat that". My One X is unlocked and I do have SuperCID. Please Help! Thank you in advance
Install HTC drivers and uninstall HTC sync
Sent from my One X using xda app-developers app
That is weird. Did you try different USB ports or a different cable? That normally helps. Try to wait 10 mins as well
Sent from my Carbon-ize Evita using xda-developers app
Why not just connect your phone normally to the computer, stop HTC sync and use adb commands to put your phone into bootloader?
Sent from my HTC One X using xda premium
Venomtester said:
Why not just connect your phone normally to the computer, stop HTC sync and use adb commands to put your phone into bootloader?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I have done that, When I connect my One X to my computer, HTC Sync starts, I shut it down. I open command pompt. Then I use adb commands to open bootloader and soon as it goes into bootloader the PC stops recognizing it and says the USB device has malfunctioned. I am unlocked, have SuperCID, Have Super user and am able to use it. I am running ViperXL rom. I have uninstalled drivers on my PC and re-downloaded them and re-installed them many times, so I know it is not drivers on my PC.
Something had to go wrong when I flashed TWRP v2.4.1.0. My problem is everything that evryone is telling me to do goes through bootloader, well if my PC does not recognize my phone while in bootloader how am I going to get past that point. I even tried to flash to TWRP v2.3.1.0, through TWRP recovery, both as a seprate zip file and by starting to reinstall ViperXL (Aroma) installer and I can't even back to TWRP 2.3.1.0 which I know is not as buggy as v2.4.1.0. When I go through the Aroma installer it says that it installed it, but when I go back to TWRP it still says v2.4.1.0.
Was on Facepalm S-OFF Thread and they recomended that I try this forum since evrything they had me try did not work. I am stuck and I just want some straight to the point advice on how to get past this issue. Don't know if this will help but when I am in bootloader this what the bootloader image says, I'm only putting the first part down as you guys know what the rest says.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PUT SHP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11.2
OpenDSPv29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
You have hboot 1.14. Aroma installer fails to flash images you may have to flash twrp manually. Also there was a bug in on of the versions of viperxl that would not mount. What version of viper are you running?
Sent from my HTC One X using xda premium
scrappy1959 said:
I have done that, When I connect my One X to my computer, HTC Sync starts, I shut it down. I open command pompt. Then I use adb commands to open bootloader and soon as it goes into bootloader the PC stops recognizing it and says the USB device has malfunctioned. I am unlocked, have SuperCID, Have Super user and am able to use it. I am running ViperXL rom. I have uninstalled drivers on my PC and re-downloaded them and re-installed them many times, so I know it is not drivers on my PC.
Something had to go wrong when I flashed TWRP v2.4.1.0. My problem is everything that evryone is telling me to do goes through bootloader, well if my PC does not recognize my phone while in bootloader how am I going to get past that point. I even tried to flash to TWRP v2.3.1.0, through TWRP recovery, both as a seprate zip file and by starting to reinstall ViperXL (Aroma) installer and I can't even back to TWRP 2.3.1.0 which I know is not as buggy as v2.4.1.0. When I go through the Aroma installer it says that it installed it, but when I go back to TWRP it still says v2.4.1.0.
Was on Facepalm S-OFF Thread and they recomended that I try this forum since evrything they had me try did not work. I am stuck and I just want some straight to the point advice on how to get past this issue. Don't know if this will help but when I am in bootloader this what the bootloader image says, I'm only putting the first part down as you guys know what the rest says.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PUT SHP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11.2
OpenDSPv29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
I already told you to uninstall HTC sync.
Sent from my One X using xda app-developers app
There is one more thing that could cause you problems and that is that your cable is bad. If you have another one that will fit your phone laying around you might want to try swapping out.
Sent from my HTC One X using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:49 PM ----------
Sorry herc didn't see you posted that already.
Sent from my HTC One X using xda premium
Venomtester said:
There is one more thing that could cause you problems and that is that your cable is bad. If you have another one that will fit your phone laying around you might want to try swapping out.
Sent from my HTC One X using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:49 PM ----------
Sorry herc didn't see you posted that already.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I just went through all of this. Been having this problem for the past few days. I tried different cable, differenent port, installing/unistalling htc sync, install htc driver/uninstall htc drivers, install android sdk/unistall android sdk, installing pdanet drivers, stopping htc sync, manually uninstalling all android related drivers and reinstalling them. In the end after 4 days of long hours of trial and error I gave up. EVERY solution on the internet fail. Every one of them. Came to the conclusion that something else besides android related drivers is interfereing with fastboot. So the only solution I found was to download virtual box and install a copy of windows in it. Install htc sync on the virtual machine and dont uninstall it. Then plug in your phone while in bootloader connect to the virtual machine and let it install the rest of the drivers. Then fastboot WILL work.
Im not saying don't try all of what everyone is telling you first. What Im saying is that if nothing else works although it may be a bit complicated I can almost guarantee it will work because everything is fresh and there should be no conflicts.
ImagioX1 said:
I just went through all of this. Been having this problem for the past few days. I tried different cable, differenent port, installing/unistalling htc sync, install htc driver/uninstall htc drivers, install android sdk/unistall android sdk, installing pdanet drivers, stopping htc sync, manually uninstalling all android related drivers and reinstalling them. In the end after 4 days of long hours of trial and error I gave up. EVERY solution on the internet fail. Every one of them. Came to the conclusion that something else besides android related drivers is interfereing with fastboot. So the only solution I found was to download virtual box and install a copy of windows in it. Install htc sync on the virtual machine and dont uninstall it. Then plug in your phone while in bootloader connect to the virtual machine and let it install the rest of the drivers. Then fastboot WILL work.
Im not saying don't try all of what everyone is telling you first. What Im saying is that if nothing else works although it may be a bit complicated I can almost guarantee it will work because everything is fresh and there should be no conflicts.
Click to expand...
Click to collapse
While I agree with you, there are steps you take with troubleshooting to narrow down the cause this way if you don't HAVE to do a fresh install of Windows on a virtual machine, you don't.
exad said:
While I agree with you, there are steps you take with troubleshooting to narrow down the cause this way if you don't HAVE to do a fresh install of Windows on a virtual machine, you don't.
Click to expand...
Click to collapse
Exactly. That was what I was trying to say in the last line of my post.
I had the same problem and tried all of these solutions. Now I tried virtualbox with XP and still no luck. What seems to be happening is that Windows 8.1 cannot even hand off my phone to the virtualbox USB controller because I am getting that error that the device malfunctioned. I've also put a filter to catch all USB devices and enabled/disabled USB 2.0 controller. Any suggestions?
A little foreshadow. I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install. I was silly and decided to clear the system... Which erased my OS completely.
For a while I was able to get to the TWRT(?) screen where I could mount my sd card, etc. While researching the problem I came across this:
a solution of fastbooting a recovery.img
I ran the fastboot recovery.img. The only problem is the only screen I can now access is the bootloader. I have bootloader 1.14.0002 loaded onto my phone if that helps.
Is there anyway to try to get a operating system or flash a rom onto this phone still or is it bricked for good? Also if I was able to put a rom onto it, what do you sugggest?
When I try to go to Recovery or Factory Reset, I get the HTC screen with the red text underneath it and it never goes any further.
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
That is the information listed in my bootloader as of now. I am not showing it listed as a drive in my computer when connected to USB. Also when I 'power off' I am in a reset cycle that doesn't stop.
I really appreciate any help in advance. This was a big wake up call to myself about how I should be a lot more careful when messing with these things.
Thank you to everyone that answers!
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
You might be hosed. Can you get into bootloader?
Sent from my One X using xda premium
Read before doing anything. Such a simple task. It's easy to read, it's hard to come back from a brick.
Sent from my One XL using XDA Premium
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer. http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.0-evita.img
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Not only does fastboot erase cache not take long it avoids many stupid little issues. I would say it's a must when flashing a new recovery.
Sent from my One X using xda app-developers app
sinkthehalffoot said:
I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install.
Click to expand...
Click to collapse
The reason it went to recovery is very simple. The OTA needs to have stock recovery in order to install. You don't have stock recovery on your phone anymore, you have custom recovery (TWRP). So the OTA stalled there, when it didn't find stock recovery.
sinkthehalffoot said:
I was silly and decided to clear the system... Which erased my OS completely.
Click to expand...
Click to collapse
Of course it did, what were you expecting to happen? Wiping the OS is the very definition of what happens when you wipe system. If you didn't know what wiping system would do, you shouldn't have done it. For that matter, you shouldn't be doing anything on your phone if you don't know what its for.
A lot of this points to a fundamental lack of reading and understanding:
- Don't know the name of the custom recovery installed on the system
- Wiping things without knowing what they are
- Basic rule (that many folks here seem to ignore, for reasons unknown): Don't install any OTA on a rooted device without first researching what will happen
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
You aren't bricked. With very few exceptions (and this isn't one of those) if the screen turns on, and you can get into hboot, the phone is recoverable. And probably fairly easily so, with the right steps. But you need to do some homework before proceeding.
redpoint73 said:
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
Click to expand...
Click to collapse
+1000
This is exactly the kind of situation that occurs when people get in over their heads and start blundering around.
http://forum.xda-developers.com/showthread.php?t=2232141
InflatedTitan said:
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer.
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In case anyone ends up stumbling here with a similar issue, this solution worked to a 'T'. Thank you again InflatedTitan.
To everyone else, yes I know, I should of read more than I had. I saw the jellybean update and have been wanting it for a while and acted with haste. I learned a valuable lesson from it all.
Lol this "solution" was around before you posted. You just didn't read or search enough.
Sent from my One X using xda app-developers app
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol :beer:
Sent from my HTC One X using xda app-developers app
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I thought I was the only one. In fact I just rooted a nook tablet and installed twrp. Slides to flash... And I could swear I was on cloud 9.
But bravo on the explanation sir. Love a good write up. Even though i already know it, feels good to read it.
Sent from my Carbon-ize Evita using xda-developers app
[HELP] Not sure if bricked or hardware issue?
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
pharrjw said:
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
exad said:
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
Click to expand...
Click to collapse
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Sent from my HTC One X using xda app-developers app
pharrjw said:
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
Click to expand...
Click to collapse
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Thanks again for the replies guys.
31ken31 said:
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Click to expand...
Click to collapse
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
exad said:
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Click to expand...
Click to collapse
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
pharrjw said:
Thanks again for the replies guys.
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
Click to expand...
Click to collapse
factory reset in bootloader corrupts the SD card. We wont worry about that just yet as there's nothing we can do about it until we can get recovery on there.
You're going to have to be very careful because it sounds like your EMMC partitions might have some issues. if you can get it to bootlaoder KEEP IT AT THAT SCREEN. don't power it off or anything, leave it there. Because one wrong move could be a perma brick. If we can get a rom on there to S-OFF with, we can RUU to restore your emmc partitions.
As the title says: I'm trying to install the 3.18 RUU for my AT&T HTC One X. I'm currently on an old build of CM10.1 (beautifully maintained by H8rift) and was wanting to try the latest build he posted with the 3.4 Kernel. I am S-Off and Unlocked. I searched the forum (internal search seems to be broken at the moment) and all I keep seeing is mostly go to fastboot THEN run the RUU. Well I'm in fastboot (enabled the menu from within CM...less I just misunderstood that completely). Fastboot shows "Fastboot USB" but the RUU still gives Error 170. What did I do wrong?
Running this on a Windows 8 x64 system, installed HTC Sync Manager (still didn't help). I updated the Android SDK Tools to the latest version. My CID is all 1's (as per the S-Off directions). I'm at a loss here hehe.
Ooh I have TWRP 2.4.1.0. And yes I barely post, just always looking, reading, etc.
Is the USB port you're using 2.0 or 3.0? If it's 3.0 (it should have the USB icon and a little ss) try switching to 2.0. Also, try running RUU while not in fastboot.
RollTribe said:
Is the USB port you're using 2.0 or 3.0? If it's 3.0 (it should have the USB icon and a little ss) try switching to 2.0. Also, try running RUU while not in fastboot.
Click to expand...
Click to collapse
Yup running it on my USB 2.0 ports. Tried my case ports and the motherboard ones, same thing. Also just tried it with the phone booted. No dice. Even using the HTC USB Cable (not like there should be a difference but hey, just in case). Maybe I should threaten the phone...with a hammer. (Nah I'm not that mean).
Turbo Mach 5 said:
Yup running it on my USB 2.0 ports. Tried my case ports and the motherboard ones, same thing. Also just tried it with the phone booted. No dice. Even using the HTC USB Cable (not like there should be a difference but hey, just in case). Maybe I should threaten the phone...with a hammer. (Nah I'm not that mean).
Click to expand...
Click to collapse
Is your phone showing up in adb?
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Turbo Mach 5 said:
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Click to expand...
Click to collapse
Hmm... is your USB debugging on? If yes, try reinstalling the driver.
Turbo Mach 5 said:
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Click to expand...
Click to collapse
It seems to me like a driver issue.
if while in fastboot mode fastboot devices does not show the device, The RUU will not work.
uninstall HTC driver and HTC sync and any other phone software (for samsung or whatever else)
Install latest HTC sync
make sure fastboot devices lists your device, then run the RUU
exad said:
It seems to me like a driver issue.
if while in fastboot mode fastboot devices does not show the device, The RUU will not work.
uninstall HTC driver and HTC sync and any other phone software (for samsung or whatever else)
Install latest HTC sync
make sure fastboot devices lists your device, then run the RUU
Click to expand...
Click to collapse
Roll, yah USB Debugging is on hehe. I even turned it off and back on. Exad: Ok. Uninstalling both HTC Sync and Samsung Kies (have to use that for my brother's Galaxy S2 Skyrocket). Uninstalling both now (might have to also run out of town so reply could be a little late).
Turbo Mach 5 said:
Roll, yah USB Debugging is on hehe. I even turned it off and back on. Exad: Ok. Uninstalling both HTC Sync and Samsung Kies (have to use that for my brother's Galaxy S2 Skyrocket). Uninstalling both now (might have to also run out of town so reply could be a little late).
Click to expand...
Click to collapse
Hey you said you were on Windows 8. You may have to manually install the driver to get it work, that's what I had to do. Or you could use the universal adb driver, but if you're gonna RUU, I'd be safe and use the HTC one.
RollTribe said:
Hey you said you were on Windows 8. You may have to manually install the driver to get it work, that's what I had to do. Or you could use the universal adb driver, but if you're gonna RUU, I'd be safe and use the HTC one.
Click to expand...
Click to collapse
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Turbo Mach 5 said:
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Click to expand...
Click to collapse
Annd now when I was all set to update to his latest one he posted, H8rift goes and begins posting nightlies and I don't have to downgrade touchpanel firmware! Hahaha (I had downgraded it and was about to install)! Still, thank you guys. I'm back in business!
Dear Turbo Mach 5,
Could you please provide the detailed steps you followed to RUU your ATT HTC One X.
I am also planning to update my ATT HTC One X with 3.18 RUU to use CM 10.2 based roms.
Please provide this information which will help me to start with my device.
1) Whether we need to re-lock the bootloader ? (I have SuperCID and S-Off)
2) After RUU ing whether we need to unclok the boot loader and root the device if we have SuperCID and S-off?
Thanks and Regards,
Sathish.
Turbo Mach 5 said:
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Click to expand...
Click to collapse
sathish804 said:
Dear Turbo Mach 5,
Could you please provide the detailed steps you followed to RUU your ATT HTC One X.
I am also planning to update my ATT HTC One X with 3.18 RUU to use CM 10.2 based roms.
Please provide this information which will help me to start with my device.
1) Whether we need to re-lock the bootloader ? (I have SuperCID and S-Off)
2) After RUU ing whether we need to unclok the boot loader and root the device if we have SuperCID and S-off?
Thanks and Regards,
Sathish.
Click to expand...
Click to collapse
You don't need to relock your bootloader to the run the RUU because you have s-off. And your s-off status and unlocked bootloader should survive the RUU process. All you need to do afterwards is flash TWRP recovery again, then you can flash a ROM. Please be aware that cm10.2 is still very alpha and multiple users have reported bricks from running it.
Sent from my Evita
Hi timmaaa,
Thank You very much for the clarification and update on cm 10.2 rom.
I was thinking with RUU my bootloader is going to re-lock even though I have S-off.
Thanks and Regards,
Sathish.
timmaaa said:
You don't need to relock your bootloader to the run the RUU because you have s-off. And your s-off status and unlocked bootloader should survive the RUU process. All you need to do afterwards is flash TWRP recovery again, then you can flash a ROM. Please be aware that cm10.2 is still very alpha and multiple users have reported bricks from running it.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm having trouble using the RUU as well. The problem seems to be getting the usb driver for my oneXL working. every time i plug it into my win7 pc, it goes through this installing drivers process but having clicked on "display details", the "android phone" component of the drivers says "failed". I've tried universal adb driver, and HTC usb driver with and without htc sync installed. the HTC sync manager keeps saying there is an update available for usb driver, even though I uninstalled the driver manager and htc sync.
Have not been able to get adb working, when i recently S_OFF my phone I had to use adb over wifi - but it worked.
Any help greatly appreciated, thanks!
Your post is a bit confusing as to which drivers you actually have installed. Download the latest HTC Sync Manager from the HTC One XL page at HTC.com, install it, connect your phone, drivers will install, uninstall HTC Sync Manager but leave drivers installed. Also, make sure you're using a usb 2.0 port and the HTC cable that came with the phone.
Sent from my Evita
thelloydr said:
Hi,
I'm having trouble using the RUU as well. The problem seems to be getting the usb driver for my oneXL working. every time i plug it into my win7 pc, it goes through this installing drivers process but having clicked on "display details", the "android phone" component of the drivers says "failed". I've tried universal adb driver, and HTC usb driver with and without htc sync installed. the HTC sync manager keeps saying there is an update available for usb driver, even though I uninstalled the driver manager and htc sync.
Have not been able to get adb working, when i recently S_OFF my phone I had to use adb over wifi - but it worked.
Any help greatly appreciated, thanks!
Click to expand...
Click to collapse
Scratch that...
Manually installed drivers and i got it working. Had to manual install twice, after one more error (171 this time), the RUU is applied. CM10.2 here i come!
htc vivid
Freinds My HTC vivid is like dead not able to turn on nor charging and not able to run ruu, its showing unrecognized malfunctioned, did uninstall and install of driver still nothing is happening please help.
biradar said:
Freinds My HTC vivid is like dead not able to turn on nor charging and not able to run ruu, its showing unrecognized malfunctioned, did uninstall and install of driver still nothing is happening please help.
Click to expand...
Click to collapse
You're in the wrong section, this is the HTC One XL section, you need to go here:
http://forum.xda-developers.com/htc-vivid
Just had the same issue trying to manually update my M9 to Nougat. Rebooted to download mode (Volume down & Power from off state) and it worked.
Hi guys!
First of all thank you for reading.
I'm probably in my 3rd day lurking around every possible forum and thread looking for an answer to my similar problem but have yet to find one.
I used to have a sensation xe but I kinda smashed the digitizer to bits. before that the was battery swollen and the back case pretty damaged (it survived a 120 kph gps reading of an rc car before going end over end across a parking lot). Meanwhile I got an Htc One, which is superb and I kinda forgot about the old gal.
A few days back I found a guy selling a sensation for spares (the mobo was fried on his) so I just bought that (for 20 euros) and figured all I needed to to was a mobo transplant and then have a nice almost new sensation.
But obviously the digitizer is not calibrated. I found the forum with the tutorial on that but it requires super CID and Soff. Cannot do either of them.
Since the mobo has been replaced the devunlock didn't work. Cannot, for the love of me succeed with the junopunutbear soff with the wire trick. Tried it on a ubuntu live cd, all goes well up until the wire trick. On a side note, I design and build 3d printers for a living, I might be a noob in the android department but that's about it. Even tried an automatic timed relay to do the two wire taps and still nothing. Obviously, it's not working on windows, I found the kgs1992 tool which requires a version of controlbear for windows which I cannot find (found one but it doesn't recognise it when I put it in the tools folder).
tl;dr
Cannot devunlock, cannot soff, nothing. Could I possibly try changing the IMEI so that i can maybe just maybe devunlock it first? I tried putting the mobo back in the old phone, still powered up but didn't recognize the token. I'm pretty much stuck right now.
Any help would be highly appreciated and if you read the whole thing, kudos to you for standing my chatter !
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
rzr86 said:
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
Click to expand...
Click to collapse
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
elktw said:
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
Click to expand...
Click to collapse
did it tell you to be rooted first?
rzr86 said:
did it tell you to be rooted first?
Click to expand...
Click to collapse
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
elktw said:
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
Click to expand...
Click to collapse
just use the temproot.bat file from juopunutbear thread
then run rumrunner again
it is mentioning also in rumrunner thread
Stuck on confirm Unlock bootloader
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
culler said:
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
Click to expand...
Click to collapse
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
elktw said:
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
Click to expand...
Click to collapse
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
culler said:
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
Click to expand...
Click to collapse
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
rzr86 said:
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
Click to expand...
Click to collapse
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
culler said:
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
Click to expand...
Click to collapse
S-OFF requires a working rom so you can't use S-OFF method
with windows 8.1 you will face connectivity issues
type in search box how to set up adb/fastboot in windows 8 but the point is that you don't have enabled usb debugging mode
so i am not sure if you will have any success
by the way what version of TWRP did you flash?
the latest? (2.7.0)
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
culler said:
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
Click to expand...
Click to collapse
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
rzr86 said:
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
Click to expand...
Click to collapse
I tried unbricking project but it hangs on start with connecting to device or waiting for device.
As I understood, it needs to access ADB which i cant succeed.
I dont have JTAG equipment so it goes to some service to see if they could repair it.
It's such a great device, i don't want to lose it so soon
I have an HTC One M7 from sprint that I owned for not even 6 months before it started randomly bootlooping and losing signal. I gave up on it and used it as a paper weight, but now I would like to finally get it functional again as my old phone is no longer usable. I am new to Android devices. I have read thread after thread for the past 2 days and have yet to fix this phone.
I have cleared all caches and done factory resets to no avail.
The phone is stuck in bootloop if it is allowed to restart as normal. Once booted, it will immediately reboot if you swipe to unlock. If you wait, it will display "com.htc.htcdialer not responding" before rebooting again. It does not bootloop if you put it into bootloader/fastboot/recovery whatever you call it. I am trying to just load Android Revolution on to the phone instead of retrying the old OS.
I have already unlocked bootloader. I originally tried to push the androidrevolution.zip to the phone, but ADB gave an "error: device not recognized". I tried to install twrp recovery, but fastboot gets stuck at "waiting on device". I understand I'm having issues with the PC not recognizing the phone. The only android thing in device manager is "Android 1.0" and it has no driver installed. I have installed multiple drivers and tried different ports and cables. I cannot use PDANet to install drivers to recognize it because I cannot get access to the phone to enable debug mode. I cannot use sideloading because I can't get the device to be recognized. Everything I try seems like a constant circle.
I don't know if I'm giving enough information or not. I'll answer any question/give whatever info you need to solve this.
Can anyone please give me any insight as to how I can get my phone to work before I get angrier and break it?
BUMP
Has anyone else been in the same boat? Still struggling to figure this out.
DoostyD said:
BUMP
Has anyone else been in the same boat? Still struggling to figure this out.
Click to expand...
Click to collapse
If its a software related error you can get rid of it by flashing (installing) the stock firmware again. First you ned to check HBoot and CID. Connect your phone in "fastboot" bode, open commandline and type
fastboot getvar all
Post the output here (Delete your IMEI). Then i will get the right firmware for you and can guide you how to install it.
If the error is hardware related (signal loss?!) you probably can't do much on your own. What brings me no the next question: If you had the phone for just 6 month when the errors occured first, why didn't you let the vendor fix it? Phone still had guarantee.
It just says :
Waiting for device
My computer won't recognize the phone properly.
I took my phone to sprint and was told I would have to pay $65 for a used phone replacement, which I thought was ridiculous. I contacted HTC and was told I would have to pay shipping to send it in, and would be a week before I got an answer for it. (Fix it or refurbished one). So I said screw it, and reactivated my old phone. I'd fix it myself eventually.
DoostyD said:
It just says :
Waiting for device
My computer won't recognize the phone properly.
I took my phone to sprint and was told I would have to pay $65 for a used phone replacement, which I thought was ridiculous. I contacted HTC and was told I would have to pay shipping to send it in, and would be a week before I got an answer for it. (Fix it or refurbished one). So I said screw it, and reactivated my old phone. I'd fix it myself eventually.
Click to expand...
Click to collapse
Make sure you install the "fastboot" driver correctly. Are you running win 8.1?
LS.xD said:
Make sure you install the "fastboot" driver correctly. Are you running win 8.1?
Click to expand...
Click to collapse
I'm pretty positive it's installed correctly. I've deleted it and reinstalled it 3 times. The first two times I did it all manually. The one I'm currently running I got from here:
http://forum.xda-developers.com/showthread.php?t=2317790
I am running Windows 7 Home Premium 64bit.
DoostyD said:
I'm pretty positive it's installed correctly. I've deleted it and reinstalled it 3 times. The first two times I did it all manually. The one I'm currently running I got from here:
http://forum.xda-developers.com/showthread.php?t=2317790
I am running Windows 7 Home Premium 64bit.
Click to expand...
Click to collapse
I meant the HTC driver (for fastboot) -> Your devices must be listed as "My HTC" in the device manager. If it has a yellow exclamation mark, try to install the driver manually for "My HTC".
@DoostyD
LS.xD said:
I meant the HTC driver (for fastboot) -> Your devices must be listed as "My HTC" in the device manager. If it has a yellow exclamation mark, try to install the driver manually for "My HTC".
Click to expand...
Click to collapse
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Newyork! said:
@DoostyD
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Click to expand...
Click to collapse
I had done that before but it didn't work. I tried it again but this time noticed a windows protection blocking it. I disabled it and got it all to work now!
I put the new rom on the phone but it gets stuck at the HTC screen and never loads. I read that I have to change the CID and change to S-OFF for it to work.
However, now I've got another problem that I can't find a solution to ANYWHERE.
I cannot get the phone to S-OFF. Everytime I try to change my CID I get this:
C:\Android>fastboot oem readcid
...
(bootloader) cid: SPCS_001
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Android>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Android>
Click to expand...
Click to collapse
I've tried manually changing the CID and using a CID script and both keep giving me the "[JAVACARD_ERR] SD/USBDISK Init error".
Any ideas??
DoostyD said:
I had done that before but it didn't work. I tried it again but this time noticed a windows protection blocking it. I disabled it and got it all to work now!
I put the new rom on the phone but it gets stuck at the HTC screen and never loads. I read that I have to change the CID and change to S-OFF for it to work.
However, now I've got another problem that I can't find a solution to ANYWHERE.
I cannot get the phone to S-OFF. Everytime I try to change my CID I get this:
I've tried manually changing the CID and using a CID script and both keep giving me the "[JAVACARD_ERR] SD/USBDISK Init error".
Any ideas??
Click to expand...
Click to collapse
Is your phone already S-OFF ? Uninstall HTC sync before changing the CID. If you want to flash a unbranded firmware later, make sure that its compatible with your MID.
BTW
Why don't you flash the sprint firmware again to check if your error got fixed.
Here is the link to the current Sprint RUU:
http://www.htc.com/us/support/htc-one-sprint/news/
Sent from my HTC One_M8 using XDA Free mobile app
Newyork! said:
@DoostyD
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Click to expand...
Click to collapse
LS.xD said:
Is your phone already S-OFF ? Uninstall HTC sync before changing the CID. If you want to flash a unbranded firmware later, make sure that its compatible with your MID.
BTW
Why don't you flash the sprint firmware again to check if your error got fixed.
Click to expand...
Click to collapse
No, the phone says it's S-ON. If I uninstall HTC Sync, won't that remove the drivers I needed to get my computer to recognize my phone?
I'm sorry I'm new to this, but what is MID?
I thought about retrying the original sprint firmware but I'd honestly rather just try out a new custom one.
c5satellite2 said:
Here is the link to the current Sprint RUU:
http://www.htc.com/us/support/htc-one-sprint/news/
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
My bootloader is unlocked and I have TWRP recovery. Would I have to remove those to use the Sprint RUU?
DoostyD said:
My bootloader is unlocked and I have TWRP recovery. Would I have to remove those to use the Sprint RUU?
Click to expand...
Click to collapse
Just relock your bootloader to use the ruu BUT if your phone is S-ON you can only RUUs that are newer or the same version number as actually installed on the phone. You can safely uninstall HTC sync, drivers persist.
The RUU link I posted is LP and was just released. Should be newer than what he was running.
Sent from my HTC One_M8 using XDA Free mobile app
c5satellite2 said:
The RUU link I posted is LP and was just released. Should be newer than what he was running.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I checked the RUU myself. Was just a general information and not a "stop, what are you doing?!''
LS.xD said:
I checked the RUU myself. Was just a general information and not a "stop, what are you doing?!''
Click to expand...
Click to collapse
Ok, cool. Just letting him and everyone else know.
Sent from my HTC One_M8 using XDA Free mobile app