I keep running into this and can't get past it for s-off. I can get the phone back up (it is up now), but if anyone knows how to get past this I would like to s-off.
At the "do the wire trick now", I am using the s-off timing metronome, and first touch causes reboot of the phone (and USB disconnect noise in Windows) but all I get at the second wire touch is "unknown device" popup from Windows for qhsusb_dload, and ControlBear can't find my phone. Phone is then stuck with black screen with totally borked SD card. I have tried this several times now.
I have, however, figured out how to get the phone back in a running state after this. Figured I would share the process in case other noobs like myself hit this same issue (see below)
I have hit two different scenarios:
I locked my phone, flashed the latest ICS release (RUU_Vigor_3.14.605.10_PH98IMG.zip), unlocked, installed AmonRa, rooted from AmonRa menu, then ran ControlBear.
I get all the way to "do the wire trick now", and no matter what I do or what wire I use, I can't cause a reboot of the phone. Eventually, I gave up (20 minutes, 3 different solid and stranded wires, and about 100 touching of the pins later), and stopped ControlBear and pulled the battery. Got back to bootable state, and tried the whole process again 4 more times. Same result each time.
Then, I installed Nils' Business ICS 4.0.3 Sense 3.6 (ICS 3.14.605.10) using s-on procedure, and tried again. Now, I can cause a reboot no problem when I see "do the wire trick now", but it results in a qhsusb_dload state. Tried 4 more times after getting the phone back up and SD formatted again. qhsusb_dload state happens every time, reboot happens first touch each time.
Anyone have any ideas on how to get past this issue?
=====================================
If you hit this same issue, here's what you need to do to get your phone back up:
1- close ControlBear
2- unplug USB from phone, then pull/replace battery
3- boot back into hboot, reconnect USB - go into fastboot
4- re-flash your boot.img
5- reflash AmonRa
6- boot into recovery
7- using AmonRa, partition SD card (just accept defaults)
Unplug, reboot, and you should be back in business.
If you read the directions on how to s-off, they say you need to be stock rooted and htc-dev unlocked. You might be having problems because your not on stock rom. Try that and see if it helps.
Sent from my ADR6425LVW using Tapatalk 2
That was how I tried it to start with:
I locked my phone, flashed the latest ICS release (RUU_Vigor_3.14.605.10_PH98IMG.zip), unlocked, installed AmonRa, rooted from AmonRa menu, then ran ControlBear.
I get all the way to "do the wire trick now", and no matter what I do or what wire I use, I can't cause a reboot of the phone.
Click to expand...
Click to collapse
Instead of a wire, use a paper clip.
Sent from my ADR6425LVW using Tapatalk 2
the_Damaged_one said:
That was how I tried it to start with:
Click to expand...
Click to collapse
No your flashing ics leak. Leave it on gb and try.
Sent from my ADR6425LVW using Tapatalk 2
nowerlater said:
No your flashing ics leak. Leave it on gb and try.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Considering I ran RUU_Vigor_3.14.605.10_PH98IMG.zip, am I not now on ICS firmware and unable to revert to GB without s-off?
h4ckers said:
Instead of a wire, use a paper clip.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
That was with stock image...now that I am on Nils, the same wire that wouldn't do anything works and causes a reboot reliably every time. It just leaves me in a hung state with qhsusb_dload drivers trying to load on the PC.
Driver issue with Windows. If you install them via HTC Sync, make sure Sync is disabled while running ControlBear. Try a reinstall otherwise.
If you would like a fresh install of just the drivers extracted from the latest HTC Sync payload:
https://rapidshare.com/files/1796700693/HTCDriver_3.0.0.021.exe
PhantasmRezound said:
Driver issue with Windows. If you install them via HTC Sync, make sure Sync is disabled while running ControlBear. Try a reinstall otherwise.
If you would like a fresh install of just the drivers extracted from the latest HTC Sync payload:
https://rapidshare.com/files/1796700693/HTCDriver_3.0.0.021.exe
Click to expand...
Click to collapse
Sounds reasonable...I made sure sync wasn't running in systray, is there anything else I should have done?
At this point, best bet is to un-install sync and use the extracted drivers above?
the_Damaged_one said:
Sounds reasonable...I made sure sync wasn't running in systray, is there anything else I should have done?
At this point, best bet is to un-install sync and use the extracted drivers above?
Click to expand...
Click to collapse
Correct.
Well, that was the problem...I uninstalled all HTC from device manager and re-installed via the exe posted above...
Success!
=== Waiting device....
(1/45)
Fastboot detected
Beer is tasty, lets take another!!
Please wait....
Found device...
Waiting for device to settle... Please wait...
Beer......more beer......more beer...
Rebooting RUU mode.......
=== Waiting device....
(1/45)
Fastboot detected
JuopunutBear S-OFF success
Do you want to install JuopunutBear modified hboot? (y/n)
y
Installing JuopunutBear hboot.....
Waiting.....
Flashing.......
Rebooting......
JuopunutBear hboot installed
Press ENTER to exit.....
Click to expand...
Click to collapse
Glad you got past that hurdle, now be sure to reinstall your recovery and enjoy your freedom. Just don't flash any bad radios or bootloader downloads and brick it worse lol. This qhsusb_dload error is just communication and phone state issue.
Since ControlBear left me at hbooot, I flashed AmonRa and the boot.img for my ROM before I did anything else.
All is well!
Sorry for the double post but really Trying to s-off as well. All attempts says still sober no reboot of phone just re run control. Just a question. What does the rezound screen look like when the program says pre form the wire trick? PC says fast boot detected and rezound screen just shows htc logo in a silver color. I watched the video and it looked like his went into boot loader not just an htc logo? Any help would be greatly appreciated.
On stock gb unlocked and rooted.
titusseid said:
Sorry for the double post but really Trying to s-off as well. All attempts says still sober no reboot of phone just re run control. Just a question. What does the rezound screen look like when the program says pre form the wire trick? PC says fast boot detected and rezound screen just shows htc logo in a silver color. I watched the video and it looked like his went into boot loader not just an htc logo? Any help would be greatly appreciated.
On stock gb unlocked and rooted.
Click to expand...
Click to collapse
When it says do the wire trick, do the wire trick. It won't tell you to do it unless it's ready so the screen doesn't really matter.
I had the same problem...when it was not working, I had the black screen with HTC logo.
After un-installing all the HTC stuff and re-installing using the .exe linked above, it was on the hboot screen when it said to do the wire trick.
Thanks so much will try again tonight
Sent from my ADR6425LVW using Tapatalk 2
I found you have to hit that pin hard so it moves down that's why a paperclip works well..
Sent from my ADR6425LVW using Tapatalk 2
Tried uninstalling all htc stuff and and just installing the drivers listed above. Still sober. ControlBear still takes me to.black screen with silver htc logo. So.sad for me will keep trying any suggestions given so.if you guys have any.please pass them on. It would be much appreciated.
Sent from my ADR6425LVW using Tapatalk 2
I assume your SDK environment is good? Can flash ROMS and such?
Also, are you using the controlbear that matches your firmware (not your ROM)?
Try going RUU to the latest leak, then flash Nils' ROM. That's the setup that worked for me. (if you do that, make sure you get ICS version of controlbear, and take the built in hboot update. Also make sure you have AmonRa handy. )
the_Damaged_one said:
I keep running into this and can't get past it for s-off. I can get the phone back up (it is up now), but if anyone knows how to get past this I would like to s-off.
At the "do the wire trick now", I am using the s-off timing metronome, and first touch causes reboot of the phone (and USB disconnect noise in Windows) but all I get at the second wire touch is "unknown device" popup from Windows for qhsusb_dload, and ControlBear can't find my phone. Phone is then stuck with black screen with totally borked SD card. I have tried this several times now.
I have, however, figured out how to get the phone back in a running state after this. Figured I would share the process in case other noobs like myself hit this same issue (see below)
I have hit two different scenarios:
I locked my phone, flashed the latest ICS release (RUU_Vigor_3.14.605.10_PH98IMG.zip), unlocked, installed AmonRa, rooted from AmonRa menu, then ran ControlBear.
I get all the way to "do the wire trick now", and no matter what I do or what wire I use, I can't cause a reboot of the phone. Eventually, I gave up (20 minutes, 3 different solid and stranded wires, and about 100 touching of the pins later), and stopped ControlBear and pulled the battery. Got back to bootable state, and tried the whole process again 4 more times. Same result each time.
Then, I installed Nils' Business ICS 4.0.3 Sense 3.6 (ICS 3.14.605.10) using s-on procedure, and tried again. Now, I can cause a reboot no problem when I see "do the wire trick now", but it results in a qhsusb_dload state. Tried 4 more times after getting the phone back up and SD formatted again. qhsusb_dload state happens every time, reboot happens first touch each time.
Anyone have any ideas on how to get past this issue?
=====================================
If you hit this same issue, here's what you need to do to get your phone back up:
1- close ControlBear
2- unplug USB from phone, then pull/replace battery
3- boot back into hboot, reconnect USB - go into fastboot
4- re-flash your boot.img
5- reflash AmonRa
6- boot into recovery
7- using AmonRa, partition SD card (just accept defaults)
Unplug, reboot, and you should be back in business.
Click to expand...
Click to collapse
The problem might be because the S-Off only supports the stock rom of v3.14.605.5 and no later (as of now).
Related
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
Get one of the old GB RUU's and run it on your phone. Start again. If your phone was truly bricked, it wouldn't power on and you wouldn't get an LED light when it was plugged in.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
This is an easy one, or would have been when you were on the black screen. Well the internal storage fix scares me, but hopefully that wont matter. Typically all you need to do is get the PH file from your rom and place on sd card, boot into hboot, and run the update I believe, then reboot.
This title needs to be edited as it's misleading.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
Relax. The S-off process blows out your recovery. You didn't brick your phone.
Put a recovery image on your SD card, go into hboot (from a powered down state, power button and volume down) and let 'er reload recovery. If you can't get the file on your SD card through your phone, pop the SD card into a card reader attached to your PC and stick it on there that way.
Once that's done, remove the image file from your SD card, put your fav ROM on it, and install it from recovery.
You may need to fix your SD card's mount points. Within the thread on S-off, there's a link to the process.
None of the commands work because the phone is not recognized. I cannot boot to hboot. Uh oh.
I had the same screen. Pull the battery and reboot into hboot, volume down+power and run the s-off program again. Something didn't finish and it will pick up where it left off in my experience.
lithium630 said:
None of the commands work because the phone is not recognized. I cannot boot to hboot. Uh oh.
Click to expand...
Click to collapse
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
tekhna said:
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
Click to expand...
Click to collapse
Yeap just pull the battery and power on with power and volume down.
This kinda stuff you'll be fine with. Just don't get too creative with "repairs" that aren't posted in here.
tekhna said:
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
Click to expand...
Click to collapse
As I understand it, the only way to brick a phone is to bork a radio installation.
Dude...pull your battery, put it back in, then power and volume down at the same time. If you can get to hboot, life is good.
After about 30 battery pulls I was able to get to hboot. I have no idea what the issue was. Finally got the phone booting now. I appreciate the replies.
lithium630 said:
After about 30 battery pulls I was able to get to hboot. I have no idea what the issue was. Finally got the phone booting now. I appreciate the replies.
Click to expand...
Click to collapse
Awesome, glad to hear. Did the s-off work?
tekhna said:
Awesome, glad to hear. Did the s-off work?
Click to expand...
Click to collapse
Sure did. Took me a little while to get the wire trick right. I just noticed the sd card is not recognized. I see the fix on the thread. That will be tomorrows project.
Constant reboots
I am able to install roms, but I get constant reboots, every few minutes at best. I tried a few different ICS ROMS. I am running the latest firmware. I BELIEVE with s-off I shouldn't have to flash PH98IMG.zip. I tried fixing permissions also but it has not helped.
How did you get the latest firmware and radios without running the PH98IMG.zip? The ics roms you are installing won't update your firmware.
Sent from my ADR6425LVW using Tapatalk 2
Chillerman said:
How did you get the latest firmware and radios without running the PH98IMG.zip? The ics roms you are installing won't update your firmware.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
lithium630 said:
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
Click to expand...
Click to collapse
Well the newest leak came out 5/7 and the one before that 5/2 so only a week ago. I would download the newest from Android Police and follow the instructions they give to install, then flash a recovery and install a rooted Rom for this firmware like Scott's.
Sent from my ADR6425LVW using Tapatalk 2
lithium630 said:
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
Click to expand...
Click to collapse
I don't know why you relocked...I think there's a thread about not so good things happening to those who relock after S-off. I downloaded and installed the 5/5 leak as PH98IMG after I S-off'd and reflashed the recovery.
I'm pretty sure my hboot said "locked" straight out of the gate after I did the S-off deed.
douger1957 said:
I don't know why you relocked...I think there's a thread about not so good things happening to those who relock after S-off. I downloaded and installed the 5/5 leak as PH98IMG after I S-off'd and reflashed the recovery.
I'm pretty sure my hboot said "locked" straight out of the gate after I did the S-off deed.
Click to expand...
Click to collapse
Nothing bad happens, you just don't ever get back to "locked" without doing S-off again. You're just at "relocked" like the old days. S-on with an eng hboot on the other hand will brick your device.
That aside, there's no need to unlock if you're S-off. Either flash a patched hboot or just flash a PH98IMG.zip of AmonRa if you don't need fastboot commands (I did the latter).
I flashed the last firmware before S-off. I followed the instructions given. I flashed the latest firmware today and this damn thing still reboots constantly. I flashed the 5-7 firmware then the Venasaur Rom.
lithium630 said:
I flashed the last firmware before S-off. I followed the instructions given. I flashed the latest firmware today and this damn thing still reboots constantly. I flashed the 5-7 firmware then the Venasaur Rom.
Click to expand...
Click to collapse
You need to try installing the radio firmware or just install the complete RUU again. And install a clean copy of the rom, not a nandroid backup. Wipe data, cache, dalvic cache, and system before flashing the rom.
Send me a private message if you would like and I'll help you get it figured out on gtalk.
I'm currently trying to S-OFF my Rezound. I have run ControlBear and it's rebooted me into the Bootloader. It tells me to do the wire trick. So, I first try it using speaker wire. No response whatsoever. It try multiple times more, nothing. I switch to an insulated paper clip. Nothing again. No reboots. No nothing. It just....doesn't register that I'm doing the wire trick. What do I do now??
UPDATE: got it S-OFF but I have a new problem. Now I can only boot into bootloader and nothing else. It just hangs on the HTC splash screen. I tried flashing Amon Ra 3.15 but I still can't get into recovery or a ROM.
Keep trying
Sent from my ADR6425LVW using Tapatalk 2
Keep trying and remember it is touch the contact points, let go and touch them again at the designated time.
i remember something like 1.75 seconds between touches,
make sure you make contact, easy not to depending on your wire size
screen wont tell you when its shorted...
it only lets you know if you got both touches correctly timed, and therefore its moving on with s-0ff, other than that, it doesnt blink or anything when you short it, but when you get it... you'll know instantly
UPDATE: got it S-OFF but I have a new problem. Now I can only boot into bootloader and nothing else. It just hangs on the HTC splash screen. I tried flashing Amon Ra 3.15 but I still can't get into recovery or a ROM.
Did you flash the Jboot?
Sent from my ADR6425LVW
I Am Marino said:
Did you flash the Jboot?
Sent from my ADR6425LVW
Click to expand...
Click to collapse
You mean HBOOT? I said yes to the prompt in ControlBear. I'm running HBOOT 2.21.2121
if it's hanging at the htc screen you're probably missing the kernel, try taking out the sdcard also. It's been a little while since I did this lol
I would download the OTA (GB or ICS) and rename to PH98IMG.zip, and place on the root of the External SD card.
Reboot the phone; you may need to boot into the boot loader to initiate this, but it was unnecessary for me as it has always automatically started the process.
This will reinstall to stock, and re-lock the boot loader; but will not remove S-OFF.
Unlock the boot loader again.
Install custom ROM of your choice.
????????????
Profit!
EDIT:
If S-OFF caused any issues to your Internal SD Card or External SD Card drivers (as it did with me when I did S-Off; I could not access either), this will fix those issues as well in the process.
I cannot get into regular bootloader. It just either sits and stalls, goes to HTC screen, or just straight to recovery. This has happened on and off before but I was always able to get it after a few tries. I've been trying for 2 days since the new ICS was released by Sprint but it's been no go.
I believe I have 1.5 Hboot, but I can't tell for sure because I can't access it. I had to take the long route when I had to root with the HTC unlock thing, etc.
I've tried to get to HBoot using QuickBoot app and using the menu option within TWRP 1.1 and now 2.2 (thought that might be the problem, but guess not)...still just stalls and nothing happens after reset
I've been using only rooted OTA's on my phone and only rooted for bloatware removal and wifi tether. No custom roms. No ICS leak.
The buttons of course work. As soon as I take my finger off of the Down volume button, the phone will activate and boot up normal in some cases.
I don't know if this is causing other issues with my phone as it self reboots or freezes a few times a week. I was looking forward to ICS update because I was hoping it would fix the reboots and freezing. Everything else works fine with the phone.
Any help would be greatly appreciated.
try "adb reboot bootloader" and see if your phone gets into bootloader.
mnomaanw said:
try "adb reboot bootloader" and see if your phone gets into bootloader.
Click to expand...
Click to collapse
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
brokenmouse said:
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
Click to expand...
Click to collapse
Look under settings/battery or power saver and uncheck fastboot?
Then you can actually get into hboot.
AFAIK, adb commands work in android, fastboot commands work in bootloader.
just make sure USB DEBUGGING is checked in settings.
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Click to expand...
Click to collapse
This caused a lot of trouble for me trying to flash MeanRom and Tribulattifather's ICS OTA with 4EXT because it kept trying to go into bootloader after the install to do the "smart install" or whatever. The phone would just black out upon reboot and sit there or if I tried doing bootloader manually, it would go straight to recovery again. I was up until 4 in the morning trying to get my phone to fully boot last night...never did.
Brought my phone to work today and left it off nearly all day. I thought I was seriously screwed and would have to do a RUU update/unbrick from work. Lo and behold it went into bootloader first try.
I'm restoring a backup now through TWRP 2.2 (because it doesn't have the smart install feature). We'll see if
What do you think is causing these problems? I don't want anything crazy...just a solid ICS rom or rooted OTA. Most ROMs I read suggest using 4EXT to flash, but I'm afraid of running into this again. Any suggestions or thoughts?
as mentioned above, installed the TWRP 2.2 from bootloader and restored a backup (that worked a long time ago). Now i'm having the same issue I had last night. It won't boot up at all except to recovery again.
For most people, being s-off is the best thing to do. S-on and ICS tend to bootloop. For some reason, 4ext and flash image GUI don't seem to work well in ICS either for some.
Have you tried flashing a GB ROM?
Save the Drama for your Mama with Tapatalk 2
I'm going to have to figure out how to get back to complete stock. Everytime I flash a rom...doesn't matter what it is, the phone will say the flash is done, then reboot to...NOTHING...just a black screen. I've let it sit and nothing happens.
Followed a guide on androidcentral that had a nice restore to stock guide. Did the RUU from my computer and now it's acting normal again. It must've been really messed up because when I had it talking to ADB and did the reboot reloader command (as someone stated), the screen was solid black, though the RUU still saw it.
So... was running the MikVirgin ICS rom on my S-on 1.50 Evo 3d. Was going to bring it back to scratch and go through the S-Off process to run something better. I have Revolutionary 4.0.1.4 installed and fastboot on my computer. For the life of me, I cannot get the phone to accept anything now :\ Trying to run the RUU gives me the 170 error and any rom I try loops at the boot loader (not the white HTC screen, but the boot image for the rom).
Help would be appreciated
bl4ckllama said:
So... was running the MikVirgin ICS rom on my S-on 1.50 Evo 3d. Was going to bring it back to scratch and go through the S-Off process to run something better. I have Revolutionary 4.0.1.4 installed and fastboot on my computer. For the life of me, I cannot get the phone to accept anything now :\ Trying to run the RUU gives me the 170 error and any rom I try loops at the boot loader (not the white HTC screen, but the boot image for the rom).
Help would be appreciated
Click to expand...
Click to collapse
The 170 error is normally a USB connectivity issue caused by a bad USB cable or Windows driver problems. You also need to have your bootloader relocked if you are S-ON.
See this post for RUU.exe troubleshooting steps. If you planning to get S-OFF you might be interested in trying my guide.
ramjet73
ramjet73 said:
The 170 error is normally a USB connectivity issue caused by a bad USB cable or Windows driver problems. You also need to have your bootloader relocked if you are S-ON.
See this post for RUU.exe troubleshooting steps. If you planning to get S-OFF you might be interested in trying my guide.
ramjet73
Click to expand...
Click to collapse
Yeah, I've tried it in Relocked status, and still no go. Even under fastboot USB (and I made sure the drivers are there) it won't recognize the phone is attached. I've factory wiped and I'm going to try and re-install the Mikvirgin rom again.
bl4ckllama said:
Yeah, I've tried it in Relocked status, and still no go. Even under fastboot USB (and I made sure the drivers are there) it won't recognize the phone is attached. I've factory wiped and I'm going to try and re-install the Mikvirgin rom again.
Click to expand...
Click to collapse
Have you tried another cable and/or PC?
ramjet73
I had a similar (not identical) problem, and I solved it by pulling the zip out of the exe by letting it run without plugging the phone in and then looking through the folders in my temp folder until I found rom.zip. Renamed it PG86IMG, put it on my sd card, re locked with fastboot, and boom! Phone rescued.
Sent from my Nexus 7 using xda premium
Was finally able to get it loaded with an ICS rom after doing a factory reset, installing the rom, and then manually installing the boot file through fastboot. Maybe I'll try again tomorrow, doing the s-off procedure first Thanks for the input all!
first off, I'm an idiot with this whole thing and shouldn't be doing it probably. i just don't know enough about it to be playing with expensive phones like this so i understand I deserve whatever i get.
i was running a custom rom on an S-ON phone. i forgot the name of the rom (was made by TEAM COOL or something). But I wanted to unroot and go back to normal stock ROM and download the JB update. First, in the SU app, I did a complete unroot. that did nothing except not let me use the app anymore.
then I tried doing the RUU way of going back, but when it would go to the loading bootloader portion, the usb would disconnect and it would fail with error 171.
so then, and i don't know how i got here, but i went into recovery and did a factory reset and now i have no rom. I have tried installing meanrom but it fails after some line regarding a kernal. my phone won't do anything except boot to the white HTC screen or into the bootloader.
i have no idea what to do, I just want it working at this point.
i've been searching forums like crazy but all the solutions are things I already have done or things that won't work for me.
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
om4 said:
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
Click to expand...
Click to collapse
thank you for your help! however, whenever i do this, it just says < waiting for device >
so i finally got a rom to install--clean rom. that is the one i used to have. but when i reboot, it gets stuck on a black screen and won't go any further.
I had the same thing happen. Had to run a boot.img flash utility i found on another thread elsewhere on xda. The flash utility was updated for jb. If i can locate where i found it then i will get back to you.
Sent from my EVO using Tapatalk 2
I was curious if you ever found that rom or if anybody can help me? The phone is still out of commission. It's been tough to make it through the holidays especially since my laptop was stolen the very next day that all this happened
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
unclefarkus said:
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
Click to expand...
Click to collapse
Have you tried meanbean? It has the boot.img flash tool baked in for s-on, just follow the instructions to the tee in the OP... It's in the Android development thread... Good luck
Sent from my EVO using xda app-developers app
Sounds like you need to flash a Rom that has the s-on installer or fastboot flash the kernel for the Rom you have installed
Most roms come with the kernel installer built in now days. just keep trying to flash em. fyi if your phone turns on , even a little bit , you are not bricked
I am trying to flash meanbean. I wiped the cahes and did factory reset, then flashed the ROM. It's been on "Installing /system..." for about 30 minutes now. Something seems wrong. I'm scared to interrupt it in case that's normal or if interrupting it will break it for good.
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
unclefarkus said:
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
Click to expand...
Click to collapse
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
mrlakadaddy said:
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Boatiy said:
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Don't forget the clear cache commands
Sent from my EVO using xda app-developers app
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
unclefarkus said:
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
Click to expand...
Click to collapse
Can you get into bootloader? If so go to the TWRP website and download the hboot zip. Put on external sd card and enter bootloader.
Sent from my EVO using Tapatalk 2
Perhaps what is happening when you try oem lock and get that error is that adb is still running from a prior attempt or because of some other program. Try opening your task manager and ending all processes of adb and other programs that connect to the phone. Then try oem locking again and go from there.
Sent from my EVO using xda premium
I made a little bit of progress!
I determined that Windows 8 was the reason I get the usb malfunctioning message. I obtained a Windows 7 computer and it worked like a charm.
That said, I'm not out of the woods yet.
I relocked the phone using fastboot and then have been attempting to flash a stock RUU now that the usb issue is sorted out.
That seems to work but it gets stuck at "sending....." for as long as 35 minutes. I've tried about 4 times, giving between 20-35 minutes and it won't go beyond sending.
I can at least fastboot now; but the phone is locked. Which is fine; I just want back to stock anyways.
Tampered
Re-locked
S-On
Hboot-1.19.0000
Radio-1.12.11.0809
OpenDSP-v29-1.0.45.0622
eMMC-boot
Aug 9 2012
I flashed the 2.13.651.1 RUU by the way.
Any new advice haha?
I loaded a PJ img via sd card and it's alive and updating to JB OTA right now! Thanks for all the help over the past month folks