I was running Resurrection Remix nougat with TWRP 3.1.1.0 and decided to flash the latest nightly of Lineage 14.1. I was surprised to find that LOS replaced TWRP with its own recovery. Every other custom rom I have ever flashed on any device has left TWRP in place.
Every time I re-installed TWRP via fastboot the tablet bootlooped into TWRP and I couldn't be bothered with fixing it via the TWRP terminal. I finally gave up and used TWRP to flash CrDroid, and all is working as I would have expected. Which is a little strange, since CrDroid is based on LOS.
So why does the official LOS not leave TWRP alone?
channeledbymodem said:
So why does the official LOS not leave TWRP alone?
Click to expand...
Click to collapse
Because official LOS nightlies contain lineage (former CyanogenMod) recovery.
Recovery is built-in kernel. So by changing kernel to LOS you remove TWRP.
All latest custom firmware kernels had TWRP integrated by the developers. But official LOS is not the case and it won't be.
Rootk1t said:
Because official LOS nightlies contain lineage (former CyanogenMod) recovery.
Recovery is built-in kernel. So by changing kernel to LOS you remove TWRP.
All latest custom firmware kernels had TWRP integrated by the developers. But official LOS is not the case and it won't be.
Click to expand...
Click to collapse
Why do you think they made that decision? TWRP is much more useful than the LOS recovery.
channeledbymodem said:
Why do you think they made that decision? TWRP is much more useful than the LOS recovery.
Click to expand...
Click to collapse
Well, their product recovery. They are not obliged to integrate (promote) another one.
Also maybe it is linked with rights for usage of TWRP.
Rootk1t said:
Well, their product recovery. They are not obliged to integrate (promote) another one.
Also maybe it is linked with rights for usage of TWRP.
Click to expand...
Click to collapse
Well, I have to say, as big a fan as I was of CyanogenMod, this will keep me from using official Lineage for any of my devices until they leave TWRP in place, like every other custom rom I've ever used.
channeledbymodem said:
until they leave TWRP in place, like every other custom rom I've ever used.
Click to expand...
Click to collapse
Official nightlies never had TWRP, and i presume will never have.
I see no point at the moment in the usage of official ones, cause custom have more features and patches integrated, which will never be in official ones.
Rootk1t said:
Official nightlies never had TWRP, and i presume will never have.
I see no point at the moment in the usage of official ones, cause custom have more features and patches integrated, which will never be in official ones.
Click to expand...
Click to collapse
Well, that's my point. I don't expect a custom ROM to include a recovery. For some time, all of them have been flashed with TWRP so I see no point in replacing TWRP with something less useful.
I have another device for which there are only a few custom ROMs and they are all lineage based. None of them will charge the tablet correctly. It is indicated as plugged in but not charging. I had to revert to stock.
I'm pretty much over Lineage myself.
I found the recovery unusable - I could never get it to load anything from the sdcard and when I managed to get gapps nano loaded from the internal storage the install failed with "not enough space on system' (Lineage 14.1, Xperia Tablet Z).
bassmanitram said:
I found the recovery unusable - I could never get it to load anything from the sdcard and when I managed to get gapps nano loaded from the internal storage the install failed with "not enough space on system' (Lineage 14.1, Xperia Tablet Z).
Click to expand...
Click to collapse
you're right. Replace it with TWRP.
Related
Hi,
hopefully someone could point me in the right direction.
So I have a Kate device.
It's been unofficially unlocked ( requested code in February, still haven't received anything ), however up until this point everything was working fine.
The problem is I can't dirty update over LOS nightlies for some reason ( both via updater and manual TWRP flash ) - stuck at boot animation ( 30+ mins ) Clean flash works fine. Problem started somewhere in March builds.
I have updated TWRP and I believe I have the proper FW, since everything works when doing a clean flash.
I'm not using any custom kernels, mods or anything like that, just SU addon + opengapps.
Any ideas?
Thanks
No idea...clean flash works...which is strange...have you tried other roms too?
For official unlock, you waited too long for code LOL. I never received any code and im officialy unlocked. You should write to them so they can manually give you permission.
You should flash via EDL latest china dev and then unlock it...
Denis:) said:
No idea...clean flash works...which is strange...have you tried other roms too?
For official unlock, you waited too long for code LOL. I never received any code and im officialy unlocked. You should write to them so they can manually give you permission.
You should flash via EDL latest china dev and then unlock it...
Click to expand...
Click to collapse
Haven't tried others, I enjoy using LOS
As far as unlock goes, unless this is actually the thing that is causing the issue, I'm also just fine with unofficial.
feiks said:
Haven't tried others, I enjoy using LOS
As far as unlock goes, unless this is actually the thing that is causing the issue, I'm also just fine with unofficial.
Click to expand...
Click to collapse
I think it is the su addon.
after u dirty flash, do not install su addon, because your device need to build up dalvik cache.
so after dirty flashing, when the device successfully boot up, reboot to recovery again and flash su arm64 addon.
Thanks for suggestion, but unfortunately it also does not help.
The only thing I haven't tried is not installing su addon at all ( when doing clean flash ), but that kind of defeats the point of having custom rom in my opinion.
Also I couldn't find any references to this ( apart from migration issues back when CM became LOS ) on LOS thread, everything seems to be working fine for everyone else, regardless of unlock or su.
Are there any other partitions that should be wiped upon clean install, besides system/data/cache/dalvik?
Simoom Sadik said:
I think it is the su addon.
after u dirty flash, do not install su addon, because your device need to build up dalvik cache.
so after dirty flashing, when the device successfully boot up, reboot to recovery again and flash su arm64 addon.
Click to expand...
Click to collapse
I don't use LOS , but what I've heard is the latest nightly has made changes to updater app so clean flash ROM and try next build & one more option is to use LOS updater from play store , make sure you have latest TWRP & it's setup after installing ROM
Sent from my Redmi Note 3 using Tapatalk
Use only ZCX twrp.
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Noter2017 said:
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Click to expand...
Click to collapse
I tried the treble versions of magisk too. Even tried the beta. No luck.
Figured it out
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
So it was a problem with the treble implementation of the ROM. I was installing treble ROMs using the stock TWRP/Redwolf recovery. These recoveries install the ROM but don't work or make the /vendor partition. This has led many people to believe that there is something wrong with their phone. Anyway, flashing a custom treble recovery did the job. Although not each one of them is perfect, TWRP_3.2.1-7_mido-treble by @NFound is the best one.
Solved every problem faced by me till now. Custom Magisk for Redmi Note 4 is available and works like a charm.
Magisk-v16.3-mido-treble
It seems no one faced this issue before, anyway this would help the new comers like me.
Thanks.
Couldn't get
I am using RR ROM Oreo since 2 weeks and finding ways to root it
But can't find any way to do it
Addonsu is not working
Treble magisk is not working
I need to change my recovery
But the ROM ended up encrypting my internal storage
So should I clean data to format and remove encryption
Or I can directly install a new recovery ?
Format then wipe everything. With a help of a pc or a laptop download a treble supported recovery or the Firefox recovery(search it).Then try again.
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
are you using the minimal adb to flash the recovery not flashtools like the root thread says to coz if your using flashtool thats y ur in bootloop im on the uk customiseed and have no issues
buzzinkeegs said:
are you using the minimal adb to flash the recovery not flashtools like the root thread says to coz if your using flashtool thats y ur in bootloop im on the uk customiseed and have no issues
Click to expand...
Click to collapse
Which root thread are you referring to? I've seen quite a few and none of the ones I followed mentioned minimal adb. I'm using Flashtool on windows to flash the ROM and I'm using linux for fastboot, since it doesn't work on Windows for some reason and it's too much effort to troubleshoot when it works fine on Linux.
RNZL3R said:
Which root thread are you referring to? I've seen quite a few and none of the ones I followed mentioned minimal adb. I'm using Flashtool on windows to flash the ROM and I'm using linux for fastboot, since it doesn't work on Windows for some reason and it's too much effort to troubleshoot when it works fine on Linux.
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
that 1
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
While flashing the ROM through flashtool, deselect option FOTA-KERNEL, this will keep twrp as your recovery.
Also you can use X-GEN Rom which is based on latest stock rom to flash it from TWRP instead of flashtool
Should I flash TWRP now and then re-flash the UK ROM?
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
while flashing stockrom, uncheck FOTAKERNEL.sin in FLASHTOOL FIRMWARE SELECTION PANEL.
this way you can keep the twrp intact
Hi!
I really would like to try some custom roms, especially without Google Apps
My phone is a SM-G800H, Android 6.0.1 (dual sim)
I would like to try Lineageos, but it seems my device is NOT listed on their wiki... should I use some unofficial version?
I got some issues with fastboot command: it doesn't recognize my device (while adb is ok).
Installing a custom rom will be easier with a rooted device?
Thank you!!
MoonRotation said:
Hi!
I really would like to try some custom roms, especially without Google Apps
My phone is a SM-G800H, Android 6.0.1 (dual sim)
I would like to try Lineageos, but it seems my device is NOT listed on their wiki... should I use some unofficial version?
I got some issues with fastboot command: it doesn't recognize my device (while adb is ok).
Installing a custom rom will be easier with a rooted device?
Thank you!!
Click to expand...
Click to collapse
Fastboot isn't for Samsung. You have Odin for it and twrp. Flash an unofficial lineage rom with gapps and you should be good to go
joluke said:
Fastboot isn't for Samsung. You have Odin for it and twrp. Flash an unofficial lineage rom with gapps and you should be good to go
Click to expand...
Click to collapse
Hi,
I think this should be fine.
I have some doubt about TWRP. If I enter in recovery mode, I already have menu like "wipe data". So why is TWRP necessary?
It is also unclear if TWRP is meant as recovery partition (instead of the stock one) or a normal apps which needs root privileges to work.
Can you just explain me that?
Thank you again!
MoonRotation said:
Hi,
I think this should be fine.
I have some doubt about TWRP. If I enter in recovery mode, I already have menu like "wipe data". So why is TWRP necessary?
It is also unclear if TWRP is meant as recovery partition (instead of the stock one) or a normal apps which needs root privileges to work.
Can you just explain me that?
Thank you again!
Click to expand...
Click to collapse
Twrp is a custom recovery. You can't install anything with the stock recovery
Have unlocked bootloader and installed TWRP 3.7.0_9-0
Have tried to flash Pixel Experience 11, Pixel Experience 12 and Arrow v11
All of them just hang at first boot, with the animated logo. I left each for over half an hour.
Have wiped everything I can think to wipe.
Is there something obvious I'm failing to do ? Lineage 18.1-20210620 was on the device before I started.
Edit: I can re-install Lineage 18.1 but nothing newer. Do I need to do something to enable newer ROM flashes?
HarpingOn said:
Have unlocked bootloader and installed TWRP 3.7.0_9-0
Have tried to flash Pixel Experience 11, Pixel Experience 12 and Arrow v11
All of them just hang at first boot, with the animated logo. I left each for over half an hour.
Have wiped everything I can think to wipe.
Is there something obvious I'm failing to do ? Lineage 18.1-20210620 was on the device before I started.
Edit: I can re-install Lineage 18.1 but nothing newer. Do I need to do something to enable newer ROM flashes?
Click to expand...
Click to collapse
To check:
TWRP/O.F
wipe/format data type yes
reboot Twrp/O.F
Flash latest firmware (if necessary).
Flash the rom as instructed by the OP.
HarpingOn said:
Have unlocked bootloader and installed TWRP 3.7.0_9-0
Have tried to flash Pixel Experience 11, Pixel Experience 12 and Arrow v11
All of them just hang at first boot, with the animated logo. I left each for over half an hour.
Have wiped everything I can think to wipe.
Is there something obvious I'm failing to do ? Lineage 18.1-20210620 was on the device before I started.
Edit: I can re-install Lineage 18.1 but nothing newer. Do I need to do something to enable newer ROM flashes?
Click to expand...
Click to collapse
Use TWRP by REIGNZ based on A12 system_ext. You can find it my POCO F1 Ultimate Collection & Guides along with Guides for clean installation.
P.S: Near the link of twrp by reign you will also find a link for the current bugs/issues and workaround for them.