I bricked my evo, after trying hboot downgrade I reinstalled to 2.17 from 2.08 then i brick him by instruction in downgrade topic, and then by all instructions i get stuked with "waiting for device..."
tryed downgrade CD, and normal files, doesn't work anything
on Windows connect device manager shows QHSUSB_DLOAD
i have very very dim red light on connection for 10 sec i think
don't boot, not normal, not recovery, not bootloader
and ./brickdetect.sh said same thing Device can't be detected
used ubuntu 12.10, 10.10 and will try on 12.04
- device manager shows QHSUSB_DLOAD
- when I tried your method, the first step I get ./brickdetect.sh Device can't be detected. Check connections
- i'm sure that it was S-ON 1.50 and original cable of HTC
fastboot doesn't shows anything too (coz of not in bootloader ?)
anyone have ideas about this?
thx for help and sry for my bad english
I never tried 12.10 or 10.10 but it worked perfectly when I tried unbricking on 10.04 64bit and 12.04 32bit (ran over my first phone with an atv, had to reroot my next one lol)
edit: I highly recommend using juopunutbear though, if/when you recover your phone from its bricked state. jbear is far easier to do. it sounds daunting when you read thru the instructions but it's actually quite simple.
edit #2: you made sure the SD card and battery were not in the phone while trying to use the detect command right?
why you think that 1.50 s-off without downgrade is better?
and first tried to restore it with CD and without Battery, then i remove all, and next, coz of failes, tried different variants...
edit: i hear that wire trick, that used in joupunutbear instruction, is not stable too... ;(
PsychoGod said:
why you think that 1.50 s-off without downgrade is better?
and first tried to restore it with CD and without Battery, then i remove all, and next, coz of failes, tried different variants...
edit: i hear that wire trick, that used in joupunutbear instruction, is not stable too... ;(
Click to expand...
Click to collapse
Where did you hear that? I have yet to hear of an Evo 3D that was not recoverable, even if the wire trick was unsuccessful, unless there was a pre-existing hardware problem. Some people try the hboot downgrade or wire trick as an attempt to fix problems that are hardware related like the digitizer failing and neither is going to do that.
With the 2.89.651.2 Sprint ICS build installed the downgrade method got more complicated because now you have to "brick" the phone twice. I definitely agree that either method will work on the CDMA Evo 3D but for most users the wire trick is simpler and easier. AFAIK there is no hboot downgrade method for the GSM model.
ramjet73
thx for explanation
i would try to recover it and write here what i would have
PsychoGod said:
I bricked my evo, after trying hboot downgrade I reinstalled to 2.17 from 2.08 then i brick him by instruction in downgrade topic, and then by all instructions i get stuked with "waiting for device..."
tryed downgrade CD, and normal files, doesn't work anything
on Windows connect device manager shows QHSUSB_DLOAD
i have very very dim red light on connection for 10 sec i think
don't boot, not normal, not recovery, not bootloader
and ./brickdetect.sh said same thing Device can't be detected
used ubuntu 12.10, 10.10 and will try on 12.04
- device manager shows QHSUSB_DLOAD
- when I tried your method, the first step I get ./brickdetect.sh Device can't be detected. Check connections
- i'm sure that it was S-ON 1.50 and original cable of HTC
fastboot doesn't shows anything too (coz of not in bootloader ?)
anyone have ideas about this?
thx for help and sry for my bad english
Click to expand...
Click to collapse
in the unlimited.io site there is a sextion to explain how to corrext the QHSUSB_DLOAD error... although the evo 3d isnt listed it doesnt hurt to try it? if it works great proceed on if not then youre still in the same spot as before...
i think that this is not a good idea, PblClear can break boot at all if it isn't compatible...
but i'm not sure, anyway tomorrow will try to restore it one more time
same boat
PsychoGod said:
i think that this is not a good idea, PblClear can break boot at all if it isn't compatible...
but i'm not sure, anyway tomorrow will try to restore it one more time
Click to expand...
Click to collapse
How is going got same issue,wondering is you solved or what is going on?
Related
I was upgrading my rom from 1.76.110.6 to 2.73.110.26. Unfortunately my pc went off and my rom upgrade got failed. Now my phone screen is displaying as follows:
HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.04.25
Jul 3 2009, 15:22:21
RUU
at the end of the screen in the image of a chip with cross sign on it)
Please help me with a solution for it. Please be kind to explain in detail from scratch, as i am not much a tech savy guy.
usmaggu said:
I was upgrading my rom from 1.76.110.6 to 2.73.110.26. Unfortunately my pc went off and my rom upgrade got failed. Now my phone screen is displaying as follows:
HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.04.25
Jul 3 2009, 15:22:21
RUU
at the end of the screen in the image of a chip with cross sign on it)
Please help me with a solution for it. Please be kind to explain in detail from scratch, as i am not much a tech savy guy.
Click to expand...
Click to collapse
I think you are lucky, as fastboot is working, so the spl is alive
Do you use a custom ROM and recovery? If not, run the update program again, and try to see if it sees the phone and does it right.
Failing that, we can help you boot amonra via fastboot and get a custom ROM on that way.
anon2122 said:
I think you are lucky, as fastboot is working, so the spl is alive
Do you use a custom ROM and recovery? If not, run the update program again, and try to see if it sees the phone and does it right.
Failing that, we can help you boot amonra via fastboot and get a custom ROM on that way.
Click to expand...
Click to collapse
I downloaded the update for Hero (T-Mobile) from HTC UK website. Now, when i run the updater again, the error says that the USB cable is not connected with either phone or computer. But the phone screen displays RUU USB, whereas my computer is not detecting any USB device.
It is just the driver is wrong. Check out my driver guide to change the driver to MyHTC for the fastboot mode.
btdag said:
It is just the driver is wrong. Check out my driver guide to change the driver to MyHTC for the fastboot mode.
Click to expand...
Click to collapse
But how should i start with this position, as even usb connection is not working. Kindly tell how to start with first step.
usmaggu said:
But how should i start with this position, as even usb connection is not working. Kindly tell how to start with first step.
Click to expand...
Click to collapse
Just follow those instructions he linked at http://forum.xda-developers.com/showthread.php?t=647353
They will work fine. Just do as they say and you will be sorted
You must have some sort of USB showing up - its probably just under the wrong name - i.e. unknown device or something. Either that or your USB port is broken on your computer/phone or the cable is broken.
Just reset
I had the exact same problem (different cause - I clicked restart computer), but same ROM on T Mobile UK. I just reset the phone: removed battery; held down back button and power button simultaneously; inserted battery. Phone came up with the option to reset, selected it, and returned to normality.
Okay, here is my problem. First off I am stuck at the HTC quietly brilliant boot screen after I successfully unlocked the bootloader. Then I tried to root the device with rootbootv5 and as i was following the instructions it was trying to backup the phone and got stuck "waiting for the device". Now my computer does not recognize the phone and when i try to factory reset it just goes back to being stuck.
Also when I go into HBOOT it is stuck "checking SD card update" until i unplug the usb cord. When entering recover from HBOOT it just goes to a triangle with a exclamation mark.. This is a AT&T phone if that matters as I have already done some research and it seems it might.. Just got this awesome phone today and I would like to fix this problem if anyone could help I would appreciate it.
treefetty said:
Okay, here is my problem. First off I am stuck at the HTC quietly brilliant boot screen after I successfully unlocked the bootloader. Then I tried to root the device with rootbootv5 and as i was following the instructions it was trying to backup the phone and got stuck "waiting for the device". Now my computer does not recognize the phone and when i try to factory reset it just goes back to being stuck.
Also when I go into HBOOT it is stuck "checking SD card update" until i unplug the usb cord. When entering recover from HBOOT it just goes to a triangle with a exclamation mark.. This is a AT&T phone if that matters as I have already done some research and it seems it might.. Just got this awesome phone today and I would like to fix this problem if anyone could help I would appreciate it.
Click to expand...
Click to collapse
I am almost positive "rootboot" is not for the AT&T phone. Even if it is I would strongly suggest avoiding it. Try relocking the bootloader and running the RUU
Forgot to mention
Forgot to mention after the other actions I tried to use X-Factor to root the device and it said something to the extent that maybe adb was out of date and something about the CID sorry I am not very knowledgeable about this stuff guys..
X factor is for a completely different device, it does a temp root then supercids the device (HTC one xl)
Why don't you just unlock the boot loader and flash a recovery?
Slithered from my HTC One X+
Kraizk said:
I am almost positive "rootboot" is not for the AT&T phone. Even if it is I would strongly suggest avoiding it. Try relocking the bootloader and running the RUU
Click to expand...
Click to collapse
Thank you very much for the reply,
How do i relock the bootloader and I dont even know what a RUU is :/.
the computer wont even recognize the phone, if i try something it just says "waiting on device"
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
treefetty said:
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
Click to expand...
Click to collapse
fastboot oem lock to lock bootloader.
search the forums for the HTC ONE X+ RUU for AT&T It is a .exe file. Put phone in boot loader and run it.
Finally found it after searching through google here:
http://forum.xda-developers.com/showthread.php?p=34744228&posted=1#post34744228
I am not sure what to do after I've downloaded it. Is there some code I put in when I am in cmd and fastboot? or just run the RUU exe when the phone is in fastboot? I am out of me league, and everything was going so well with the bootloader unlock...
Thanks to all who are helping me!! :good:
treefetty said:
Finally found it after searching through google here:
http://forum.xda-developers.com/showthread.php?p=34744228&posted=1#post34744228
I am not sure what to do after I've downloaded it. Is there some code I put in when I am in cmd and fastboot? or just run the RUU exe when the phone is in fastboot? I am out of me league, and everything was going so well with the bootloader unlock...
Thanks to all who are helping me!! :good:
Click to expand...
Click to collapse
Lock the boot loader using the fastboot command from my previous post. stay in bootloader and run the htc ruu (double click) while the phone is plugged in. This will hopefully revert your phone to stock.
**THE PHONE WILL REBOOT SEVERAL TIMES. LET IT. THIS IS NORMAL. DO NOT UNDER ANY CIRCUMSTANCES UNPLUG IT**
I'll just leave this here.
http://forum.xda-developers.com/showthread.php?t=2066390
Thanks
Okay I got it to work following your instructions. Thanks so much. Normally I can figure this stuff out by goggling but I was stumped last night and freaking out! lol Thanks again.
PS. Can my At&t hox+ even be rooted? My original goal was to root the device so that I would find a workaround At&t's wifi tether subscription that apparently they make you pay for.
treefetty said:
Okay I got it to work following your instructions. Thanks so much. Normally I can figure this stuff out by goggling but I was stumped last night and freaking out! lol Thanks again.
PS. Can my At&t hox+ even be rooted? My original goal was to root the device so that I would find a workaround At&t's wifi tether subscription that apparently they make you pay for.
Click to expand...
Click to collapse
It certainly can be rooted, just check out the link Hasoon posted before your post.
Yes it can be rooted and is fairly simple. I would avoid the tool kit and just flash the recovery yourself ans then the super user zip file.
Sent from my HTC One X+ using xda premium
Also please keep in mind all this stuff- roms, kernels, recoveries are very device specific. Do not flash anything that does not explicitly state it is for the AT&T One x+.
Dear All,
I am a newbie on this so please bear with me. I did take the time out to read up on some of the basics before I posted this but I am not familiar with most of the acronyms.
I bought a HTC One X+ with no power button. The seller claimed he bought the phone as is and didnt know if the phone worked or not.
When I received it, I placed a power button and put it on charge. Within minutes the phone loaded with the 3 logo (UK) but to the bootloader screen. I tried all the various options from Hboot, Restart, Restart with Bootloader and Power Down. When I choose HBoot, I get the following error:
sd checking....
Failed to open USB master mode
(preload) Failed to open USB master mode
loading image....
Failed to open USB master mode
Plug off device.
When I try to power down, it simply restarts. When I choose Recovery, nothing works. I just keep coming back to the bootloader screen no matter what I do.
I read the following thread but I didnt understand some of it, eg RUU. I assume this is the type of ROM that is flashed to the phone.
http://forum.xda-developers.com/showthread.php?t=1940194
I have tried connecting phone to the laptop to see if I can see the drive in windows explorer. Laptop recognises the HTC phone in System Device (loaded HTC Sync Manager from HTC website) but it wont recognise the phone's drive. When I try to use the CMD box, i get same issue. It cannot find the phone's storage, therefore I cannot write anything to the phone.
It seems like whoever tried to flash this phone which is on the 3 network made a hash of it, as from reading the above thread, it looks like 3 networked HTC One X cannot be unlocked.
Therefore is it possible to get this phone back to working mode as it was, given the issues I am having.
Any help will be mightily appreciated! :good:
Thanks
Shanni
you got those "errors" because you have the usb cable plugged in too soon.
Lloir said:
you got those "errors" because you have the usb cable plugged in too soon.
Click to expand...
Click to collapse
I have tried it with cable in early and late. It is the same issue
I just realised it is NOT on the 3 network, that is my HTC One X! Cant believe I got that mixed up!
Actually I dont know what network this is on as I cant get out of bootloader!
I have been informed by a friend that the phone needs to be s-off before it can be flashed. How can I do this?
this device DOES NOT need s-off so your friend is talking out of his ass,
the guide to flash ruu's is in the general section
also there is NO WAY to s-off the X+
Lloir said:
this device DOES NOT need s-off so your friend is talking out of his ass,
the guide to flash ruu's is in the general section
also there is NO WAY to s-off the X+
Click to expand...
Click to collapse
Ok cool, I will have a look at flashing ruu's. Will that fix my phone?
shanni10 said:
Ok cool, I will have a look at flashing ruu's. Will that fix my phone?
Click to expand...
Click to collapse
I keep getting signature errors everytime I try a different UK network RUU! I dont even know what this signature error means!
Also how do I know which RUU to use as there are so many different types. Any help will be gladly appreciated
I have followed Hasoon's directions using his utility tool. I have managed to unlock the phone but cant get beyond that.
Every single viable HTC One X+ RUU I use simply doesnt work. I cant access the USB drive to my phone (prob because the person previously never ticked USB Debugging when he/she attempted to root the phone) so cannot transfer the RUU files to my phone.
I have tried to run the original RUU for this phone but it keeps giving me an error. I have no idea what to do next. I have read all the posts on the General Forum for instructions on ADB, rooting, unlocking, RUUs etc.
I would truly be thankful if I can get some assistance here please.
shanni10 said:
I have followed Hasoon's directions using his utility tool. I have managed to unlock the phone but cant get beyond that.
Every single viable HTC One X+ RUU I use simply doesnt work. I cant access the USB drive to my phone (prob because the person previously never ticked USB Debugging when he/she attempted to root the phone) so cannot transfer the RUU files to my phone.
I have tried to run the original RUU for this phone but it keeps giving me an error. I have no idea what to do next. I have read all the posts on the General Forum for instructions on ADB, rooting, unlocking, RUUs etc.
I would truly be thankful if I can get some assistance here please.
Click to expand...
Click to collapse
where in the UK are you? if you are close to me i can sort it out for you. Also you need to relock the bootloader put the device into bootloader > fastboot usb and THEN run the correct RUU
Lloir said:
where in the UK are you? if you are close to me i can sort it out for you. Also you need to relock the bootloader put the device into bootloader > fastboot usb and THEN run the correct RUU
Click to expand...
Click to collapse
I am in Manchester. I have relocked the bootloader but now the phone wont charge. I have seen a post here how to fix that, so I will try that.
I have done the above but I simply do not know what the correct RUU is. How do I even know which is right? I have tried around 10 so far and none have worked.
Fixed It!!!!
I cant believe it! I fixed it!!!!
I accidentally came up on a post here on this forum looking for something else and a member discussed the same problem as me. The reason why he was getting the signature error etc because he had the wrong recovery loaded.
I therefore loaded the latest TWRP version from here (link provided from General Settings) - http://techerrata.com/browse/twrp2/enrc2b
I didnt use Hasoon's recovery as TWRP is user friendly. I relocked the phone, loaded the correct RUU and it worked!
So to summarise this is how I fixed my phone
1. Downloaded Hasoon2000's toolkit from here - http://forum.xda-developers.com/showthread.php?t=2066390
2. Rooted the phone
3. Unlocked the phone
4. Flashed latest recovery file using his toolkit (Your Own Recovery)
5. Loaded the correct RUU - RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1204.168.32_release_299688_signed.exe from http://androidfiles.org/ruu/?dir=ENRC2B
NB to know which RUU to use, go into bootloader and you will see the RUU details at the top part of the screen - in my case it was Radio_3.1204.168.32. Also when I tried to run any RUU.exe file it told me the version I had was 1.17.401.1. I searched for it on the android files and found the above RUU to match my RUU. This I guess is the stock RUU.
As a newbie, it can be very tough trying to understand this, but this forum is just awesome!! I am an accountant by profession, and I cant believe I figured how to fix an HTC One X+ by going through this forum! The FAQ has it all - http://forum.xda-developers.com/showthread.php?t=2179337
Thanks to everyone who gave their advice here!
I am now going to try performance tweaks next as I am feeling confident
http://forum.xda-developers.com/showpost.php?p=34021248&postcount=2
Shanni
im trying to root my hand me down evo 3d... Hboot 1.58.0000 / 2.95.651.6 710RD...
there is no RUU avail... htcdev unlock doesnt work im assuming the motherboard was repaired... i have no clue... the goal is to get back down to a low enough hboot so i can root with revolutionary... any help is greatly appreciated!
think i blew it... went with URT recovery cd....did bricking part.. unplugged... now shows no light... does show up as qhsusb_dhload in windows... tho no mass memory controller for 5 seconds like the guide says =\ device wont power on.. or do anything.. and doesnt get recognized when i plug into linux URTlivecd for hboot downgrade............ so is it official? i have a new paperweight?
ok scratch that.... i had my battery in... taking the mattery out then plugging in usb gave me mmc for 5 seconds on windows also dim light shows up.... phone was properly bricked.... computer i was using wasnt recognizing phone in linux i switched to another one and phone was recognized.. downgrade to hboot 1.40.0000 was successful tho im now stuck in a boot loop..... guide says to run 1.13 ruu while in fastboot im not sure which one =\
1.13.651.7 .exe's (PC Based .exe, run from Windows, phone on Android OS or Fastboot USB)
RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10. 0530_NV_NV_SPCS_1.16_release_198109_signed.exe - 405.24 MB (mpgrimm2 DevHost)
going to go with that one.... tho i had to find another mirror.... that im not allowed to post... ugh
success... software is downgraded ran revolutionary now have s-off.... now to install a recovery.... thinking i will go with 4ext.... thanks! =)
Ok so I have been looking for a few days on how to fix this and have navigated to about every thread from here and xda and still haven't done anything but make things worse.haha Here is my situation.
My evo v 4g is relocked but i am getting the security warning (which makes it to where I can't flash any recovery files, ruu, etc... through the bootloader)
When I relocked my device it also took away my recovery which i had no idea it would do until it was too late. So now I can't even get into any recovery,
Adb and fastboot won't read my device for some reason. They were reading it for a little while until i relocked my bootloader.
I can't run any ruu because my computer won't read that my phone is connected, it just tells me that my device isn't plugged in (and i have downloaded all the drivers from htc sync)
I'm S-ON 1.57 Hboot
relocked bootloader (with security warning)
NO recovery, NO adb, NO fastboot, NO ruu, and NO flashing through hboot.
Any idea what I might be able to do to get my phone to function again? Any ideas would be great because I've tried them all.
Don't panic
I think, that you use fasboot on linux, and Windows doesn't recognize your phone, when he is in bootloader. True?
When you use Linux system like Fedora or Ubuntu and you install important package to run fastboot (from Android SDK), your phone is visible
If you more help, write there.
get the latest drivers from here: http://forum.xda-developers.com/showthread.php?t=2217396
just uninstall htc sync. its a worthless piece of crap software
and try changing usb ports to see if that helps.
sure enough, I just didn't have the right drivers installed. Stupid HTC sync. Thank you so much, I literally have been messing with this for probably over 50hrs now trying everything I could think of. Figures it would be something so simple.lol You rock!!!!!!!!!!!
lucky it was just the drivers though