Develop Bugs

[Q] TWRP recovery Stuck at Booting recov image

Hi, it's the second time i try to install TWRP recovery v2.2.0+ and each time it keeps getting stuck at the boot with the message
Bootloader version 0.03.06-ics unlock mode
Booting recovery kernel image.
Waited for more than 10 minutes and nothing happened.
i can reboot and and log into ics normally i just don't have access to a recovery.
---I want to know how to properly install twrp , what went wrong and how to fix it.:
the script:
@echo off
cls
echo reboot to bootloader
adb wait-for-device
adb shell su -c "mount -o remount, rw /system/ && mv /etc/install-recovery.sh /etc/install-recovery.offsh;"
adb reboot-bootloader
echo flashing recovery
fastboot flash recovery recovery-A100ICS-TWRP-2.2.0.img
echo -
echo -
fastboot reboot
adb wait-for-device
echo check the recovery XXXXXXXXXXXXXXXX--This is where i'm stuck at.
adb reboot recovery
MY SETUP:
ROM FLEX-A100-REAPER-RELIX_Rev2 , OC A 1500, CWM was working ok.
WIN64

I would suggest downloading the image again, then trying the install script after you delete the current image with the newly downloaded image.
If you feel OK using a terminal its pretty straight forward
Open a terminal and CD to the folder with adb fast boot and recovery image
Example
cd c:\recovery
If powered on type
adb reboot bootloader
After it boots into download protocol type
fastboot erase recovery
fastboot flash recovery twrp.img
Twrp.IMG being whatever the file name is.
fastboot reboot
Let it boot into android then
adb reboot recovery
See what it does.
Tapatalked from my Galaxy S II.

a100/openrecovery-twrp-2.2.2.1-a100.img
renamed to recovery.img and flashed properly.
Same problem. Can it be related to the bootloader number ?

IamModeste said:
a100/openrecovery-twrp-2.2.2.1-a100.img
renamed to recovery.img and flashed properly.
Same problem. Can it be related to the bootloader number ?
Click to expand...
Click to collapse
That's the only boot loader we can flash on so that's fine. Did you download the image again?
Tapatalked from my Galaxy S II.

pio_masaki said:
Did you download the image again?
Click to expand...
Click to collapse
yes i did , donloaded openrecovery-twrp-2.2.2.1-a100.img,
renamed to recovery.img and flashed without any problem.

I redownloaded and flashed it again,
To no avail...
Nothing else to suggest ? I'd like to use a touch enabled recovery.
Sent from the usual suspects.

IamModeste said:
I redownloaded and flashed it again,
To no avail...
Nothing else to suggest ? I'd like to use a touch enabled recovery.
Sent from the usual suspects.
Click to expand...
Click to collapse
Did you erase recovery before flashing?

Theonew said:
Did you erase recovery before flashing?
Click to expand...
Click to collapse
Agreed.
I would try again make sure to: 'fastboot erase recovery', then 'fastboot flash recovery recoveryname.img' (make sure it's recovery [space] then the img name).
You can also try Zeronull's 2.1.1/2.2.0 and Linuxsociety's 2.2.2.0. It could be a bad upload of the 2.2.2.1 img

Answer
There's a file in /system/etc/ called install_recovery.sh that may need to be deleted for the custom recovery to stick. You need root to remove it.
sounds like you may need to start fresh.
Use fastboot to erase the system, boot, recovery and cache, perform a fastboot -w and then install the new recovery and ROM. Erasing the system will kill that recovery file from above.
Let me know. There are a couple of other options that I can think of.
---------- Post added at 06:48 AM ---------- Previous post was at 06:32 AM ----------
Here is what it should look like in fastboot on the command prompt yours will be different of course because mine is setup differently. But basically load up fastboot on windows or whatever you use and first erase the recovery then run fastboot -w and then flash the twrp recovery image and finally fastboot reboot. After reboot hold down volume button and enter recovery as usual. Should work then. My explanation is above. It's the install_recovery.sh file fastboot -w takes care of it! Sorry for bumping and old thread. But it doesn't look like it ever got solved.
Code:
C:\>C:/android/fastboot.exe erase recovery
erasing 'recovery'... OKAY [ 0.733s]
finished. total time: 0.734s
C:\>C:/android/fastboot.exe -w
erasing 'userdata'... OKAY [ 5.480s]
erasing 'cache'... OKAY [ 2.052s]
finished. total time: 7.533s
C:\>C:/android/fastboot.exe flash recovery C:/recoverytwrp.img
sending 'recovery' (4410 KB)... OKAY [ 0.491s]
writing 'recovery'... OKAY [ 0.255s]
finished. total time: 0.746s
C:\>C:/android/fastboot.exe reboot
rebooting...
finished. total time: 0.001s

[Q] Cannot Boot Into Temporary Custom Recovery

Hey guys. I am attempting to boot into custom recovery to make a backup of my stock rom with stock recovery intact. Here's what I have done so far:
(Fastboot and ADB is up and running)
1) Downloaded the custom recovery
2) Placed custom recovery in my ADB/Fastboot file folder location
3) Renamed custom recovery img to recovery.img
4) checked md5 sums in adb
5) adb booted to fastboot
6) entered cmd: fastboot boot recovery.img
Once I do that it says :
downloading 'boot.img'...
OKAY [ 1.139s]
booting...
OKAY [ 0.001s]
finished. total time: 1.143s
BUT nothing happened. It stays in fastboot on the phone and freezes the phone. What in the entire hell am I doing wrong?
UPDATE: Nevermind. I pulled the recovery image out of Zar's decrypted RUU file and flashed it. Then I just did a full backup in adb

[Q] Samsung Galaxy Nexus File Transfer?

I have a GSM Galaxy Nexus with bootloader TWRP v2.1.2 installed. The OS has been wiped...how do I load files onto the device to flash a new OS since the device doesn't have a microSD card slot? TWRP v2.1.2 it seems does not support adb transfers and I'm not sure how I can update the bootloader or get files to the device's storage?

In short: get to fastboot mode, update bootloader if necessary (most likely not), reboot bootloader, flash a new version of TWRP, reboot into recovery and start pushing ROMs with ADB.
Sent from Samsung Galaxy Nexus @ CM11

How do I get into fastboot mode on the phone? I have the necessary files on OS X for adb and fastboot commands. What would I type to send a file to the phone once in fastboot?

rhattan503 said:
How do I get into fastboot mode on the phone? I have the necessary files on OS X for adb and fastboot commands. What would I type to send a file to the phone once in fastboot?
Click to expand...
Click to collapse
Looks like you need more assistance.
Get to fastboot: when powered off, hold VOLUME+ and VOLUME- and press POWER until it shows a green Android with START on top.
Flash a bootloader: connect to PC, and use this command: "fastboot flash bootloader *PATH-TO-BOOTLOADER*". Flashing a recovery goes similarly.
Once you have a higher version of recovery set up, get to recovery and enable ADB Sideload. Then on PC, use command "adb sideload *PATH-TO-ROM*" to sideload (push and flash) a ROM to the phone.
Sent from Google Nexus 4 @ CM11

Thank You!
I thought my phone was bricked...Thank you for taking the time to go into more details for me.
-Robert

Fastboot flashing not working?
I tried the following commands for both the latest Galaxy Nexus CWM and TWRP.
I tried "./fastboot flash bootloader ./recovery.img"
sending 'bootloader' (7124 KB)...
OKAY [ 1.206s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 1.237s
Galaxy Nexus displays: "FASTBOOT STATUS - FAILWite Fail"
I also tried
"./fastboot flash boot recovery.img"
sending 'boot' (7124 KB)...
OKAY [ 1.207s]
writing 'boot'...
OKAY [ 0.430s]
finished. total time: 1.637s
Galaxy Nexus displays "FASTBOOT STATUS - OKAY" but when I reboot into recovery the old TWRP is still running.
What am I doing wrong?

Fixed!
Ran the command "./fastboot flash recovery recovery.*img" and it worked like a charm. Now I have a new recovery image installed...sweeeet!

[Q] TIFU going from GPE5.1 Back to Sense, Please help :)

So, the instructions are below pulled out of the Back to Sense thread.(http://forum.xda-developers.com/showthread.php?t=2733523) got to the end of what i've pasted no problems......
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Everything went well until the after that... I stuffed up royally.. my failure is below...
PS C:\adb> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
PS C:\adb> fastboot flash recovery TWRP_Recovery_2.8.6.2_M8_CPTB.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16804 KB)...
OKAY [ 1.515s]
writing 'recovery'...
OKAY [ 0.940s]
finished. total time: 2.455s
fastboot boot TWRP_Recovery_2.8.6.2_M8_CPTB.img
I realize i skipped the below steps...
Boot into stock recovery
Factory reset
Reboot into bootloader
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever.... one thing worth noting, i can see the internal storage(well some of it) the device is recognized in windows and then internal storage is 10.5gb free out of 10.6gb, Navigating to the internal directory shows 3 directories: 0, obb, and TWRP. 0 is a neverending folder. every 3rd layer deep click it shows the root directory again...
Help would be very very much appreciated!
cheers!
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!

Cameltoemcgee said:
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever....
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Click to expand...
Click to collapse
If the bootloader was overwritten, damaged or corrupted, the phone would be bricked, and the screen would not come on at all.
This is the second post on the first page where the OP solved their own issue. You guys are getting good at fixing your own problems.

Install TWRP and then to root.

Hello please can anyone advise me and forgive any wrong terms..
I am trying to push twrp to my lg g4 H815 20g using adb and fastboot but everytime it comes back with
error: cannot load 'twrp.img': No such file or directory
PS C:\Users\Anthony\Desktop\ADB>
i have tried renaming twrp file to various things and changing the command fastboot flash twrp.img or fastboot flash recovery.img
but i keep getting errors of one discription or the other..
I have followed guild after guild but still not made the magic happen..
Bootloader is officially unlocked via LG and twrp for lg g4 downloaded from twrp site.
Been trying for two days to install a recovery so i can also root but having no luck.
please any help or advise would be appreciated..

you must put the "twrp.img" into to your "ADB" folder and then exec this:
Code:
fastboot flash recovery twrp.img

Hi thanks for your help
yes I have the img file in adb/fastboot folder and been doing this and still comes back in cmd as no such file etc..
Tried renaming twrp img file and changing fastboot flash line to match but still no joy..
Tried earlier g4 twrps same outcome it’s as if downloaded recovery’s are corrupt or something as they don’t appear to be being seen..
What is best name for the twrp image or do you leave it as it came downloaded and run the
fastboot flash recovery twrp.img Regardless of what twrp called when downloaded..
Thanks

Have you changed directory to the sdk folder? Or shift + right clicked in folder "open cmd here"?
The command is "fastboot flash *whatever recovery is called in adb folder*"
I ended up changing the name to "twrp3.1.1" or whatever cause it had a hell of a name when downloaded. Just name whatever you want as long as you call it same thing when flashing.
Make sure you also have a copy of it on your SD too because it wont stick and when you reboot to the recovery you then need to reflash the image from in there.

Hi I think it was successful i changed name of twrp on second attempt and it seemed to work..
only problem was when i tried to manually boot into recovery via volume down and power i did something wrong and accidentally reset the dam thing instead of booting into twrp......will have to do it all over again but hopefully i have it sorted..
PS C:\ADB> adb reboot-bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
PS C:\ADB> fastboot flash recovery twrp.img
error: cannot load 'twrp.img': No such file or directory
PS C:\ADB> fastboot flash recovery twrp-3.1.1-1-g4.img
target reported max download size of 536870912 bytes
sending 'recovery' (33952 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 0.422s]
finished. total time: 1.219s
PS C:\ADB> fastboot reboot
rebooting...
finished. total time: 0.031s
PS C:\ADB>

Hello! I reopen this tread.. I have an issue with flashing twrp, via adb I start into bootloader, but when i put the command to flash it.. <waiting for device>. Why?