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! =)
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.
I did a search and it doesnt seem like anyone else had my problem. Basically, I'm on stock ICS with S-On, unlocked. I saw that the S-Off method now supports ICS and decided to give it a try.
I have all HTC drivers installed, downloaded jbear, extracted it to a directory all by itself, ran as admin..
All is going fine until my phone reboots to the green arrow screen. Then it just waits for the device, except it cant find my phone. I get an error message asking me to check my adb and fastboot drivers.
If I have the HTC drivers installed, doesn't that automatically give me the adb and fastboot drivers?
I've tried on 2 computers now, and still no luck. I've been flashing ICS all day. Help!
no, you need to have Android Development kit.. or w/e its called lol, I forgot its name..
either way, just get it from here:
http://developer.android.com/sdk/index.html
xologist said:
no, you need to have Android Development kit.. or w/e its called lol, I forgot its name..
either way, just get it from here:
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
So I just download it, install it, and then I can attempt S-off again?
Anything special I need to do?
FINALLY got it to work. This was a crap shoot for me. Basically, what was happening was that I get stuck on the green arrow screen because Windows refused to recognize my phone as a phone ONLY ON THAT SCREEN, so my device manager didn't have an 'Android Phone' device. What I did to get it to recognize my phone was to relock my phone in fastboot, and then unlock it again in fastboot. And poof! My phone was recognized as an Android Phone on the green arrow screen. Got S-Off on 1st try
Thread can now be closed.
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?
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
So now after a year of thinking I should root my phone, buying your book and then a week ago bricking myoff the phone I find myself here.
On the experts forum, where dreams are made and phones are fixed.
Only, there not.
I unlocked my phone installed twrp without installing superuser because twrp or unlocking switched off the wifi on my phone so twrp couldnt install superuser.
Since then I get this error
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
I've unlocked it and re locked it with hasoon and tried to run an RUU, it tells me I need the RUU 2.17.206.3 I cant find it.
Ive got HBoot 1.72 at the moment, the phone wont switch off when charging, if indeed it is charging?
So I figure if its always had S-ON and there is an image file still there I must be able to boot that file and restore my phone?
My thoughts are to find the correct RUU am I right?
Oh and the phone now is not being recognised by the computer and adb cant see it because every time i plug it in it goes to fastboot.
Do I need to reunlock it?
Can anyone help me sort it out so I can experience the joys of custom roms and not the expense of a bricked phone?
And yep Im sorry I did run into it blind!
It's kinda cathartic, just used bat file to recharge and re unlock.
But Im still none the wiser.
Whatd do I need a ROM an RUU or a KERNEL?
I have that PM35IMG.ZIP