I'm trying to flash twrp to my lg g4. I've reached the part where I run
Code:
fastboot flash recovery twrp.img
And everything seems to work fine, but when I try to enter recovery mode, I get the default lg recovery (restore factory mode options) and not twrp.
Here's what it prints out when I run the flash command:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (32060 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 0.341s]
finished. total time: 1.168s
What am I doing wrong?
I tried doing it from a different computer and tried flashing older version of twrp.
No mate, you're not doing something wrong. You must overwrite the stock recovery, because it auto-flashes every time when phone starts. Best way is to use these commands :
adb reboot bootloader
fastboot boot recovery.img (rename recovery recovery.img , without .img (that's the extension, only "recovery", to make it clear)
I'm waiting the results....
Boot the image like. Azza_09 said then when TWRP has booted click on install then change to img instead of zip and select your twrp image. That should work, but Lg front end will be shown when booting to bootloader, simply answer both questions with yes then TWRP will load
Related
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.
Hi All.
Just bought a Wileyfox Swift. I'd like to install Lineage OS.
Reboot into bootloader, fastboot sees correctly my phone.
I run "fastboot oem unlock-go", my data gets wiped, then "fastboot reboot" and Android starts optimizing apps. Fine.
I go back into bootloader, now I try to flash TWRP:
Code:
# fastboot flash recovery twrp-3.0.3-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16908 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.284s]
finished. total time: 0.816s
I reboot, Android starts correctly, power off. Go back into recovery but I still have the original Cyanogen recovery, no TWRP. What I'm doing wrong?
Thanks in advance for any hint!
If you are on the fastboot screen after flashing you should just select recovery and go there
There's no selection menu in fastboot mode on this phone. To go back into recovery I have to power off the device and power on again with volume-down + power button; but the recovery I got into isn't the TWRP I flashed but still the original cyanogenos recovery.
Pull battery after flashing recovery via fastboot. Then boot straight into recovery (not fastboot, not normal ROM), TWRP should be there.
I just uninstall magisk, download and install last security patch (february 2018) from https://developers.google.com/android/ota
When I try to re-install twrp on my LG Nexus 5X, everything seems fine :
Code:
fastboot flash recovery twrp-3.2.1-0-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16477 KB)...
OKAY [ 0.485s]
writing 'recovery'...
OKAY [ 0.210s]
finished. total time: 0.695s
But after several reboot (and several tries reinstalling twrp in fastboot mode) twrp is not installed
The screen just says "No command" with a dead bugdroid
Am I the only one ?
greee said:
I just uninstall magisk, download and install last security patch (february 2018) from https://developers.google.com/android/ota
When I try to re-install twrp on my LG Nexus 5X, everything seems fine :
Code:
fastboot flash recovery twrp-3.2.1-0-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16477 KB)...
OKAY [ 0.485s]
writing 'recovery'...
OKAY [ 0.210s]
finished. total time: 0.695s
But after several reboot (and several tries reinstalling twrp in fastboot mode) twrp is not installed
The screen just says "No command" with a dead bugdroid
Am I the only one ?
Click to expand...
Click to collapse
Do this. First boot twrp, fastboot boot twrp.img. Once in twrp install magisk. Then either boot back into the bootloader and flash twrp or if you have the twrp.img on your device flash that with twrp that you're already booted into.
Sent from my [device_name] using XDA-Developers Legacy app
Thank you, it works
What I've done precisely is
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
Then reboot in RECOVERY MODE choosing recovery on my phone with sound volume button (do not fastboot reboot to normal mode at this point !)
then in twrp recovery mode I have :
install magisk.zip (version 15.3 for now), and also (don't exit twrp now!)
install again (just after rooting) the img file of twrp to the recovery partition (if not on your memory, you can connect and mount your phone during this twrp session)
then wipe dalvik and cache and "reboot System" to end the twrp recevery session
and it works !
On my first normal boot, I've installed Magisk manager (version 15.3 for now) and tested succesfully the abality to boot in twrp recovery mode again
Hi everyone,
I was in the process of unlocking my bootloader, flashing a recovery and rooting my Pixel C with the Skipsoft Toolkit when something went wrong.
The bootloader unlocked (30 sec screen and chirp) and I flashed TWRP but it got stuck there.
TWRP kept asking for the password to decrypt data, and now everytime I start my Pixel C it goes straight there again.
I've tried different options in the Skipsoft Toolkit but nothing seems to work and goes back to the 'Mount Decrypt Data' TWRP screen.
A few things that Ive tried are listed below.
Any help with me getting back to stock and having the Pixel C working again would be greatly appreciated.
Thankyou
4. Root/UnRoot/Disable Encryption/Flash Stock Boot/Check Root Status [ADB Mode]
7. Unroot, Uninstall Busybox and Restore Stock Boot/Recovery [ADB Mode]
1. Push file, reboot to Custom Recovery and install manually [simplest method]
Working out the best location to set for Internal Storage..
Waiting for Adb Mode ...
Device mode detected [recovery adb]
Android Version Detected: 7.1.2 Serial Number:
Pushing Unroot-SuperSU.zip to: /sdcard/
root\Unroot-SuperSU.zip: 1 file pushed. 0.1 MB/s (3574 bytes in 0.064s)
File/s pushed successfully
Device mode detected [recovery adb]
Device Serial Number:
Rebooting to Fastboot Mode and continuing..
Device mode detected: Fastboot Mode
Device Serial Number:
Device Bootloader State: Locked
Booting TWRP recovery-twrp-3.1.1.1-ryu.img ..
creating boot image...
creating boot image - 13051904 bytes
downloading 'boot.img'...
OKAY [ 0.323s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.328s
An Error Occured
Press any key to return to the Main Menu..
5. Rename Recovery Restore Files [Fix system flashing stock recovery on boot]
Device Bootloader State: Locked
Booting TWRP recovery-twrp-3.1.1.1-ryu.img ..
creating boot image...
creating boot image - 13051904 bytes
downloading 'boot.img'...
OKAY [ 0.331s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.331s
An Error Occured
Press any key to return to the Main Menu..
9. Download/Extract/Flash Google Factory Stock Image [Flash Part or Whole Rom]
2. Flash Google Stock Image [in the put_google_factory_image_here\device folder]
image-ryu-opm1.171019.015.zip
ryu-opm1.171019.015-factory-64c65be2.zip
Are you ready to proceed? Type y[yes] or n[no]:
Google Stock Image found [.zip format] in the correct folder.
Filename of image to flash: ryu-opm1.171019.015-factory-64c65be2.zip
Processing archive: put_google_factory_image_here\GooglePixelC\image-ryu-opm1.171019.015.zip
Extracting android-info.txt
Extracting boot.img
Extracting cache.img
Extracting recovery.img
Extracting system.img
Extracting vendor.img
Everything is Ok
Starting Flash Process..
Flashing Bootloader Image..
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.416s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.431s
An error occured when flashing the image
Try rebooting the device manually back to fastboot mode:
1. Unplug the usb cable
2. Stand the tablet in landscape mode [power button on top] and Press and Hold the
Power and Volume Down buttons for 10-15 seconds until it reboots to Bootloader
mode. Then select 'Switch to fastboot mode' using the volume button and press
the power button. The device will say 'Waiting for fastboot command...'
From the main menu in the Toolkit choose the Download/Extract/Flash menu, then
select Flash previously downloaded image.
Sometimes there is a glitch in the flash process and doing it again will fix it.
You can skip the password and change data file system partition to ext3. Then install custom systems like lineage os.
rhmanoa said:
You can skip the password and change data file system partition to ext3. Then install custom systems like lineage os.
Click to expand...
Click to collapse
Hi and thanks for the response.
How do I change data file system partition to ext3?
I can skip the decrypt password screen in TWRP and go into the general settings, but I dont know how to convert the system partition to ext3.
Thanks
Go to wipe data/cache then advanced wipe then change partition setting select data partition change to ext3.
I am new to flashing custom roms, and I got lineage running but I wanted to try Evo X, when I tried flashing through lineage Recovery it booted back into lineage, ok, so I erased all datat through lineage recovery and installed TWRP. I got that on but within a few clicks of messing around I found myself with no recovery or OS and im only stuck in fastboot, I have no idea how to get out of it. mods take this post down if posted in the wrong community. I just though this would be the best place to post it. I am new to XDA, I have these ADB logs from the command I was trying to run
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot boot C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools\TWRP-3.5.1-lemonadep-Nebrassy-2.img
Sending 'boot.img' (196608 KB) OKAY [ 4.500s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
I have no idea why it keep failing, I would greatly appreciate any help to get my phone working again.
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
oddlyspaced said:
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
Click to expand...
Click to collapse
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
Click to expand...
Click to collapse
I guess you should try msm tool then
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
RazOne said:
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
Click to expand...
Click to collapse
I have gotten msm tool and my firmware, but nothing is showing up in msm when my device is connected
ive linked a screenshot of what my msm tool looks like, im just so desperate to get my phone back
Power off phone, position mouse cursor o er start button on msm tool, hold down vol up and down simultaneously, plug phone into computer wait a quick second and press start. That should work.
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
Click to expand...
Click to collapse
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
I LITERALLY CANNOT THANK YOU ENOUGH, YOU ARE LIKE THE DAD I NEVER HAD.
Lol, i'm not that old found the answer myself in a forum after 2 days of being stuck in fastboot.
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
hello guys i am facing that same issue but my own show slot_b and then i try to use your step but still not work help me plizzz
Googled the error you have. Check this post (and following ones)
[SOLVED] - Bootloop with completely new OPO9pro after oem unlock
Hello, just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup) Enabled developer options, OEM unlocking and USB debugging. After update, 1*reboot. then another reboot to bootloader, and executed...
forum.xda-developers.com
I think you should start over and use "fastboot flashing unlock" instead of fastboot oem unlock.
Follow the link in that thread. Droidwin has the best tutorials for oneplus you'll find. Never had this error myself, so can't say for sure what to do.