- computer: ubuntu 23.10
- device: asus X00PD, can only root it from the computer (no install from usb option available on the device).
On the computer, I ran:
fastboot flash recovery /home/alice/TWRP/twrp.img
it returned:
Sending 'recovery' (50272 KB) OKAY [ 1.596s] Writing 'recovery' OKAY [ 0.464s] Finished. Total time: 2.068s
I thought I have flashed TWRP to the device’s recovery partition.
However, after booting to recovery, I don’t see TWRP, I see the stock Android recovery.
Unless the recovery partition can support both Android recovery and TWRP at the same time I haven’t installed TWRP.
How do I install TWRP?
Have a look on xdaforums for your device, there will be guides. With the Samsung for example you have to enable bootloader flashing in existing rom developer options otherwise it will overwrite on a fresh boot. Gxda is a trove of info though
Look at the steps in https://wiki.lineageos.org/devices/X00P/install/ for more details.
It looks like the native OS will flashy the original recovery partition back if you try to boot Android without flashing a custom. ROM.
It looks like the native OS will flash the original recovery partition back if you try to boot Android without flashing a custom. ROM.
so if I cannot install lineage on my device (package no longer maintained) and I’m stuck with the native OS, that means I’m also stuck with the original recovery partition and cannot install TWRP?
You can boot TWRP and mess with the system image from there. If you
fastboot boot your-recovery-image.imginstead offastboot flash...you should be able to load TWRP once without ever writing something to disk. From there, you may be able to prevent the re-flashing of the original recovery, and then perhaps flash TWRP permanently. You’ll have to look around and figure out what’s possible, but there’s still some hope for you.If your native OS is maintained longer than Lineage, it may be wise to stick with that. You can also look got alternatives to LineageOS. For example, my device only has partial Lineage support, with community builds on XDA as the only source for ROMs, but crDroid has maintained images available and PixelOS even has an Android 14 ROM I can try.
For your phone, crDroid seems to be released last, almost exactly a year ago, but Asus updated it a month ago. I would stick with Asus’ ROM in this case, and focus on sabotaging the recovery re-flashing.
You could also try to just… build LineageOS and see what happens. Once initial porting is done for an Android version, there’s a good chance very little device specific features will break until the next major version comes out. If you have access to get a Linux server with at least 16GB of RAM and about 50-100GB of free space (Windows may work through WSL but no promises), you can build the entire ROM yourself.
Oh that’s interesting. Never seen that before.
The same thing can be seen on some MIUI device that i used before. Need to quickly press the recovery keys combination to enter TWRP. Entering recovery command from terminal would directly boot into OS.
Removed by mod
Removed by mod
You need to unlock your bootloader.
-
Enable USB debugging in the developer options;
-
Reboot the phone in fastboot;
-
Connect the phone to your PC;
-
Run the commands bellow, line by line:
touch key.txt fastboot oem get_unlock_key key.txt fastboot reboot-bootloader-
It should show a warning that the bootloader is unlocked;
-
Reboot in fastboot and install TWRP again.
-
Its been a while since i tinkered around but i think firstly you can try directly booting into twrp recovery and see if that’s working.
For some phones overwriting the recovery straight away doesn’t work they will just let you temporarily run custom recoveries.
If that’s the case then you can figure out for your specific phone how to overwrite the stock recovery permanently.
Again i could be completely wrong but you can give this flow a try.
