Related
Q&A for [Firmware] [LP] [5.0.1] Lollipop Update for DevEd [N910VVRU1BOAF]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Firmware] [LP] [5.0.1] Lollipop Update for DevEd [N910VVRU1BOAF]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
hsbadr said:
I've updated the partial firmware hoping it may fix the brightness issue. Please follow all steps to reinstall & report me back!
Click to expand...
Click to collapse
Did not work for a fresh install/upgrade for me, the slider moves but the screen is still full brightness.
Bent_MG said:
Did not work for a fresh install/upgrade for me, the slider moves but the screen is still full brightness.
Click to expand...
Click to collapse
Try to change Display Mode in Settings/Display & disable "Auto adjust screen tone" & "Automatic brightness"...
hsbadr said:
Try to change Display Mode in Settings/Display & disable "Auto adjust screen tone" & "Automatic brightness"...
Click to expand...
Click to collapse
Still no success by disabling those settings, everything else seems to be running great though
Bent_MG said:
Still no success by disabling those settings, everything else seems to be running great though
Click to expand...
Click to collapse
That's good news. I think it's a minor issue compared to the issues users of Note 3 DevEd have had for running KK on JB bootloader. I hope it could be fixed with official images (unlikely, I guess). Also, running a custom kernel can fix it if you want to try... good luck!
Delete. Didn't know "DevEd"
First of all @hsbadr thank you thank you. Next, has anybody figured out a workaround for the brightness issue? Someone suggested a 3rd party app to control brightness but I didn't see that anyone had confirmed whether that worked.
Thanks @hsbadr and @ryanbg for all the good information!
FWIW, I flashed the retail NJ5 on my DE and took both the updates OTA. The brightness issue does not exist with retail bootloader. I then flashed my original DE bootloader to Lollipop. That went fine. This is when the brightness issue exists.
I was able to root and go back to the Lollipop retail bootloader and the brightness issue went away. Seems like one could flash DE bootloader to unlock, root, modify, then go back to retail Lollipop bootloader to fix brightness issue. Not sure if there are any further consequences of doing this!
Thanks for all the good work everyone!
-Christian
jpfulton248 said:
First of all @hsbadr thank you thank you. Next, has anybody figured out a workaround for the brightness issue? Someone suggested a 3rd party app to control brightness but I didn't see that anyone had confirmed whether that worked.
Click to expand...
Click to collapse
using lux ,setting it to manual, and adjust to any level below 0 will allow you the illusion That the brightness is being adjusted. I believe it's just a screen filter but it's working for me in the meantime. Also disable taptracker protection in supersu so that it doesn't interfere when asked to grant apps su.
Blackiisky said:
using lux ,setting it to manual, and adjust to any level below 0 will allow you the illusion That the brightness is being adjusted. I believe it's just a screen filter but it's working for me in the meantime.
Click to expand...
Click to collapse
So does that mean the automatic feature in the paid version of lux is working as well? I'm considering flashing Lollipop but the auto-brightness on this phone is pretty amazing when going from inside the house to in the car. Amazing how well the brightness compensation works.
jpfulton248 said:
So does that mean the automatic feature in the paid version of lux is working as well? I'm considering flashing Lollipop but the auto-brightness on this phone is pretty amazing when going from inside the house to in the car. Amazing how well the brightness compensation works.
Click to expand...
Click to collapse
im not sure because i don't have the paid version but i imagine you could maybe set the max brightness to -1 and lowest to -99 or something like that... and then adjust the app to when the sensor senses high amounts of light it will go to the max... I don't have much experience with the app so im not sure that it's possible. I will check out it when i have more time later
Does anyone know of any flashable mods that we can use as an alternative to xposed (since it doesn't work for LP)? I'm hoping some mods from the other carriers may work.
Sent from my SM-N910V using Tapatalk
Observation-Dev Editions with OTA Lollipop Update
I haven't seen any Dev Edition users post observations about their devices running the OTA update to Lollipop that Hsbadr has provided us, link is below. So, I thought I'd take a few minutes to post my results and observations. I have been running the Lollipop OTA update (http://forum.xda-developers.com/not...e-rooted-lollipop-update-deved-t3073561/page9, post 87. I strongly recommend you read the entire thread even though the one step ODIN flash is in post 87) for a couple of days now and I am very pleased. Aside from the display brightness issue (cannot adjust) my Note 4 is running faster and smoother than it did on KitKat. Everything works (data, phone, wifi, bluetooth, gps, s-pen etc) just as it should. If you're not a big video streaming user or gamer and your typical daily use is such that you don't have a lot of display on time to begin with then you won't have an issue. For example: with a full charge on KItKat and my typical daily use I would turn my phone off after about 18 hours of phone on with 85-87% battery left at the end of the day. With Lollipop that has fallen to 80% (because of the screen brightness all the way up). That decrease in battery % left is not bad at all. So, if you haven't made the leap to Lollipop and you're not a big video streamer or gamer the go ahead and make the jump...it is well worth it.
I know a lot of users hate TouchWiz, but I got to tell you that TouchWiz on Lollipop is not at all bad...it is fast, no lag, smooth and very responsive. If you are a big Exposed and Viper user your out of luck right now, neither of those work on Lollipop as I understand it.
Here is what I am running:
Lollipop 5.0.1 (flashed in ODIN from link above)
Nova Pro launcher
Self debloated (initial boot showed 451 MB of RAM remaining after Lollipop installation. After debloat...1.16GB RAM remaining)
Running the following apps requiring root - Titanium Backup Root, Greenify (paid version), SD Maid Pro, Root Explore, Busy Box).
Total Internal Stoage remaining after installations of 37 user apps - 94.3%
Night Mode works too. I don't know how it compares to Lux though.
Thank you very much for your kernel fix
Has anyone had any freezing issues with lollipop? if I don't restart my phone daily my phone will freeze up completely while running apps flipboard in particular. I don't think it is app related as it happens with any app chrome inclued that is displaying lots of pictures. I have tried reflashing lollipop, but it still starts freezing after a day or so of running. I have also tried flashing your mulisystem kexec kernel to see if it was kernel related, but still having freezing issues. Will try reflashing in the next day or two, or flashing morom to swe if that fixes any issues.
Verizon 910V 5.0.1 root process question
I have a 910V Develepor Edition which had been running 4.4.4 and CF Auto Root. Worked great!
Recently I saw this thread that I interpreted to say that you can follow these steps to have 5.0.1 and root.
http://forum.xda-developers.com/note-4-verizon/development/firmware-rooted-lollipop-update-deved-t3073561
I followed the instructions but I was not successful in having both 5.0.1 and having root.
My problem arises when I use odin to flash updates, after the first stock update, odin always fails.
After upgrading to 5.0.1 and not having root, I carefully went back and did the following.
Stock update to 4.4.4 : N910VVRU1ANJ5 Stock Restore: N910VVRU1ANJ5_StockRestore.tar.md5.7z
this worked fine.
I then used the updated instructions for taking the phone from KK to LP : DevEd_OAF_update.tar.7z
When I was done, I had 5.0.1 but no root. If you take a stock NJ5 and then apply DevEd_OAF_update.tar.7z will you end up with a rooted 5.0.1? Or did I misunderstand the instructions?
I then went back, completely wiped my phone, reinstalled stock update: N910VVRU1ANJ5 Stock Restore: N910VVRU1ANJ5_StockRestore.tar.md5.7z
It took some fiddling with clearing caches and resetting the device to factory settings but I got back to a working 4.4.4 NJ5.
Then, I decided to make sure that CF Auto Root would work on 4.4.4 NJ5 (which I think it did originally) so I tried CF Auto Root with the 910V 4.4.4 download: CF-Auto-Root-trltevzw-trltevzw-smn910v.zip
However, when I used odin to flash this CF auto root, I also got a fail message. I restarted my phone, I cleared the cache, I reset to factory defaults, all to no avail - odin failed every time trying to flash CF-Auto-Root-trltevzw-trltevzw-smn910v.zip.
To make my sad story even sadder, I used Titanium to carefully backup my phone in case something went wrong. But now that I can no longer get root on my phone, I can't restore my phone!
Can someone help me get my 910V developer edition to either a KK root or a LP root so I can use titanium to recover my data? I'd obviously like to get to LP so I can try it out, but I'd be happy to just have KK rooted.
BTW, LP 5.0.1 with almost no apps on the phone seems to have halved the life of my battery. I thought 5.0.1 fixed the battery life issue which is why I tried this in the first place....
Any help will be greatly appreciated.
Marlon1691 said:
I have a 910V Develepor Edition which had been running 4.4.4 and CF Auto Root. Worked great!
Recently I saw this thread that I interpreted to say that you can follow these steps to have 5.0.1 and root.
http://forum.xda-developers.com/not...irmware-rooted-lollipop-update-deved-t3073561
I followed the instructions but I was not successful in having both 5.0.1 and having root.
My problem arises when I use odin to flash updates, after the first stock update, odin always fails.
After upgrading to 5.0.1 and not having root, I carefully went back and did the following.
Stock update to 4.4.4 : N910VVRU1ANJ5 Stock Restore: N910VVRU1ANJ5_StockRestore.tar.md5.7z
this worked fine.
I then used the updated instructions for taking the phone from KK to LP : DevEd_OAF_update.tar.7z
When I was done, I had 5.0.1 but no root. If you take a stock NJ5 and then apply DevEd_OAF_update.tar.7z will you end up with a rooted 5.0.1? Or did I misunderstand the instructions?
I then went back, completely wiped my phone, reinstalled stock update: N910VVRU1ANJ5 Stock Restore: N910VVRU1ANJ5_StockRestore.tar.md5.7z
It took some fiddling with clearing caches and resetting the device to factory settings but I got back to a working 4.4.4 NJ5.
Then, I decided to make sure that CF Auto Root would work on 4.4.4 NJ5 (which I think it did originally) so I tried CF Auto Root with the 910V 4.4.4 download: CF-Auto-Root-trltevzw-trltevzw-smn910v.zip
However, when I used odin to flash this CF auto root, I also got a fail message. I restarted my phone, I cleared the cache, I reset to factory defaults, all to no avail - odin failed every time trying to flash CF-Auto-Root-trltevzw-trltevzw-smn910v.zip.
To make my sad story even sadder, I used Titanium to carefully backup my phone in case something went wrong. But now that I can no longer get root on my phone, I can't restore my phone!
Can someone help me get my 910V developer edition to either a KK root or a LP root so I can use titanium to recover my data? I'd obviously like to get to LP so I can try it out, but I'd be happy to just have KK rooted.
BTW, LP 5.0.1 with almost no apps on the phone seems to have halved the life of my battery. I thought 5.0.1 fixed the battery life issue which is why I tried this in the first place....
Any help will be greatly appreciated.
Click to expand...
Click to collapse
You can't flash a zip file with Odin. Use this instead. This is the latest version of TWRP.
Update: After flashing LP it's normal to lose TWRP and root. Also be sure to either apply the Brightness Fix Kernel or get the MultiSystem Kernel.
stueycaster said:
You can't flash a zip file with Odin. Use this instead. This is the latest version of TWRP.
Update: After flashing LP it's normal to lose TWRP and root. Also be sure to either apply the Brightness Fix Kernel or get the MultiSystem Kernel.
Click to expand...
Click to collapse
That is an excellent point and I am sorry that I wasn't clear. Chainfire has neatly packaged the OS patch with odin into a zip. Once you unzip Chainfire's zip file, then you get this:
marlon-air-2:CF-Auto-Root-trltevzw-trltevzw-smn910v marlon$ ls -ls
total 78696
76328 [email protected] 1 marlon staff 39075917 Jan 20 13:36 CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5
1848 [email protected] 1 marlon staff 943616 Jan 20 13:36 Odin3-v3.07.exe
8 [email protected] 1 marlon staff 707 Jan 20 13:36 Odin3.ini
312 [email protected] 1 marlon staff 159744 Jan 20 13:36 tmax.dll
200 [email protected] 1 marlon staff 102400 Jan 20 13:36 zlib.dll
(Note, that I am not on a Mac laptop at the moment and I unzipped Chainfire's zip locally so I could list the files. I realize Odin doesn't work on a Mac.)
As a result, I wasn't trying to flash a zip file using odin. I was flashing CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5 with odin.
Any other thoughts?
Marlon1691 said:
That is an excellent point and I am sorry that I wasn't clear. Chainfire has neatly packaged the OS patch with odin into a zip. Once you unzip Chainfire's zip file, then you get this:
marlon-air-2:CF-Auto-Root-trltevzw-trltevzw-smn910v marlon$ ls -ls
total 78696
76328 [email protected] 1 marlon staff 39075917 Jan 20 13:36 CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5
1848 [email protected] 1 marlon staff 943616 Jan 20 13:36 Odin3-v3.07.exe
8 [email protected] 1 marlon staff 707 Jan 20 13:36 Odin3.ini
312 [email protected] 1 marlon staff 159744 Jan 20 13:36 tmax.dll
200 [email protected] 1 marlon staff 102400 Jan 20 13:36 zlib.dll
(Note, that I am not on a Mac laptop at the moment and I unzipped Chainfire's zip locally so I could list the files. I realize Odin doesn't work on a Mac.)
As a result, I wasn't trying to flash a zip file using odin. I was flashing CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5 with odin.
Any other thoughts?
Click to expand...
Click to collapse
Ok I don't use a Mac. If you have access to a pc use Odin 3.10 to flash that file I linked you to and it should work.
Sent from my SM-N910V DE
Short history of what I've done/where I'm at now:
The History
Wanted to upgrade rooted D855 from 4.4.2KK to 5.X Lollipop
De-rooted using SuperSU. Rebooted, and went to update center to apply update. Message saying "Phone has been noted to be rooting. Software update not available for rooted phones." or something thereabouts.
Decide to factory reset phone. Does nothing.
Follow this guide (Link) to completely wipe and start fresh. All goes well.
Bunch of bloatware comes pre-installed. What the hell?
Decide to combat this by following this guide (The KDZ way) (Link) and this Image (3 UK variant) to attempt to get back to my original version.
Used this one-click root (Link) to re-root my Android 5.0 variant (question on this later)
Goes well pretty much; everything seems about right. However, here are the problems.
The Problems
I have rooted and have Titanium Backup Pro; tried using this to remove the bloatware. Doesn't do anything, and if I try to do them individually I get the message "cannot remove System app. Failed to locate the APK file." This is my #1 problem. I have a bunch of European apps that I can't pronounce, plus rubbish like 'Orange Antivirus'. Even things like Deezer is now pre-installed system crap, listed under the Software center portion of the LG Updates area on the phone.
My 3 splash screen no longer comes up, which is fine, makes the booting either faster or just seem smoother. However, it makes me wonder whether I'm on the right version of Android now; will I miss updates to future version of Android from hereon out?
Is Android 5.0 the latest update for the EU D855? I heard 5.0 was having problems on the G3, hence why I've updated so late. However, if I'm now stuck on the version WITH the problems, that's not good.
Bump; anyone? This is driving me nuts!
Hi,
1. To uninstall the antivirus you need to remove it from the phone administrators.
2. There should be at least the LG boot animation.
3. Yes. The latest update is still 5.0.
I suggest that you move to a custom Rom based on stock like cloudy 2.5.
Much better Rom and free of bloatware.
Regards
Sent from my phone
ypsmav said:
Hi,
1. To uninstall the antivirus you need to remove it from the phone administrators.
2. There should be at least the LG boot animation.
3. Yes. The latest update is still 5.0.
I suggest that you move to a custom Rom based on stock like cloudy 2.5.
Much better Rom and free of bloatware.
Regards
Sent from my phone
Click to expand...
Click to collapse
I gave up on waiting (the bloatware was driving me crazy, not usually so impatient), and just installed TWRP, wiped it and reinstalled a fully stock ROM, so all sorted now. Any benefit to using Cloudy 2.5 over complete stock? Any performance/battery benefits?
Thanks for your response though
BRPW said:
I gave up on waiting (the bloatware was driving me crazy, not usually so impatient), and just installed TWRP, wiped it and reinstalled a fully stock ROM, so all sorted now. Any benefit to using Cloudy 2.5 over complete stock? Any performance/battery benefits?
Thanks for your response though
Click to expand...
Click to collapse
Felt faster for me plus a load of newer updated app versions for stock apps and a lot more customization options :good:
Will_Xda said:
Felt faster for me plus a load of newer updated app versions for stock apps and a lot more customization options :good:
Click to expand...
Click to collapse
Maybe I'll look into it then On another note, you're from Leicester? Where abouts you from?
I've been running a version of cm12 on my galaxy tab s 8.4 WiFi (t700) tablet for a while and had twrp 2.8.5 installed. I recently wanted to see how far roms have come and what was out there. I noticed there were recent lollipop roms and even marshmallow in the wild now! No matter which ROM I try to install now, i get a black screen when it goes to reboot and simply won't boot. With button presses I have managed to get into twrp (hold buttons on boot) and restore an old lollipop rom of mine. I'm not new and know all about clean flashing (which is what I did). Then i start reading and some of the threads talk about how you need the newest official bootloader from now on. I have now updated to the newest twrp (2.8.7.2 and I have a few questions regarding a few things:
1. Why do new lollipop roms all of a sudden require a bootloader change? I have lollipop roms saved in restore (2 different ones) but those are 5.0.2 roms. Could the fact that the new ones are 5.1.1 be the difference here?
2. If i just update the bootloader alone will that trip Knox?
3. Why is knox so important not to trip? Will it eventually not allow installation of roms in general?
4. I noticed there are a few versions of the new boot loaders here. Which version should I use? Also, those are listed as needing to be extracted and re-tared as there was a mistake with the upload. I think I've done it right but does it matter if the new tar I created is just called sboot.bin (same as contents)?
5. Will doing this update hurt any of my root stuff?
6. Anything else I should know?
I do not plan to run official firmware on this tab. Thanks to anyone and everyone for the help. Great information available on here!
I have a Note 4 on Sprint, still running KitKat. Here's my problem:
I really don't want the Lollipop update. I don't want it because I love KitKat so much and I tried Lollipop out on my friend's phone and hated the look and feel of it. I don't want it to finish downloading because I hardly have any space on my phone as it is.
I don't want to
-root my phone
-factory reset my phone
-trip Knox
Right now, I'm pretty angry because I'd like to use WiFi, but can't because every time I turn it on the update starts to download. I tried going into settings and turning off auto update, but that didn't stop it. I also tried filling my device storage so that there were less than 800 megabytes left, but that had no effect on the update either, it just continues downloading. I realize that there are similar posts on this issue, but none of them really apply to me. Thank you in advance for any help.
Just update it then use a kk theam the update will help i dont think you can stop the ota update
chad.420.419 said:
Just update it then use a kk theam the update will help i dont think you can stop the ota update
Click to expand...
Click to collapse
Thank you for replying, but that really doesn't help me at all. As I said several times over in my original post, I don't want the update at all. I'm constantly hearing about people choosing to keep KitKat, so there must be some way. And even if I could apply a theme to my whole phone without being rooted, it wouldn't fix all the other problems that I have with lollipop.
But the 3 things to consider or note before you begin:
1) if you update beyond OB7, the bootloader gets upgraded to one with a reactivation lockable bootloader. That will prevent you from being able to Odin back to KitKat. You need to disable auto update and stop the update notices before they start; otherwise the nags persist and you may accidentally update.
2) the lollipop file system is different than KitKat do better off formatting your data and wiping cache and dalvik-cache and powering down and pulling battery prior to Odin OB7 stock tar. Let it boot and setup wizard prior to Odin of TWRP (uncheck auto reboot for recovery flash only), boot into TWRP recovery and flash the ROM.
3) dalvik gets built on initial boot of lollipop ROMs; the stock tar still not much quicker. You'll likely see the phone hang at the second boot splash screen with blue LED slowly blinking before you see the app optimization and app start pop-ups. You can expect that with lollipop. Give it 30 minutes to boot before you panic. To avoid CPU heating and slowing the process, remove your phone from its case and ventilate if it gets too warm. You need to start with battery charged to about 80% to full to be safe. It's best to not try and update apps or restore apps until you've flashed and booted the custom ROM. More apps means the process takes longer. You can format the data again prior to flashing the custom ROM to speed things along. If possible, backup your media, and downloads that you want to keep and wipe internal sdcard to get a cleaner start with lollipop. That's optional but don't lose your keepsakes. What you flash should be on extSdCard to avoid the wipe-loss if it.
BTW, the post you're referring to may have been an attempt to recover phone after attempting to downgrade to OB7 or KitKat. It's since been discovered that although Odin wouldn't downgrade, there's a possibility to flash older ROMs in recovery and immediately flash a 5.1.1 rooted kernel to get it to boot without looping. That doesn't have to apply to you; the general rule is to Odin flash the tar that matches the ROM you want to flash in recovery. But again, if you upgrade beyond OB7, you cannot go backwards with Odin. Only few exceptions apply; generally it is forward, not backwards. OB7 is the divide that separates the simple from more complex conditions. So these last 3 paragraphs shouldn't apply to you as long as you're wanting to stay with OB7 or KitKat.
Just for an idea of what to consider in other lollipop updates. The ram optimization got a bit crazy after OB7 and continued until it improved in OJ6. Personally, I think OJ6 and OK1 updates are the best lollipop updates yet. You'll certainly find more security updates in those updates. But lollipop 5.1.1 also introduced the need to root the kernel but Chainfire has recently brought us a patch to use stock kernel again; it's married from experimental to beta. I've mostly ran with stock kernel on my phone, especially before lollipop 5.1.1
Things were once simpler but got a tad more complex as time and updates followed OB7.
Sent from my SM-N910P using Tapatalk
7H3N3RD said:
I have a Note 4 on Sprint, still running KitKat...
I don't want to
-root my phone
-factory reset my phone
-trip Knox
Right now, I'm pretty angry...
Click to expand...
Click to collapse
That's a tough ask for a definitive answer, IMO. IDK if it can be done but I'll offer an idea for discussion. Consider pros and cons and alternatives and even constructive differing because l don't know if it's been tried and proven to stop the persistent update on stock KitKat. There are root alternatives but your request is taken into some consideration below.
Odin stock tar will not trip Knox or require root. There are 2 stock tars for KitKat (those end with NIE and NK2, last 3 letters only, NIE being the original, NK2 the last KitKat update).
My theory is that you could...
1) Odin the first tar, NIE stock tar is linked below, let it download the OTA for NK2 but postpone the update long enough to go into Settings/System update/Auto update and uncheck the option.
2) Turn phone off and boot into recovery. It should find the NK2 update and prompt to apply it. If not there's an option to apply from cache, I think.
3) Once booted, make sure the auto update is still unchecked.
https://www.androidfilehost.com/?fid=95784891001612590
The instructions for Odin stock tar are found here but early posts in that thread may be relative to Odin if stock KitKat tar. The stock tar above is actually linked in post #2
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If auto update resets during the process, it most likely promptly starts the OTA download, negating the effort. No guarantees but reason the risks before you proceed. That's the whole theory, if someone knows the system update gets reset to auto or if that's not enough to prevent it, please advise. On a rooted Lollipop phone, uncheck auto update seemed to be enough to prevent the OK1 update from downloading and being persistent to update... I may have overlooked something in my simple theory. Did I?
Don't be angry with me if it doesn't work. Your data may not be lost but backup what you can on PC via USB, particularly photos, media and downloads on internal memory before you start. KIES may actually work to backup a lot on a stock un-rooted phone but be careful about what you restore; don't want to start the persistent update again if you succeed in preventing it.
Sent from my SM-N910P using Tapatalk
You definitely can stop it from nagging you to update by turning off notifications (I think you turn it off for Google services framework, and if not that, it's Google play services). This worked for me when I stayed on kitkat.
But deleting the downloaded update file is an issue without root. It lies in /cache or /cache/FOTA directory I believe, which you can't access without root. You may be able to wipe cache with stock recovery, but I'm not sure if it has that option (I'm not on stock recovery so can't check) or if it even works for what you want. Perhaps you can try deleting the cache for Google services framework or Google play services, not sure if the works either. Just some thoughts which may help you
I have a D855 with KitKat 4.4.2 (10h). It is rooted and (now) has the latest TWRP (3.3.1.0)
I have never updated from Kitkat because it runs perfectly rock solid. Until now.
I have noticed that a number of apps I use on Play Store can no longer be updated. I think they have stopped supporting KitKat, so I must upgrade to the latest version of Android, to make sure my beloved G3 lives a little longer.
I have updated TWRP to the latest version from the TWRP website. Which was surprisingly hard to achieve, as I was unable to get into Fastboot or Download modes. After several tries, the TWRP app finally flashed successfully.
Also, I finally got the G3 into Download mode (although I had to hold down the power button for about 30 seconds to get back out of Download mode, after disconnecting the USB cable).
I now need to flash a new rooted MM custom ROM, but I seem to remember the partitions changed from KK to LP/MM.
So before jumping and in, and potentially bricking the G3, I just wanted to ask if any one could offer me some advice on upgrading from Kitkat to MM. To ensure I am successful.
Looking at the old threads, people usually did this back in 2017, and things are a little different two years later, so I thought that it would be worth asking the question now, in case there are newer/different options to consider.
I would appreciate some advice. Thanks.
Many thanks for those who had a look at my question.
I was hoping for some advice on RPM/TZ partitions etc. , Modems, Bump! etc but I guess it was naive to expect the forum for a 5 year old phone to be active.
For my part, a good phone is a good phone. And the LG G3 was a good phone.
I came from a Sony Z1 which was a great daily driver, slightly workman-like but rock solid with good vanilla-style OS.
Moving to the G3,the build quality wasn't quite up to Sony's standards but I suddenly discovered how good audio on a phone could be. The screen was great, the OS was rock solid, which is why I stayed on Kitkat for so long. Also, the G3's removable battery allowed me to use a Mugen 6000mah battery, which has provided amazing battery life.
FYI, I considered going back to a Sony but the G3 was so good, I bought a G5. Which is a decision I have always regretted.
The G5 OS was good, like the G3. The bootloader could be unlocked. The audio and screen were as good as the G3. But the hardware was only mostly good. The phone overheats all the time and successive ROM updates have never resolved this issue. Also, battery life is beyond poor, possibly the worst I have ever experienced with a mobile phone.
If I brick my G3, I think I will replace it with a Sony.
I am going to go ahead and flash an MM ROM, Fulmics or CleanROM. I have a Kitkat bootloader so hopefully that will help (now that Autorec has been removed from Playstore).
I will post how things go.
Safest way to do it:
1. Upgrade to LP from KDZ. Root the phone, install TWRP and flash some MM (or newer) ROM.
2. Upgrade to MM (30b or 30f) from KDZ. Root the phone with king root, install twrp and flash some MM (or newer) ROM.
Thanks for the advice, MESA.
Unfortunately, I have already flashed the latest Fulmics for d855.
Did a clean flash. Appears to be working with no issues.
Upgrading does appear to have resolved the various app issues I was having. Looks like some big companies/organisations are no longer supporting KitKat.
But, now, I have no idea which RADIO/MODEM, RPM, TZ or CUST I now have installed. Also, I do not know whether the kernel is set to permissive.
If you have any advice on anything I should do now, please let me know.