Related
Hey guys, sorry for a new post. I did a search and wasn't totally sure about what i found so i figured i'd start a new post and get some help.
I bought a nexus off a guy for cheap but it was stuck at the fast boot (?) screen
image
the trackball doesnt work so i cant select anything. the only thing i can do is pull the battery out to shut it down. what can i do to fix this phone? I have no idea what to do to an android. I switched yesterday from wm6.5 so you're going to have to explain everything.
thank you!
You search the forums. That's what you do.
Trackball might be effed up. Replace that
That phone is unlocked
You get to that screen by holding down the trackball when you press power. (Like the above poster said)
Make sure the volume buttons or the trackball are not stuck in a pressed state.
I thought to navigate that screen you use the volume button and power button to select. Trackball doesn't work in that menu
Rellikzephyr
Sent from my Nexus One using Tapatalk
thanks for the helpful comments guys. :]
i meant to also add that none of the buttons work either, volume or power button. i tried to flash amonra's recovery thru cmd prompt but i couldnt do much after that. i couldnt get into the adb prompt. it says the device isnt found, although fastboot promt found the device fine. anyway so after i flash the amonra recovery img i can't get into recovery mode. holding the power and vol down button gets me to the hboot (i believe it is?) but again, i cant navigate the menu with any buttons to put it into recovery mode so i'm pretty much stuck here.
and just to clarify, I have done a few searches as i've said and I didnt feel sure enough that the problems mentioned were my problem so that is why I'm asking for help here.
You should not go to any forum and feel bad for posting or have to say over and over that you did a search. There are many people that can do better and some will show up, hopefully with answers that are not painful to someone who has purchased a new phone... cheap. I would flash amon ra which you can do adb without using any of the phone hardware buttons and then see where you are at. There are many posts on installing amon ra and the instructions are also in the offical thread. With any luck you just have a hosed recovery and the flash will get you rolling.
Can you not navigate the fastboot/hboot screen with the volume buttons? If not then you're gonna run into serious problems. Make sure both the volume buttons and trackball are clear. You can clean the trackball by pressing it in with a piece of cloth and pushing it in different directions while pressed in, this should clear most of the junk on it.
You can also clean the volume buttons and power button a little better by removing the battery cover. Good luck bud.
trackball+power -> fastboot mode.
volume+power -> recovery mode. if you see androids on skates you have the stock recovery.
trackball+volume+power held = reboot
Recovery, boot etc can be flashed from fastboot only.
just to clarify, the first thing that pops up when i press just the power button is the fastboot. i dont have to press anything else, just power.
i flashed amonra recovery img while i was on fastboot mode from my computer (cmd i used was fastboot flash recovery recovery-RA-nexus-v1.7.0.1.img) and it was successful.
Then i tried to put it into recovery mode w the command adb shell reboot recovery. It said that the device wasn't connected.
when i input the cmd fastboot devices i see my device connected, but when i input adb devices it says its not connected.
So i figured I'd put it into recovery mode on my phone by pressing volume+power. I get to the hboot screen with the three androids on skateboards (i realize the screen looks the same as fastboot but the selectable options here are different) but the volume buttons, trackball, power buttons don't work so i can't select "recovery" on the phone.
so this is where i'm stuck
It sounds like you have a stuck or f..d up trackball.
P_
I have the same problem has anyone figured out a solution?
Fastboot scree
GldRush98 said:
You search the forums. That's what you do.
Click to expand...
Click to collapse
Hi guys, sorry i have a nexus one i bought it and try to install and new rom. Was working at the beginning but now i am stuck with the bootloader screen. I tried everything don't know what to do. Is my phone dead and nothing else to do??
Please really need a big help there.
Can you make selections on the screen, by following the instructions on the screen?
can you help me
charnsingh_online said:
Trackball might be effed up. Replace that
Click to expand...
Click to collapse
sorry i can get some help from you to move from fastboot screen?
nsdragons said:
just to clarify, the first thing that pops up when i press just the power button is the fastboot. i dont have to press anything else, just power.
i flashed amonra recovery img while i was on fastboot mode from my computer (cmd i used was fastboot flash recovery recovery-RA-nexus-v1.7.0.1.img) and it was successful.
Then i tried to put it into recovery mode w the command adb shell reboot recovery. It said that the device wasn't connected.
when i input the cmd fastboot devices i see my device connected, but when i input adb devices it says its not connected.
So i figured I'd put it into recovery mode on my phone by pressing volume+power. I get to the hboot screen with the three androids on skateboards (i realize the screen looks the same as fastboot but the selectable options here are different) but the volume buttons, trackball, power buttons don't work so i can't select "recovery" on the phone.
so this is where i'm stuck
Click to expand...
Click to collapse
You cannot use ADB commands when you are in the bootloader (i.e., fastboot) screen. You need to be booted into the ROM or into the recovery for those commands to work.
What I find difficult to understand is how come your volume buttons work to boot into the bootloader, but don't work once you are there?
Try flashing each partition from a stock FRG33 ROM (from here). Unzip the files, and flash the boot, system and data images using fastboot (e.g., fastboot flash system system.img) and then try to reboot normally.
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
So, my volume up key stoped working from one day to the next. Didn't slam the phone on the floor or anything, it just stoped working. I already tried it on recovery mode, no luck so i'm asuming it's not software related.
Anyone faced this issue at some point? I did the eb40 battery mod a month ago, didn't notice anything unusual since then.
Thanks guys for any help.
Anyone?
I'm worried i might need to enter recovery or bootloader using keys instead of software reboot at some point, and won't be able to since my keys don't work.
I mean you could open the phone and check the connection for the button and the contacts. Does it feel loose? Maybe the button is upside down ( which shouldn't matter but you never know). Get back to us!
Sent from my MB886 using Tapatalk
And if is broken then flash phils advance recovery and you will never need it again. Lol
TecknoFreak said:
And if is broken then flash phils advance recovery and you will never need it again. Lol
Click to expand...
Click to collapse
Wait what? I have the same problem (volume up key is broken) and I'm constantly paranoid about bootloops since fastboot reboot recovery doesn't work. I have Philz recovery as well. Is there some feature I'm not aware of?
Papahyooie said:
Wait what? I have the same problem (volume up key is broken) and I'm constantly paranoid about bootloops since fastboot reboot recovery doesn't work. I have Philz recovery as well. Is there some feature I'm not aware of?
Click to expand...
Click to collapse
The touch recovery does not require the use of volume or power button. Same with Touch CWM.
audit13 said:
The touch recovery does not require the use of volume or power button. Same with Touch CWM.
Click to expand...
Click to collapse
Oh. Well of course you don't need the volume key to navigate the menu in a touch recovery. That's not the problem. The problem is getting *into* recovery without the volume up key. The only way to do so is if you have a functioning ROM, so if you're in a bootloop, you have to FXZ back to stock from fastboot, reroot, and install a reboot to recovery app. Then commence doing whatever it was you needed to do in recovery (assuming flashing a custom rom again and hope you don't get a bootloop)
Papahyooie said:
Oh. Well of course you don't need the volume key to navigate the menu in a touch recovery. That's not the problem. The problem is getting *into* recovery without the volume up key. The only way to do so is if you have a functioning ROM, so if you're in a bootloop, you have to FXZ back to stock from fastboot, reroot, and install a reboot to recovery app. Then commence doing whatever it was you needed to do in recovery (assuming flashing a custom rom again and hope you don't get a bootloop)
Click to expand...
Click to collapse
I understand now. Yes, it's tough to access fastboot or recovery mode without volume keys working.
Not at all there are ways to get around this. Install xposed framework with an advance power option and install it. Or go to play store and look for an app name i believe quick reboot
audit13 said:
I understand now. Yes, it's tough to access fastboot or recovery mode without volume keys working.
Click to expand...
Click to collapse
Indeed. I've wasted several development hours just getting back to a workable system when I end up with a bootloop. Makes testing very frustrating.Volume down key still works (it seems people only ever have problems with the volume up button) so can still get into fastboot. It would all be good if the "fastboot reboot recovery" command worked on this phone, but it's blocked.
EDIT: @Technofreak, once again that won't work if you're in a bootloop.
Papahyooie said:
Indeed. I've wasted several development hours just getting back to a workable system when I end up with a bootloop. Makes testing very frustrating.Volume down key still works (it seems people only ever have problems with the volume up button) so can still get into fastboot. It would all be good if the "fastboot reboot recovery" command worked on this phone, but it's blocked.
EDIT: @Technofreak, once again that won't work if you're in a bootloop.
Click to expand...
Click to collapse
Yes, and fastboot only works while in download mode, which you can't access while on a bootloop.
mmm... is there any way to make the device boot into download mode by default? That would be maximum safety.
Btw, did your vol up key broke by itself? did you do the battery mod? Thanks for your input.
jaweinre said:
Yes, and fastboot only works while in download mode, which you can't access while on a bootloop.
mmm... is there any way to make the device boot into download mode by default? That would be maximum safety.
Btw, did your vol up key broke by itself? did you do the battery mod? Thanks for your input.
Click to expand...
Click to collapse
You mean download mode as in the menu where you can choose recovery or fastboot? You can't get to that without the volume up button at all. You should be able to still enter fastboot, even from a bootloop. Just hold down the power and vol down button until it vibrates, then let go. Then hit power button once more, and you should be in download mode. But that still won't get you into recovery, so you still have to FXZ back to stock from there and redo everything. There IS a way (sort of) to get it to boot to fastboot every time. Just flash an FXZ and unplug it while it's flashing system.img. Then manually flash a system.img. That should trigger the sticky bits deal where it boots into fastboot every time... but I really don't know what that will accomplish, because every time you reboot your phone you'll have to plug it into a computer and use "fastboot reboot." There isn't a reboot to recovery command in fastboot, and there is no option within fastboot itself to reboot, so you'd have to plug it into the computer and use fastboot reboot.
I wish there was a software option to always ALWAYS boot into recovery from a cold boot. That way you could always get back to recovery no matter what. FXZ is surely a last resort, but you can always restore a backup from recovery.
Yes, I have an EB40 battery mod. But the volume button didn't stop working until a couple of months after doing that. It was seemingly random. Just stopped working one day. I can't way whether it's related or not.
Papahyooie said:
Yes, I have an EB40 battery mod. But the volume button didn't stop working until a couple of months after doing that. It was seemingly random. Just stopped working one day. I can't way whether it's related or not.
Click to expand...
Click to collapse
Mine did the same, broke down randomly after the EB40 mod. Can't check the frickin button since the black t5 screws got worn out (****ty quality).
What about fastboot update? isn't that suposed to flash zip files, as in cm zips?
EDIT: Been trying the vol down + power for a while, it behaves as normal power button, can't get to bootloader.
jaweinre said:
Mine did the same, broke down randomly after the EB40 mod. Can't check the frickin button since the black t5 screws got worn out (****ty quality).
What about fastboot update? isn't that suposed to flash zip files, as in cm zips?
EDIT: Been trying the vol down + power for a while, it behaves as normal power button, can't get to bootloader.
Click to expand...
Click to collapse
I have never been able to get fastboot update to work. I believe it is restricted on this phone just like fastboot reboot recovery is. Don't quote me on that as I've never seen anyone outright say that is the case, it just has never worked for me.
If it makes you feel better,don't bother trying to get the scews out. I have taken mine all the way down to the motherboard to see if there was anything obviously wrong with the volume button. Mine seems to have nothing physically wrong with it. The button (the bare button on the mobo, not the plastic piece) pushes well and even gives a nice tactile click when you push it down with the tip of a screwdriver or soemthing pointy. Hell, I've even booted it up with the case off, bare motherboard, while holding down the button with said screwdriver and it still won't work. It's got to be something like a trace burned or cracked on the motherboard, but with all the componants and shields around it I can't tell. It looks normal, and no different than the volume down button.
That sucks that you can't use the vol down and power button to get to fastboot. I just tried it myself to make sure I said it right and it worked fine. Maybe your volume down button doesnt work either??? You have to be very VERY careful if you cant get into fastboot. Don't get into a bootloop, because I don't know if there is any other way to recover at all. The only way I would know would be to short the circuit on the mobo to force the mobo to recognize a volume button press, and nobody wants to mess with that crap. Don't do any mods that are too exotic lol.
Vol down key is ok. Do you press both buttons while phone is off? For how long? This is weird.
jaweinre said:
Vol down key is ok. Do you press both buttons while phone is off? For how long? This is weird.
Click to expand...
Click to collapse
Well, I believe the correct way to do it is to hold all three buttons down at one time, but for me just holding down the power and volume down button works. If the phone is on, just hold those two buttons down until it vibrates a couple times. At that point let go of the power button. Then press the power button again, and it should boot into fastboot mode.
If the phone is off, I would assume just hold down the power button and volume down buttons. Then let go of the power button while still holding down the volume button and it should boot to fastboot mode.
Papahyooie said:
If the phone is off, I would assume just hold down the power button and volume down buttons. Then let go of the power button while still holding down the volume button and it should boot to fastboot mode.
Click to expand...
Click to collapse
worked. thanks.
jaweinre said:
worked. thanks.
Click to expand...
Click to collapse
Good good. That will at least allow you to FXZ if all else fails. Just don't flash anything unless you have the time to FXZ back and do the whole process over, because in the event of a bootloop, AFAIK that is your only choice.
But we can always go to the recovery mode using the command prompt.
Connect the mobile to computer and use adb fastboot commands.
swapnil0545 said:
But we can always go to the recovery mode using the command prompt.
Connect the mobile to computer and use adb fastboot commands.
Click to expand...
Click to collapse
Once again, fastboot reboot recovery does not work on the Atrix HD. Let me qualify that, because there may be some people that it does work for, but the majority of us, the command is locked. In most cases, that is an invalid point, because we cannot get to recovery using fastboot.
im on rooted 4.4, all works fine but the exchange,, trying to replace the email 4.4.2 apk, so my eschange will work, when i try to boot into recovery, i get "no command error"
can anyone plese help?
ericizzy1 said:
im on rooted 4.4, all works fine but the exchange,, trying to replace the email 4.4.2 apk, so my eschange will work, when i try to boot into recovery, i get "no command error"
can anyone plese help?
Click to expand...
Click to collapse
what are you using to reboot into recovery?
here's the failsafe way to access recovery:
power off the phone, press and hold volume down + power for a few seconds then release to access bootloader menu. press volume down to highlight recovery, then volume up to select it.
Q9Nap said:
what are you using to reboot into recovery?
here's the failsafe way to access recovery:
power off the phone, press and hold volume down + power for a few seconds then release to access bootloader menu. press volume down to highlight recovery, then volume up to select it.
Click to expand...
Click to collapse
thats exactly what i did and still got the error. even tried with adb, no luck
ericizzy1 said:
thats exactly what i did and still got the error. even tried with adb, no luck
Click to expand...
Click to collapse
strange, are you unlocked and using twrp/cwm or locked and using slapmymoto? if you're unlocked, i'd recommend reflashing twrp/cwm recovery image, sounds like it may be corrupt. if you're locked, i can't help as i haven't messed with any of the locked device stuff.
im on a locked device, used slapmymoto, thanks for trying,can anyone else help?
Why do you need to be in recovery. You should have write protect off already. If you are trying to flash something you can't without safestrap and the zip needs yo be made for safestrap. Just manually move the emails and change the permissions
Sent from my XT1060 using xda app-developers app
Press Power + Volume Up at the same time when it shows "no command" (And if that doesn't work try Power + Volume Down )
ericizzy1 said:
im on a locked device, used slapmymoto, thanks for trying,can anyone else help?
Click to expand...
Click to collapse
If the button presses while rebooting to get to where you can select recovery doesn't work... You could try Quick Reboot -> https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot to reboot into recovery, or open a command prompt on your PC.. and issue the command.. adb reboot bootloader then pick recovery from there.. If those ways also error with that same message you are seeing now, then your phone doesn't has a problem with its recovery partition.
As others have said, if you are rooted with Write Protection disabled (SlapMyMoto v1 thread tells you to run MotoWPNoMo first, to disable write protection, then follow its process), you should be able to go in, rename the old APK, and replace it with the new one (and set the attributes the same) without needing to be in recovery.
Then again, if you rooted with SlapMyMoto .5 (before the MotoWPNoMo was available), or you never did the MotoWPNoMo process that would explain why you want recovery... you're trying to boot to "recovery" so that you can boot with the Write Protection disabled so you can make this change.
ericizzy1 said:
im on a locked device, used slapmymoto, thanks for trying,can anyone else help?
Click to expand...
Click to collapse
Power off your Moto X
Next, boot into bootloader mode by holding Volume Down and Power
At the bootloader screen, use Volume Down and scroll to Recovery, then press Volume Up to select it
Once you rebooted into recovery mode you will see No Command. Hold Volume Up and press Power to show the recovery menu
apm_ said:
Power off your Moto X
Next, boot into bootloader mode by holding Volume Down and Power
At the bootloader screen, use Volume Down and scroll to Recovery, then press Volume Up to select it
Once you rebooted into recovery mode you will see No Command. Hold Volume Up and press Power to show the recovery menu
Click to expand...
Click to collapse
That almost didn't work for me, till it did.
I was holding down volume up first, and about half a second to a second later the power button (while not having released volume up button). That didn't work.
I pressed both buttons exactly together, and it worked.
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