Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
So does it power on at all?
Sent from my Evita
timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!
Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Hi from Canada!... I just wanted to be part of the greetings.. :laugh:
exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)
I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.
My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita
timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:
Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now
Related
Tried this but I have this error after Fastboot :
HBOOT > FASTBOOT > no image or wrong image
also, tried factory reset but it just freeze or nothing happens after I chose FACTORY RESET.
Please help.
MarlX said:
Tried this but I have this error after Fastboot :
HBOOT > FASTBOOT > no image or wrong image
also, tried factory reset but it just freeze or nothing happens after I chose FACTORY RESET.
Please help.
Click to expand...
Click to collapse
Some questions, is your phone a standard DESIRE S, S-ON, with standard HBOOT etc?
I'd wait for someone with more Android experience than myself to confirm this, but, I believe that you should attempt to re-flash your original ROM (RUU). Which you should hopefully find somewhere in this post http://forum.xda-developers.com/showthread.php?t=1002506
ben_pyett said:
Some questions, is your phone a standard DESIRE S, S-ON, with standard HBOOT etc?
I'd wait for someone with more Android experience than myself to confirm this, but, I believe that you should attempt to re-flash your original ROM (RUU). Which you should hopefully find somewhere in this post http://forum.xda-developers.com/showthread.php?t=1002506
Click to expand...
Click to collapse
Thanks for the reply.
It's S-ON, this is untouched so I guess standard HBOOT?
Is flash(ing) ROM can be done even phone is not rooted?
Also, been searching around and found this (almost) same problem encountered, regarding "No image...", but I'm hesitant coz now I have to start from scratch again after that(?). :/
http://forum.xda-developers.com/showthread.php?t=648864
MarlX said:
Thanks for the reply.
It's S-ON, this is untouched so I guess standard HBOOT?
Is flash(ing) ROM can be done even phone is not rooted?
Also, been searching around and found this (almost) same problem encountered, regarding "No image...", but I'm hesitant coz now I have to start from scratch again after that(?). :/
http://forum.xda-developers.com/showthread.php?t=648864
Click to expand...
Click to collapse
You should be able to flash an official HTC ROM, without ROOT. Although if you are operator locked ie T-Mobile/Vodafone etc you may have to install one of their ROMS. Although I'm a little out of my depth/comfort zone with all this...
I may be well off the mark here, but, have you tried it, without your SD card inserted? give it a go?
What you found is related to something different. and related to image files stored on your SD card used for updating....which is what made me make the above suggestion.
After a factory reset you will have to start a fresh anyway.
Ohh. So it's not related.
My phone looks like this :
SAGA PVT SHIP S-ON RL
HBOOT-0. 98. 0000
RADIO-38. 03. 02. 15_M
e-MMC-boot
Mar 10 2011, 14:58: 38
HBOOT
vol <up>......
vol <down>......
POWER
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
FASTBOOT goes to BOOTLOADER menu which shows me the "No image..."
RECOVERY works but then after the process it turns off, and vibrate several times.
FACTORY RESET if selected, nothing happens, like it froze or something.
Did you try it without an SD as suggested?
The IMAGE errors I think (but could be wrong) are as a result of FASTBOOT auto checking for the existence of update files on your SD and simply not finding any!
Does it say Checking.....
If you select FASTBOOT then REBOOT what happens? Phone hangs? with what screen?
Hopefully someone else will add some advice soon?
ben_pyett said:
Did you try it without an SD as suggested?
The IMAGE errors I think (but could be wrong) are as a result of FASTBOOT auto checking for the existence of update files on your SD and simply not finding any!
Does it say Checking.....
If you select FASTBOOT then REBOOT what happens? Phone hangs? with what screen?
Hopefully someone else will add some advice soon?
Click to expand...
Click to collapse
Yes, I did. It's same.
If I put the SD in it, when chosing FASTBOOT the errors looks like the attachment in this topic : http://forum.xda-developers.com/showthread.php?t=703761
Yes it say Checking...
Doing FASTBOOT then REBOOT shuts down the phone then restarts it and hangs at the green HTC logo.
I really wish someone can help me.
BTW, regarding the ROM's you provided above, what do you suggest is the one for me? I really don;t have any idea. I'm from Asia (Philippines) and phone is not locked by a mobile carrier.
MarlX said:
Regarding the ROM's you provided above, what do you suggest is the one for me? I really don;t have any idea. I'm from Asia (Philippines) and phone is not locked by a mobile carrier.
Click to expand...
Click to collapse
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Same problem
I had the same problem much times!
I had to Factory Reset my phone every time it freezes!
When i did a factory reset, it was all ok until it appeared again
The only solution i found was to factory reset the phone..
ben_pyett said:
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Click to expand...
Click to collapse
Yes, I also did that. Unfortunate, nothing happens, if it does not froze it boots to that green HTC logo and stops there.
I guess the only solution is to bring this to the store where I purchased it.
ben_pyett said:
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Click to expand...
Click to collapse
Yes, I also did that. Unfortunate, nothing happens, if it does not froze it boots to that green HTC logo and stops there.
I guess the only solution is to bring this to the store where I purchased it.
MarlX said:
I guess the only solution is to bring this to the store where I purchased it.
Click to expand...
Click to collapse
Did you read the very similar sounding thread that I found http://forum.xda-developers.com/showthread.php?t=1107016&highlight=boot? unfortunately this is what that person ended up doing
If someone can advise which ROM would be the best for you to select then I'd possibly try that before returning it?
Good luck...
I've seen another user @Skanob also from the Phillipines, if you look at the details within his signature in the following post http://forum.xda-developers.com/showpost.php?p=14748687&postcount=4 you should see details of the RUU ROM that you can/should try to flash.
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
MarlX said:
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
Click to expand...
Click to collapse
I'll be perfectly honest, I don't know if this voids warranty....sorry..
Ultimately, you're only putting back the same ROM as the phone has on it originally, but, bear in mind that in the other thread I posted above, re-flashing the original ROM didn't resolve the issue, so if there's any doubt that this might void the warranty - don't do it!
MarlX said:
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
Click to expand...
Click to collapse
Flashing RUU won't void the warranty. How long are you waiting on the htc logo screen? It can take a while after factory reset...
It might be that some files were corrupted so flashing RUU should help. If not, connect your device to computer and see what logcat is showing
Sent from my HTC Desire S using XDA App
The longest was 25 minutes, then had it reboot again coz nothing happened. Also, when doing the Factory Reset it just hangs/do nothing, can't choose any option from the menu, have to remove the battery to turn the device off.
I'm gonna bring the phone to the service center in a while.
Hi guys, a little background :
I S-Off'd my Desire S a few weeks ago and installed/clicked gingerbread which i gather roots it?
One day my screen went blank randomly with just the notification bar showing up top. No buttons worked, couldn't turn it off etc.. so I did a battery pull. It then got stuck on the HTC screen, so I googled, tried clicking recovery/factory reset etc.. all while not really knowing what i was doing, but in the end it randomly loaded after a long wait.
Phew, or so I thought.
Now it constantly crashes, turns itself off, the camera doesn't work, force closes galore.. it's a mess. Figured the battery pull messed something up.
Searched a bit more and figured i should try and flash a ROM which might fix it and get it stable again.
Tried installing using 'download ROM' in Rommanager, it did all the installing and whatnot, but when it rebooted nothing had changed. Tried three times, same deal. Figure I should install a ROM via the SD card instead.
Found this forum and a relatively simple/safe guide :
I'm using the guide here : How to flash a perfect ROM.
http://forum.xda-developers.com/showthread.php?t=1257731
The Rom is MIUI.
However, I'm only on step 2 : Format data. (Formatting /system was fine)
Clockworkmod says Formatting /data for about 5 minutes, then : Error formatting /data.
Help!
A big thanks in advance.
Spare yourself a lot of troubles - use RUU and start fresh...
Sent from my HTC Desire S using XDA App
Could be a faulty eMMC chip on the phones motherboard, these tend to break after a few bad battery pulls?
If installing a new ROM on the phone wont work and you get data format problems I would do as posted above. If this doesnt work I would suggest a faulty eMMC chip.
amidabuddha said:
Spare yourself a lot of troubles - use RUU and start fresh...
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Is there a fairly easy to follow guide that includes every step on here?
According to the FAQ I might have a fried chip.. the e:Unable to mount errors.
Can I still save it with the RUU?
I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?
I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.
Much appreciated.
wax_addict said:
Is there a fairly easy to follow guide that includes every step on here?
According to the FAQ I might have a fried chip.. the e:Unable to mount errors.
Can I still save it with the RUU?
I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?
I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.
Much appreciated.
Click to expand...
Click to collapse
Since you still can boot into your system you are good.
Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:
1) use Revolutionary
2) no need of Gingerbreak since you will flash a rooted ROM
3) flash custom ROM from recovery
amidabuddha said:
Since you still can boot into your system you are good.
Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:
1) use Revolutionary
2) no need of Gingerbreak since you will flash a rooted ROM
3) flash custom ROM from recovery
Click to expand...
Click to collapse
Ok, I have the RUU downloaded.
Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?
Soooo.. plug in USB cable, run the RUU file in Windows.. should work?
Cheers again.
wax_addict said:
Ok, I have the RUU downloaded.
Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?
Soooo.. plug in USB cable, run the RUU file in Windows.. should work?
Cheers again.
Click to expand...
Click to collapse
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone
amidabuddha said:
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone
Click to expand...
Click to collapse
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR
I can't get into the phone to go into settings and turn USB debugging on though As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?
All I can get is HBOOT/ClockworkMod.
Tried RUU with the HTC white screen on and also while in Clockwork Mod.
Anything else I could try?
Thanks.
Are you using windows?
If yes download HTC sync and instal it, could be a missing driver.
Swyped from my Desire S
wax_addict said:
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR
I can't get into the phone to go into settings and turn USB debugging on though As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?
All I can get is HBOOT/ClockworkMod.
Tried RUU with the HTC white screen on and also while in Clockwork Mod.
Anything else I could try?
Thanks.
Click to expand...
Click to collapse
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon
amidabuddha said:
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon
Click to expand...
Click to collapse
It worked, can't thank you enough!!
Cheers all.
wax_addict said:
It worked, can't thank you enough!!
Cheers all.
Click to expand...
Click to collapse
Good to know
Congratulations!
great to read another XDA forum rescue complete successfully!
Please update post#1 (using Go advanced edit) and prefix the post title with [SOLVED] to indicate that the problem is resolved.
Tectas said:
Are you using windows?
If yes download HTC sync and instal it, could be a missing driver.
Swyped from my Desire S
Click to expand...
Click to collapse
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed.
wax_addict said:
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed.
Click to expand...
Click to collapse
If your intending on re-running revolutionary to S-OFF your device again then you must first de-install the program HTC SYNC from your PC, don't worry the drivers are left behind and there are all that you need.
This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...
I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum
Could be true.
I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.
Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.
Swyped from my Desire S
Tectas said:
Could be true.
I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.
Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.
Swyped from my Desire S
Click to expand...
Click to collapse
I will write a "calming" thread besides the Guide that is in my signature or as a part of it, just waiting for more confirmations that generally the chip is not affected when there is an error. But it seems not much people are reading the guides they prefer to start a new thread...Anyway I have a friend that is working at a centre of a Mobile Operator for my country and according to him among the hundreds (!) Nokia's, Samsung's, etc., he got only one faulty HTC for repair for the last 2 years (and there is a practice to replace rather than repair as well)
amidabuddha said:
This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...
I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum
Click to expand...
Click to collapse
Good point although hopefully any new user experiencing this problem for the first time will create a post in this forum and can get pointed in the right direction, or better still there's always the hope that they will look at the INDEX/GUIDES themselves and read some of the resources that have been made available for them to use.
Possibly create a list of most likely resolution strategies in a new thread so that they can be tried in order and I'll refer users to that in the section on eMMC issues at the bottom of the INDEX thread, where I've tried not to scare users into thinking that its all too late and its game over in the textual intro bit!
ben_pyett said:
...
Possibly create a list of most likely resolution strategies in a new thread ...
Click to expand...
Click to collapse
Yep. My "[GUIDE] Read this before going for eMMC replacement" is updated with the solutions that worked so far..
Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help
If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.
You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium
ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?
I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..
The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?
Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help
Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.
Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff
Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX
THAT is AWESOME
Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2
Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .
Heh it must have been so
Sent from my HTC One X using Tapatalk 2
Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??
That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.
CNexus said:
Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??
Click to expand...
Click to collapse
I've had that happen a couple times but it was because it was something I did/flashed, I agree with prboy, ruu back and format memory card (save your stuff to the computer first)- I've forgotten to save first a couple times
prboy1969 said:
That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.
Click to expand...
Click to collapse
I'll definitely try that, I don't know if this shed anymore light on it but my sdcard doesn't mount through my phone anymore either...happened around the same time as the restarting thing
But I'll tr and see what happens, if not I'll just take it in to sprint, I know it can't be something I flashed, I've been on stock for a while because of my utility
Sent from my PG06100 using xda premium
I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.
prboy1969 said:
I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.
Click to expand...
Click to collapse
Nope, no custom anything. 100% stock 2.2 with temproot, but since I can't reboot its really permroot lol
Sent from my PG06100 using xda premium
Then I would defiantly try what I stated above. See if it can resolve the issue.
prboy1969 said:
Then I would defiantly try what I stated above. See if it can resolve the issue.
Click to expand...
Click to collapse
Will do
Sent from my PG06100 using xda premium
Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
KiDxNinja said:
Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Click to expand...
Click to collapse
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?
prboy1969 said:
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?
Click to expand...
Click to collapse
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Have you tried booting it up while connected to a USB cord? That works for me because my phone will otherwise go into a bootloop whenever I restart it
Sent from my PG06100 using xda premium
KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?
prboy1969 said:
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?
Click to expand...
Click to collapse
Yes and Yes, read my first post -_-
KiDxNinja said:
Yes and Yes, read my first post -_-
Click to expand...
Click to collapse
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.
KiDxNinja said:
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.
Click to expand...
Click to collapse
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I was just about to say that, if the name of the file isn't correct, the bootloader won't pick it up.
Yeah i know, i was just too lazy to type it out. I know what im doing as far as general modding and flashing, and I actually managed to fix it. I'm not positive how but I used the unroot back to stock guide for the stock locked bootloader. After flashing it through hboot I tried the 2.3.4 RUU. Still bootlooped but I was at stock with locked bootloader. I then used htcdev to reunlock the bootloader and I was then able to flash partitions through fastboot. I flashed cwm and was able to adb through it. I basically just reran through the rooting phase and gained temproot. From here I redid the steps to engineer hboot and finally received s-off. After this it booted normally. I might be leaving steps out but if anyone needs specifics, just pm me and maybe I can figure it out again for you.
Sent from my PG06100 using Tapatalk 2
help with boot loop loop loop
hi
someone can help whit phone?
in summer i restart phone and it stuck in loop htc logo in white over and over agen
till batrtery go down and nothing happen when trying to charg only led was flashing
no to long ago i plug to charger ad phone torn back on, sd card was out
I turn it off put sd card back on phone turn back on, try to software update one and second time it go back to loop agen=[
rand battery down agen and it does not torn back on, to hboot
well it does if i play whit it holding power bottom volume down longer time
speed xe ship s-on
hboot-0.99.0001
radio-1.08.01.0111
emmc-boot
can some one give me step by step instruction?
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.