Develop Bugs

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.

Xperia m Lineage OS recovery and possibly bootloader issues

I'm not sure if it's right place to start this thread but the problem is that after clean install of lineageOS nightly build from 25th of January I have no recovery that's what ROM manager app says, phone doesn't show "SONY" logo while booting which means that I can't boot into recovery mode (and that's obvious because I think I don't have recovery) also phone is not rooted and works without gapps. Is there any option to fix it?

Lineage OS recovery
I installed Lineage OS for my Xperia M which was running on Cyanogenmod 14.1.
After installing the OS I pressed the recovery option after pressing power option, but the set do not boot to recovery by to Lineage OS only. I used TWRP recovery.
I tried to flash TWRP recovery via ADB, but the message is
C:\adb>fastboot flash recovery twrp.img
sending 'recovery' (11208 KB)...
OKAY [ 0.705s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.721s
Can some one help me.
I am new to this forum and a non - techie.
I have moto G2, Sony XperiaM and Nexus 6 all phones rooted. MotoG2 and Nexus 6 are running with resurrection remix.

Xperia M does not have a recovery partition like some other devices. See the "some info" section on this post
I don't know of a fix at the moment, but as a work around in the meantime you could:
flash an image containing a recovery to the boot partition
Code:
fastboot flash boot recovery.img
Then when booting the phone you'd have the recovery options
If you wanted to boot to android, you would need to reflash the boot partition with the boot.img file in the lineageOS zip

Thanks for the reply. Will post after trying this solution.

Sriwelcomesu said:
I installed Lineage OS for my Xperia M which was running on Cyanogenmod 14.1.
After installing the OS I pressed the recovery option after pressing power option, but the set do not boot to recovery by to Lineage OS only. I used TWRP recovery.
I tried to flash TWRP recovery via ADB, but the message is
C:\adb>fastboot flash recovery twrp.img
sending 'recovery' (11208 KB)...
OKAY [ 0.705s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.721s
Can some one help me.
I am new to this forum and a non - techie.
I have moto G2, Sony XperiaM and Nexus 6 all phones rooted. MotoG2 and Nexus 6 are running with resurrection remix.
Click to expand...
Click to collapse
I haven't tried to flash recovery via adb yet but thanks for information that it won't work
Edit:
You flashed twrp.img as far as I remember you should change file name to boot.img and then flash. I'll try it later hopefully phone will boot in recovery mode

I had the same problem on my girlfriend's Sony Xperia M.
Just download the latest Lineage OS nightly (I used 20170131) and extract boot.img from the zip. Then go into bootloader mode (settings -> developer options -> advanced reboot, long press of lock button -> reboot -> bootloader, you should now have the blue light on and the screen turned off), connect it to the PC and run
Code:
fastboot flash boot boot.img
TWRP should now work again

Motherjoker said:
I had the same problem on my girlfriend's Sony Xperia M.
Just download the latest Lineage OS nightly (I used 20170131) and extract boot.img from the zip. Then go into bootloader mode (settings -> developer options -> advanced reboot, long press of lock button -> reboot -> bootloader, you should now have the blue light on and the screen turned off), connect it to the PC and run
Code:
fastboot flash boot boot.img
TWRP should now work again
Click to expand...
Click to collapse
Thanks, you saved me a lot of time.
For anyone else who are in the same shoes:
Note that it is crucial to only connect the USB when it is already in fastboot mode, since if you have to unplug and replug it for driver detection/reinstall purposes, when you unplug it the device simply turns off or reboots to system.
If it is stuck <waiting for device> you might have to visit the device manager and update the fastboot device's driver.

Thanks everybody for your replies. This is how i solved the issue.
Got the phone to fastboot mode using key combination
connected to pc
Confirm device status by typing fastboot devices
Then flashed recovery by typing
Fastboot flash boot boot.img
Twrp was renamed as boot before flashing.
After completion used key combination to go to recovery and i was in twrp.this booting to twrp will take around 10 mins. Be patient.
The os will not be there. We need to flash os and gapps

after install of february security patch, twrp install failed :(

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

Bricked? Bootloop to TWRP > Stuck on TWRP Logo > Fastboot not recognized > No way out?

Hope you guys can give me a hand and get me out of this situation...
What I am using
Xiaomi Redmi Note 5 Pro with:
- Pixel Experience Rom
- TWRP 3.5.2_9
Windows 10 21H1 x64
What happend
- Updating Pixel Experience Rom failed
Downloaded update
Booted into Recovery (battery 85%)
Recovery stuck on Logo
After 30m I tried to reboot to system (thinking update failed or never started)
Reboot in to Recovery
Stuck on Logo
What I tried
- I tried XiaomiFastBootADBTools (latest version)
Device is recognized in Recovery mode
In recovery I can't do anything
Rebooting to System from here results in reboot into Recovery
Booting to fastboot works, but device is not recognized
Re-installed drivers, but no luck
Still recognized in Recovery mode
Still NOT recognized in Fastboot mode
Windows Device Manager > The drivers for this device are not installed. (Code 28)
And turning of phone is not possible, just goes back to Recovery
Don't know what else to do. I have installed all the drivers I could find. Even used Snappy Driver, but nothing seems to do the trick when the phone goes into Fastboot mode. PC just doesn't recognize it.
So can't do anything in Recovery mode; just watching the TWRP logo.
And device is not recognized in fastboot mode; forgot usb debugging?
And can't boot into system to change that, because of bootloop to Recovery.
So, am I **** out of luck and bricked my phone?

While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.

zaqm said:
While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.
Click to expand...
Click to collapse
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.

FlashyDuck said:
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.
Click to expand...
Click to collapse
What about trying to flash latest fastboot rom with MiFlash since fastboot now works?

Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!

FlashyDuck said:
Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!
Click to expand...
Click to collapse
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy

--double, woops--

zaqm said:
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy
Click to expand...
Click to collapse
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?

FlashyDuck said:
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?
Click to expand...
Click to collapse
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!

zaqm said:
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!
Click to expand...
Click to collapse
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.

FlashyDuck said:
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.
Click to expand...
Click to collapse
Maybe some glitch of OrangeFox recovery and yeah, let's hope that this issue won't appear anymore.
All the best, zaqm!

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.