Bootloader problem after HTC Dev unlock - HTC Rezound

After sucessful HTC Dev bootloader unlock, now unable to access bootloader thru typical vol down/pwr method. Problem suggestions?

pull the battery once maybe? but you can get into it by typing "adb reboot-bootloader"

Battery pull did not work. Where do I type this script?

craZhorse said:
Battery pull did not work. Where do I type this script?
Click to expand...
Click to collapse
Using ADB...
con247 said:
...you can get into it by typing "adb reboot-bootloader"
Click to expand...
Click to collapse

download the SDK, steal the ADB.exe from it and put it in a new folder (C:\Android is always a safe bet,) go to command prompt and CD to the folder with ADB in it, and then type "adb reboot-bootloader"
it will look like
C:\Users\Name>CD c:\Android
c:\Android>adb reboot-bootloader
*Edit* or just use the adb i attached to my post

Related

URGENT !! PLS HELP !! Can not boot into RA

Noticed this morning, when I power up holding HOME the phone lockes on the 'HERO' first screen and I can not get into RA...
Anyone got any ideas ?
somebody ? anybody ? this is a disaster, i can not get into my boot menu to install or flash or anything. the phone boots normally if i dont hold the HOME button, but when i power on with the home button held, it locks..... please help me...
Ian_4614 said:
somebody ? anybody ? this is a disaster, i can not get into my boot menu to install or flash or anything. the phone boots normally if i dont hold the HOME button, but when i power on with the home button held, it locks..... please help me...
Click to expand...
Click to collapse
Happened to me too.. no worries..
Re-flash AR through fastboot and it will work again..
adb shell reboot bootloader
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot
that's it .. you can rename recovery-RA-hero-v1.6.2.img to something shorter so you don't have to type so much
inertiax3 said:
Happened to me too.. no worries..
Re-flash AR through fastboot and it will work again..
adb shell reboot bootloader
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot
that's it .. you can rename recovery-RA-hero-v1.6.2.img to something shorter so you don't have to type so much
Click to expand...
Click to collapse
thanks, but i do not understand, how do i access fastboot ? i am keen to learn but this is new to me...
I'm pretty sure that this is the process, got this from the RA-heroc-v1.6.2.img thread:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Click to expand...
Click to collapse
muzz3256 said:
I'm pretty sure that this is the process, got this from the RA-heroc-v1.6.2.img thread:
Click to expand...
Click to collapse
Appreciate that,, but i am sorry to say it does not make any sense to me. How to i get into FastBoot,, what do I press etc,, and once I am there,, what do I do ?
Ian_4614 said:
Appreciate that,, but i am sorry to say it does not make any sense to me. How to i get into FastBoot,, what do I press etc,, and once I am there,, what do I do ?
Click to expand...
Click to collapse
I NEVER DONE THIS BEFORE...
back + power button will take you to fastboot...
BUT, I believe "adb shell reboot bootloader" will take you to the right place instead of trying button combinations. So, you can run these commands from normal boot itself.
so when you say, run from normal boot itself, you mean from a file manager etc ?
Ian_4614 said:
so when you say, run from normal boot itself, you mean from a file manager etc ?
Click to expand...
Click to collapse
No!
Do you have adb setup? If not set it up using this link:
http : // theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Check this link as well: http://forum.xda-developers.com/showthread.php?t=502010
no, you start your phone up normal, go to settings and make sure usb debugging is enabled, then connect your usb-cabel, go to your sdk-directory and type adb shell reboot bootloader, then your phone will reboot into fastboot
Not sure,, this is what I added when I flashed the phone..
boot up the hero, plug in the usb, execute the commands that were given to you on the pc. that is all. you need adb on the pc for that.
right, i dod not know i had to have a programe on the PC,,, I will look for adb and see where I can find it. Is this an app I need to install on the PC ? where do I get it ?
Ian_4614 said:
right, i dod not know i had to have a programe on the PC,,, I will look for adb and see where I can find it. Is this an app I need to install on the PC ? where do I get it ?
Click to expand...
Click to collapse
cracked it, downloaded ROM MANAGER app and this enabled me to flash alternative RA Recovery,, and all now working,

Help with S off

I really need some help here. I am very close to facepalm s offing my evo 4g lte. I am currently on meanbean rom v.3.09 and I'm having trouble using commmands in the adb shell whenever I try to reboot into the bootloader during the facepalm s off process. If I enter "adb devices" before typing "adb shell" and then "su" after then It shows my device like it normally would. However if I enter the adb shell first, then It doesn't show up in the devices at all and If i try to run a command it gives me an error: device not found message. Can anyone help me with this?
ownagemaximus said:
I really need some help here. I am very close to facepalm s offing my evo 4g lte. I am currently on meanbean rom v.3.09 and I'm having trouble using commmands in the adb shell whenever I try to reboot into the bootloader during the facepalm s off process. If I enter "adb devices" before typing "adb shell" and then "su" after then It shows my device like it normally would. However if I enter the adb shell first, then It doesn't show up in the devices at all and If i try to run a command it gives me an error: device not found message. Can anyone help me with this?
Click to expand...
Click to collapse
I had to manually go to bootloader and fastboot and issue the commands. Mine would not reboot via the commands. My supersu would also not allow adb root access until I upgraded to supersu pro.

[Q] Terminal Command "Stop". Phone not boot up.

Hi everyone! Please help me. I've accidentaly typed in Terminal Emulator commad "stop" with SU permissions and my phone first freezed then don't want to boot up. How can i start my phone? I can access only recovery and fastboot.
Edit: Also i can run adb commands. So the question, what command i need to run for start phone?
If you have access to fastboot you could simply use RSD Lite to reflash your phone to stock.
DeathChaos said:
If you have access to fastboot you could simply use RSD Lite to reflash your phone to stock.
Click to expand...
Click to collapse
I don't want to flash stock then again set everything i need. I just need a correct command to run thru adb for start.
It's like "adb start" or "adb shell start", i don't know.
Abstractionist said:
I don't want to flash stock then again set everything i need. I just need a correct command to run thru adb for start.
It's like "adb start" or "adb shell start", i don't know.
Click to expand...
Click to collapse
Honestly, i never heard of the command "stop".
You could check the documentation for adb.
Edit: There is a command called start which "restarts execution of an emulator/device instance."
Abstractionist said:
Hi everyone! Please help me. I've accidentaly typed in Terminal Emulator commad "stop" with SU permissions and my phone first freezed then don't want to boot up. How can i start my phone? I can access only recovery and fastboot.
Edit: Also i can run adb commands. So the question, what command i need to run for start phone?
Click to expand...
Click to collapse
Can also connect that bad boy of yours to comp and run start command in terminal. I have done this too. I also ran bootanimation in android terminal, continous bootloop. But fun is had running those xbin/bin commands. Lol
XT912 RaZR SpYdEr CDMA
hit ThAnKs if I was helpful!!!
I have done this stop command too but my phone still boots up normally it just goes blank and my touch buttons are lit up and all I did was power off by holding power button for 6 seconds and power back on and booted up normally ? I'm alittle scared to play with commands now because I was just typing all random root user commands and I went through a bootloop like 5 times and I reflashed through RSD lite but I know now that I shouldn't play with those cmds now??

[Q] my HTC fails to switch on... How to install a new rom?

Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
lorenk93 said:
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
Click to expand...
Click to collapse
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
oziboy said:
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
When I write adb sideload file_name.zip, it
returns "error: closed". why?
lorenk93 said:
When I write adb sideload file_name.zip, it
returns "error: closed". why?
Click to expand...
Click to collapse
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
oziboy said:
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
Click to expand...
Click to collapse
so... I have to write "ADB usb file_name.zip". tath's right?
lorenk93 said:
so... I have to write "ADB usb file_name.zip". tath's right?
Click to expand...
Click to collapse
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
oziboy said:
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
Click to expand...
Click to collapse
I don't know why, but when I write adb usb it returns "error: device not found"
lorenk93 said:
I don't know why, but when I write adb usb it returns "error: device not found"
Click to expand...
Click to collapse
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
oziboy said:
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
Click to expand...
Click to collapse
I did it... Thanks to you... So thank you so much...
lorenk93 said:
I did it... Thanks to you... So thank you so much...
Click to expand...
Click to collapse
No problem, I had almost the same problem and just told what I did xD

Unlocking bootloader

When is type in command line adb devices it lists my device but as soon as i try a fastboot command it says <waiting for device> for hours and does not work
ACFH said:
adb devices
adb reboot bootloader
Wait for phone reboot then type
fastboot devices
Click to expand...
Click to collapse
When i do the thing you've said i get stuck with a screen with fastboot mode on the top left corner
Right click on task bar at bottom not tap any app click task manager stop adb then open command window shift+right click then type
Fastboot OEM unlock
Put recovery into adb and FASTBOOT folder then rename to TWRP.img type in
Fastboot flash TWRP.img then boot into TWRP
---------- Post added at 12:52 PM ---------- Previous post was at 12:51 PM ----------
Danyaelgaina said:
Right click on task bar at bottom not tap any app click task manager stop adb then open command window shift+right click then type
Fastboot OEM unlock
Put recovery into adb and FASTBOOT folder then rename to TWRP.img type in
Fastboot flash TWRP.img then boot into TWRP
Click to expand...
Click to collapse
Remember to boot into fastboot and enable adb in developer options
ACFH said:
Yeah. Its fastboot screen. Now you can try any fastboot command. After that, "fastboot reboot" will bring you to system.
Edit: be carefull with fastboot command or you will brick your phone
Click to expand...
Click to collapse
When I try any fastboot command when it's on this screen it says <waiting for device> and when on this screen i type adb devices it shows my device but fastboot commands do not work.
It could be about drivers. Try reinstalling adb with this tool: https://forum.xda-developers.com/showthread.php?t=2588979
Now you install adb correctly. But you might still stuck at waiting for device. You need to setup windows for detecting android to do that go to this link : http://www.codeshuffle.in/2016/12/kenzo-fastboot-adb-connection-fix.html?m=1
This is how I fixed mine. Hope it will work for you
Device Manager shows when phone in fastboot mode
[IMG="This is what device manager shows in fastboot mode"
https://mail.google.com/mail/u/0/?u...&attid=0.1&disp=safe&realattid=f_j2o9k1gg0&zw

Categories

Resources