[Q] How to turn on fastboot without recovery? - HTC EVO 3D

I have been through a day of torment with my VM Evo 3D since deciding to throw a new ROM on yesterday. Several months ago, I rooted the phone and installed a new kernel, but was still running the stock ROM.
On previous phones, I had never had to deal (that I can recall) with the s-on/s-off issue, so I just chose to be cavalier, grab a ROM and install it without reading some very necessary details which I have definitely studied since! Every ROM that I tried put me into boot loop, and after a few I realized there was no getting around s-off. Since I am on 64-bit Windows, I downloaded Ubuntu 12.10 and ran live disk to try the unlimited.io wire trick, however, the software failed and I was unable to even get to the point of doing the wire trick itself.
This morning, dejectedly I decided to just un-root my phone and start from scratch. I relocked it and installed a stock ROM with RUU. I decided that I am going to work through the steps again and be very careful at each step. I went to reboot into recovery and was unable to do so from power/volume-down. I went ahead and booted into regular mode and ran >adb reboot recovery. At this point it rebooted, but came up to a screen with a picture of a phone and a red triangle and exclamation mark. Some googling seems to indicate that my recovery image is jacked up, so I went to run >fastboot flash recovery recovery.img, but fastboot is not enabled. When I do >adb devices, I see my phone. When I do >fastboot devices, it returns nothing. The only way that I know how to turn on fastboot is to go into recovery, but since I can't get into recovery, I am unable to do that.
Does anyone have any advice on a good next step? Is it possible to turn on fastboot via adb? I am hoping that someone has a response other than 'you are screwed'. Thanks in advance if so.
[EDIT] Please disregard. For some reason, after powering it off for a while and trying again, I am now able to get into recovery. I have no idea why it wasn't working then and is now, as I haven't change anyway, but that is pretty much how my last 24 hours has gone anyway. :/

olllllo said:
I have been through a day of torment with my VM Evo 3D since deciding to throw a new ROM on yesterday. Several months ago, I rooted the phone and installed a new kernel, but was still running the stock ROM.
On previous phones, I had never had to deal (that I can recall) with the s-on/s-off issue, so I just chose to be cavalier, grab a ROM and install it without reading some very necessary details which I have definitely studied since! Every ROM that I tried put me into boot loop, and after a few I realized there was no getting around s-off. Since I am on 64-bit Windows, I downloaded Ubuntu 12.10 and ran live disk to try the unlimited.io wire trick, however, the software failed and I was unable to even get to the point of doing the wire trick itself.
This morning, dejectedly I decided to just un-root my phone and start from scratch. I relocked it and installed a stock ROM with RUU. I decided that I am going to work through the steps again and be very careful at each step. I went to reboot into recovery and was unable to do so from power/volume-down. I went ahead and booted into regular mode and ran >adb reboot recovery. At this point it rebooted, but came up to a screen with a picture of a phone and a red triangle and exclamation mark. Some googling seems to indicate that my recovery image is jacked up, so I went to run >fastboot flash recovery recovery.img, but fastboot is not enabled. When I do >adb devices, I see my phone. When I do >fastboot devices, it returns nothing. The only way that I know how to turn on fastboot is to go into recovery, but since I can't get into recovery, I am unable to do that.
Does anyone have any advice on a good next step? Is it possible to turn on fastboot via adb? I am hoping that someone has a response other than 'you are screwed'. Thanks in advance if so.
[EDIT] Please disregard. For some reason, after powering it off for a while and trying again, I am now able to get into recovery. I have no idea why it wasn't working then and is now, as I haven't change anyway, but that is pretty much how my last 24 hours has gone anyway. :/
Click to expand...
Click to collapse
Glad it decided to work. I would try the linux bootable cd with the pull the battery trick to get s off. It worked for me although it took quite a few tries to get the battery out at the perfect time. I was not cool with the wire trick or any kind of htc dev unlock. The cd also gives you options for the hboot downgrade as well. Good luck!!!

Related

tale of a rooting gone terribly wrong

I can laugh about it now, but...
First let me say that I am new to rooting, but not to toys Here's my train wreck comedy of errors, maybe someone can tell me how all of this was even possible?
I started by rooting using Doomlord's rooting script. That went super-easy. Then I decided I wanted to do a nand backup, so following the instructions here I went and installed ROM manager and used it to flash Clockwork Recovery Mod. CWR wouldn't load when I tried to get to recovery mode to do my backup so I asked around and I discovered that my Atrix was not unlocked. It all goes downhill from there.
Following all the unlocking instructions in the Pudding sticky, I used RSDLite, and the IHOP sbf (since I'm on Bell Canada). Well that looked like it was working, but when RSD showed me at 100% reboot after it was all done, the program stopped showing any further status to say it was complete. I've seen this happen a lot before doing other smartphone activities, and I knew it wasn't going to proceed further. So after giving it another 10 minutes just in case, I unplugged from my PC. And yes, of course, now RSD protests that it wasn't done. Typical. I shut down my phone and rebooted. Time for the Fastboot stage.
(at this point I want to point out that BriefMobile's guide is wrong. you do NOT skip to instruction #13 if you are on gingerbread because that does not work. I ran into a couple of other people who reported the same problem with his guide)
(also at this point, I want to clarify that all my USB drivers needed for this to work were installed, and many of the links provided by Pudding sticky are out of date and don't work. or both so I had to get software from other sources and cross my fingers)
So, now onto the fast boot. But wait! Briefmobile guide (linked as the guide to use in Pudding sticky) never informed me I need to put my sim card back in now. or not. I decided since NO instruction is being given either way, I left it out. Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.
Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.
The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot. The instructions for Bell Atrix 2.3.6 are all extremely outdated and/or irrelevant in some cases. Before all this happened I was considering flashing custom ROMS. Now I am absolutely terrified to do so, and would rather just use TiBU to freeze some bloatware and leave it at that. How did this all go so terribly wrong? Are days like this normal in the custom ROM scene?
no ideas anyone? I'm still baffled how my phone went through the train wreck that happened in the above post but still manages to be unlocked and rooted after the factory reset and 2.3.6 re-installed OTA. I still have root, and the phone is still unlocked.
omnius1 said:
Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.
Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.
The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot.
Click to expand...
Click to collapse
Yep, sounds a little like the night I had when I unlocked the bootloader. If it helps, I've done a little bit of rom flashing since and have had exactly zero problems there. (I'm not a new-rom-every-week kind of gal, just wanted something more functional than stock.)
So that SBF was known to cause a soft-brick; RSD Lite would predictably choke on itself and your phone would display "failed to boot" with a bunch of options. You enter the fastboot oem unlock command and keep going. My fastboot procedure went as advertised, but upon reboot it did stick for ~15 minutes on the startup screen and I had to do a battery pull. After that, up it came and everything was peachy.
Did you pull the battery and attempt another reboot before doing the factory reset? Just curious.
Yeah, second battery pull was because both the phone and the PC cmd window became non responsive after I executed the final stage of the OEM unlock procedure.
The phone went into bootloop. Wouldn't reboot. Had to hard factory reset with the 3 finger salute
Huh. Well, unlocking the bootloader also causes a factory reset, so in this case your end outcome was the same. Sorry it was such a pain in the meantime.
Seriously, though, that's the hardest part. Installing CWM recovery and other roms is a piece of cake, just do plenty of reading before changing anything.
well looks like I got all the final kinks worked out. I froze all of my bloatware with TiBU including Motoblur Launcher and I'm now running my phone using Launcher 7. Everything's pretty zippy now and I think I may have just extended my phone as a keeper for the rest of this year

Boot loop help

I bought a used Sprint HTC EVO 3D in ebay, knowing it had a boot loop problem as described by the seller. Before buying, I researched to see if I can possibly fix the issue, and at that time I saw a few ways to do it. Unfortunately, now that I have the phone and tried those ways, my phone is still stuck in a boot loop.
This is what I've done so far:
1) Received the phone w/ HBOOT 1.5 (unlocked using HTC method).
2) I tried to flash TWRP 2.1.1, TWRP 1.0.3, ClockWork Mod 4.0.1.4, ClockWork Mod 5.8.0.1, and 4EXT RC3. The flashing seems to work as indicated by fastboot (it says OKAY after flashing).
3) I tried launching the recovery via fastboot command line and also tried launching recovery via power cycle while holding volume button down. Neither method allowed me to get to recovery. I would see the HTC logo, and then boot loop.
Other things I've tried:
1) Relock the phone.
2) Run the latest RUU (Sprint 2.17.651.5). I also tried the PG86IMG version. Flashing seems to succeed either way. But when I reboot, boot loop is still there. ROM doesn't boot.
Other things I've tried:
1) With the relocked phone, I did the HBOOT 1.4 downgrade and was successful downgrading.
2) I ran the RUU (Sprint 1.13.651.7) after the successful downgrade as described in the downgrade method so that I can try the Revolutionary S-OFF if my ROM boots.
3) The RUU succeeds, but the phone is still stuck in boot loop. ROM doesn't boot.
Again, the only thing that seems to work is fastboot commands. Adb commands don't work since the ROM doesn't even boot up.
I'm not sure if there's anything else I can do with the phone. I'm thinking now this may be a hardware issue. But before I send it in to HTC, I'd like to get opinions from the experts out there to see if there's anything else I can try.
Thanks!!!
none
Try to plug it into your computer, open a command prompt and type.
"adb reboot recovery"
Just like you see it, that should get you into recovery so you can flash a new rom onto it. And if you can swing it, by a new one next time lol
As stated above, adb commands won't work since you need a bootable ROM in the first place.. My EVO 3d reboots right after the first HTC logo pops up.. I've also tried launching recovery via fastboot command line and via power cycle and holding volume down button and selecting recovery. Both methods just reboots the phone and reboots over and over til I pull the battery out.
exact same problems, any help?
i have the exact same problems as Alpine Man.
tired everything, and i was hoping that if i downgraded to hboot 1.4, everything would be ok in terms of bootloops, but no =[
Can anyone shed light on this, software issue? hardware issue?
Anyone have a solution for this? or just send it to htc/
Have u tried installing new custom Rom?
I can't remember the creator's name but the file name is EVO 3d v2. I used the file to fix my bootloop. It's actual use is to relock ur bootloader back and it also install the ruu file. But it worked for me.
It might help u too. Maybe give a shot.
Sent from my AWESOME HTC EVO 3D. Click THANKS if u find my post is helpful.
I tried everything... And nothing fixed it. I finally sent it to HTC. They replaced the motherboard and all is well again.
i've read almost every guide availble regarding bootloop problems. my sister's evo 3d has no problems whatsoever. mine won't boot for anything!! have to go to work now but i will try it when i get home. if that doesn't work i'll probably have to send it in too.
alpineman - does the 1 year manufacturer warranty transfer over when you buy the phone used off ebay? i got my phone in great condition on ebay, with no mention of bootloop problems =[ . i'm not with sprint. i bought the phone hoping to flash it to metro. do i call htc instead of sprint? i'm not really sure how this warranty thing works.
any help is greatly appreciated thanks!
HTC did not ask for receipt, proof of ownership, or whether I had an active Sprint contract. They went by the serial number to determine warranty status. This is the 2nd HTC phone I had to do this with. Both times, no warranty problems whatsoever.
that's great! if all else fails, i'll give them a call on monday. thanks for the help!
good news! Come came back from HTC with new motherboard, boots up nicely now. I haven't done anything to it yet.
Bad new: the battery cover doesn't sit nice and flush anymore, its kinda crooked
It's sooo minor i almost don't wanna bother with HTC, but physically it was mint when I sent it in.
Need help
Hi can any one help, I am trying to gain S-Off on my Evo 3D, hboot 1.49.0018, I have Htc sync driver (Sync Un Installed)
adb devices command works fiine and gives me the serial number
but any other command with adb or fastboot it stucks on waiting for device.
Please Please Help me.
Regards,

Bricked?

Hey all,
I’ve heard that the Rezound is impossible to brick, but all I can guess is that I managed to do the impossible.
I bought a used Rezound a month or so ago. The previous owner had already rooted it and upgraded it to ICS – I honestly wasn’t happy he did this and didn’t mention it in his listing; I just wanted a stock phone and didn’t want to mess with rooting. I didn’t know exactly what he had done to it, so my idea was to reflash it myself, so I knew exactly what was on the phone. Battery life and overheating had been a real problem with the phone, so I was suspecting he might have done something to cause it, so I wanted to rule that out before concluding it was a hardware issue.
ANYWAY – I used cwm, backed everything up, wiped the phone’s memory, then booted back into recovery mode to flash the new ROM. I was able to pick the new ROM and get the process started. It worked its way through the process, rebooted, then sat on the intro screen for-ever. No matter how long I let it sit, it would not complete the install. At that time, I was able to boot back into recovery mode, at which point I cleaned out all the data caches, wiped it as clean as I could, and then tried to repeat the install. Eventually, I used every option in recovery mode and nothing made a difference – I never managed to get the phone working again.
In my last effort, I left the phone on overnight, figuring I’d give it all the time I could to sort itself out, settle into the new ROM, etc. NOW, the battery is dead and the phone won’t charge it. If I remove the battery, put it back in, and plug it in, the charge light goes on for about 5 seconds and then turns back off. At this point, the phone is completely dead.
Do I have any options at this point? Or am I just pretty much SOL?
And no, I don’t know WTF I’m doing, clearly the main issue is probably typing on the keyboard right now. Any help is appreciated.
phermes1 said:
Hey all,
I’ve heard that the Rezound is impossible to brick, but all I can guess is that I managed to do the impossible.
I bought a used Rezound a month or so ago. The previous owner had already rooted it and upgraded it to ICS – I honestly wasn’t happy he did this and didn’t mention it in his listing; I just wanted a stock phone and didn’t want to mess with rooting. I didn’t know exactly what he had done to it, so my idea was to reflash it myself, so I knew exactly what was on the phone. Battery life and overheating had been a real problem with the phone, so I was suspecting he might have done something to cause it, so I wanted to rule that out before concluding it was a hardware issue.
ANYWAY – I used cwm, backed everything up, wiped the phone’s memory, then booted back into recovery mode to flash the new ROM. I was able to pick the new ROM and get the process started. It worked its way through the process, rebooted, then sat on the intro screen for-ever. No matter how long I let it sit, it would not complete the install. At that time, I was able to boot back into recovery mode, at which point I cleaned out all the data caches, wiped it as clean as I could, and then tried to repeat the install. Eventually, I used every option in recovery mode and nothing made a difference – I never managed to get the phone working again.
In my last effort, I left the phone on overnight, figuring I’d give it all the time I could to sort itself out, settle into the new ROM, etc. NOW, the battery is dead and the phone won’t charge it. If I remove the battery, put it back in, and plug it in, the charge light goes on for about 5 seconds and then turns back off. At this point, the phone is completely dead.
Do I have any options at this point? Or am I just pretty much SOL?
And no, I don’t know WTF I’m doing, clearly the main issue is probably typing on the keyboard right now. Any help is appreciated.
Click to expand...
Click to collapse
Well, not sure about the installation issues...but the reason the phone died is because you have CM recovery. Known issue .. probably a hundred threads just not recently because people have either switched or don't let their phone run down. Phone can't charge from CM recovery and you need to switch back to Amon Ra recovery. http://forum.xda-developers.com/showthread.php?t=1434532
Basically, pull battery and then replace and hold volume down and power at the same time to boot into bootloader. Plug phone into computer . Put Amon recovery img into the same folder containing fastboot. Then make sure phone is in fastbootUSB . http://forum.xda-developers.com/showthread.php?t=1339679&highlight=amon+ra
Latest is 3.15 .. so once it is placed in the right folder type fastboot flash recovery recovery-ra-vigor-3.15-gnm.img ... this will flash amon ra recovery.. then you can charge. Once charged then you can attempt to recover your rom.
Sounds like you need an external charger to get the battery a little juice. I never thought that it was possible for a battery to not be able to charge because it was super dead unit I saw it happen on a Thunderbolt. You could take the battery to Verizon and have them give it a quick charge, just to get you back on your feet or got to an electronics store and buy a charger (can always take it back). Get it to boot again then work it from there maybe flash the Stock or Leaked PH98IMG just to get back to working so you can breath again..
Getting yourself out of a jam is part of the learning curve in flashing phones.
Yep, known problem with CWM. Plug it in powered off for a long time. It might not seem like it is charging, but it is, very little.
What ROM did you flash?
Also need to know the firmware version.
Once you get into hboot, tell us what radios you have and what version of hboot. You have three options, 2.11, 2.21, and 2.25. Also tell us if it has S-On or S-Off.
All of this is crucial for us to help you get back to stock.
Great, thank you for the good info! I was about ready to toss the thing in the trash, but it sounds like there may be hope yet!
EmerikL said:
Yep, known problem with CWM. Plug it in powered off for a long time. It might not seem like it is charging, but it is, very little.
What ROM did you flash?
Also need to know the firmware version.
Once you get into hboot, tell us what radios you have and what version of hboot. You have three options, 2.11, 2.21, and 2.25. Also tell us if it has S-On or S-Off.
All of this is crucial for us to help you get back to stock.
Click to expand...
Click to collapse
I'll have to get back to you on all of that - I'm not entirely sure right now, and everything is at home. Pretty sure it was a Venasaur ROM.
I wish the mods would delete any and all links to CWM. These threads keep cropping up.
its possible you need to flash the ICS firmware patch as well and thats why its not booting
Sorry to hassle you guys with what has probably already been answered a few times. I did some searching – yes, I should have done a little more - and the results I found were all folks that had phones that would still power on to some degree. I didn’t find many where the phone was completely dead, and if I did the responses were generally, “You’re screwed, throw it out.” Issues with cwm really didn’t cross my mind, so I didn’t think to search on that.
Anyway, I appreciate the help. I’ll sit down tonight and see if I can’t figure this thing out.
It is likely that he is S-ON and if he had a sense 4 rom installed, the new rom won't boot.
To the OP, can you please tell us the hboot version # (2.xx) it is either 2.10, 2.11,2.21, or 2.25. Also tell us if it says S-ON or S-OFF and unlocked, locked, or relocked, or juponutbear in purple at the top.
Easiest way to brick it is to take out battery while flashing a hboot haha.
No worries about the question, we're glad to help (since you didn't post this in the Development section lol)
Anyway, as long as you are S-ON, it shouldn't be too bad of a process, just lengthy. First, you'll need the Android SDK so you can get Fastboot, etc, as well as all the HTC device drivers installed, and you'll need to flash Amon RA recovery over.
Amon RA can be found here:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
**Make sure the Recovery file is in .img format, not .zip or anything, and place in the same folder as Fastboot (which is located in the Android SDK folder).**
You'll need to pull the battery, plug the USB cable into the computer, plug into the phone, replace battery, and hold down 'Power' + 'Volume Down' until the screen flashes the HTC screen. (Not sure if that's the only order, but it works). This will take you into Fastboot.
Next, you'll need to open a command prompt and 'cd' to your folder with Fastboot in it. Type:
Code:
fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
into the command prompt and hit enter. It should show on the command prompt a couple lines of time it took, etc. and when done you will have Amon RA recovery.
Now you will at least be able to charge your phone!! From the phone, you can select 'Bootloader' then 'Recovery' and you will boot into recovery, which will allow you to charge your battery. You can check the charge status of the battery while in recovery in one of the menus, can't remember which one. (Fun tip: you can use 'Home'/'Menu' to scroll up/down, 'Back' to go back and 'Search' to select, since the hardware buttons are so difficult to press)
Once you get the phone charged, you have a couple of options. Since you stated you wanted to go to stock, I'll explain the steps to get back to the state the phone shipped with.
Once you get a good charge, you will also need to re-lock the bootloader to go back to stock, which is also done in fastboot by typing:
Code:
fastboot oem lock
(Get to fastboot by Battery Pull>Battery Put Back>Power + Volume Down, all while connected to a computer, just like when doing the Recovery flash)
BACK TO STOCK::
You can do this one of two ways, either run the revert using a .zip, or as a .exe connected to your computer. Personally, (and I know I'll probably lose credibility here lol) I prefer the .zip method, although many swear by the 'True RUU' .exe method.
**Here's a little aside to get you so you can get all of these files onto your phone. There's an option in Amon RA that mounts as removable storage to your computer so you can transfer files. Select 'USB-MS toggle' and then select 'USB-MS Toggle SDCard'. Then you can transfer all the files you need before continuing.
First, download the stock "ruu" zip from here:
http://goo.im/stock/vigor/ruu/RUU_V..._1.12_9k_1.83_V_APT_release_221502_signed.zip
and you will need to rename it to PH98IMG.zip and it will need to be placed on the root of your SDCard, not in any folder. Then download the MainVer.zip from here:
http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4\
which can be placed anywhere on the SDCard, but I would place it in the same place as the PH98IMG file for ease.
Once you have the PH98IMG file on the root of the SDCard, and have the MainVerLow zip there also, continue on.
To flash, go to the 'Flash zip' menu in recovery, and locate the setMainVerLow.zip. All this does is set the Main Version low, so hboot (or whatever) doesn't kick it back saying you can't downgrade. This flash will only take a second, and when complete, go back to the main Recovery menu.
It probably doesn't matter, but I would wipe data/factory reset again just to be safe. Do this by selecting 'Wipe' then 'Wipe ALL data/factory reset'. Once done, go back to the main Recovery screen.
Now you will want to reboot into bootloader, which I believe is under either 'Other' or 'Developer Options'
The phone will reboot, and book back into a screen similar to what you saw in fastboot. Some purple text will scroll saying stuff about looking for some file, and will find the one you just put on there and ask if you want to update now. Click the power button to confirm the update. It will show a progress bar on the side, as well as list the parts it has updated for you. It will get around halfway done or so and reboot itself, but DON'T TOUCH ANYTHING OR REMOVE THE BATTERY!!! lol it will reboot and finish the second half of the install. Once it's done, I think you need to hit 'Power' one more time to reboot, but once it does you will be rebooted and load up the completely stock ROM that originally shipped with the Rezound. Of course, from here you can go to the system update menu and update to the latest released OTA.
EDIT:: Just wanted to add, none of what I have written was developed/discovered/first-posted by me, it is the work of other, MUCH more intelligent people other than myself. So don't thank me for anything other than putting them all here lol
con247 said:
It is likely that he is S-ON and if he had a sense 4 rom installed, the new rom won't boot.
To the OP, can you please tell us the hboot version # (2.xx) it is either 2.10, 2.11,2.21, or 2.25. Also tell us if it says S-ON or S-OFF and unlocked, locked, or relocked, or juponutbear in purple at the top.
Click to expand...
Click to collapse
Will try to do that tonight.
I need to get it to power up first. I've had it plugged in at my desk all day and no luck so far. Let me get that taken care of and I'll go from there.
See if you can borrow a friends battery. A thunderbolt or my touch 4g slide battery will work too. You can also manually charge your battery by wiring a USB cable directly to it. Then you can get rid of the broken recovery and charge the battery fully.
good luck.. if you figure all this out you might like being rooted. i had several issues coming from an htc incredible to rezound the cwm was one.
Definitely get Amon Ra.
Sent from my ADR6425LVW
con247 said:
You can also manually charge your battery by wiring a USB cable directly to it. Then you can get rid of the broken recovery and charge the battery fully.
Click to expand...
Click to collapse
OK, that looks interesting. How do I do that?
EDIT - NEVER MIND - just found it.
phermes1 said:
OK, that looks interesting. How do I do that?
EDIT - NEVER MIND - just found it.
Click to expand...
Click to collapse
might be worth your while:
http://www.amazon.com/HTC-Thunderbo...ords=htc+thunderbolt+external+battery+charger
It doesn't charge very fast, but nice to have around.
Hopefully im not too late, but click my name and look at the threads that i have started. I used a ghetto IMO method to charge a dead droid x battery. You njeed a useless usb cable and a little time. Basically you strip the red and black wires and respectively touch them to the + and - leads on your battery. This will charge it relatively fast, you only need to hold it on the battery for a minute or so, just long enough.
But use this as a last plan method, i dont know how safe this is because the voltages may go in wrong or damage the battery, but to this day my droid x still works and i got it on the release week so its relatively old.
If you can, you should get a legit charger instead but if you want it done fast, give this a try or find another way. hope i helped but just make sure that if the battery heats up if you try this, you stop immediately. That could mean that the battery is about to explode or its breaking.
hope i helped, but if you want more help there is bound to be youtube videos on how to do this.
If you try this and something goes wrong its not my problem, but i have done this before and it should work.
Here is the link to the forum i made:
http://forum.xda-developers.com/showthread.php?t=1656547
Yakuzagang5 said:
No worries about the question, we're glad to help (since you didn't post this in the Development section lol)
Anyway, as long as you are S-ON, it shouldn't be too bad of a process, just lengthy. First, you'll need the Android SDK so you can get Fastboot, etc, as well as all the HTC device drivers installed, and you'll need to flash Amon RA recovery over.
Amon RA can be found here:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
**Make sure the Recovery file is in .img format, not .zip or anything, and place in the same folder as Fastboot (which is located in the Android SDK folder).**
You'll need to pull the battery, plug the USB cable into the computer, plug into the phone, replace battery, and hold down 'Power' + 'Volume Down' until the screen flashes the HTC screen. (Not sure if that's the only order, but it works). This will take you into Fastboot.
Next, you'll need to open a command prompt and 'cd' to your folder with Fastboot in it. Type:
Code:
fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
into the command prompt and hit enter. It should show on the command prompt a couple lines of time it took, etc. and when done you will have Amon RA recovery.
Click to expand...
Click to collapse
Update on my efforts. The steps above are where I'm currently at - so I haven't gotten far.
I got the $5 charger as suggested, so my phone will power on and I can at least get to the bootloader screen.
For whatever reason, it will NOT power on if I follow the steps above. It won't power up when I have it plugged into the PC. I can only power it on with it unplugged. So, when I run through the command prompt to install Amon Ra, it seems to be unable to connect to the phone. It displays 'Waiting for device' and nothing ever happens. At this point, it looks like I have everything I need on the PC side, but the phone is too boogered up to communicate with it.
I'm trying the options to clear out the memory right now. The problem there is that it goes to the screen with the top hat and orange circular arrow, and just sits there forever. It never acknowledges that it's done clearing memory.

[Q] Thunderbolt stuck in bootloader with s-on. What to do?

So long story short I have this thunderbolt that is not working any longer. All of this happened over a year ago so I am vague on what I did to get the phone in its currently ruined state. It was rooted with the stock image and after trying to put a CM rom on it that didn't work I mistakenly booted into the phones recovery instead of clock work.
I now get a security warning and it is now s-on. If i do a recovery or factory reset it just boots back into the bootloader. Attached is an image of what is current on the screen when I power it on. I can't get ADB working on this pc but my spare rig has it working in OSX. ADB does not display the device. I have a way to get files onto the sd card but I am still kinda new to all of this stuff and just looking for some help. So where do I proceed from here?
I am going out of my mind.
So the phone just literally booted into my rooted rom. So now the question is, how do I get rid of the security warning and get s-off permanently?
At my end.
After a long day of trying to fix this thing and crawling all over the internet reading different posts I officially don't have a damn clue as to how to fix this. I am pretty sure the bootloader is corrupted and seeing as the phone is so old now it's really hard to find working links to downloads for this device.

I think I have turned my brand new HTC 10 into a concrete block...

Hello all!
First of all, I am no developer.
Long story short.. I purchased an HTC 10 because I was sick and tired of my at&t galaxy s5 being bootlocked. I received the 10 and set out the next day to root it. I followed a video on youtube (not saying that the info was not correct...I may have done something wrong...not trying to discredit anybody) to the letter and lo and behold I ended up in a bootloop. My heart probably came close to a complete blockage at this point. This bootloop lasted maybe a minute before it would reboot. So... In my infinite wisdom I chose to relock the bootloader. Oh Boy!!! Fun times were ahead for me!! As soon as I relocked said bootloader, the bootloop increased its timing to about 1 point 5 seconds. I remember waking up on the floor in the fetal position. Now I am stuck with a phone that adb will not recognize. It does however recognize the device at the fastboot devices prompt. So my question is this.... Is this a salvageable phone? If so, How would one go about fixing this problem?
*** Relocked ***
htc_pmew1 pvt S-ON
os-2.28.617.8
I would prefer that the money I spent on this thing would amount to something more than a small ant bed.
Any help at all would be greatly appreciated. Also I have been doing a lot of digging around and (I may be wrong) but. I could not find this scenario in the forums here. I apologize if this has already been covered.
...So..after looking around for a bit more, I discovered out that there is a way to flash a ruu/zip from an sd card. I have tried multiple times with what I thought were the right ones. As I am unable to boot into recovery, I feel I am limited as to what I should do. I have read about that I should wipe dalvik but I am very limited in my knowledge on an android system and would prefer to not mess this phone up anymore than it already is. I was trying to root and I used TWRP as the recovery but I never made it to the end before it started the loop. The Phone is an htc 10 unlocked version. and it just constantly reboots about 3 seconds apart. ADB says no device connected, so I cannot execute commands that way... really at a loss here. all the tutorials I have read refer to using and and being able to boot into rrecovery. when i boot into recovery, I get an immediate reboot and the 3 second bootloop forever. Is there a way to use twrp to somehow resolve this?Is there a tool that will help me at least get into recovery mode?
SOLVED... Ran across Batchtool by sneakyghost. Quite the bunch of tools there! Ended up solving my problem by placing the stock RUU in the root folder as the batch tool. Before I could not install from a factory RUU (would not recognize the phone through ADB or install the RUU. After the install of the batch tool I was able to get a clean install back to my factory settings.. Now I am free to mess it up again!!
BIG THANKS TO SNEAKYGHOST!!!!!
I'm unsure why the batch tool has worked for you and the sdcard method didn't - getting fastboot to work and all the bits and pieces together (drivers, Windows VCRedist, correct fastboot, correct adb) is usually more error prone than just identifying the correct zip and placing that in your sdcard root.
At this time, I'm a bit in a "scratch my head" mood, thinking this is weird. Same zip? Really the same zip didn't work from sdcard but would work in fastboot? I think I haven't come across that myself yet (non booting phones are a daily thing, almost).
I wish I had the time to analyze your steps with you, so I could gain understanding as to why that happened, so I can use that in the future, but alas! I have no time for XDA and deep digging around in issues of other people. Lately I can't even solve my own phone's problems anymore due to too many other things going on.
Well, glad it worked for your phone, anyhow. I'll keep this in mind for the next one messing up his/her phone.

Categories

Resources