A friend of mines son was installing roms on his HTC Hero and bootlooped it. I've followed all the methods I could find to put this thing in a flash mode, or a recovery mode but all it does is flash the HTC logo. Home/End seems to be the way to get into the recovery mode but it does nothing.
Can you put this thing into a flash only mode and at least get it to its original state? It is unknown as to what exactly he did to it. I was told that he had been installing lots of roms and eventually one made it do this.
I found this link http://forum.xda-developers.com/showthread.php?t=682551&page=2 but pushing the volume up/end keys only makes it vibrate 3 times then sit idle not doing anything.
thanks.
talktojer said:
A friend of mines son was installing roms on his HTC Hero and bootlooped it. I've followed all the methods I could find to put this thing in a flash mode, or a recovery mode but all it does is flash the HTC logo. Home/End seems to be the way to get into the recovery mode but it does nothing.
Can you put this thing into a flash only mode and at least get it to its original state? It is unknown as to what exactly he did to it. I was told that he had been installing lots of roms and eventually one made it do this.
I found this link http://forum.xda-developers.com/showthread.php?t=682551&page=2 but pushing the volume up/end keys only makes it vibrate 3 times then sit idle not doing anything.
thanks.
Click to expand...
Click to collapse
The only way to effectively help you/him is to know how he got there, and what recovery/rom/kernel/theme/etc he is running. It would also help to know if this phone has an eng-spl fastboot or an s-off hboot.
il Duce said:
The only way to effectively help you/him is to know how he got there, and what recovery/rom/kernel/theme/etc he is running. It would also help to know if this phone has an eng-spl fastboot or an s-off hboot.
Click to expand...
Click to collapse
theres no standard way to get to a flash mode with a sprint htc hero? what are some other key combinations i might try?
talktojer said:
theres no standard way to get to a flash mode with a sprint htc hero? what are some other key combinations i might try?
Click to expand...
Click to collapse
you mean like this: hold home and then power?
il Duce said:
you mean like this: hold home and then power?
Click to expand...
Click to collapse
yeah, so if that didnt work..screwed?
talktojer said:
yeah, so if that didnt work..screwed?
Click to expand...
Click to collapse
Not really... in very rare cases has the hero been bricked.
If nothing else, you could always run the Sprint/HTC RUU through your computer, that will restore the Hero to "Out-of-Box" state. From there you could root back again and flash any ROM you would like.
With the phone turned off, press and hold the volume up button. Whole holding it press the power button. When you see the logo let go of the volume up button. If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Sent from my HERO200 using XDA App
unCoRrUpTeD said:
With the phone turned off, press and hold the volume up button. Whole holding it press the power button. When you see the logo let go of the volume up button. If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
how do I get into this fastboot mode? I'd love to restore it to factory software, but I'm unable to figure out how to get the phone into a mode that the PC will recognize. Volume up/end vibrates 3 times but never actually turns on or shows a logo. just stays black. If I could get this thing back to its original state that would be great.
unCoRrUpTeD said:
If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Click to expand...
Click to collapse
Anyone know how to do this? I can't figure out how to get into the fastboot mode. I run the ruu executable, and it says it can't find the phone. I'm sure I need to put it in some kind of flash mode, but seem to be unable.
Not to hijack your thread, but I'm having this same problem. I've run several ROMs including cyanogen 6.0 and 6.1 and today was installing the cyanogen 7 with 2.3 android. I wiped everything and flashed the rom and the gapps and the phone went into constant reboot cycles. I could at that point, hold the power/home and get it back to the recovery menu. I had the Amon RA recovery and thought I would try the 3.0 clockwork, so I flashed that recovery image...rebooted without a problem. I tried wiping and reflashing, but still the constant reboot. So I took the advice on the wiki and flashed the DecaFuct-12222010-691.zip kernel. My phone rebooted and did not start the cycling, so I thought it was an improvement. However, 1/2 an hour later, it's still sitting at the HTC logo and the power/home does not reboot into recovery. Nor does trying to adb find any devices.
Apparently I haven't posted enough on these forums to be able to post to the dev thread. But I've done some base development work on the phone and have been using adb for over a year now. Any help on getting back to a working phone would be greatly appreciated!
Lynne
Ah, a coworker manager to get the buttons to respond. Yay! At least I'm back to recovery and can push a different ROM. Tho not CM7 since it keeps rebooting constantly!
lrandolph said:
Ah, a coworker manager to get the buttons to respond. Yay! At least I'm back to recovery and can push a different ROM. Tho not CM7 since it keeps rebooting constantly!
Click to expand...
Click to collapse
any idea what he/she did to get the buttons to respond? I still am unable to get into the recovery mode.
talktojer said:
any idea what he/she did to get the buttons to respond? I still am unable to get into the recovery mode.
Click to expand...
Click to collapse
First, power off and remove the battery. Make sure the USB is not plugged in
This is why you get 3 vibrations and no power on. If it does this again, remove the battery and start over
With the power off and the USB unplugged, hold Vol Up and press power on (End key)
It should then boot into fastboot. (a white page with green letters) At this time, plug the USB in (should change from Fastboot to Fastboot USB) and run the RUU .5 or .6 from your computer.
AT some point the RUU install will say waiting for bootloader. When this happens, you will already be in bootloader (Fastboot USB)
This should work to get you back to fully unrooted stock ROM. From there, reroot, install a custom recovery and rom.
Let me know if this works
ccrosno said:
First, power off and remove the battery. Make sure the USB is not plugged in
This is why you get 3 vibrations and no power on. If it does this again, remove the battery and start over
With the power off and the USB unplugged, hold Vol Up and press power on (End key)
It should then boot into fastboot. (a white page with green letters) At this time, plug the USB in (should change from Fastboot to Fastboot USB) and run the RUU .5 or .6 from your computer.
AT some point the RUU install will say waiting for bootloader. When this happens, you will already be in bootloader (Fastboot USB)
This should work to get you back to fully unrooted stock ROM. From there, reroot, install a custom recovery and rom.
Let me know if this works
Click to expand...
Click to collapse
here's what happens.
1. Remove battery
2. Replace battery
3. Press and hold volume up
4. While holding volume up, press and hold end key to turn unit on.
5. Unit vibrates 3 times and never powers on
This is without USB plugged in.
I asked the guy who owns the phone what he was doing, he said he had flashed ASOP Gingerbread or something and it never worked again.
talktojer said:
here's what happens.
1. Remove battery
2. Replace battery
3. Press and hold volume up
4. While holding volume up, press and hold end key to turn unit on.
5. Unit vibrates 3 times and never powers on
This is without USB plugged in.
I asked the guy who owns the phone what he was doing, he said he had flashed ASOP Gingerbread or something and it never worked again.
Click to expand...
Click to collapse
Interesting. Mine only does the 3 vibrate thing when I have the USB plugged in and I am trying to enter Fastboot. I unplug the USB, remove the battery, replace the battery, hold vol up and press end. Bing, right into Fastboot.
Do you know if he has the ENG SPL/S-Off installed? If not, the issue may lay in that. Not for sure though.
Also, it may have to do with the way the phone was originally rooted, that has an affect on things as well. Some of the overclocked kernels have an affect on boot. Some Heros wont boot with the kernel set to over 691.
I have installed every build pf ASOP 2.3.2 GB that has been posted, now grated they each had there issues but none of them put me in a loop or froze the phone.
I would also suggest downloading android commander to your computer. Just Google android commander and you will find it. With this program you can boot to bootloader. If you are getting to the HTC screen then Android Commander should recognize the phone. It is a great program.
talktojer said:
Anyone know how to do this? I can't figure out how to get into the fastboot mode. I run the ruu executable, and it says it can't find the phone. I'm sure I need to put it in some kind of flash mode, but seem to be unable.
Click to expand...
Click to collapse
Not sure, but you may try removing the sdcard and/or putting a different one in. Or when the phone first gets to the HTC screen press and hold the menu button and keep holding it.
Sent from my dual-booted liquidsense 2.1
unCoRrUpTeD said:
Not sure, but you may try removing the sdcard and/or putting a different one in. Or when the phone first gets to the HTC screen press and hold the menu button and keep holding it.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
ive removed the sdcard, results are no different.
ccrosno said:
Interesting. Mine only does the 3 vibrate thing when I have the USB plugged in and I am trying to enter Fastboot. I unplug the USB, remove the battery, replace the battery, hold vol up and press end. Bing, right into Fastboot.
Do you know if he has the ENG SPL/S-Off installed? If not, the issue may lay in that. Not for sure though.
Also, it may have to do with the way the phone was originally rooted, that has an affect on things as well. Some of the overclocked kernels have an affect on boot. Some Heros wont boot with the kernel set to over 691.
I have installed every build pf ASOP 2.3.2 GB that has been posted, now grated they each had there issues but none of them put me in a loop or froze the phone.
I would also suggest downloading android commander to your computer. Just Google android commander and you will find it. With this program you can boot to bootloader. If you are getting to the HTC screen then Android Commander should recognize the phone. It is a great program.
Click to expand...
Click to collapse
android commander relies on adb..i've already tried adb and it can't see the device. already tried that the first night. I think I'm about out of options.
talktojer said:
android commander relies on adb..i've already tried adb and it can't see the device. already tried that the first night. I think I'm about out of options.
Click to expand...
Click to collapse
Interesting you say that. Here are 2 snips taken at the same time. One of my ADB shell showing no devics found and the other of my android command shell clearly showing connection to the device.
Try the android commander. It is a great program and it is GUI based.
Let me know
Edit: Even stranger, although ADB shows no devices, if I type LS, a list of the phone directories shows up.
ccrosno said:
Interesting you say that. Here are 2 snips taken at the same time. One of my ADB shell showing no devics found and the other of my android command shell clearly showing connection to the device.
Try the android commander. It is a great program and it is GUI based.
Let me know
Edit: Even stranger, although ADB shows no devices, if I type LS, a list of the phone directories shows up.
Click to expand...
Click to collapse
You would actually do
adb devices
You don't do it from inside adb.
Sent from my dual-booted liquidsense 2.1
Related
Hi folks,
This is a repost from a wrong forum. Sorry guys
I have a HTC Dream which I guess I tried unsuccessfully to root. I used the method to load the software as described here:
http://forum.xda-developers.com/show...&postcount=130
At step 10, "10.Apply “update.zip”, wait until phone idles, then press the HOME + BACK buttons. It will reboot, finish writing “hboot.img”, then reboot again into Recovery mode by itself. Do not interrupt it at all until it's done."; I think I followed it verbatem only to find my phone is now in a constant boot loop
It shows a Rogers logo and I'm unable to boot into any mode (recovery or otherwise) with any key combo (I've tried Camera+Power, Home + Power/End) but the phone doesn't respond and keeps showing the Rogers screen.
I saw some instructions on what to do when this happens. One suggestion was to copy DREAIMG.nbh to the SD-Card and try booting with the Camera +End Button sequence, but the phone doesn't respond at all).
Any ideas on what can be done? Is it bricked? I can see the logo and I know it boots...perhaps the bootloader is trashed and needs to be reinstalled. Any help would be greatly appreciated!
LOL, ok, I'll bite.....
Unfortunately all the same responses from the other thread you started still apply. Have you taken any of the advice from AdrianK?
DirectMatrix said:
LOL, ok, I'll bite.....
Unfortunately all the same responses from the other thread you started still apply. Have you taken any of the advice from AdrianK?
Click to expand...
Click to collapse
Haha...if I wasn't insane atm, I would find that funny . Come one...there's gotta be a way into this thing
bdelbono said:
Haha...if I wasn't insane atm, I would find that funny . Come one...there's gotta be a way into this thing
Click to expand...
Click to collapse
Your link to the post you followed is invalid....I don't know much about the rogers process, but it sounds like if you are unable to get any key combos to work then your bricked.
DirectMatrix said:
Your link to the post you followed is invalid....I don't know much about the rogers process, but it sounds like if you are unable to get any key combos to work then your bricked.
Click to expand...
Click to collapse
I guess you are right. The phone does boot. It simply stays at the boot screen showing the rogers logo. Taking the battery turns if off. No response any key combos and it doesn't show up anywhere with adb/fastboot when connected to USB. Any ideas or hopes?
DirectMatrix said:
Your link to the post you followed is invalid....I don't know much about the rogers process, but it sounds like if you are unable to get any key combos to work then your bricked.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4280573&postcount=130
bdelbono said:
I guess you are right. The phone does boot. It simply stays at the boot screen showing the rogers logo. Taking the battery turns if off. No response any key combos and it doesn't show up anywhere with adb/fastboot when connected to USB. Any ideas or hopes?
Click to expand...
Click to collapse
What happens when you put the battery back in? Comes on by itself and starts bootlooping or do you have to turn it on? If you have adb setup properly, you can run the ddms.bat file that's in the tools folder of the sdk. With you phone plugged in via usb, run a logcat and follow it for a while....if it starts repeating over and over, then its a definite bootloop. That, combined with you not getting any key combos to work suggests a brick
DirectMatrix said:
What happens when you put the battery back in? Comes on by itself and starts bootlooping or do you have to turn it on? If you have adb setup properly, you can run the ddms.bat file that's in the tools folder of the sdk. With you phone plugged in via usb, run a logcat and follow it for a while....if it starts repeating over and over, then its a definite bootloop. That, combined with you not getting any key combos to work suggests a brick
Click to expand...
Click to collapse
The phone does not turn on, when the battery is put in. Only hitting the power button, which is when it vibrates slightly and becomes unresponsive. Given what I'm seeing, its doing something...the devices become hot until the battery runs out.
I did setup adb (and java for ddms.bat). Though there is no output in logcat (Simply Failed at the top). I've tried various key (Home+Power Camera+power etc) combinations to see if it burbs, but nothing.
Any ideas on what I can try. I'm fairly good with linux/unix and setting up development environments. Thanks.
If it's looping on the second screen, then you're not bricked. If I was to guess, maybe your SD is not partitioned correctly for the ROM you're flashing...if I was to guess.
BlackElvis79 said:
If it's looping on the second screen, then you're not bricked. If I was to guess, maybe your SD is not partitioned correctly for the ROM you're flashing...if I was to guess.
Click to expand...
Click to collapse
Hmm...where is this second screen? I unfortunately have no output (from the time I hit power to any useable/known key combos ) on my mmda.bat java interface. None whatsoever. Is there a way to see the raw data thru USB to see what it does when it boots up? And if so, how?
Same problem here
bdelbono said:
I guess you are right. The phone does boot. It simply stays at the boot screen showing the rogers logo. Taking the battery turns if off. No response any key combos and it doesn't show up anywhere with adb/fastboot when connected to USB. Any ideas or hopes?
Click to expand...
Click to collapse
same problem here, the device comes on when the power button is pressed, a slight vibrate confirms this, then just hangs on "HTC Dream" screen.
Tried every key combo I can find to no avail, please, anybody help!!!!
Hello people,
I recently installed GalaxySense Rom (Search "oozeroo" on Google) for my Samsung Captivate AT&T, and it was working fine, until I changed a few settings, then it said it was going to Hot Boot, so the hot boot worked fine. Then, I turned off my phone and turned it back on, and it does not boot. I tried some stuff (check the Situations). My phone is stuck at "Galaxy S Cyanogen(Mod)" (Picture Included!!!)
Situation:
-No Download Mode
-No recovery mode
-Flashed this rom with rom manager (wiped dalvik cache only)
-TRIED installing Clockworkmod recovery, but wont work (not booting into recovery)
-Only an internal SD inside phone, 14 Gigs.
(Ask me for more info if needed please)
Thank you so much, and please help.
--DV
dvasavda said:
Hello people,
I recently installed GalaxySense Rom (Search "oozeroo" on Google) for my Samsung Captivate AT&T, and it was working fine, until I changed a few settings, then it said it was going to Hot Boot, so the hot boot worked fine. Then, I turned off my phone and turned it back on, and it does not boot. I tried some stuff (check the Situations). My phone is stuck at "Galaxy S Cyanogen(Mod)" (Picture Included!!!)
Situation:
-No Download Mode
-No recovery mode
-Flashed this rom with rom manager (wiped dalvik cache only)
-TRIED installing Clockworkmod recovery, but wont work (not booting into recovery)
-Only an internal SD inside phone, 14 Gigs.
(Ask me for more info if needed please)
Thank you so much, and please help.
--DV
Click to expand...
Click to collapse
What key combo are you trying for recovery? You have a JIG laying around? If not, I'd go get one regardless of how invincible you think your phone may be. Maybe you could try Adam's one-click unbrick. http://forum.xda-developers.com/showthread.php?t=1153310 I don't know what conditions need to be met for it (your phone) to be recognized, but I'd give it a shot anyway.
I am using:
take out battery, hold both volume buttons, plug in USB, then put in battery, all with both volume buttons held the whole time.
No, I do not have a jig, I want to get one though
-I do not care to erase everything I have, I tried using Odin3 one click downloader, it worked for me once, when my phone actually went download mode
dvasavda said:
I am using:
take out battery, hold both volume buttons, plug in USB, then put in battery, all with both volume buttons held the whole time.
No, I do not have a jig, I want to get one though
-I do not care to erase everything I have, I tried using Odin3 one click downloader, it worked for me once, when my phone actually went download mode
Click to expand...
Click to collapse
remove sim and microsd. You have to have your batt back in before you hold volume+- and insert USB
what recovery key combo you using?
still nothing buddy, tried your technique
thanks dude
i did try returning it, but they didnt accept it (costco), NOT because I had another romm installed... but because it wasnt booting!
-although, I do not have the battery sign show up, it just has the circle, then it goes to galaxy s screen
Twicebak3d said:
What key combo are you trying for recovery? You have a JIG laying around? If not, I'd go get one regardless of how invincible you think your phone may be. Maybe you could try Adam's one-click unbrick. http://forum.xda-developers.com/showthread.php?t=1153310 I don't know what conditions need to be met for it (your phone) to be recognized, but I'd give it a shot anyway.
Click to expand...
Click to collapse
Dont have linux
post as much as you want on this thread, i dont really care
any other ideas?
Well..... has galaxysense been actually ported to the captivate yet? I doubt this'll work but.... try vol down + home + power. You could vary vol down with vol up for recovery mode as well. Like I said.... doubt they'll work.
It has ported to captivate, there is a captivate section on website
Home button? you mean the touchscreen/virtual home button? When do you press it:when it lights up?
-btw, i tried the brick fix thing, but it didnt recognize my phone, because it was only booting
dvasavda said:
It has ported to captivate, there is a captivate section on website
Home button? you mean the touchscreen/virtual home button? When do you press it:when it lights up?
-btw, i tried the brick fix thing, but it didnt recognize my phone, because it was only booting
Click to expand...
Click to collapse
There's a reason I didn't think it'd work lol. Those are i9000 key combos lol. Get a jig imo.
what are the sgh-i897 combos?
can you go into safe mode with this?
and my home button question please?
dvasavda said:
what are the sgh-i897 combos?
can you go into safe mode with this?
and my home button question please?
Click to expand...
Click to collapse
Yeah I meant that virtual key. cappy combos are vol up/down + power for recovery mode for me.
no recovery for me
actually, at first, I had no recovery on my new rom, so... (I dont want to tell you this!) but I looked for a stock recovery, and I put it over the old recovery file in the system.
dvasavda said:
no recovery for me
actually, at first, I had no recovery on my new rom, so... (I dont want to tell you this!) but I looked for a stock recovery, and I put it over the old recovery file in the system.
Click to expand...
Click to collapse
Do you know if you flashed 3 button? try vol up vol down power. hold those while inserting usb
nothing dude yet, i did not flash the 3 button fix, (oops!)
i did notice that, when the phone is booting up, and I connect, the phone is half recognized with computer, and yes I did install drivers.
If i go to device manager, it says Captivate, but with a yellow exclamation mark
have to go to, talk to you tommorow morning!
thanks buddy, i appreciate it!
dvasavda said:
nothing dude yet, i did not flash the 3 button fix, (oops!)
i did notice that, when the phone is booting up, and I connect, the phone is half recognized with computer, and yes I did install drivers.
If i go to device manager, it says Captivate, but with a yellow exclamation mark
Click to expand...
Click to collapse
I wonder if it'd be recognized by ADB if you install Nexus S drivers. try using that as the drivers for the marked captivate in dev manager. http://developer.android.com/sdk/win-usb.html#
If it changes name to Android Composite ADB interface, then you can ADB into recovery and reflash. I don't see how but if you don't have a jig.... might as well try.
(just raised your thanks meter!)
can I cut off an old charger that fits the captivate, and use that?
dvasavda said:
(just raised your thanks meter!)
can I cut off an old charger that fits the captivate, and use that?
Click to expand...
Click to collapse
For a JIG? Possibly. You have to jump pins 4 and 5 with 300k worth of resistors. if you look in my sig, there's also a guide to just making one without a USB. Regardless of how you apply the resistance to your phone, you still need 301k. There is a window. I've seen 294k jigs work, so just as long as resistance is in a certain range across those two pins, it will work.
ok, thanks
I tried adb rebooting, but says error device not found
(same thing happened when my device was working and on)
RESOLVED
Silver HTC One for AT&T; bootloader unlocked, rooted, s-on
I tried to flash a 4.1.2 ROM on the phone earlier today through CWM. No errors were given during the process. After the phone restarted the touch screen is now disabled. All three hardware keys seem to be working fine (power, v-up, v-down). Since the touchscreen is not working I cannot get past the initial lock screen. If I try and restart the phone by holding power it takes a long time >5 minutes of holding down power, "To restart your phone continue to press and hold power for 3, 2, 1, comes up and then stays at 1 for a long time.
If I connect the phone to my mac android file transfer opens up and I can see the files on the phone. However, if I try to find the device using 'adb devices' the list of attached devices is empty.
I would like to put a different ROM on and then flash that but because I am unable to do a power down (only restart after a long time) or use adb to re-boot into fastboot or recovery I am stuck.
Anything you guys could give me to point me in the right direction would be greatly appreciated.
also I installed HTC sync manager and it launches after the device is attached, but does not indicate that my device is attached.
Thanks!
You need a 4.3 based ROM. Push via ADB and install via cwm or adb sideload
sent from my mobile device
SaHiLzZ said:
You need a 4.3 based ROM. Push via ADB and install via cwm or adb sideload
sent from my mobile device
Click to expand...
Click to collapse
But wouldnt I need adb to recognize my device? At the moment I cannot even get it to show up in devices when it is connected.
slapshot123 said:
But wouldnt I need adb to recognize my device? At the moment I cannot even get it to show up in devices when it is connected.
Click to expand...
Click to collapse
Just copy the 4.3 rom via the file manager, then restart with however long it takes. While restarting, keep the vol-down button pressed. You'll reboot to bootloader. From there, go to recovery and select your 4.3 rom.
Sent from my iPod touch using Tapatalk
slapshot123 said:
But wouldnt I need adb to recognize my device? At the moment I cannot even get it to show up in devices when it is connected.
Click to expand...
Click to collapse
Put ur phone on Recovery then try to adb push or Sideload....
OTG cable is also an option!
sent from my mobile device
somesli they
SaHiLzZ said:
OTG cable is also an option!
sent from my mobile device
Click to expand...
Click to collapse
Can you elaborate on the OTG cable? It may be my best option at the moment because I cannot get the phone to reboot at all let alone into recovery. I tried to restart while holding down power and vol-down (like n1234d said) for about 20 minutes and the phone did not restart.
You could use an OTG cable and a USB drive to get the ROM onto the phone inside recovery. Unfortunately, you still need to reboot to recovery. If the phone can't reboot, I'm not sure what to do.
slapshot123 said:
Can you elaborate on the OTG cable? It may be my best option at the moment because I cannot get the phone to reboot at all let alone into recovery. I tried to restart while holding down power and vol-down (like n1234d said) for about 20 minutes and the phone did not restart.
Click to expand...
Click to collapse
Just hold the power button and power it off....
then try to get in recovery from bootloader....
the phone wont get recognized via adb if not in recovery mode cause the USB debugging would be turned off....
the phone WILL power off if you keep the power button pressed for 20-30 seconds and should reboot.
SaHiLzZ said:
the phone WILL power off if you keep the power button pressed for 20-30 seconds and should reboot.
Click to expand...
Click to collapse
Thanks, but for whatever reason it took holding down the power button for 40 minutes.
fenstre said:
You could use an OTG cable and a USB drive to get the ROM onto the phone inside recovery. Unfortunately, you still need to reboot to recovery. If the phone can't reboot, I'm not sure what to do.
Click to expand...
Click to collapse
Thanks for you suggestions, as I mentioned above I got the phone to reboot into recovery after holding down power for an insanely long time. From there I was able to use adb to get everything sorted out.
So my problem is resolved, how do I close/delete this thread? Thanks for all your suggestions.
slapshot123 said:
Thanks, but for whatever reason it took holding down the power button for 40 minutes.
Thanks for you suggestions, as I mentioned above I got the phone to reboot into recovery after holding down power for an insanely long time. From there I was able to use adb to get everything sorted out.
So my problem is resolved, how do I close/delete this thread? Thanks for all your suggestions.
Click to expand...
Click to collapse
Haha 40 minutes, yeah right.
Sent from my HTC One using Tapatalk
xcrazydx said:
Haha 40 minutes, yeah right.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Cool, nice productive comment. I can assure you it was, watched two episodes of workaholics waiting for the damn thing.
slapshot123 said:
Cool, nice productive comment. I can assure you it was, watched two episodes of workaholics waiting for the damn thing.
Click to expand...
Click to collapse
I'm pretty sure you unknowingly kept leaving the power/volume buttons because of which the phone finally rebooted when you got it right
Sent from my HTC One using Tapatalk
n1234d said:
I'm pretty sure you unknowingly kept leaving the power/volume buttons because of which the phone finally rebooted when you got it right
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Is this really necessary?
slapshot123 said:
Thanks, but for whatever reason it took holding down the power button for 40 minutes.
Thanks for you suggestions, as I mentioned above I got the phone to reboot into recovery after holding down power for an insanely long time. From there I was able to use adb to get everything sorted out.
So my problem is resolved, how do I close/delete this thread? Thanks for all your suggestions.
Click to expand...
Click to collapse
Sorry to hear it took a while, thats odd. But you are all done now. Edit your first post and change the subject to [SOLVED] .. thats all
Is the One Mini 2 possible to root? I've seen a lot saying 'not yet', but it's all fairly old. If so, is there a tutorial/walkthrough somewhere?
koberulz said:
Is the One Mini 2 possible to root? I've seen a lot saying 'not yet', but it's all fairly old. If so, is there a tutorial/walkthrough somewhere?
Click to expand...
Click to collapse
yes root its possible for htc one mini 2.
1- use htc dev website to unlock bootloader and choose all other supported phones. Follow directions.
2-Flash recovery TWRP and flash superuser.zip.
Google it or find in forum tutorials for 2nd step.
I've tried searching, but all I can find is either out of date and stating there's no solution yet, or applies to the original Mini, not the Mini 2.
koberulz said:
I've tried searching, but all I can find is either out of date and stating there's no solution yet, or applies to the original Mini, not the Mini 2.
Click to expand...
Click to collapse
like i said:
go to http://www.htcdev.com/ unlock bootloader. and follow instructions above.
mine its rooted and so lot of others in this forum.
http://forum.xda-developers.com/one-mini-2/help
I got that, it's the "flash TWRP and superuser.zip" that's the issue.
koberulz said:
I got that, it's the "flash TWRP and superuser.zip" that's the issue.
Click to expand...
Click to collapse
1- Download the TWRP Recovery file here and copy it to the C:/Unlock folder created in the Bootloader Unlock Tutorial or the folder you use for HTC unlock
2- Now use the Shortcut “Windowskey + R” and type cmd into the textfield. Press OK to start the Shell.cmd
3- Now we need to navigate to our Unlock Folder by using the command “cd c:/Unlock“ (without “”) and pressing enter
4- Power off your HTC One Mini and boot it back up while holding the Volume Down and Power-Key until you see the bootloader
5- Select “Fastboot” with the volume keys and press power to select
6- Connect your HTC One Mini through original usb to your pc
7- In the Command-Window enter the command „fastboot flash recovery "twrp-2.7.1.0-20140802-memul.img“ (without „“) and press enter
8- The Installation should only take a few seconds and will give a short reports at the end
9- Your HTC One Mini should now have the TWRP Custom Recovery installed
TWRP will try flash SuperUser, it didnt work for me so,
Send UPDATE-SuperSU-v2.02.zip to sdcard and use TWRP to flash it
You must have updated drivers (install htc sync) and original usb cable.
kativiti said:
1- Download the TWRP Recovery file here and copy it to the C:/Unlock folder created in the Bootloader Unlock Tutorial or the folder you use for HTC unlock
2- Now use the Shortcut “Windowskey + R” and type cmd into the textfield. Press OK to start the Shell.cmd
3- Now we need to navigate to our Unlock Folder by using the command “cd c:/Unlock“ (without “”) and pressing enter
4- Power off your HTC One Mini and boot it back up while holding the Volume Down and Power-Key until you see the bootloader
5- Select “Fastboot” with the volume keys and press power to select
6- Connect your HTC One Mini through original usb to your pc
7- In the Command-Window enter the command „fastboot flash recovery "twrp.img“ (without „“) and press enter
8- The Installation should only take a few seconds and will give a short reports at the end
9- Your HTC One Mini should now have the TWRP Custom Recovery installed
TWRP will try flash SuperUser, it didnt work for me so,
Send UPDATE-SuperSU-v2.02.zip to sdcard and use TWRP to flash it
You must have updated drivers (install htc sync) and original usb cable.
Click to expand...
Click to collapse
I got TWRP in. None of the buttons worked. Eventually the screen went blank, I powered back on and just got a 'swipe to unlock' screen. Couldn't swipe, either. So...somehow the touchscreen isn't working?
koberulz said:
I got TWRP in. None of the buttons worked. Eventually the screen went blank, I powered back on and just got a 'swipe to unlock' screen. Couldn't swipe, either. So...somehow the touchscreen isn't working?
Click to expand...
Click to collapse
Try and reboot the phone by holding volume down and power for 10 seconds.
That doesn't do anything. Seems like the only button that does anything is power, and that just turns the screen on if it's off, or to full brightness if it's dimmed (which it does for a second or two before turning off).
I've kept the screen on and managed to run the battery down to 52%. My plan at this point is to run it completely flat, forcing the phone to shut down, then charge it up a bit and see if I can boot. Beyond that, I'm out of ideas and even if I manage to reboot I don't see how TWRP's going to magically start working.
It boots into Android by default, right? And you have to use the Fastboot menu to get to TWRP? No idea how I got to it the first time, actually, and it's been years since I've used it on my old phone.
EDIT: It's TWRP v2.7.1.0. According to the website, the newest version, 2.8.0.0 "[fixes] a bug that caused weird graphics and touch issues". Should I be using this version instead? It doesn't seem to support the Mini 2.
Check this http://forum.xda-developers.com/showthread.php?t=2394744
Try holding power under a bright light..
turn screen off. and under bright light turn it back on. see if it works
No dice. Down to 15% battery at this point anyway, shouldn't be too much longer before it's flat. Then, fingers crossed it works.
How do I get back to TWRP? Fastboot then select 'recovery' (I think I recall that being one of the options)?
koberulz said:
No dice. Down to 15% battery at this point anyway, shouldn't be too much longer before it's flat. Then, fingers crossed it works.
How do I get back to TWRP? Fastboot then select 'recovery' (I think I recall that being one of the options)?
Click to expand...
Click to collapse
just to be on the safe side, i would stay in fastboot and re-flash TWRP
The battery finally went flat, but then as soon as I plugged the phone in it booted into TWRP...which still doesn't work. Have unplugged it again. No idea where to go from here. Tried the "adb reboot bootloader" command from the thread you linked to, and all it did was boot right back into TWRP.
koberulz said:
That doesn't do anything. Seems like the only button that does anything is power, and that just turns the screen on if it's off, or to full brightness if it's dimmed (which it does for a second or two before turning off).
I've kept the screen on and managed to run the battery down to 52%. My plan at this point is to run it completely flat, forcing the phone to shut down, then charge it up a bit and see if I can boot. Beyond that, I'm out of ideas and even if I manage to reboot I don't see how TWRP's going to magically start working.
It boots into Android by default, right? And you have to use the Fastboot menu to get to TWRP? No idea how I got to it the first time, actually, and it's been years since I've used it on my old phone.
EDIT: It's TWRP v2.7.1.0. According to the website, the newest version, 2.8.0.0 "[fixes] a bug that caused weird graphics and touch issues". Should I be using this version instead? It doesn't seem to support the Mini 2.
Click to expand...
Click to collapse
this happened to me, just hold power + vol down + vol up for 10 seconds, phone will reboot.
edit: whilst doing this dont have the usb plugged in. I have noticed having the usb plugged in, a restart sends it straight back to twrp - hence the same issue.
It reboots straight into TWRP when plugged into either the wall or my computer, and just shuts down when not plugged in at all. Can't get it to boot at all, with either volume down + power or just power, but the second I plug it in it boots TWRP.
koberulz said:
It reboots straight into TWRP when plugged into either the wall or my computer, and just shuts down when not plugged in at all. Can't get it to boot at all, with either volume down + power or just power, but the second I plug it in it boots TWRP.
Click to expand...
Click to collapse
ok try, plugging laptop usb port and hold power + vol down + vol up together for 10secs.
Left it plugged in for a while, let the battery build up, and managed to get it booted into Android. So that's a start, at least.
So: fastboot, "fastboot erase recovery" then "fastboot flash recovery twrp.img"?
koberulz said:
Left it plugged in for a while, let the battery build up, and managed to get it booted into Android. So that's a start, at least.
So: fastboot, "fastboot erase recovery" then "fastboot flash recovery twrp.img"?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img should override. i would also download another version just in case that one is corrupted
this is where i got it originally
http://forum.xda-developers.com/one-mini-2/orig-development/recovery-twp-2-7-1-0-one-mini-2-t2801370
You mean another version from another source, or another copy via that link? Not sure where else to get a copy; I assume you get links from the TWRP website after selecting your phone model but the HTC One Mini 2 isn't listed.
I saw somewhere that simply overriding could cause problems, therefore it's best to erase first?
koberulz said:
You mean another version from another source, or another copy via that link? Not sure where else to get a copy; I assume you get links from the TWRP website after selecting your phone model but the HTC One Mini 2 isn't listed.
I saw somewhere that simply overriding could cause problems, therefore it's best to erase first?
Click to expand...
Click to collapse
Check post above this.
TWRP for htc one mini 2 its not yet avaiable in the site, so this is custom.
I have send another file mega https://mega.co.nz/#!C9sRXCAC!OKDm7Df5o95elxtSnF19hiLgsjKn8nq0KplYL9KriIc and changed instructions
or you can get it from the forum http://forum.xda-developers.com/one-mini-2/orig-development/recovery-twp-2-7-1-0-one-mini-2-t2801370
Good luck
So i installed the rooted stock download on my s-on SprHtc one m7 and the install was seemingly successful, but now my touch screen isnt working. i cant unlock the phone and when i press the volume keys i cant touch the slider, or slide the drop down menu down. when i try to restart the phone it hangs at the "1" count indefinitely it seems. any ideas as to what went wrong? to make matters worse, i usually back up my data on twrp and then port it to my laptop to save space, but now my laptop is having trouble recognizing my phone.
Enishi44 said:
So i installed the rooted stock download on my s-on SprHtc one m7 and the install was seemingly successful, but now my touch screen isnt working. i cant unlock the phone and when i press the volume keys i cant touch the slider, or slide the drop down menu down. when i try to restart the phone it hangs at the "1" count indefinitely it seems. any ideas as to what went wrong? to make matters worse, i usually back up my data on twrp and then port it to my laptop to save space, but now my laptop is having trouble recognizing my phone.
Click to expand...
Click to collapse
Sounds like you flashed a really old rom.
Flash a rom that is based on 3.xx.xxx.x or higher and make sure you are using the latest version of twrp.
BD619 said:
Sounds like you flashed a really old rom.
Flash a rom that is based on 3.xx.xxx.x or higher and make sure you are using the latest version of twrp.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2368907&highlight=restart&page=37
this is the rom i flashed and its one of the latest, any advice as to how to get out of the situation im in tho?
although my twrp isnt up to date so thar may be an issue
Enishi44 said:
http://forum.xda-developers.com/showthread.php?t=2368907&highlight=restart&page=37
this is the rom i flashed and its one of the latest, any advice as to how to get out of the situation im in tho?
although my twrp isnt up to date so thar may be an issue
Click to expand...
Click to collapse
Yeah that rom is old there was a Touch Panel driver update between 1.31.xxx.x and 3.04.xxx.x
btw the latest is 5.05.651.x so that will tell you how old the rom you flashed is.
You should be able to hold the pwr button until the lights stop flashing at that point it will be off or it will try to reboot.
If it's off press pwr until it starts to boot and hold vol down that will take you to bootloader.
If it reboots hold vol down to get to bootloader.
BD619 said:
Yeah that rom is old there was a Touch Panel driver update between 1.31.xxx.x and 3.04.xxx.x
btw the latest is 5.05.651.x so that will tell you how old the rom you flashed is.
You should be able to hold the pwr button until the lights stop flashing at that point it will be off or it will try to reboot.
If it's off press pwr until it starts to boot and hold vol down that will take you to bootloader.
If it reboots hold vol down to get to bootloader.
Click to expand...
Click to collapse
ive been trying that. the menu pops up and says "3-2-1" but hangs at the "1" indefinitely. it wont reset. im waiting for it to die, but my backups are on my laptop and my phone isnt being recognized properly for some unknown reason
Enishi44 said:
ive been trying that. the menu pops up and says "3-2-1" but hangs at the "1" indefinitely. it wont reset. im waiting for it to die, but my backups are on my laptop and my phone isnt being recognized properly for some unknown reason
Click to expand...
Click to collapse
Keep holding power til the screen goes completely black
super freaking face palm. i thought that this was the stock rom for the latest sense. omfg. ruined by my own stupidity..
i cant hard reset my phone, attempting to let it die of battery loss and maybe i might be able to restart it in twrp.
will my touch screen work if its in twrp?
Enishi44 said:
super freaking face palm. i thought that this was the stock rom for the latest sense. omfg. ruined by my own stupidity..
i cant hard reset my phone, attempting to let it die of battery loss and maybe i might be able to restart it in twrp.
will my touch screen work if its in twrp?
Click to expand...
Click to collapse
It's been a while but I think it will. If you can manage to get to bootloader you can update twrp.
Maybe try pwr + vol down to reset just keep holding both.
http://forum.xda-developers.com/showthread.php?t=2472413
also here is touchscreen drivers.
edit: This needs s-off nvm that
lerenturk said:
http://forum.xda-developers.com/showthread.php?t=2472413
also here is touchscreen drivers.
edit: This needs s-off nvm that
Click to expand...
Click to collapse
You need to be s-off to use those.
lol ninja'd
holding down the pwr and vol button isnt working..im just gonna have to let it die.
do you think the side load option will let me push my backup over to my phone?
assuming i can even use twrp, knowing my luck, i wont be able to access recovery..
Enishi44 said:
holding down the pwr and vol button isnt working..im just gonna have to let it die.
do you think the side load option will let me push my backup over to my phone?
assuming i can even use twrp, knowing my luck, i wont be able to access recovery..
Click to expand...
Click to collapse
Sideload very rarely works from what I've seen.
You could adb push the backup but I'm not sure if it would flash I've never tried.
A last resort is RUU and start fresh.
i managed to restore my phone,but im having trouble getting twrp to recognize that my backup is in the folder. i copied it back and it doesnt show up in recovery. is there anyway around this?