Develop Bugs

[Q] Phone not showing up in adb shell

Here's my issue:
I create a folder on my Nexus ".A." primarlily because it'd be first up top, well I realized after I wiped all data/cache/system that my phone doesn't recognize this folder with the ROM I have in it via Clockwork. So I reboot my phone, stuck in Google boot logo. I'm able to get into Fastboot mode, and my phone shows up when I ./fastboot-mac devices
However, adb devices lists nothing, and adb shell says device not found.
I'm trying to push this AOKP zip file to the phone so that I can boot back into recovery and flash it.
Any ideas on what I need to do to make this happen?

MacPro:android-sdk Home$ fastboot flash boot boot.img
sending 'boot' (3776 KB)...
OKAY [ 0.428s]
writing 'boot'...
OKAY [ 0.257s]
finished. total time: 0.685s
MacPro:android-sdk Home$ adb push update.zip /sdcard/update.zip
error: device not found
boot.img was taken from AOKP 38
i then changed the name of the rom zip to update and tried to adb push it and received this error. :/

followed these instructions :
Android 4.0.2 factory images
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
got past the google start up screen and it looks like i'm now boot looping on the stock nexus boot screen

fastboot flash'd clockwork mod recovery, cleared data system wiped
now i'm stuck on google boot, however this time instead of just sitting on the google logo it's rebooting itself every 10 seconds and vibrating each time.
pulled battery, rebooted, same thing.
letting it sit and continue to do this.
phone still not showing up in adb devices

Just in case you didn't know, adb doesn't work when you're in bootloader mode, only in recovery mode and when you're booted will adb work. Regarding your boot looping problem, I'm not too sure but are you flashing the correct image and is it not corrupted? Check the hash for the zip and compare it.

[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

LG G4: Installing SuperSU through TWRP renders device unbootable

FOR LG-H815, bought in Germany.
a) Went through the effort and unlocked the bootloader through LG's official method.
b) Confirmed, several times, that the bootloader is indeed unlocked.(via 'fastboot getvar unlocked' and verifying that the response is "unlocked: yes")
c) Tried to swap the Stock Recovery Mode with TWRP, using 'fastboot flash recovery twrp-2.8.6.0-h815.img'. The process ends in 1 sec. After booting in recovery mode, I find out it doesn't actually flash it.
d) Inside cmd: adb reboot bootloader
fastboot boot twrp-2.8.6.0-h815.img
At this point I am trying to boot TWRP for a one-time job of rooting the device.
-Install>>Select UPDATE-SuperSU-v2.46.zip>>Swipe to Install>> Reboot System
e) After reboot: PERMANENTLY STUCK, will not boot past LG's Logo. It is still possible to enter the Stock Recovery Mode, and Stock Download Mode.
I have repeated the process twice, reflashing the stock ROM, to the same effect. Any help is greatly appreciated.

You're flashing outdated versions of TWRP and SU...

I helped with this problem about 100 times now but I will do it one more time...
Firstly, reflash the stock MM ROM again.. Then download the better looking TWRP 3.0.2-0 from official twrp site -> https://dl.twrp.me/h815/twrp-3.0.2-0-h815.img.html
Now a little explanation. As far as I know in 6.0.X Google changed their policy a bit and the option to root the phone/ flash recovery is locked even though you have unlocked bootloader, and as well system root doesn't work, so instead of old SuperSU 2.46 you want to download newest systemless root zip -> http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 . Now, since there is no stock modified boot.img for G4, you have to download and unpack the custom kernel like SimpleGX and take it's boot img that you want to flash via fastboot, or you can try flashing boot.img from the Autoprime's V20D flashable zips, I didn't try that one and I will not be able to because my G4 got a bootloop issue that I recovered it of by my self but I cannot boot it up on Marshmallow stock firmware. Anyway once you flashed the modified boot img you should be able to flash recovery and boot it up normally, then flash systemless root and if you used boot.img from custom kernel, flash the full package because you did not flash all the stuff from the package what may cause software problems in the long term I suppose. I think that's all you need to do to root it on MM.

Adam Myczkowski said:
I think that's all you need to do to root it on MM.
Click to expand...
Click to collapse
And you would be correct. Although I have to wonder why guides on XDA don't even mention flashing a custom kernel like SimpleGX_KERNEL_H81520X_v1.3.2.zip
Additional steps for installing ROOT/TWRP on LG G4:
Inside CMD:
C:\adb>adb reboot bootloader
error: device '(null)' not found
C:\adb>adb devices
List of devices attached
LGH81539bf5a8e device
C:\adb>adb reboot bootloader
C:\adb>fastboot boot twrp-3.0.2-0-h815.img
downloading 'boot.img'...
OKAY [ 0.956s]
booting...
OKAY [ 0.028s]
finished. total time: 1.000s
Inside TWRP: Install>>Select SimpleGX_KERNEL_H81520X_v1.3.2.zip>>Swipe to the right>>Reboot // .zip file is ~19MB
Inside CMD:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp-3.0.2-0-h815.img //now attempting to overwrite the stock recovery
target reported max download size of 536870912 bytes
sending 'recovery' (31652 KB)...
OKAY [ 0.969s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.365s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>adb devices
List of devices attached
LGH81539bf5a8e device
C:\adb>adb reboot recovery //to verify that TWRP has been installed.
Inside TWRP:
Install>>Select BETA-SuperSU-v2.71-20160331103524.zip>>Swipe to the right>> Reboot
DONE.

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?

Problem with installing TWRP on OOS 10.0.1

Hello guys,
Please help me because I'm stuck. I'm trying to install latest TWRP on my OP5 with no success. Let me tell you what I tried.
- I'm running on OOS 10.0.1
- sucessfully installed ADB and drivers on Windows 10.
- sucessfully unlocked bootloader
Then I downloaded latest TWRP, renamed it to twrp.img and placed it in a folder where ADB and fastboot are. Device is seen in both ADB and fastboot.
When in fastboot I tried first the command:
C:\>fastboot boot twrp.img
fastboot: error: cannot load 'twrp.img': No such file or directory
then I googled and tried with file directory:
C:\>fastboot flash recovery c:\adb\twrp.img
Sending 'recovery' (35228 KB) OKAY [ 1.025s]
Writing 'recovery' OKAY [ 0.164s]
Finished. Total time: 1.220s
The second command with direct source I tried both using USB 3.0 and via USB hub and it doesn't work. When I reboot to recovery it enters to the stock OP recovery and no sign of TWRP.
Can you please help me?
Thanks in advance!
Maciej

Hi, i could be misreading your steps but have you tried renaming the twrp image to twrp and then try fast booting with twrp.img again. It may be that by including the .img in the file name it is looking for twrp.img.img.
I'm no ADB expert but that may be all that's needed as it reads like everything else is working as should from my limited experience.