Database Users

[Q] Phone Not Going To Recovery! Need Help!

So my rooted Mytouch 4g S=OFF is stuck at the MyTouch screen and stays there, then when i do volume down plus power it takes me to hboot then automatically starts going through my sd card for like 3 files then says do u want to start update volume up yes down no i have tried both in the end it reboots and is again frozen! I tried rebooting it with the vol down and power with my sd card out but i still cant do anything! Please help!

ashmal411 said:
So my rooted Mytouch 4g S=OFF is stuck at the MyTouch screen and stays there, then when i do volume down plus power it takes me to hboot then automatically starts going through my sd card for like 3 files then says do u want to start update volume up yes down no i have tried both in the end it reboots and is again frozen! I tried rebooting it with the vol down and power with my sd card out but i still cant do anything! Please help!
Click to expand...
Click to collapse
It sounds like you have a PD15IMG.zip file in the root of your SD card. That's what the bootloader is detecting when it asks you if you want to update or not. Remove that file and it will bypass the update step and take you to the bootloader main menu. There you can select recovery. From there, I would re-download your ROM installation file, full wipe (data, cache, Dalvik-Cache), and re-flash your ROM.

I tried that
i tried that too but it still checks for those but then lets me select recovery but when i click recovery it gives me a picture of a phone and a red triangle thanks though any more help would be much appreciated!

ashmal411 said:
i tried that too but it still checks for those but then lets me select recovery but when i click recovery it gives me a picture of a phone and a red triangle thanks though any more help would be much appreciated!
Click to expand...
Click to collapse
I don't think you have a custom recovery yet, download the rom manager from the market and have it flash a recovery for you. When you go back you should see something very different.
If for you already have flashed the recovery, press the power button when you see the lil phone pic and your recovery should come up

mark manning said:
I don't think you have a custom recovery yet, download the rom manager from the market and have it flash a recovery for you. When you go back you should see something very different.
If for you already have flashed the recovery, press the power button when you see the lil phone pic and your recovery should come up
Click to expand...
Click to collapse
I cant download anyting because i cant even get to my homescreen

ashmal411 said:
I cant download anyting because i cant even get to my homescreen
Click to expand...
Click to collapse
can you get into your phone using adb/fastboot?
flash recovery that way.

saranhai said:
can you get into your phone using adb/fastboot?
flash recovery that way.
Click to expand...
Click to collapse
sorry im a noob at this i dont know how to do that thank you for trying to help though if you have anymore please help

ashmal411 said:
sorry im a noob at this i dont know how to do that thank you for trying to help though if you have anymore please help
Click to expand...
Click to collapse
google search androidSDK, and install it on your computer.
there are millions of threads out there telling you how to set it up so i'd suggest you read some of those. once you get adb set up, connect your phone (USB DEBUGGING ON! enable in settings/applications/development).
type "adb devices" without quotes to see if your device is connected. then type
Code:
su
adb reboot bootloader
the phone should reboot into fastboot, if it isn't in fastboot, manually scroll to it with the volume buttons and select with power button.
now, you need the recovery image, i'll post it at the bottom of this post. after you get the recovery image, move it to androidSDK/tools or wherever your adb/ fastboot folder is located, and rename it to "recovery.img".
now, type
Code:
fastboot flash recovery recovery.img
it should give you two OKs, if it does, then you're all set, reboot the phone into bootloader, select recovery, and flash a rom on there

saranhai said:
google search androidSDK, and install it on your computer.
there are millions of threads out there telling you how to set it up so i'd suggest you read some of those. once you get adb set up, connect your phone (USB DEBUGGING ON! enable in settings/applications/development).
type "adb devices" without quotes to see if your device is connected. then type
Code:
su
adb reboot bootloader
the phone should reboot into fastboot, if it isn't in fastboot, manually scroll to it with the volume buttons and select with power button.
now, you need the recovery image, i'll post it at the bottom of this post. after you get the recovery image, move it to androidSDK/tools or wherever your adb/ fastboot folder is located, and rename it to "recovery.img".
now, type
Code:
fastboot flash recovery recovery.img
it should give you two OKs, if it does, then you're all set, reboot the phone into bootloader, select recovery, and flash a rom on there
Click to expand...
Click to collapse
here's the recovery image:

saranhai said:
google search androidSDK, and install it on your computer.
there are millions of threads out there telling you how to set it up so i'd suggest you read some of those.
Click to expand...
Click to collapse
To make it easier for the OP, this thread gives you all you need to know to get ADB up and running.
Also, the above fastboot instructions are correct, but will only work with the engineering bootloader. Hopefully the OP's phone has that.

i cantturn on usb debuggiing because io cant get into my phone

TeeJay3800 said:
To make it easier for the OP, this thread gives you all you need to know to get ADB up and running.
Also, the above fastboot instructions are correct, but will only work with the engineering bootloader. Hopefully the OP's phone has that.
Click to expand...
Click to collapse
lol thanks for the tip

ashmal411 said:
i cantturn on usb debuggiing because io cant get into my phone
Click to expand...
Click to collapse
was usb debugging on before..?

nope it was not on

ashmal411 said:
nope it was not on
Click to expand...
Click to collapse
oh.... that's a problem...

ashmal411 said:
nope it was not on
Click to expand...
Click to collapse
ok that's ok, you can still flash recovery through fastboot, which doesn't need USB debugging on.
so steps:
1) download the recovery image and rename to "recovery.img"
2) move the image to wherever your adb/fastboot tools are located
3) open command prompt (in windows)
4) cd to where your adb/fastboot tools are located
5) REBOOT PHONE INTO HBOOT, THEN CONNECT TO COMPUTER
6) manually scroll and select fastboot using the volume and power buttons
7) type
Code:
fastboot devices
to make sure your phone is detected.
8) if it is, type
Code:
fastboot flash recovery recovery.img
should give you two OKs.
9)once the recovery is in there, flash a rom on

Major Issue with Recovery

Hi
I just wiped my phone using the HD revolution script to install, I had a 'bad file' error so rebooted... my phone's volume down button doesnt work so now I cannot get into Hboot or Recovery, is there any other way?

Using adb - if it works.
Plug your phone in to your PC, switch on then run this command.
Code:
adb reboot recovery

Ah of course! Thanks, forgot about adb

Did I brick it?

So I successfully downgraded back to Froyo. I followed the Rooting process exactly, mdr #'s 2 and 3 matched. I entered the reboot command, and now my phone only vibrates 3-4 times when you turn it on. the led keeps flashing. and nothing is happening with the screen. I cant get it to the bootloader screen either

is it being recognized through adb?
Sent from my HTC Glacier using xda premium

No, adb is not recognizing it.

Nvmd. I just got adb to recognize it. when i enter adb devices it returns...
SH0B5T600504 Recovery.
what can i do from here?

TurboBrickMike said:
Nvmd. I just got adb to recognize it. when i enter adb devices it returns...
SH0B5T600504 Recovery.
what can i do from here?
Click to expand...
Click to collapse
adb reboot recovery

THEindian said:
adb reboot recovery
Click to expand...
Click to collapse
Ok , so I open up adb. enter in adb reboot recovery, then it should be ok to work with after that? Sorry for being so inexperienced at this. I'm just a car guy who has been geeking on his android lol.

THEindian said:
adb reboot recovery
Click to expand...
Click to collapse
Ok, so i tried adb reboot recovery... Same thing, just 4-5 vibrations and flashing amber LED. What is my next option?

I can now get into the bootloader and Clockwork. but now it just gets stuck on the Clockwork mod loading screen when i update .zip file from sd. I tried the factory reset, nothing. It shows S-Off though lol. Is there any info that I can give you guys from the menus I have available in order to help decode what I did wrong/what went wrong?

Try this...Take the original 2.3.4 update and put it in your sd card.(assuming your pc detects the sd card). Take the battery out if the phone for about 10 min. try to boot into hboot and reflash the phone back to stock. Then redowngrade and root again.
Sorry if I'm not too much help. I'm learning from what I read here and there.
Sent from my Dark Unicorn Resurrected v.1 using xda premium

Brick
TurboBrickMike said:
I can now get into the bootloader and Clockwork. but now it just gets stuck on the Clockwork mod loading screen when i update .zip file from sd. I tried the factory reset, nothing. It shows S-Off though lol. Is there any info that I can give you guys from the menus I have available in order to help decode what I did wrong/what went wrong?
Click to expand...
Click to collapse
Hey Mike, I am having the same issue with my phone I tried the adb reboot recovery command in adb but the phone just reboots. I wanna know how did you boot into clockworkmod recovery or the bootloader. Please help me out I am trying to fix my phone. thanks

clockwork is "adb reboot recovery"
bootloader is "adb reboot bootloader"
you can only do this stuff if the device is recognized. If it just reboots when you do reboot recovery, you probably don't have it flashed correctly or don't have the right bootloader

danishanif said:
Hey Mike, I am having the same issue with my phone I tried the adb reboot recovery command in adb but the phone just reboots. I wanna know how did you boot into clockworkmod recovery or the bootloader. Please help me out I am trying to fix my phone. thanks
Click to expand...
Click to collapse
Download PD15IMG.ZIP here, copy and paste on the root of your SD card. Don't forget to rename the files to PD15IMG.zip before you copy them to the SD Card, otherwise it won't work
Turn off your phone.(you should have enough battery charge)
Press POWER and VOL DOWN simultaneously (this will bring your boot loader)
It will automatically install the PD15IMG.ZIP, need to confirm some actions.
Wait till the process is done....
If you did not encountered any error such as FAIL- PU, you can open your phone normally and start setting it up...
regards

download mode

I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?

May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)

bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler

What's up now ?
Sorted it out or still issues there ?

I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going

bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #

Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.

bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"

I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"

I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...

*SOLVED* Embarrassed to ask for help - but please help!

Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil

nstirton said:
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
Click to expand...
Click to collapse
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool

marcus.linkenbach said:
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
Click to expand...
Click to collapse
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?

nstirton said:
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
Click to expand...
Click to collapse
Try vol+ + vol- + power

it seems that the only time my device will show as connected in ADB is when I navigate through Recovery and select the "Apply Update from ADB" option. But even then, whilst it shows as connected, it only seems to allow the "sideload" command. Please see screenshot of Terminal. So at no other time will it show as a connected device.
Similarly, to have it show up in Device Manager, it'll only show when I switch the phone off, hold down Vol+ & Vol- and attached the power cable.

You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“

marcus.linkenbach said:
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.

nstirton said:
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
Click to expand...
Click to collapse
But what if it shows your device as sideload? Can't you there reboot into fastboot?

No, it doesn't accept the command. Only one accepts is sideload. You can see from my screenshot a few posts back that the device is connected but shows different to how it normally would.

Breakthrough!
I seemed to follow the steps I've tried 100 times today and I now have TWRP installed again!
Thanks again to those who helped