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

No fastboot, TWRP flickering screen

Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...

djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??

Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.

I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.

As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?

You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.

_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found

djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot

Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.

djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.

where can i wirte this codes i dont know , can anyone help me??? i have same problem

i can not connect device also in adb mode pc didnt accept the drivers

y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices

berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag

y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240

now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work

y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window

sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file

berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??

y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.

[Q] Problems pushing ROMs to my M8

I want to start off saying that I'm a complete noob to this and I now realize I was stupid for biting of waaay more than I can chew.
I turned s-off and rooted using firewater exploit. I installed ViperOne with TWRP and all was well, until I decided I wanted to try Android Revolution HD (here) I stupidly decided that in addition to wiping the normal stuff, I would just format. I backed up to my pc just by copying everything into a folder (downloads, pictures, etc) and I wiped it. Now I've got the ROM on my computer and I'm trying to put it on the phone. I've tried using adb sideloader, and adb push but neither are working (I'm fairly certain I typed everything in correctly in cmd.)
How can I install ANY rom so that I can download with the phone and install from TWRP without formatting?

you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0

jova33 said:
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
Click to expand...
Click to collapse
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"

chobungus said:
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
Click to expand...
Click to collapse
You probably didn't have USB debugging enabled, do you have access to a micro SD card?
If you do, load the rom onto that and flash from there.
Sent from my HTC6525LVW using Tapatalk

Well I was able to get it working, but as usual, I don't really know how. I redownloaded adb and the rom and restarted my computer. Tried the exact same sideload command and it worked.

Can't write through adb

I wonder is there anything I can do to save this phone? At the moment it doesn't haven any ROM in it and only has a third party recovery. I don't know how can I identify which recovery this is but it's in Chinese. I'm able to enter recovery mode. And "adb devices" on PC can recognise the phone.
I have a zip file of a ROM, and I tried "adb sideload ROM.zip". It says:
loading: 'ROM.zip'
error: closed
Click to expand...
Click to collapse
I tried again, and it says:
loading:'ROM.zip'
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
Click to expand...
Click to collapse
I tried "adb push ROM.zip /sdcard/ROM.zip" trying to copy the ROM file into the phone, it waited for a while and then it says:
failed to copy 'ROM.zip' to '/sdcard/ROM.zip': No such file or directory
Click to expand...
Click to collapse
So I thought maybe this phone doesn't have a "sdcard" folder. I tried "adb shell" and then "ls", and found there is a "sdcard" folder there. But if I type "cd sdcard", it says:
/sbin/sh: cd: can't cd to sdcard/
Click to expand...
Click to collapse
I don't really know what's going on here, but I tried "cd /sdcard/", and it looks like this:
~ # cd /sdcard/
/data/media #
Click to expand...
Click to collapse
I don't know why it is not sdcard on the left. I tried "ls" to see what's in there, and there are four things (I assume they're all folders?): 0; clockworkmod; legacy; obb. Now I don't even know whether they're actually files in the sdcard folder or was I led to a completely different directory.
I was thinking maybe it is a problem with this particular recovery. So I was trying to find a way to install a new recovery into it. What I've found by google was that I should be able to do that in boot loader. However I also had difficulty trying to get into boot loader.
As far as I know, the phone itself (Smartisan T1) doesn't have a button combination to enter boot loader (I tried many combinations on another T1 which is still good to use). And I don't know how to check whether the boot loader on this phone is unlocked. The recovery has an option of "enter bootloader" so I tried that, it asked me if I want to root this device, if I choose "yes" it only gets stuck when showing the logo. I also tried "adb reboot bootloader" and it also stucks at the logo. (I tried the same command on another phone and it gets me into fastboot mode)
I think I've tried everything I could think of but the problem is still unsolved. Does anyone have any idea what else might fix this issue? Thank you so much for your help!

[Q] XT1039 bootloop and can't get adb to pull files

Hi,
all of a sudden, my XT1039 Moto G has entered a never ending bootloop that goes like this:
- powers up, motorola animation runs fine
- if the sim is inserted, it lets me tap the numbers for 5 seconds, then it soft reboots by itself
- if the sim is not inserted, it loads fine, it lets me do what I can do in 5 seconds, then it soft reboots by itself
my XT1039 is totally stock, unrooted, the last app I've installed is a flashlight app from the Google App Store, to turn on and off the back led, three days ago, and has been working fine for three days since then.
What I have done so far:
- booted android to safe mode: 5 seconds, and it bootloops again
- booted to recovery and wiped the cache partition, rebooted to android and the problem is still there
- when powered off, held the vol up and down buttons for two minutes: somebody wrote it worked for him, it doesn't work for me
- tried all the other options on the recovery menu (Factory, BP Tools, QCOM), but they all seem to do nothing, and get me again to the bootlooping
- booted to flashboot with an otg cable and a usb pendrive, hoping a magic "backup to usb" option would show up, but it doesn't
- disconnected the battery for 5 minutes, and replaced it with a known good working one out my wife's XT1032 (same battery model), still no luck
now I'm almost ready to boot to recovery and wipe data/factory reset, but I still would like to copy the Pictures folder out of the device first, so I tried with adb:
- installed the Motorola (and the universal too) drivers on my Win 8.1 and downloaded a recent version of adb.exe (Android Debug Bridge version 1.0.32)
- during the 5 seconds of bootloop life, I can browse the XT1039 folders from Win 8.1 explorer, but 5 seconds is too short to do anything
- booted the XT1039 in flashboot, but the command adb devices doesn't see my device
- while in flasboot, navigated in Recovery --> Apply Update from ADB, the Win 8.1 alerts me there's something new on the USB chain, and adb devices says:
List of devices attached
TA98601*** sideload
but in the sideload mode it seems I can't run the pull command to get my files out of the damned device, every command like adb pull, push, shell, returns the same error:
error: closed
Is there anything else I can try to get my files out of the XT1039, before restoring it to factory ?
Any hint is highly appeciated, thanks

I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.

Professor Gibbins said:
I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.
Click to expand...
Click to collapse
You can't install TWRP with a locked bootloader, and unlocking the bootloader wipes data...

Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?

Professor Gibbins said:
Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?
Click to expand...
Click to collapse
Yes, unfortunately the bootloader is locked, the phone is stock as if just bought out of a shop.
Here's the sequence of commands ran while in fastboot
C:\adb>adb kill-server
* server not running *
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
C:\adb>adb pull /system/app/Settings.apk
error: device not found
and the here's the sequence of commands ran in fastboot-->recovery --> apply update from ADB (the only option I've found that seems to enable some adb functionality)
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
List of devices attached
TA98601*** sideload
C:\adb>adb pull /system/app/Settings.apk
error: closed