Related
So I had quite the experience upgrading to lollipop.
Started with:
CM11 4.4.4 Nightly
600mb system
Philz Touch
1) I flashed Flintman TWRP within Philz Touch 6.0.4.9.
2) Downloaded Milaq's CM12 and PA Gapps 5.0.2. Pico.
3) Booted into TWRP, and created a backup.
4) Ran a factory reset in TWRP, and attempted to flash CM12. I had no idea where the /Downloads/ folder was, and I ended up finding it by going to /Internal Storage/data/media/0/Downloads
5) Encountered an error in mounting system, nothing was flashing.
6) Booted the touchpad into Web OS Recovery, and ran TPToolbox. An error was detected in the system partition, and 'Repair Partition' failed.
7) I then booted into WebOS and ran Preware 'Tailor'. Tailor also failed on 'Check Filesystem'. I then proceeded to delete the Android system partition. I never figured out why my system became corrupted.
8) I removed 400 mb from Android Data, and created Android System with 1000mb.
9) I booted back into TWRP, and successfully flashed CM12, and gapps.
10) After booting, I then proceeded to download Xposed for lollipop. I activated root in developer settings,.
11) I booted in to TWRP, and flashed Xposed, and rebooted the tablet.
12) All subsequent apps resulted in a -504 error when installing. It was discovered that Xposed was the culprit.
13) I then reflashed cm12, without xposed.
14) I downloaded Trickster MOD and set my CPU to 1782 Mhz and performance governor.
15) I experienced odd slowdowns and crashes when any audio played (include keyboard taps). I then proceeded to flash Viper4Android. I installed the driver, rebooted, and now my Touchpad audio sounds great! Make sure to select the best audio quality, and play with the Viper settings!
I now have a blazingly fast lollipop tablet. I tried 5.1.1, but I find it too unstable for daily use. The next step is to figure out how to get Xposed working.
Thanks to the devs for the hard work in development!
fwiw, all 4.4.4 and 5.x roms that I have tried excepting the Evervolv 5.0.2 last nightly have problems with the sound locking up the system, unless you turn off "OK Google" detection completely.
EricBlade said:
fwiw, all 4.4.4 and 5.x roms that I have tried excepting the Evervolv 5.0.2 last nightly have problems with the sound locking up the system, unless you turn off "OK Google" detection completely.
Click to expand...
Click to collapse
I had similar issues with the exception of Evervolv. Their 5.1.1 is even pretty solid now at this point; they're setting their sights on Marshmallow next!
rfoster2009 said:
I had similar issues with the exception of Evervolv. Their 5.1.1 is even pretty solid now at this point; they're setting their sights on Marshmallow next!
Click to expand...
Click to collapse
I still gget that lockup in 511.. hoping 6 kills the weird bugs
Sent from my Touchpad using Tapatalk
Interesting yet annoying
BuffMcBigHuge said:
So I had quite the experience upgrading to lollipop.
Started with:
CM11 4.4.4 Nightly
600mb system
Philz Touch
1) I flashed Flintman TWRP within Philz Touch 6.0.4.9.
2) Downloaded Milaq's CM12 and PA Gapps 5.0.2. Pico.
3) Booted into TWRP, and created a backup.
4) Ran a factory reset in TWRP, and attempted to flash CM12. I had no idea where the /Downloads/ folder was, and I ended up finding it by going to /Internal Storage/data/media/0/Downloads
5) Encountered an error in mounting system, nothing was flashing.
6) Booted the touchpad into Web OS Recovery, and ran TPToolbox. An error was detected in the system partition, and 'Repair Partition' failed.
7) I then booted into WebOS and ran Preware 'Tailor'. Tailor also failed on 'Check Filesystem'. I then proceeded to delete the Android system partition. I never figured out why my system became corrupted.
8) I removed 400 mb from Android Data, and created Android System with 1000mb.
9) I booted back into TWRP, and successfully flashed CM12, and gapps.
10) After booting, I then proceeded to download Xposed for lollipop. I activated root in developer settings,.
11) I booted in to TWRP, and flashed Xposed, and rebooted the tablet.
12) All subsequent apps resulted in a -504 error when installing. It was discovered that Xposed was the culprit.
13) I then reflashed cm12, without xposed.
14) I downloaded Trickster MOD and set my CPU to 1782 Mhz and performance governor.
15) I experienced odd slowdowns and crashes when any audio played (include keyboard taps). I then proceeded to flash Viper4Android. I installed the driver, rebooted, and now my Touchpad audio sounds great! Make sure to select the best audio quality, and play with the Viper settings!
I now have a blazingly fast lollipop tablet. I tried 5.1.1, but I find it too unstable for daily use. The next step is to figure out how to get Xposed working.
Thanks to the devs for the hard work in development!
Click to expand...
Click to collapse
I have been hving fun running Milaq 4.4 and i seen this post but Milaq's link and the link to the gapps and Exposed all are well i have no Idea how to download from those sites. IE can't find a link, only more info into what they are. can you check this out? repost if needed , thanks for sharing.. I hope i can get these files downloaded...
This is just stock LineageOS for the vs985 with no modifications (except baked in root in one edition) built daily from their source code. It's not terribly useful to anyone but people who want to be on the bleeding edge of development for whatever reason (like me), but I figured I'd share. I'll be doing these daily builds for the foreseeable future as long as I own the device or don't change OSes personally.
To install, do one of the following:
If you want to start fresh (or are coming from a non-Lineage based rom):
1.) In TWRP, wipe system, cache, dalvik, and data. Install the standard build (or the standard build with root). Do not install a migration build. Now Install open-gapps if desired. Reboot.
If you want to keep your data (and are coming from a Lineage based rom, official most likely)
1.) In TWRP, wipe system, cache, and dalvik. Install the migration build first, and then an open gapps build if desired. Reboot (it may take a bit). Once you are at your homescreen, reboot back to TWRP, and AGAIN wipe system, cache, and dalvik. Now flash a NORMAL build (with or without root) of your choosing. Again, flash open-gapps. Reboot. All done.
To upgrade, you simply wipe system/cache/dalvik and flash a non-migration build and appropriate gapps.
A warning about migration builds
Migration builds only need to be used once, but they appear to be a one way street. Once you are on my build, you can't "migration-build" your way back to official builds (or at least, I was not able to). You will need to data wipe to go back there. So, caveat emptor. Be sure this is what you want.
Find my dailies (along with build dates) here:
https://www.androidfilehost.com/?w=files&flid=164143
Open-gapps can be downloaded here: http://opengapps.org/
LineageOS Source can be found from the LineageOS github. It was compiled unmodified from this repo:
https://github.com/lineageos
Please, although these are stock code based, they are UNOFFICIAL BUILDS. Please do not bother the LineageOS project for support of these unless you can confirm the issue in an official build.
Thanks for looking! I'll most likely have a new build up tomorrow.
EDIT: Please make sure you are on the 35B bootstack prior to install:
Just flash this via TWRP if you are not sure: https://www.androidfilehost.com/?fid=24052804347843993
Has anyone installed this yet and can confirm compatibility?
I use them daily so they are compatible (if you can trust my word that is).
That said, they are not exactly bug free, but no LineageOS build bleeding edge ever can be.
The build server was thrashing it's disk space for a few days due to a build script failing to clean up after itself... this means a few days of builds were missed. This has been fixed, and we should have daily builds again.
Not sure if anyone uses this, but hey, just an update.
Hands down best ROM I've used on the G3. Everything works, very little FC if ever and I've even gotten Dolby Atmos to work with it. Never going back to anything else.
Glad to hear it. My build server had issues again yesterday, but it appears to be related to a bad stick of ram. I hope to have daily builds moving again tonight.
I wiped system, cache, dalvik and data, on my rooted, VS985 with TWRP 3.0.2-0.and got an "error 7: error installing zip file" when I tried to install the lineage-14.1-20170402-UNOFFICIAL_WROOT-vs985.zip. "Checking for baseband 35B. Error: It appears you are running an unsupported baseband. assert failed: g3.verify_baseband(35B:2.0.1C1.13.4-00005) =="1""
Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
Any hints would help. I would really like to see this work on my phone.
dweezle said:
I wiped system, cache, dalvik and data, on my rooted, VS985 with TWRP 3.0.2-0.and got an "error 7: error installing zip file" when I tried to install the lineage-14.1-20170402-UNOFFICIAL_WROOT-vs985.zip. "Checking for baseband 35B. Error: It appears you are running an unsupported baseband. assert failed: g3.verify_baseband(35B:2.0.1C1.13.4-00005) =="1""
Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
Any hints would help. I would really like to see this work on my phone.
Click to expand...
Click to collapse
You'll need to flash the bump-friendly 35B bootstack first. You can get it here:
https://www.androidfilehost.com/?fid=24052804347843993
Forgot to mention that, will edit it in.
R-T-B said:
You'll need to flash the bump-friendly 35B bootstack first. You can get it here:
https://www.androidfilehost.com/?fid=24052804347843993
Forgot to mention that, will edit it in.
Click to expand...
Click to collapse
Do you know if the "updater-script" fix would also work in this case?
If I do choose to flash the 35B bootstack, will I be able to get back to the backup of my current configuration simply by restoring it in TWRP or would I need to flash back the existing 24B then restore?
Lastly, how is your build different from the official LineageOS version for the VS985?
Thanks for your work with this. I think my VS985 still has lots of life in it, your ROM should give it even more.
Question please.
What's different about this "unofficial" stock Lineage from the "official" Lineage that is avail for VS985?
Why would one want this one vs that one?
It is just built more frequently from source to get more daily changes. Otherwise it is identical. It's mainly for those who like to track bleeding edge changes.
dweezle said:
Do you know if the "updater-script" fix would also work in this case?
If I do choose to flash the 35B bootstack, will I be able to get back to the backup of my current configuration simply by restoring it in TWRP or would I need to flash back the existing 24B then restore?
Lastly, how is your build different from the official LineageOS version for the VS985?
Thanks for your work with this. I think my VS985 still has lots of life in it, your ROM should give it even more.
Click to expand...
Click to collapse
A twrp restore should work regardless of the bootstack flash.
I just Flashed lineage-14.1-20170623-nightly-vs985-signed and open_gapps-arm-7.1-mini-20170707 it all went ok but it don't find my SIM card on boot, so how am I gonna get my sim card active. plz otherewise I would have to withdraw my choice of this Namely Custom ROM.
Please helpp!! I was using Lineage OS on my LG G3 VS985 it doesn't come with prebuilt root so I was rooting through SuperSU. I reboot my phone into twrp recovery and installed SuperSU.zip and then reboot my phone but now it is showing Secure Boot Error, boot certification failed. Please tell me how to fix this issue
and how is the camera quality of this rom as compared to stock and other aosp/cm based rom?
I flash the 35B bootstack before all and my phone goes wrong.. It is on power off, there's just 2 flicking red and blue led. When I go to the recovery mode, I can choose any proposition, my phone come back to this condition.. Can someone help me please ?^^ I was on Fulmics Rom
This rom hasn't been updated in some time as I no longer have the phone, so I am unsure how to help.
Hi Guys,
I'm hoping the community can provide some advice.
I have an LG G5 H850 and with an unlocked bootloader. After trying fulmics rom temporarily to look at improvements, I wanted to try the latest Resurrection Remix, however, after wiping data, system cache etc and formatting data in TWRP the installation 'failed'. I have put failed in inverted commas because the installation says it has been successful but the phone boots straight back into TWRP and the is clearly no OS on the device when I open file manager. This is the same when I attempt to install any OS (Prime's 10E, Lineage, Fulmics again) none of them take.
Does anybody know what might have happened or what I can do to fix it? I do have access to download mode still.
Thanks in advance,
Chris
unsrm said:
Hi Guys,
I'm hoping the community can provide some advice.
I have an LG G5 H850 and with an unlocked bootloader. After trying fulmics rom temporarily to look at improvements, I wanted to try the latest Resurrection Remix, however, after wiping data, system cache etc and formatting data in TWRP the installation 'failed'. I have put failed in inverted commas because the installation says it has been successful but the phone boots straight back into TWRP and the is clearly no OS on the device when I open file manager. This is the same when I attempt to install any OS (Prime's 10E, Lineage, Fulmics again) none of them take.
Does anybody know what might have happened or what I can do to fix it? I do have access to download mode still.
Thanks in advance,
Chris
Click to expand...
Click to collapse
Search XDA LG G5 boots into TWRP there are several threads that cover causes and solutions.
I wouldnt hurt to format some of your partitions especially DATA as it can get encrypted automatically depending on the rom, although ive used fulmics and it has never encrypted my data partition (RR did though!).
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
gordonthegopher said:
Formatting /data in TWRP uses up all the blocks, but encryption from Lineage needs 16kb of free space at the end of the partition to store the headers.
Click to expand...
Click to collapse
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Hi guys,
I'm kind of stuck right now because I cannot encrypt my phone anymore and I don't know why. I got my phone last year and installed LOS 14.1 right away. For security reasons I also encrypted it - without any issues whatsoever. When LOS 15.1 came out, I upgraded my phone, with encryption still working. A couple of days back for some reason I decided to do a factory reset. Obviously, the device wasn't encrypted anymore after the reset. I then installed the new nightly of LOS (20180807) and tried to encrypt my phone once again. When I select "Encrypt phone", I need to enter my PIN, the phone restarts and reboots without encryption being started.
What I've done so far:
I've flashed two different TWRP versions: 3.2.3.0 and a customized one (https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465).
I've clean installed different LOS versions (unofficial LOS 14.1 and LOS 15.1 starting from the 20180710 release)
I've clean installed Omnirom (current release and a release from 20180107).
I've even flashed MIUI 9 and reinstalled LOS thereafter because some guy in the above mentioned LOS thread wrote, that this did the trick for him.
I've disabled WI-FI and mobile data before trying to encrypt my phone, because I found a blog article stating that this might help.
Nothing helped. The phone just reboots and stays unencrypted.
Do you guys have any additional hints or ideas how I can manage to encrypt my phone once again? Could another TWRP version do the trick? Is TWRP even involved in any kind when it comes to encryption of the OS? Do you think another ROM could be helpful?
Click to expand...
Click to collapse
Try orangewolf recovery ....
Sent from my Redmi Note 4 using Tapatalk
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
shakil002 said:
Try orangewolf recovery ....
Click to expand...
Click to collapse
Thanks for the advice. But I'm afraid it didn't help
CanBostanci said:
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
Click to expand...
Click to collapse
That's the most ****ed up part. For some people it does work, for some not.
There surely must be some ridiculous small detail we're not getting. Like disabling WI-FI while Bluetooth is enabled.
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
parkbank said:
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
Click to expand...
Click to collapse
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
CanBostanci said:
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
Click to expand...
Click to collapse
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
parkbank said:
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
Click to expand...
Click to collapse
I'm looking forward to hear the results. I'm about to become insane because of this encryption issue.
I've flashed both the dev and stable firmware found in this thread. No success
By flashing I mean factory reset, flashing the firmware and then installing LOS. I noticed, that flashing a new firmware while a ROM is still installed leads to some random ****ups.
After a couple of days of flashing, factory resetting, re-flashing, reading and a lot of cursing I finally found a working solution. I've added the fix to my initial post. Hopefully this helps
I was looking for solutions for quite a while and nothing else worked but did this and my device is encrypted again.
Thank you!
parkbank said:
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Click to expand...
Click to collapse
You have save my day "my MIDO" hehehehe
After the 1st PIE Rom the encryption was broken.
Your Step by Step save this and now Syberia 9 was able to encrypt with success :good:
Thank you one more time for sharing.
Thx!
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Orangefox worked
is there any plan to fix twrp itself?? thx
Thank you. It worked for me to get Havoc OS 9.0 with hardware encryption on my Redmi Note 3 SE.
I bypassed unlocking the bootloader by doing this. Then I installed TWRP 3.1.0.0 from the recovery, did the reset and everything as instructed here, updated it to 3.3.1.0, rebooted, then flashed the Pie ROM and latest gapps without any further wiping.
I use the first link, I've modified the partition size -> did the trick wihtout formating nor loosing datas
Great, thank-You.
Hi, I want to ask, what is this encryption features you been using? can u tell me?
Typical disclaimer, etc etc.
You nuke your phone, I'm not paying for it
Thanks to @zefie for converting the kdz to a zip.
The zip
The anti-root removal
I flashed the zip in TWRP, rebooted to the OS, and was unrooted.
Reboot into the bootloader, and flashed TWRP.
Rebooted into recovery, flashed the lucye anti root removal, then rebooted into recovery again, and flashed Magisk.
Phone has been fine since Thursday.
Did you flash this dirty or clean?
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Link to his thread
jjohn7293 said:
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Click to expand...
Click to collapse
Here's a link to his thread https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
monark88 said:
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Click to expand...
Click to collapse
Dirty from 21B worked fine for me
Dirty flash from 20A worked perfectly.
FYI: This ROM has the recovery image removed, so if you already have TWRP, flashing this won't remove TWRP. No need to reinstall TWRP.
I actually started having bad idle drain. Flashed LOS for now, will go back to stock soon. If anyone else notices idle drain, please do let us know.
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
MetalMan2 said:
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Click to expand...
Click to collapse
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
BeardKing said:
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
Click to expand...
Click to collapse
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
Good to hear. :good:
US997 14a to 21c (Keeping Root)
I'm using the US997 still on 14a (rooted, TWRP installed) would I need to (CLEAN) flash up to 17a and then the 21c? After that flash the anti-root and flash an updated version of Magisk? (currently stuck on v16.4) Can't find my stock boot image to update. Only got the phone back in October and stopped all updates before I unlocked the bootloaded, installed TWRP and used Magisk to get root. I had a hard time finding a version of TWRP with a kernel that worked for my phone (Melina v3.2.1-0) would I have to update that also? Was waiting to see the highest update I could get without losing root. Anyone done this? Any help would be greatly appreciated.
My wife and I both have G6 phones. On mine, I dirty flashed this over 20A with absolutely no problem. My sequence was: flash Eliminator74 TWRP, reboot to recovery, flash 21C zip, reboot to recovery, flash lucye anti-root, reboot to recovery, flash Magisk, wipe cache and Dalvik, reboot to system. I'm guessing I really didn't need those extra reboots but it felt safer. Phone is perfectly stable.
On my wife's phone it was another matter. Her data partition was encrypted, due to the phone having been reimaged by LG during warranty repair. I'd rooted it but never decrypted it. None of the default ways to decrypt it worked, so I was forced to format /data. I thought that would do it, but the resulting installation was unstable, and wouldn't get through setup successfully without continually looping, freezing, and returning to start. Finally I realized it was probably flashing over the LG factory image that caused the problem. I wiped /system and started over, and had much better results.
LPMatt said:
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Click to expand...
Click to collapse
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Malezar said:
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Click to expand...
Click to collapse
This probably won't help, but are you using this version of TWRP?
BeardKing said:
This probably won't help, but are you using this version of TWRP?
Click to expand...
Click to collapse
Yep. Just downgraded the bootloader back to 17a through it.
Malezar said:
What steps did you take MetalMan2?
Click to expand...
Click to collapse
I exactly followed LPMatt's list which you quoted.
Still no problems. Pretty sure the battery life is less than 17A, but I think we all know that and for me it's "good enough".
How to remove root checker?