:crying: please somebody help me, im desperate, my dad just bought me the htc one x at&t for a gift after my galaxy s 2 got stolen a while back, i had previous exerience rooting, unlocking, and modding basic stuff, the only thing i didnt like about the phone was the multitasking button instead of a menu button, so i rooted it and unlocked the bootloader using the method on onexroot.com and it all worked and i installed twrp recovery, but when i flashed the button remap (cant remember which one) it now gets stuck at the one x screen, i figured this wasnt a problem and i could just download another rom and flash it, but from recovery usb wont moun it get and error something like
something about the sdcard
checking partitions
E: cant mount sd card
E: failed to open lunfile (doesnt exist)
i might be messing up but i am unable to get it to appear in adb always says device not found
am i screwed? am i stuck with a broken rom that cant be fixed?
Please help, it will mean the world to me
Uh read up on ODIN. I used it to get my friends SGS out of a soft brick. I'm not sure if it's for the one x though. What it does is after you put your phone into recovery mode or force pushes a ROM to the SD card then flashes it. Also try googling a tool to force it into recovery. ODIN might I'm not too sure though.
Sent from my HTC One X using XDA
Can you load into the bootloader..?
<Hold power button for ~10 seconds until the buttons flash at the bottom>
<Once its off, hold the power button and the Volume Down [NOT UP = Very bad]>
That should load up the bootloader. Then you can attempt to go into the recovery again OR reinstall it through bootloader.
Now if that doesn't work, You can attempt running the 1.85 RUU from your computer. It <might> overwrite all existing partitions and create a solid and fresh foundation for re-rooting and all.
And to answer your question if you're screwed, in my experience it is almost never an issue to get your phone out of a soft brick as long as you can access some sort of recovery.
Sent from my HTC One X using XDA
heres the rundown
bootloader - yes
recovery - yes
adb - no
fastboot - yes
mount storage - no (makes recovery kinda useless)
i sure hope im not screwed, but since i cant find a way to get a clean rom on the phone i dont see a way to fix it, odin is strictly samsung sadly, and i know nothing about ruu, i dont care about root or anything anymore i just want my phone to work so whatever it takes
Ok, I wasnt sure about ODIN. Try an RUU. Basically an RUU is an .exe or executable file that is almost completely automated that flashes the complete package (Rom, radio, kernel). It might not work depending on what you have installed on windows (drivers and such). You might have to uninstall HTC drivers & sync and try again if that doesn't work install the drivers only then rerun the RUU. RUU is your best bet now. Download one and start the exe. Remember if you're on Mac OSX or linux you're going to have to use a Virtual machine or windows emulator to run the RUU
Sent from my HTC One X using XDA
Pm me if you need further help
Sent from my HTC One X using XDA
i have my mac dualbooted with windows 8 consumer preview, interestingly fastboot doesnt work on the windows end but it does on a mac, im gunna assume i did more than one thing wrong when i previously tried (failed to detect device) to ruu it, where do i get the ruu, where do i get the drivers, and if i use a virtual machine do i need the drivers?
your help is much appreciated
Mac OSX is not the right platform to be using nor is windows 8 (because it is unproven and still in beta). I would recommend using a fresh installation. If you have a windows 7 .ISO you can install it and use it for 30 days before they lock you out with out a key.
Here is a helpful tool to install it as fast as possible VIA USB (provided you have a >4GB drive) http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool
If you are running Mac OSX here is an XDA developers guide for linux (Mac OSX is based off of Free BSD a linux distribution) by Jeepfreak. The process will differ some but not a lot.
Here it is....
http://forum.xda-developers.com/showthread.php?t=1668156
I want to emphasize NOT using Windows 8... It is unproven Beta software....
i have a computer i can use, it has vista, but i would need to go where i can get wifi and know the exact files i need to download as i have a horribly slow connection off a mifi card an am pushing my cap as it is, if you could tell me exactly what to download and run i would be increadibly greatful
http://forum.xda-developers.com/showthread.php?t=1649658 This is still rootable
or
http://forum.xda-developers.com/showthread.php?t=1644338 This is the RUU the phone likely shipped with
Transfer the RUU's to your Vista comp using a USB drive.
Make sure you don't have HTC Sync or if you do it is not running in the background.
ok so i download the ruu, got that, i think i have the android sdk on that computer, will that cover any drivers i need? and for the ruu what to i have to do on the phone end?
i ran "fastboot getvar version-main" and it returned "version-main: 1.73.502.1" will the difference between .502 vs .502.1 make a differnece?
Shouldn't make a difference.... And i would try running the RUU first then download the necessary drivers if that doesn't work...
Jtn.Siren said:
i ran "fastboot getvar version-main" and it returned "version-main: 1.73.502.1" will the difference between .502 vs .502.1 make a differnece?
Click to expand...
Click to collapse
The .1 is for att. But you'll want to run the ruu in fast boot that's either the same version or a higher version like 1.85.502.1.
Sent from my HTC One X using xda premium
thank you so much thus far, as a matter a fact i already have the 502.1 downloaded, could you please explain to me any drivers, files, and commands i will need to execute this
dkirchik said:
The .1 is for att. But you'll want to run the ruu in fast boot that's either the same version or a higher version like 1.85.502.1.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes but if he trys to root it all bets are off unless he did superCID. I would recommend the first RUU I posted
---------- Post added at 12:24 PM ---------- Previous post was at 12:22 PM ----------
Jtn.Siren said:
thank you so much thus far, as a matter a fact i already have the 502.1 downloaded, could you please explain to me any drivers, files, and commands i will need to execute this
Click to expand...
Click to collapse
The drivers you can get off of htc's website under ATT ONE X, or just search XDA for them...
You do not need any commands to run an RUU. Like I said it is completely automated...
and what mode on the phone off, bootloader, fastboot?
Jtn.Siren said:
and what mode on the phone off, bootloader, fastboot?
Click to expand...
Click to collapse
Try Bootloader then Recovery. It usually does it for you though if you were booted into a ROM.
Jtn.Siren said:
and what mode on the phone off, bootloader, fastboot?
Click to expand...
Click to collapse
Irish has it right and fastboot make sure the fasboot USB is there. Then open and run the RUU and you're golden.
Sent from my HTC One X using xda premium
Related
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
you are lucky to have white screen
You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium
xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.
vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...
xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.
can anyone please help
Where can I get stock recovery, stock boot for the phone?
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^
thanks for the reply, however ur link is broken.
And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??
Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though
xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up
I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app
Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.
Hello.
I could really do with some help, please.
I have a HTC Desire S, completely stock standard, un-rooted, s-on etc etc, and it i stuck on the hboot/fastboot.
First off it became unresponsive, so pulled the battery and tried restarting it. It bootlooped a few times, so decided to use volume down/power buttons and tried fastboot then recovery. I can't remember what it did in those options as it was a few days ago now and I've been trying to find a solution since.
Anyway, I eventually did a factory reset from hboot and that seemed to do the trick for about an hour after which it crashed and entered the state it's in now.
The only thing it'll do is boot into fastboot. It doesn't matter what option I choose, it shows the android on a skateboard and returns to fastboot. The only thing it'll do is power down.
The phone is un-rooted, s-on.
The only details I have are on the fastboot screen which says
*** LOCKED ***
SAGA PUT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-BOOT
Oh and if I plug in into my Mac, it says "Fastboot USB" & "hboot USB plug" but not seen on by the Mac.
Help. Please.
I've bricked it, haven't I?
Unlock the bootloader through htcdev, flash a custom recovery, flash a ROM (see sticky guide for more details). Or Run a RUU , use windows
Sent from my HTC Desire XS using xda app-developers app
razi914 said:
Unlock the bootloader through htcdev, flash a custom recovery, flash a ROM (see sticky guide for more details). Or Run a RUU , use windows
Sent from my HTC Desire XS using xda app-developers app
Click to expand...
Click to collapse
htcdev wont work because adb is not working, and he'll keep getting "fail to verify signature" error. or the screen will stuck on "Waiting device"
I'm having the exact same problem, and I'm trying to fix it since yesterday...
Have you tried running an ruu?
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde
I've tried plugging it into a windows machine with the same results - nothing.
I'm at work at the moment so don't have time to read the sticky mentioned (I will do later this evening), but I've run adb (on mac and windows) and it doesn't find a device.
I cannot 'get onto' the device, via USB or sd card, to do anything with it. I would've tried running RUU's and whatever but all the guides need the phone to be seen by a computer or run something from an sd card.
I've even tried swearing at it while gesticulating angrily..
I'm hoping you guys are going to tell me it's not an ineffectual doorstop just yet, but I fear it may be so.
biloz_nexus said:
htcdev wont work because adb is not working, and he'll keep getting "fail to verify signature" error. or the screen will stuck on "Waiting device"
I'm having the exact same problem, and I'm trying to fix it since yesterday...
Click to expand...
Click to collapse
no, no need for adb ,, only fastboot ,
u should install the drivers on windows , then type in adb/fastboot cmd 'fastboot devices' (ur phone should be in fastboot mode) unlock the bootloader (baby easy) please read this guide [Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002 not so hard, OR run a ruu through fastboot
edit: use windows 7 , it will automatically install the drivers
I shall have go at that tonight and let you report back.
Thank you.
Sent from my GT-I9305 using xda app-developers app
sim-o said:
I shall have go at that tonight and let you report back.
Thank you.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
What windows os are you using
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde
jugg1es said:
What windows os are you using
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde
Click to expand...
Click to collapse
err, either Vista or 7. The wifes laptop is 7, but she'll probably be busy with something important like facebook, and the other win machine I think is Vista.
or 7.
maybe...
If I've gotta download drivers, I've gotta download drivers.
sim-o said:
err, either Vista or 7. The wifes laptop is 7, but she'll probably be busy with something important like facebook, and the other win machine I think is Vista.
or 7.
maybe...
If I've gotta download drivers, I've gotta download drivers.
Click to expand...
Click to collapse
Only asked because win8 has issues installing the driver's
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde
If you pulled the battery and that's when the problems started, you might have bricked the emmc. In that case you do NOT want to unlock.
Verify that your emmc is OK first before unlocking through htcdev!
Ah, I think I read some mention that in another thread I read.
So, first check the emmc is ok then follow the guide mentioned above if it's ok.
Sent from my GT-I9305 using xda app-developers app
Can't find out how to check if emmc is fried or not.
Can't get PC to see phone.
Can't even get chuffing drivers installed on the chuffing PC:
"HTC Sync - InstallShield Wizard
The installation of HTC Driver Installer 4.0.1.001 appears to have failed"
grrrr
Thanks for you're suggestions, gentlemen. but I think I'm just gonna take a sledge hammer to the phone and the pc.
try another computer?
razi914 said:
try another computer?
Click to expand...
Click to collapse
I will, just not tonight. It's been a bad week for me and dodgy tech. I'll try again tomorrow or Sunday.
For the record, I've tried another computer and HTC Driver Installer 4.01.001 failed again.
This is ridiculous.
Unless someone has a link to the drivers form somewhere other HTC, which I doubt, I'll be back, but I could be sometime.
Try a computer running win 7 , dont download any drivers, make sure internet connection is okay on pc, just connect ur phone in fastboot mode with PC, it will automattically download drivers,, also install htc-sync
Sent from my HTC Desire XS using xda app-developers app
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?
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
bimplebean said:
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
Click to expand...
Click to collapse
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
glevitan said:
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
Click to expand...
Click to collapse
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
you can run the RUU exe file from fastboot usb
glevitan said:
you can run the RUU exe file from fastboot usb
Click to expand...
Click to collapse
It's an EXE. How do I run that from fastboot?
bimplebean said:
It's an EXE. How do I run that from fastboot?
Click to expand...
Click to collapse
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
glevitan said:
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
Click to expand...
Click to collapse
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
bimplebean said:
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
Click to expand...
Click to collapse
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
glevitan said:
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
Click to expand...
Click to collapse
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
bimplebean said:
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
Click to expand...
Click to collapse
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
bananagranola said:
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
Click to expand...
Click to collapse
I apologize, this is not my strong suit. I've been through so many things I'm not sure I remember all the things I've tried. I think I tried flash the recovery with Ace Hack Kit.
Let me describe what I DO know.
I can boot in to Fastboot (Vol Down + Power)
Here's what it says:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011, 00:55:45
There is no LOCKED or UNLOCKED indicator at all.
I'd he happy with an RUU stock ROM, but when I try to re-run the RUU from my computer, the system tries to reboot the phone into the bootloader. This is when I get the HTC screen and it just sits there. The RUU program reports a connection error.
I have several ZIP files, one for the Froyo image, one for the Gingerbread one, they're supposed to be for this phone.
I tried to reload the Gingerbread one from the SD card (I renamed it update.zip) but it failed. I booted into fastboot, then selected Recovery. While I had the green symbol I waited...after a bit it went to HTC screen and froze.
Tried again - this time when I had the green symbol I pressed vol up + power and got to the recovery options.Here's what I see
formatting / data
can't open /data/cwpkg.zip
can't open /data/cw.prop
can't open /cache/cwpkg.zip
can't open /cache/cw.prop
formatting /cache.....
Then I get the blue list of options. I select apply update from SDCard...
-- Invalid Operation ---
Then it reboots into the HTC screen and stays there.
Suggestions?
would love a copy of your file...
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
pharoah1974 said:
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
Click to expand...
Click to collapse
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
glevitan said:
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
Click to expand...
Click to collapse
Thanks. I will try that.
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.