It is any way to install TWRP without overwriting Android's bootloader (LineageOS changes recovery to LineageOS recovery)
lineage did this to me also, without my help !
i'd love to get back to twrp, but now all i have is a very basic device and no option to boot into bootloader mode to do a reinstall
frustrating ++ as it was my alarm clock and now it's essentially a brick
Related
Hi guys
So, i've been at this for most part of today. Looked all around and tried everything i found, and im still clueless.
I've done this steps twice, with the second time being more step-by-step instead of bulk actions, always starting from miui 8 global stable rom:
1 - flash twrp via fastboot with twrp-installer.bat for redmi 3s
2 - reboot into stock bootloader with power + vol+ and choose recovery to boot into twrp
3 - in twrp, slide to modify system and disable dm-verity in advanced options
4 - reboot into stock rom and power off phone
5 - boot into twrp in the same way as in step 2
6 - clean dalvik, system, data and cache partitions
7 - flash lineageos 13 from lsferreira and gapps
8 - reboot into custom rom and power off phone
9 - try to boot into twrp in the same way as in step 2 - NOK, just gets stuck at the MI logo
10 - reboot into custom rom and reboot into recovery from the power menu, twrp OK
11 - flash something, like goodix fix or xposed
12 - reboot into custom rom, verify installed packages OK
From this point on, i can not get back into recovery, either stock bootloader or twrp. Tried from the power menu, vol+ button, reflashing twrp through fastboot and adb, booting directly from recovery.img from fastboot and even reflashing stock recovery. The rom always boots fine and so does fastboot.
I saw some posts saying to hold both vol- and vol+, but this just seems to boot the phone in some deep recovery mode, judging by the drivers that the PC tries to install (EDL maybe?)
The only way i can get the bootloader/recovery (the vol+ chinese menu) back is to reflash stock miui 8 through miflash tool, which gets me to the starting line.
Will anyone be kind enough to point me to the blatantly obvious mistake im making?
I think I found a solution. I flashed a different twrp recovery (the one provided by fedosis, by cofface) instead of the one linked in every how-to in both this and miui's forums.
Now i can boot to recovery everytime.
i install twrp with autorec and after that, flash lineage os. at first, lineage os doesnt working, just blinking lg logo and black screen. i can get twrp menu and do recovery to old stock rom. but after that i get throught this problem and install lineage os.
but now, i cant open twrp menu. it says secure booting error. i have to open cuz i didnt flash gapps yet.
also, device couldnt install supersu after installing lineage os, because it needs twrp menu or play store.( i downloaded apk, but it didnt work.) now system has not root access. cant install supersu because cant open twrp menu. and there is root access menu under development settings, but doesnt look like it changing anything at all. also root checker apps says no root.
i think maybe i should have to reflash twrp. i can plug this device to my mac and use adb commands. but
reboot bootloader -->goes download mode(firmware update screen with %0 download) and fastboot commands dont work at this screen
reboot fastboot ---> nothing happens, reboot system and open lineage os.
reboot download --->nothing happens again. only reboots system.
i need root access and fix at least twrp screen for flash gapps. and that is the situation. i didnt know what can i do at this point? can you help me?
Its happen to me. I only use SRK Tool to enter in download mode and fix the phone.
What i did stepwise -
1. Unlocked bootloader of my g5 plus
2. Flashed twrp-3.2.3-1-potter.img via adb
3. Booted to TWRP
4. Wiped to decrypt phone
5*. Booted to system to enable usb debugging, enabled it . Transfered magisk , arrow 9.0 rom , gapps to my internal storage of phone
6. Open bootloader , selected recovery mode and got nothing except error "No Command"
So i cannot flashed anything what i wanted to
What and Where i made the mistake ?
How can i get TWRP back?
Thanks all in advance
Solution
1. Flashed magisk17.1 and lazyflasher
2. Updated magisk manager and got root
3. Installed official TWRP app , granted root and downloaded same TWRP.img from which i decrypted the phone.
4. Flashed twrp fom the official twrp app.
5. No irritating No Command error again
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
echo92 said:
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
Click to expand...
Click to collapse
Thanks for your answer sir , but it didn't work
What I did again
1.I flashed same twrp from adb
2. Booted to recovery , but this time TWRP didn't asked password and I could see internal storage in twrp but not on my PC
3*.However I took the whole backup of stock nougat and cross check from restore option as there was backup in TWRP folder. I wanted copy that backup to my PC . But PC cannot detect my phone while in recovery
4. So booted to system and my PC detected my phone but there was no backup in TWRP folder.( But around 6gb(backup) of storage was used but I couldn't see it)
5.Again booted to recovery mode but "No Command" showed again .
I tried several times but I keep losing TWRP and couldn't see the backup which I make
Same problem. Resolved by flashing alternately several times twrp-3.2.1-0-potter.img and twrp-3.2.1-1-potter_persist.img and finally updated twrp-3.2.3-1-potter.img
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
NZedPred said:
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
Click to expand...
Click to collapse
I flashed magisk 17.1 and lazyflasher ,i got magisk and root but cannot install modules may be becoz of f2fs bug . By the way i lost twrp after booting to system again and No command still present in recovery mode . I am frustrated Moto software is just pain in head :silly:
Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore
Hi - I am trying to update my OP6T to OOS v11.1.2.2 and keep root.
I patched my boot.bin file, and was attempting to boot the phone into TWRP in fastboot to create a backup before proceeding.
However, when I try to boot into TWRP using fastboot boot twrp-3.6.2_9-0-fajita.img, I always end up in Crashdump mode.
Is there a way for me to fix it?
Thanks,
¿GJ?
OK ... I was able to boot into TWRP v3.6.2 and create a phone backup after I swapped slots and then pulled some shenanigans. I doubt that the backup is really usable, though, based on what I needed to do to create it.
So, this appears to be my current configuration:
I'm currently on the previous version of OOS 11
I'm rooted with Magisk v25.1
One slot bootloops into TWRP
The other slot boots up into OOS 11 fine, but can't boot into TWRP - even when booting into a TWRP image through fastboot mode.
How can I clean this up? And, how can I upgrade to OOS v11.1.2.2, keep Magisk root, and not lose any data in the process?
Do you have a Android 12 Custom Rom installed