Database Info

Can't enter recovery mode

I've had my Sprint Hero rooted for the past few months and decided today to try out a custom ROM from Modaco. In November I rooted using the method described in these forums by theresthatguy.
The reoccurring problem I am having is that I can't enter recovery mode, after flashing the img, or just on a normal reboot using Home-End. The device just stalls out at the black HTC screen (for hours). I can backtrack to the Sprint 1.29.651.1 RUU, and from there I have no problems entering recovery mode. Of course, my phone isn't rooted either. So, if I follow the aforementioned procedure and root again, after I install the recovery image I can't get into recovery mode. I've also tried bypassing the img file used in the rooting procedure, and going directly to the Modaco img, but that doesn't work either and I get stuck at the black HTC screen.
I've seen many mentionings here that I am not allowing the img to fully flash to the device. I've tried waiting up to 3 hours, and I don't think this is the problem.
Any thoughts on how I can resolve this?

Which recovery image are you using? Is your hero a "with Google" hero?

when you do this command:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
as a part of the rooting guide/process what response do you get back from your computer?
should say something to the effect of how much data was transferred and how fast it copied.
after that and you get to the part where you enter the following into the adb shell prompt:
flash_image recovery recovery-RA-heroc-v1.5.2.img
what response do you get then? This could take a minute or two, no longer to finish.
once those two things are done completely.... turn your phone completely off and then hold the home button while turning it on to get into recovery.

What happens when you run these commands:
Code:
adb remount
adb reboot recovery
?

Kcarpenter said:
Which recovery image are you using? Is your hero a "with Google" hero?
Click to expand...
Click to collapse
I'm using recovery-RA-heroc-v1.5.2.img, and yes, on a "with Google" Hero.
obelisk79 said:
when you do this command:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
as a part of the rooting guide/process what response do you get back from your computer?
should say something to the effect of how much data was transferred and how fast it copied.
[/QUOTE
After pushing the image I get "1699 KB/s (3356672 bytes in 1.929s)"
obelisk79 said:
after that and you get to the part where you enter the following into the adb shell prompt:
flash_image recovery recovery-RA-heroc-v1.5.2.img
what response do you get then?
Click to expand...
Click to collapse
Following the flash_image command, my response, after ~2-3 seconds is:
flash_image recovery recovery-RA-heroc-v1.5.2.img
#
obelisk79 said:
once those two things are done completely.... turn your phone completely off and then hold the home button while turning it on to get into recovery.
Click to expand...
Click to collapse
This works, as it did previously. Th RA-heroc-v1.5.2 build and rooting is successful. After I boot, I power down, and then power on and into recovery mode. This works, but I don't think it was case before, even though there is no difference in the process between now and then.
If I continue, and use this procedure to apply the Modaco custom ROM (created via kitchen), it fails and I can't enter recovery mode
Procedure:
cmd
cd c:\android-sdk-windows\tools
adb devices
adb push c:\android-sdk-windows\tools\2.2-update-heroc-modacocustomcustomrom-signed\boot.img /sdcard
response: "1303 KB/s (2265088 bytes in 1.697s)"
adb shell reboot
after reboot..
adb shell
su
cd /sdcard/
flash_image recovery boot.img
response, after 2-3 seconds:
flash_image recovery boot.img
#
power off
note: USB cable still connected
power on via recovery mode (home-power buttons)
Does not enter recovery mode - stalls at black HTC screen.
After 2 minutes, reset battery and power on.
Reboots normally.
gu1dry said:
What happens when you run these commands:
Code:
adb remount
adb reboot recovery
?
Click to expand...
Click to collapse
When I try to remount, I get the following error message:
remount failed: Operation not permitted
At this time, I noticed HTC Sync was not able to connect. Wondering if there was some sort of relationship, I uninstalled the ADB Interface from the Device Manager, disconnected the USB cable, and rebooted. After reboot, I reinstalled the ADB Interface using the HTC Sync drivers and tried the remount again - failed.
Click to expand...
Click to collapse

you are flashing wrong.
go into recovery mode and from the menu select:
flash zip from sdcard....
select the modaco rom zip file and then it should flash....
you shouldn't be flashing any more .img files after you;ve rooted and isntaled recovery. let the recovery menu install zipped rom files for you.

the modaco custom rom signed zip fil e is a custom signed zipfile that allows you to flash the files held withiin via your recovery menu. so again, the only thing you should try to flash from adb using the flash_image command will be the recovery image which is pretty much a one time deal.

Seriously, no offense to any one here but... I can't believe you don't have a brick on your hands. I guess are phones really are very difficult to brick.

as long as you don't mess with the radio you should almost always be able to recover with the sprint RUU.

obelisk79 said:
you are flashing wrong.
go into recovery mode and from the menu select:
flash zip from sdcard....
select the modaco rom zip file and then it should flash....
you shouldn't be flashing any more .img files after you;ve rooted and isntaled recovery. let the recovery menu install zipped rom files for you.
Click to expand...
Click to collapse
Well hot piss! That definitely takes care of it! I certainly felt a little unsure of the img vs. zip file, as well as the use of the recovery parameter. Thank you much for clarifying this!
Kcarpenter said:
Seriously, no offense to any one here but... I can't believe you don't have a brick on your hands. I guess are phones really are very difficult to brick.
Click to expand...
Click to collapse
No offense taken - I'd done enough research to know now to mess with the radio, and thought I had a clear enough understanding of the procedure I needed. Regardless, I am glad I don't have a brick. Thanks for your help as well!

Kcarpenter said:
Seriously, no offense to any one here but... I can't believe you don't have a brick on your hands. I guess are phones really are very difficult to brick.
Click to expand...
Click to collapse
After reading many posts on this forum I feel like many people shouldn't be allowed to root their phones.

begginers make mistakes. gotta start somewhere

bddc said:
I'm using recovery-RA-heroc-v1.5.2.img, and yes, on a "with Google" Hero.
obelisk79 said:
when you do this command:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
as a part of the rooting guide/process what response do you get back from your computer?
should say something to the effect of how much data was transferred and how fast it copied.
[/QUOTE
After pushing the image I get "1699 KB/s (3356672 bytes in 1.929s)"
Following the flash_image command, my response, after ~2-3 seconds is:
flash_image recovery recovery-RA-heroc-v1.5.2.img
#
This works, as it did previously. Th RA-heroc-v1.5.2 build and rooting is successful. After I boot, I power down, and then power on and into recovery mode. This works, but I don't think it was case before, even though there is no difference in the process between now and then.
If I continue, and use this procedure to apply the Modaco custom ROM (created via kitchen), it fails and I can't enter recovery mode
Procedure:
cmd
cd c:\android-sdk-windows\tools
adb devices
adb push c:\android-sdk-windows\tools\2.2-update-heroc-modacocustomcustomrom-signed\boot.img /sdcard
response: "1303 KB/s (2265088 bytes in 1.697s)"
adb shell reboot
after reboot..
adb shell
su
cd /sdcard/
flash_image recovery boot.img
response, after 2-3 seconds:
flash_image recovery boot.img
#
power off
note: USB cable still connected
power on via recovery mode (home-power buttons)
Does not enter recovery mode - stalls at black HTC screen.
After 2 minutes, reset battery and power on.
Reboots normally.
When I try to remount, I get the following error message:
remount failed: Operation not permitted
At this time, I noticed HTC Sync was not able to connect. Wondering if there was some sort of relationship, I uninstalled the ADB Interface from the Device Manager, disconnected the USB cable, and rebooted. After reboot, I reinstalled the ADB Interface using the HTC Sync drivers and tried the remount again - failed.
Click to expand...
Click to collapse
I think this may help. A friend of mine wanted to know how to flash custom ROMs to his phone. I wrote a document (complete with screenshots) that will take you step-by-step through the process.
Just click here: http://www.darktremor.com/howto.html
Hopefully, that will help you.
Click to expand...
Click to collapse

[Q] HELP HELP HELP Bricked

Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me

Meat6911 said:
Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me
Click to expand...
Click to collapse
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:

When I connect to PC it makes the connection sound but doesn't show as a removable drive so I can't use Easyflash or any program like that also like I said APX mode wont work it makes the sound that it detects the tablet but then makes the remove sound right away. and this happened when I installed the Cyangenmod 9. I found someone who says he may be able to fix it for $50 using Odin but I am worried that he wont be able to and its an hour drive to take it to him... At this point I just want it back to stock ...

erm... ODIN won't work with a transformer, it's only for samsung devices.
Alright, you probably used ROM manager judging by your Recovery version.
You need to just NvFlash the device back to stock:
Download your region's Stock ROM from here: (WW if outside of US, US if inside.) Stock Rom
Download Wheelie NvFlash tool from here: Wheelie
Unzip the stock rom .zip first, into it's own folder. Then unzip the wheelie tar.bz2 into the folder you just made by unzipping the stock rom. Overwrite any files with the wheelie files.
Next find out your Sbk variant, Look at the serial number on the sticker on the bottom of your tablet.
If it says B70, or a higher number like B80 or any C, then you are Sbkv2
If the number is B60 or lower, you are Sbkv1.
Remember this for the next step.
Make sure the tablet is off totally, Then hold the Volume-UP key and Then press power, keep holding volume up. It will enter APX mode.
Plug it into your computer, the screen will stay blank.
It should be detected, if it says unknown device or similar, use the windows device manager to select the 'asus bootloader interface' or 'Unknown device' or similar, with Nvidia ASUS or APX or Bootloader, something along those lines, to update the driver, right click this and navigate to the 'usbpcdriver' folder in the folder you unzipped earlier. It will install and detect.
Then run the .bat file that says Reflash_(Your Sbk version).bat while the tab is connected in apx mode.
It will return to stock, give it time, DO NOT UNPLUG IT.
The screen may flash, and the tablet may/will reboot.
When done you will be on Stock latest from ASUS.
If you want safe root / recovery, download and run my PERI tool, link in signature.
good luck.

ok I am trying that now but I wish I had someone to walk me through everything in real time...

OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you

Meat6911 said:
OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you
Click to expand...
Click to collapse
erm, I guess it worked?
The best thing you can do for someone on xda is hit the 'thanks' or donate buttons, and thanks is free!
Any other questions, I'm guessing it worked alright?

frederuco said:
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:
Click to expand...
Click to collapse
I had similiar problem when I tried to downgrade and go back to stock. After flashing stock from asus, I did it wrong by unzipping (stock_ics_kernel_9.2.1.24US-secure) first then flash the file under the downloaded zip files. Now I am also stuck at Eee Pad, can't get into recovery because it probably wiped out everything. Hopefully this can recover my Eee Pad!!!! I got my fingers cross. This may be my only hope for my asus pad .

Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use

Meat6911 said:
Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use
Click to expand...
Click to collapse
You should be able to with Dolphin HD browser and Flash installed, make sure flash is integrated into the Dolphin. That or the sites should just work..
I use Adaway.

[Q] Phone stuck in setup wizard

Hello, I recently updated from CWM 10.1 to CWM 10.2, but didn't like it and after a full wipe flashed CWM 10.1 with Teamwin recovery to my phone. Then I saw I forgot to flash gapps, so i downloaded them with goomanager and flashed them again. After I did this my phone keeps popping the messages "Installation wizard has stopped working" and "The process com.google.process.gapps has stopped working". I can't get to the menu or settings.
I tried to boot into recovery by holding down volume down and the power button, but this doesn't seem to work. I also tried several programs which allow booting into recovery or hboot, but they don't seem to detect my phone. I still can put files onto my sd-card.
Does anyone know what I could do in this situation to get into recovery again?
I really appreciate the time you put into giving an answer or reading this question.

cmleon said:
Hello, I recently updated from CWM 10.1 to CWM 10.2, but didn't like it and after a full wipe flashed CWM 10.1 with Teamwin recovery to my phone. Then I saw I forgot to flash gapps, so i downloaded them with goomanager and flashed them again. After I did this my phone keeps popping the messages "Installation wizard has stopped working" and "The process com.google.process.gapps has stopped working". I can't get to the menu or settings.
I tried to boot into recovery by holding down volume down and the power button, but this doesn't seem to work. I also tried several programs which allow booting into recovery or hboot, but they don't seem to detect my phone. I still can put files onto my sd-card.
Does anyone know what I could do in this situation to get into recovery again?
I really appreciate the time you put into giving an answer or reading this question.
Click to expand...
Click to collapse
do this
power on the device normally and connect it to pc
go to adb and fastboot folder and open there a command window and do
adb
adb devices
adb reboot bootloader
edit did you remove the battery(then reinsert it) first before holding power button and volume down?

rzr86 said:
do this
power on the device normally and connect it to pc
go to adb and fastboot folder and open there a command window and do
adb
adb devices
adb reboot bootloader
edit did you remove the battery(then reinsert it) first before holding power button and volume down?
Click to expand...
Click to collapse
I did remove the battery, but also tried it by shutting down and then booting into recovery.
I did the following:
-Downloaded ABD and Fastboot and put in on the Sd-card of my phone
-Then I ran the CMD file
-Typed adb and adb devices
-After typing adb reboot bootloader it said the device was not found
The phone was in usb storage mode when I did the above actions.

cmleon said:
I did remove the battery, but also tried it by shutting down and then booting into recovery.
I did the following:
-Downloaded ABD and Fastboot and put in on the Sd-card of my phone
-Then I ran the CMD file
-Typed adb and adb devices
-After typing adb reboot bootloader it said the device was not found
The phone was in usb storage mode when I did the above actions.
Click to expand...
Click to collapse
actually you aren't putting nothing in your sdcard
adb and fastboot files must be on c:android folder on your pc
do this on your pc
create a folder in c and name it as Android
put in that folder these three files
fastboot
adb
AdbWinApi.dll
connect your device in to pc and open in that foder the cmd window

rzr86 said:
actually you aren't putting nothing in your sdcard
adb and fastboot files must be on c:android folder on your pc
do this on your pc
create a folder in c and name it as Android
put in that folder these three files
fastboot
adb
AdbWinApi.dll
connect your device in to pc and open in that foder the cmd window
Click to expand...
Click to collapse
I never used abd and fastboot, so I misunderstood the proper way to use the files.
The problem is solved at last I managed to boot into recovery and flash my rom again.
Many thanks for your help!

stuck with bootloop and no alternative rom

i have a slight problem. i grabbed the ubuntu touch alpha and went in to recovery, loaded it (according to thread instructions) but ended up with a bootloop.
in the end i thought "lets just put another rom back on for now" and then realised i had deleted the other rom from the sdcard! so i'm stuck with it not booting in to ubuntu, and not able to get another rom on as it doesn't boot in.
can i connect to the internal sdcard area myself by plugging the usb in to the pc or something?
i have twrp loaded as recovery
thanks

ah, TWRP adb sideload to the rescue!

problem
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found

partti86 said:
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
Click to expand...
Click to collapse
The issue, Superwipe wipes the internal /sdcard/ and also this is where it flashes from.
You need to boot to recovery and then use ADB to push files to the sdcard.
If you have never used ADB, it can be a bit daunting.
First, you need adb from the Android SDK. It is a big file for the few you need. I have a copy of the relevant ADB files here: https://db.tt/b9dQ6xzp
Unzip this to c:\adb folder on windows. If you are using Linux, it should already have adb in the /usr/bin/ folder.
Next, you need the Universal Naked Drivers: http://forum.xda-developers.com/attachment.php?attachmentid=1934814&d=1367674531
Unzip these to c:\universal_naked_drivers
Boot to CWM and then plug in your USB cable. It should show a new device found. It may find 2, an MTP and then there should be another either Unknown device or an Android ADB device. Right click and update the driver. Be sure to search for driver, then tell it you want to pick from a list. Hit the Have Disk button and then hit the browse button and browse to c:\universal_naked_drivers and hit OK. It should show you a driver to select and hit OK. If you are using Win 8, there is an additional step that is required to used non-signed drivers.
Once the driver is updated, download the zip file you want to flash on your PC. I assume it is a ROM.zip file for this example. Place this file in the c:\adb folder and call it ROM.zip (can be named something else, but this is what we will use for this example).
Now, open a command prompt and execute the following:
Code:
> [B]c:[/B]
c:\> [B]cd c:\adb[/B]
c:\adb> [B]adb devices[/B]
It will probably say some messages about the daemon is not running, restarting adb.
Then it should show a list. There should be some numbers followed by "recovery"
If no devices are shown, check that your ADB device is showing in the Device Manager.
Once you see it in the adb devices list, continue:
Code:
c:\adb> [B]adb push ROM.zip /sdcard/[/B]
successfully pushed xxx bytes
c:\adb>
At this point you should now see the ROM.zip file on the internal storage in CWM to allow you to install it.
Choose to install the file then reboot (not to recovery). You have to let it flash the file (progress bar will show). Once the screen goes black and the progress bar disappears, it should now boot to your ROM..
If your ROM requires a custom kernel and/or GAPPS to be flashed, use the same procedure to push your kernel.zip and GAPPS.zip to the /sdcard/ directory.

mk2media said:
ah, TWRP adb sideload to the rescue!
Click to expand...
Click to collapse
Can you explain what you did please? what is adb sideload?

How do I use ADB to pull files from my Galaxy tab 2 while it's in Recovery Mode?

Hello, I'm trying to pull files from my Samsung Galaxy tab 2 10.1 while it's in Recovery Mode (I'm using Clockworkmod Recovery 6.0.1.0), with ADB. How do I do this?
I can't copy files when my tablet is booted normally because it restarts unpredictably if it sits in the lockscreen or homescreen long enough. The only time it can stay on for long periods of time is while it's in Recovery Mode, and only in Recovery Mode.
I'm running ADB via the Command Prompt and I need help pulling files off of my device while my device is in Recovery Mode. ADB recognizes my device when I type in 'adb devices', and labels it as 'xxxxxx... recovery'. I'm having trouble accessing the files within, and I'm a noob when it comes to using the right ADB commands.
I've tried typing in the command: 'adb pull /sdcard.../' and that command didn't work, telling me 'remote object not found'. Now I know for sure the path I'm using is the right one, because I was able to pull files using the path when the tablet's booted normally (but my tablet restarts halfway into the copying process when doing this, which I why I need to find a way to do this in Recovery Mode!). I figured that the device's internal sdcard storage probably isn't mounted, so I tried doing that in Recovery Mode via Mounts and Storage, and still, ADB couldn't access my device's internal storage, telling me once again 'remote object not found'.
Then I tried mounting my SD Card in ADB with the following command:
adb shell
~ # mount sdcard
It returns with:
mount: mounting /dev/null on /sdcard failed: no such device
I don't know what else to do ... the only way I can keep the device on long enough to copy ANYTHING is while it's in Recovery Mode, and the ADB commands I'm using aren't working. Someone halp!

I tried installing the latest CWM Recovery 6.0.4.5 (which should let me use ADB in recovery mode, yes?) for the Galaxy Tab 2, and it seems my device is in some kind of ... read only mode. I can't successfully install the .zip file in recovery, because when I reboot it still says, at the bottom of the screen, CWM Recovery 6.0.1.0.
I'm beginning to lose hope, here.