My bootloader is unlocked. I used LG Bridge to update to 20A. Now I cannot get root back. I boot into fastboot. Flashing TWRP seems to work, but I cannot get into it. I'm aware that I have to boot directly into TWRP after flashing for it to stick (or it will be overwritten with stock recovery). I've tried fastboot commands to boot (see below). I've also tried the volume down button combo to boot to recovery, which gets me to the prompts about erasing data, but No exits and Yes prompts x 2 never boots to TWRP. It doesn't load it at all. I've re-downloaded TWRP to be sure I didn't have a bad file.
C:\LGH850>fastboot flash recovery twrp302-h850-2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17524 KB)...
OKAY [ 0.665s]
writing 'recovery'...
OKAY [ 0.206s]
finished. total time: 0.873s
C:\LGH850>fastboot boot twrp302-h850-2.img
downloading 'boot.img'...
OKAY [ 0.657s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.679s
I've read in forums about other devices that folks lost some Fastboot commands after an update, but the instructions are device specific. Is anyone else having this issue after updating to stock 20A Nougat? Does anyone have any ideas? Many thanks!
EDIT: New problem!
I had this issue before when it reported as unlocked:
C:\LGH850>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
NOW, though...
C:\LGH850>fastboot getvar unlock
unlock:
finished. total time: 0.005s
C:\LGH850>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.014s]
finished. total time: 0.014s
C:\LGH850>fastboot getvar unlock
unlock:
finished. total time: 0.009s
C:\LGH850>fastboot flash unlock unlockH850.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.038s]
writing 'unlock'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.063s
So, now I'm at a complete loss.
So flash recovery and remove the battery and boot by following steps
1. Press and hold (at the same time) the Power and the Volume Down buttons until the LG Logo is being displayed on your G5
2. Next, release the power button for only a moment and then press it again (keep holding)
3. Keep pressing the buttons until the recovery mode menu is displayed
4. Answer both questions with "YES" (no worry won't reset your phone as described) and then TWRP should boot
5. Now swipe to allow modifications in TWRP
Bonus step:
6. Format DATA partition (note format not wipe) and flash SuperSU
gwolfu said:
So flash recovery and remove the battery and boot by following steps
1. Press and hold (at the same time) the Power and the Volume Down buttons until the LG Logo is being displayed on your G5
2. Next, release the power button for only a moment and then press it again (keep holding)
3. Keep pressing the buttons until the recovery mode menu is displayed
4. Answer both questions with "YES" (no worry won't reset your phone as described) and then TWRP should boot
5. Now swipe to allow modifications in TWRP
Bonus step:
6. Format DATA partition (note format not wipe) and flash SuperSU
Click to expand...
Click to collapse
Thanks. I was aware of the clicking YES twice, but when I do that, it never gets to TWRP. That was the behavior before my new issue (noted above, showing questionable bootloader unlock).
your bootloader is already unlocked
why do you try to flash unlock again?
anyway, the key combination should work
just tested...
you just have to get the proper timing
using a H850 variant
gwolfu said:
your bootloader is already unlocked
why do you try to flash unlock again?
Click to expand...
Click to collapse
I did this when the 'fastboot getvar unlock' command no longer showed 'yes' status.
gwolfu said:
anyway, the key combination should work
just tested...
you just have to get the proper timing
Click to expand...
Click to collapse
I agree that it SHOULD work, and yet it doesn't. It isn't a timing issue--I get to the wipe data prompts and click yes, but it doesn't load into TWRP after that. I'm doing this immediately after flashing recovery per the instructions.
https://dl.dropboxusercontent.com/u/27540838/20161126_142933.mp4
jaybird779 said:
I did this when the 'fastboot getvar unlock' command no longer showed 'yes' status.
I agree that it SHOULD work, and yet it doesn't. It isn't a timing issue--I get to the wipe data prompts and click yes, but it doesn't load into TWRP after that. I'm doing this immediately after flashing recovery per the instructions.
https://dl.dropboxusercontent.com/u/27540838/20161126_142933.mp4
Click to expand...
Click to collapse
I had the same problem on my h850 you have to install twrp 3.0.2.1 otherwise twrp won't stick, loads of guides advise a previous version, I wasted hours going around in circles
rpsweb said:
I had the same problem on my h850 you have to install twrp 3.0.2.1 otherwise twrp won't stick, loads of guides advise a previous version, I wasted hours going around in circles
Click to expand...
Click to collapse
That's great, thanks! I'll give it a try. The TeamWin site shows 3.0.2 is the latest. Are you using a version for the S7 (or other device)? Any chance you could post the version that you used?
jaybird779 said:
That's great, thanks! I'll give it a try. The TeamWin site shows 3.0.2 is the latest. Are you using a version for the S7 (or other device)? Any chance you could post the version that you used?
Click to expand...
Click to collapse
https://build.nethunter.com/test-builds/twrp/lge
Thanks for that resource!
Related
Hi,
I followed this article -> phandroid DOT com/2014/11/05/how-to-root-nexus-9/ (Sorry, new account, can't link) to the letter, and everything seemed to go well, until the last step where I ran "fastboot reboot" which returned "error: device not found" I thought nothing of this as there was a reboot option on the devices screen, so I rebooted, I get the google logo, followed by the four orbs, then it says "Optimising app x of 99" once this is done, its back to the orbs again and it just repeats.
I tried restoring to factory defaults from the recovery menu, that did nothing, then sometime after I noticed I actually cant turn the device off any more, if I hold the power button it turns off, but reboots instantly. I tried going through the steps again, but no luck, the only change was that I didn't have the error at the end, and the first Optimising dialogue said 104 apps, not 99, but all the rest afterwards have said 99.
I'm not sure what do do from here, any advice?
Here's my cmd output:
Code:
## First attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot bootloader
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
...
(bootloader) ability is 1
(bootloader) RUU_frame_buffer_enable_flag=0
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Unlock device successfully!
OKAY [ 23.489s]
finished. total time: 23.489s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot nexus9\inject.img
downloading 'boot.img'...
OKAY [ 0.783s]
booting...
OKAY [ 0.156s]
finished. total time: 0.939s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot nexus9\patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.541s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.798s]
finished. total time: 1.339s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
## Second attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
< waiting for device >
...
(bootloader) ability is 1
(bootloader) Device stete is unlock already
OKAY [ 0.141s]
finished. total time: 0.141s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
downloading 'boot.img'...
OKAY [ 0.749s]
booting...
OKAY [ 0.158s]
finished. total time: 0.908s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.539s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.787s]
finished. total time: 1.326s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot reboot
rebooting...
finished. total time: 0.066s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Try returning to stock and trying again. See method 2 of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
That root method is for the old 5.0 Android; it doesn't work anymore with 5.1.1. Go back to stock using jd1639's link, then run Chainfire's Auto-root and you should be good to go. Link is here: https://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip. There's supposedly an update coming in the next week or so to fix the stagefright vulnerability, make sure you do NOT take it in case it does weird things that could cause you to lose root.
(I know it says Volantis and not flounder but the Nexus 9 is known by both names, just to keep things confusing)
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
TheShryke said:
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
Click to expand...
Click to collapse
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
bynarie said:
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
Click to expand...
Click to collapse
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
bynarie said:
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
Click to expand...
Click to collapse
Just take notice that this will wipe everything on your device, so make a backup first.
dictionary said:
Just take notice that this will wipe everything on your device, so make a backup first.
Click to expand...
Click to collapse
cobyman7035 said:
...
Click to expand...
Click to collapse
Yes, my apologies... I forgot to mention this. You will definitely want to pull any pictures or other files you might want to keep from the /sdcard partition. Or anything else because ALL DATA WILL BE WIPED.
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU? do i need to wipe dalvik or cache?
im installing that huge android SDK studio setup into my laptop for prep
cobyman7035 said:
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU?
Click to expand...
Click to collapse
Here > https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
ok i just unlocked my bootloader....so i rebooted in android again...i have to go back and enable usb debugging and developers again?
---------- Post added at 10:16 AM ---------- Previous post was at 10:01 AM ----------
when i typ adb reboot fastboot. ...my n9 reboots into the android o.s and NOT into fastboot?
---------- Post added at 10:23 AM ---------- Previous post was at 10:16 AM ----------
nm i installed and flash twrp and SU! i didn't do a dalvik cache wipe...is that ok? booting in android o/s again to setup!
my next step is to go unencrypted... don't wanna setup too many apps cuz its just gonna be all deleted again
I'm going to upgrade it to MR, but i can't have it root after try whole the night, i tried
AndroPlusKernel v4 and v10 but none of them did the work, what i'm following is successfully verified by a few people, can some help on this?
I'm a HK version with '28.0.A.8.260' firmware.
Here is my command output.
#[email protected]:/ $ su
/system/bin/sh: su: not found
#[email protected]:/ $ reboot bootloader
#fastboot devices
CB5A26CPBC fastboot
#fastboot oem unlock **************
...
FAILED (remote: Device is already rooted)
finished. total time: 0.008s
# fastboot flash boot boot.img
sending 'boot' (40420 KB)...
OKAY [ 0.996s]
writing 'boot'...
OKAY [ 0.330s]
finished. total time: 1.325s
#fastboot reboot
rebooting...
finished. total time: 0.060s
#adb shell
[email protected]:/ $ su
/system/bin/sh: su: not found
DId you also flash the TWRP recovery from AndroPlus? Also, from there you need to flash the SuperSU 2.46 .zip file.
jelbo said:
DId you also flash the TWRP recovery from AndroPlus? Also, from there you need to flash the SuperSU 2.46 .zip file.
Click to expand...
Click to collapse
Thanks a lot for your help.
No, the link what i'm following tells it's enough by just unlock and flash the boot.img.
I tried flashing TWRP, but i can never boot into recovery mode both by hold the 'Volume -' and 'Power' button or by executing 'adb reboot recovery', the display never light up and will go to normal boot after a while, looks like the flash don't make sense, is it possibly caused by the firmware version? i'm at 28.0.A.8.260.
# fastboot flash recovery ../TWRP-2.8.7.0_adb_shell_only.img
sending 'recovery' (11653 KB)...
OKAY [ 0.315s]
writing 'recovery'...
OKAY [ 0.123s]
finished. total time: 0.438s
# fastboot reboot
rebooting...
finished. total time: 0.052s
[[email protected] Root-img-v10]# adb reboot recovery
get the latest recovery from Androplus' website - the shell only thing was a first attempt
as jelbo writes you need to flash SuperSU
adb reboot recovery is OK if volume up does not work on device normal boot
Wei Xu said:
Thanks a lot for your help.
No, the link what i'm following tells it's enough by just unlock and flash the boot.img.
I tried flashing TWRP, but i can never boot into recovery mode both by hold the 'Volume -' and 'Power' button or by executing 'adb reboot recovery', the display never light up and will go to normal boot after a while, looks like the flash don't make sense, is it possibly caused by the firmware version? i'm at 28.0.A.8.260.
# fastboot flash recovery ../TWRP-2.8.7.0_adb_shell_only.img psending 'recovery' (11653 KB)...
OKAY [ 0.315s]
writing 'recovery'...
OKAY [ 0.123s]
finished. total time: 0.438s
# fastboot reboot
rebooting...
finished. total time: 0.052s
[[email protected] Root-img-v10]# adb reboot recovery
Click to expand...
Click to collapse
Hi,
Don't use the recovery TWRP-2.8.7.0_adb_shell_only.img but use the twrp 2.8.7.0(not)fixed.img. Shut down the tablet
Press and old down the power button when the light become yellow press volume down button the led become orange released the power button and volume down button. The twrp screen must be appear
killdozer56 said:
Hi,
Don't use the recovery TWRP-2.8.7.0_adb_shell_only.img but use the twrp 2.8.7.0(not)fixed.img. Shut down the tablet
Press and old down the power button when the light become yellow press volume down button the led become orange released the power button and volume down button. The twrp screen must be appear
Click to expand...
Click to collapse
Great, this is caused by the recovery.img version, i tried 2 other img in official link, both of them failed,
'(not)fixed' works well.
when i used TWRP to install the MR ROM, it refused to continue with 'could not find 'META-INF/com/google/android/update-binary' like error.
so i unzip the ROM and booted to recovery mode to make a manual flash, but it hangs up for 15 minutes and stills don't finish, is this abnormal? should i wait for it to complete? does it will crash the system if i terminate it forcely?
I had brush CM 12 on an OnePlus One before, looks it's very fast and often finished within 10 mins, what's the matter?
# fastboot flash system system.img
sending 'system' (859570 KB)...
Wei Xu said:
when i used TWRP to install the MR ROM, it refused to continue with 'could not find 'META-INF/com/google/android/update-binary' like error.
so i unzip the ROM and booted to recovery mode to make a manual flash, but it hangs up for 15 minutes and stills don't finish, is this abnormal? should i wait for it to complete? does it will crash the system if i terminate it forcely?
Click to expand...
Click to collapse
What is this MR ROM you speak of? There is no such thing as MR ROM for the Z4 Tablet. Afaik we only have AOSP 5.02, 5.1.1, 6.0 and the latest stock 5.0.2 ROM. Flashing anything else would likely end up in it hanging, like you experience.
With the current state of ROMs, I advice to just flash the official stock ROM, benefit from it's stability and full copmpatibility, SuperSU it, try Xposed (v79, sdk21, arm64) and freeze/uninstall system bloatware with an app like Titanium Backup.
jelbo said:
What is this MR ROM you speak of? There is no such thing as MR ROM for the Z4 Tablet. Afaik we only have AOSP 5.02, 5.1.1, 6.0 and the latest stock 5.0.2 ROM. Flashing anything else would likely end up in it hanging, like you experience.
With the current state of ROMs, I advice to just flash the official stock ROM, benefit from it's stability and full copmpatibility, SuperSU it, try Xposed (v79, sdk21, arm64) and freeze/uninstall system bloatware with an app like Titanium Backup.
Click to expand...
Click to collapse
OK, MR is MarshMallow, i did see someone has made an AOSP ROM works and i'm eagerly to have a try, i terminate it forcely and now it hangs on 'starting apps', looks it's already upgraded because i lose
adb connection, anyway to rescue this?
Everytime I type the command 'fastboot oem unlock', the screen says;
OKAY [ 0.002s]
finished. total time: 0.002s
but then when I want to flash a recovery it says;
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.498s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)<<< Why does this happen? -_-
finished. total time: 0.501s
Anybody has a solution for this?
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
seems like you locked the bootloader while you are rooted...iam stack on same step too...
Exodusche said:
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
Click to expand...
Click to collapse
But everything else works. And yeah, I did try flashing the stock recovery too
Fastboot oem unlock>fastboot reboot>doesn't ask about wiping
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Ubuntu_noobi said:
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Click to expand...
Click to collapse
Not necessarly.
If it 's device unlock-true , you're OK. If not...
Hi all,
I have an LG G5 H850. I'm trying to install TWRP using ADB. I've had it previously and it worked fine. I'm pretty sure the bootloader is unlocked. Anyway, when I do "fastboot flash recovery twrp-3.1.1.1-0-h850.img" I get the following output:
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.345s]
finished. total time: 0.781s
To me, that looks as though thats worked fine. Now when I try fastboot boot twrp-3.1.1.1-0-h850.img I get the following:
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.456s
Has anyone got any ideas on this?
Same here
I am having the same problem, please help
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
lywyn said:
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
Click to expand...
Click to collapse
Don't happen to know where I could get a rom that it would work with do you?
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Barsbeh said:
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Click to expand...
Click to collapse
That is the required way of doing it. You have to boot into recovery after flashing the recovery or it gets reset.
Hi,
Having a similar problem since trying to update my ROM ... and the Magisk install failed. Now I can only get to fastboot, can't get to recovery. And, tried this,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-h830.img
target reported max download size of 536870912 bytes
sending 'recovery' (18644 KB)...
OKAY [ 0.439s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.461s
Help!?! ... and thanks!
I tried to install lineage OS 17.1 on a Moto-Z with Android 6.0.1, and failed.
Here is one error I'd like to solve - this command:
fastboot flash recovery twrp-3.3.1-0-griffin.img
Results in:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20536 KB) OKAY [ 0.443s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.481s]
Finished. Total time: 0.932s
twrp-3.3.1-0-griffin.img is the lastest image, from here.
The same error appears when I try to flash the lineage recovery:
fastboot flash recovery lineage-17.1-20201211-recovery-griffin.img
So what is wrong here?
I've been flashing a Moto e5 Plus today, and the ADB messages were the same, except without the "has slot" line. I think they are standard.
I also had trouble getting TWRP to "stick". What ended up working was booting into the bootloader, flashing TWRP and instead of rebooting I selected "recovery" with the volume buttons.
The TWRP site says this in its instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
but holding Power + Volume Up after reboot didn't seem to work for me.
mfs-ness said:
What ended up working was booting into the bootloader, flashing TWRP ...
Click to expand...
Click to collapse
How did you flash TWRP - from the bootloader?
Or from the PC via fastboot - in which case there is always the above error, not just with TWRP images.
This is how I flashed TWRP from a linux desktop:
Code:
./adb -d reboot bootloader
sudo ./fastboot flash recovery ~/Downloads/twrp-3.4.0-0-hannah.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (19798 KB) OKAY [ 0.795s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.552s]
Finished. Total time: 1.352s
The first line results in the screen with the open-chested android. Then I ran the fastboot command. Then I selected "recovery mode" on the phone.
mfs-ness said:
This is how I flashed TWRP from a linux desktop:
...
Click to expand...
Click to collapse
Not different from my technique.
So we seem to have different conditions on the phone, firmware, whatever.