I was so excited when I successfuly unlocked my bootloader on LG US997 running Oreo (US99721d with android security patch Dec 1 2018). The first thing I tried was TWRP. I downloaded the latest TWRP image from eliminater74's page. tobe more specific this one https://sourceforge.net/projects/twrp-recovery/files/US997/
I executed adb to flash twrp image. the logs are here
Code:
C:\Users\XXXX\Downloads\fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Users\XXXX\Downloads\fastboot>fastboot flash recovery twrp.img
Sending 'recovery' (27800 KB) OKAY [ 1.174s]
Writing 'recovery' OKAY [ 0.236s]
Finished. Total time: 1.472s
C:\Users\XXXX\Downloads\fastboot>fastboot reboot
Rebooting
Finished. Total time: 0.016s
C:\Users\XXXX\Downloads\fastboot>
Everything looks fine. the issue starts when I go to recovery using the key combination. The device asks to wipe data twice, what is exactly what is supposed to happen, but instead of starting recovery. It erases all my data!
In other words, no TWRP image is installed. I jut lost plenty of data on my device because looks like recovery is untouched. I tried the other releases but none of them works.
What am I doing wrong? I want to install some mod on my G6 but without root and TWRP I can't
For TWRP to "stick" you must 1st boot into TWRP and not boot back into Android until you flash SuperSU or Magisk
Related
Everytime I install TWRP and boot into it. It shows Zero internal storage and when I reboot it outlines there isnt an OS installed.
The system OS isnt wiped (although I thought that the first 50 times). When I enter fastboot again TWRP inst installed.
No idea what going on... tried latest and previous TWRP files.
thanks in advance
Heres the Log
-------------
Z:\NewNexus7Root\platform-tools>adb reboot bootloader
Z:\NewNexus7Root\platform-tools>fastboot flash recovery twrp-2.8.7.0-flo.img
sending 'recovery' (8956 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.271s]
finished. total time: 0.564s
Z:\NewNexus7Root\platform-tools>adb reboot recovery
error: device not found
error: device not found
Got it working after I found the MultiRom fix on this site.
Seems I had one of those unique "locked down" Nexus's 2013; mines from Amazon.
Hey there,
So yesturday I wiped/factory reset my phone and installed a new ROM, but when I flashed the ROM zip file through the TWRP recovery menu, I forgot to flash TWRP ^^'...
So right after the flash, I went to FASTBOOT mode and tried to boot into twrp image to, then, flash the twrp's zip installer :
Code:
MacBook-Pro:Downloads User$ fastboot boot twrp-3.2.1-0-tissot.img
downloading 'boot.img'...
OKAY [ 0.891s]
booting...
OKAY [ 0.627s]
finished. total time: 1.518s
But when I do so, my phone reboot just normally. No Twrp.
The OEM is unlocked and the ROM is stock (flashed with the official xiaomi images).
newbie to a oneplus 2. I acquired this phone locked and with OOS 3.61. been doing some searches but apparantly not enough and not getting very far.
Actions performed so far
set oem unlocking in dev-options to enabled.
rebooted to fastboot
"fastboot oem unlock" was succesful and rebooted and completed setup
rebooted to fastboot
from fastboot installed twrp "fastboot flash recovery recovery.img" (recovery.img being twrp-3.2.1-0-oneplus2.img)
results:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.934s
:end results
then boot directely to twrp with "fastboot boot recovery.img"
performed nandroid backup.
rebooted device and tried booting to recovery but still has oem recovery.
any ideas? would like twrp native not via fastboot only.
thanks in advance.
Update solved:
booted twrp from .img file and installed su.zip and installed twrp.apk and used the app to install twrp. works now. not sure why it was saying it was working from from fastboot and writing but hope this helps someone else.
TWRP 3.2.1 doesn't work properly yet on the OnePlus 2 for some reason. I can assume that you wanted root so I can give you 2 options:
1) If you want to stay on stock OxygenOS 3.6.1 or a custom rom Nougat or lower, then flash TWRP 3.1.1
2) If you want to have an Oreo rom, then you have to get your hands on the unofficial TWRP from anupritaisno1. The download link for that on his forum doesn't work so if you want, I can link my Google Drive.
This is my first time trying to root my android and I am having the same problem with my oneplus 2 3.6.1 OOS. I have successfully unlocked oem but can't seem to flash twrp.
I have downloaded twrp 3.2.1 on my desktop and renamed it to "recovery".
I used the same command "fastboot flash recovery recovery.img" but it just says "error: cannot open 'recovery.img' "
Can you please tell me how you managed to install twrp and root your android?
you need to downgrade the OOS to ver 3.002 or 3.1, then you re-unlock the bootloader then flash twrp recovery.
Finally flash your phone with root of your liking.
rp201 said:
newbie to a oneplus 2. I acquired this phone locked and with OOS 3.61. been doing some searches but apparantly not enough and not getting very far.
Actions performed so far
set oem unlocking in dev-options to enabled.
rebooted to fastboot
"fastboot oem unlock" was succesful and rebooted and completed setup
rebooted to fastboot
from fastboot installed twrp "fastboot flash recovery recovery.img" (recovery.img being twrp-3.2.1-0-oneplus2.img)
results:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.934s
:end results
then boot directely to twrp with "fastboot boot recovery.img"
performed nandroid backup.
rebooted device and tried booting to recovery but still has oem recovery.
any ideas? would like twrp native not via fastboot only.
thanks in advance.
Update solved:
booted twrp from .img file and installed su.zip and installed twrp.apk and used the app to install twrp. works now. not sure why it was saying it was working from from fastboot and writing but hope this helps someone else.
Click to expand...
Click to collapse
dear,
do you mind sharing the twrp.img you used?
Thank you
Android stock 8.1 / g5 plus 32/2.
help, unlock the bootloader.
Now when I install the recovery twrp (latest version) I get the following error:
sending ‘recovery’ (10236 KB)…
OKAY [ 0.379s]
writing ‘recovery’…
(bootloader) Image not signed or corrupt
OKAY [ 0.239s]
finished. total time: 0.634s
after that I try to enter the twrp and if he lets me in. The problem is that I enter the system and everything is fine, but when I restart the recovery it does not appear anymore and I skip an android logo with a sign of admiration (without commands).
And I have to install the recovery twrp again, so on.
someone has an idea what could be ..
After you not into TWRP the first time, restart into recovery again before rebooting into system. That should ensure that it stays.
If it doesn't, you may need to use a zip that disables dm-verity.
NZedPred said:
After you not into TWRP the first time, restart into recovery again before rebooting into system. That should ensure that it stays.
If it doesn't, you may need to use a zip that disables dm-verity.
Click to expand...
Click to collapse
Solved, thank you :good:
Hi all, I have a Sony Xperia X Compact which still worked perfectly fine.
Today I tried to install Lineage OS but had trouble making it work properly - see the thread.
I managed once to successfully install TWRP but then it got removed during the formatting. I tried many times to reinstall it but it didn't work:
$fastboot flash recovery twrp-3.7.img Sending 'recovery' (27424 KB)
OKAY [ 0.863s] Writing 'recovery'
OKAY [ 0.340s] Finished. Total time: 1.214s
$ fastboot getvar recovery
recovery:
Finished. Total time: 0.002s
Click to expand...
Click to collapse
Strange... So instead, I boot to recovery through the fastboot. It always worked, I've done it 10+ times today
fastboot boot twrp-3.7.img
Click to expand...
Click to collapse
But after my last install of Lineage OS, I can't boot anymore to TWRP and get stuck on a black screen. I tried other versions of TWRP and it's the same result.
Now I have
- a buggy Lineage OS which crashes while accepting the Google terms, which means I cannot activate the debugger mode and cannot use adb
- a buggy TWRP which doesn't load
-----
Solution: install the Sony flash tool and flash the original firmware.