TWRP 3.5.0 Released
TWRP 3.5.0 is out now for most currently supported devices.
twrp.me
I don't know if essential needs different build than the official release, hoping someone with a spare essential can test it out.
Main things I'm hoping is fixed is encryption on A10+ and touchscreen issues.
If you're not familiar, encryption is/was broken on all(?) android 10+ twrp, so you either lived with encryption on but no way to make/restore backups, or leave your install unencrypted.
Touch screen never worked out of the gate on the last twrp (for essential's version at least) and first time installers always got stuck on this part.
Related
My phone had been working fine for quite some time running praetorians 3.2.1 twrp and the weekly version of AICP 8.1 Last week I tried to flash Bliss 9.0 and everything went wrong. (Note I'm not blaming anyone for this, I know stuff happens when you play with your phone)
After much trial and error I finally got the stock os loaded through erecovery and got praetorians twrp back on. But, now when I flash into twrp and it asks for the password to decrypt data it rejects the password. When I installed the stock os this time it asked for a 6 digit pin instead of the 4 digit pin when I initially setup the phone but twrp won't take either the new one or the old one. I pm'd praetorian but he didn't know what the problem was.
I have a copy of removeencryption.zip which I think I've used in the past but now when I run it, even though it reports sucessfully installed, nothing changes. So now I can't do a nandroid backup of /data, although I can do one of system for all the good that does. I've tried official twrp and the 3.2.3 version referenced in the Bliss rom thread but I've not been able to get to the point I was at prior to last week, with data decrypted. In the blur of activity over the last week I think I tried to install a rom but couldn't because data was encrypted. Does that sound right?
If I'm stuck here that's ok - I've got the stock os rooted with xposed running and my favourite launcher installed. I can live with that on this great phone. But I'd like to get back to where I was before. Is that possible?
encrypted media filesystem will be mostly overwritten or a part of it, if not full (esp the critical start)
low level recovery tools will not recognize the data at all
only long shot is to dd your entire disk content as an image and experiment with it on PC while you enjoy the favorite launcher
What partitions get updated when one does the full update using the full image found in the firmware finder? I saw in one thread (ota update on rooted phone) a mention of flashing both ramdisk and ramdisk_recovery.
I wonder if doing such an update - hopefully with Pie after Saturday, might 'reset' my phone back to where I can decrypt data using praetorians twrp?
I'm still on 47.1.A.5.51 and was having some issues with my phone frequently restarting itself and I tried updating Magisk from 14.3 to 18.0 and TWRP from 3.1.1.0 to 3.2.X.X (can't remember offhand). It seems to have stopped the rebooting issue but now DRM fix doesn't seem to work anymore. I am using the kernel and fix provided by shoey63.
I did consider updating to Pie but it seems that there's still a bunch of bugs and stuff. Also couldn't find a proper step by step guide of what the flash order is for it to not lose userdata.
Help would be much appreciated. I just need to hold on to this device for another couple of months before XZ4.
EDIT: It's Magisk that is causing the problem, updating it makes the rebooting issue disappear. Can't update because the free version of DRM fix isn't updated for the newer versions of Magisk.
EDIT2: To heck with it, I installed the DRM and kernel from Janjan's thread even though my firmware is an older version and everything seems to work. It's on Magisk 17.1 and not the latest 18.0 but as long as it doesn't reboot it's mission accomplished for now. Bonus points because now it passes SafetyNet too.
[SM-G930F]
I flashed LineageOS in early 2018 and I'm still using it, but those updates get sometimes stuck in TWRP.
I had to wait for the battery to ran out (I think force-rebooting isn't save while updating the ROM) etc. On my first install the GApps broke my alarm app (I still haven't repaired it, but my S7 is in daily use), the phone got laggy at some games - and - suddenly the screen froze and the hw buttons were blocked.And my external SD card is now corrupted, too.
But root access is working fine, and LineageOS has some little additional features.
Do you guys can tell me what's better:
Installing those updates anyway and always make tons of Nandroid Backups
OR
Full factory reset, TWRP update, new ROM (like Resurrection Remix OS or similar), ...
What do you think?
SeucheAnemone56 said:
[SM-G930F]
I flashed LineageOS in early 2018 and I'm still using it, but those updates get sometimes stuck in TWRP.
I had to wait for the battery to ran out (I think force-rebooting isn't save while updating the ROM) etc. On my first install the GApps broke my alarm app (I still haven't repaired it, but my S7 is in daily use), the phone got laggy at some games - and - suddenly the screen froze and the hw buttons were blocked.And my external SD card is now corrupted, too.
But root access is working fine, and LineageOS has some little additional features.
Do you guys can tell me what's better:
Installing those updates anyway and always make tons of Nandroid Backups
OR
Full factory reset, TWRP update, new ROM (like Resurrection Remix OS or similar), ...
What do you think?
Click to expand...
Click to collapse
With any custom ROM update you have to decide if you really need the updated part of the ROM. Often if the ROM is working fine for you there is no need to keep updating it. Before i update a ROM i read what bugs the update is fixing and if i don't really need that fix then i don't update.
ROM's such as Lineage are forever updating because so many people are working on it but the official stable version ended with Nougat (7), so now we have unofficial Oreo, which will require lots of tweek's and updates to get rid of all the bugs. Lineage is a good ROM but there are others which are stable clean and don't need updating so often,
Unfortunately, I have a problem. My phone was on the power cord overnight and pulled the latest update (EEA 12.5.5.0 Enhanced). It was then booted into OrangeFox (OrangeFox recovery with OTA support) and waited for my OK. I didn't think anything of it and didn't make a backup either, as I assumed that everything would go smoothly like the last update.
The update then went on, but there was probably an error, because now I have a bootloop (yellow Poco lettering for about 2 seconds). I can't use an old backup because I'm abroad right now and I don't want to lose the apps I've already set up (pandemic, tracking apps, certificates, ...).
Does anyone have a quick trick or the latest full ROM that I can just iron over or any other good quick idea? Change bootloader slot or other options? OrangeRecovery and Fastboot are still accessible. Now I only have ADB/Fastboot on my work laptop, but I still can't list the device with adb devices. I guess I still need to install the Xiaomi driver for it, but that should be the minor issue.
Update: I am currently downloading the different ROM versions (fastboot, recovery and incremental update), just in case they are needed.
OTA for the rom and using ofox? hmm it's not supported unless you will flash stock rom maybe. I don't know much more. Correct me if im wrong.
OTA works very well with orangefox and AICP 16.1...
I have struggled to find good info on backup and restore options. I would like to do a full phone backup directly to my computer. Any advice on the best method to do so? I am on Lineage 19-20220824-microG-Lemonade. It shows there are updates available, however this phone is in daily use so I don't want to risk so update-induced meltdown and would like to be ready with a good backup/recovery setup. I have been "using" seedvault with nextcloud but I don't trust it as it constantly throws errors, and I'm afraid if I were to try to restore from the seedvault backup and it were somehow corrupted I could be worse off than before.
Also, can I take the updates that are offered by the phone (OTA, I think) over the microg build or would I need to do a clean install of the latest microg ROM?
Thanks.
If anyone comes here, TWRP official doesn't work, but this does:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
After getting a backup to my PC, I felt safe enough trying the update directly via the LineageOS system interface, and it appears to have worked fine.
Now I wonder whether I should wait to go from 19.1 to 20.0