Related
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
Hello,
I was facing some of the problems everyone is reporting here about random restarts and bootloops even (and mostly) using stock firmwares. As many of you started to have the problems after updates my problem started when I tried to root for the first time when SuperSU was not totally working yet. These problems didn't stop even flashing everything to stock (bootloader, modem, firmware, csc) and other stock firmwares from other countries so I was thinking that my phone was faulty too.
Every reboot my phone asked me for a password that I never set, so there was nothing to put there and I always had to reboot into recovery and flash the "no-verity" script or else I would get stuck in a bootloop or the phone asking me for a decrypt password (that didn't exist).
Sometimes when the phone randomly restarted gave me the "verity encryption" error at the beginning when using the stock recovery, if using TWRP it asked me for a password after semi loading Android (since it didn't found the official recovery to show that error from it), so I always suspected that the Samsung encryption was causing all my problems. Tried everything and even made a post about it (http://forum.xda-developers.com/note-7/help/random-restarts-password-doesnt-exists-t3450678)
So I kept waiting for something that disabled the phone encryption to verify that this was the real cause of this random behaviour before going to Samsung for warranty. Finally @Tkkg1994 came up with the Hydrakernel that disables the encryption so after trying it and formating everything MY PROBLEMS ARE TOTALLY GONE.
My suspects were finally confirmed..... The Samsung encryption was causing all these sh1ty problems (at least in my phone).
So everyone that is flashing stock firmwares even going back to old ones, it seems that doing this doesn't fix anything once you got into this problem for the first time, only disabling the encryption solves it. So my recommendation would be to disable the force encryption from Samsung by using the Hydrakernel and testing again (http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433)
I would like to thank all the devs that are doing their best effort to give us a free Note 7 to enjoy. @Tkkg1994 @dr.ketan @Chainfire it is very admirable that common people like them can solve things that not even Samsung has figured them out yet.
PS: Have you guys flashed this ROM and kernel instead of stock firmwares and continue to have problems with your Note 7??? Give your feedback!!!
Interesting, keep us posted with your phone status...
nice job keeping on testing & we waiting your next result
Until the maintainers (see Lineage Info/Maintainers at http://wiki.lineageos.org/d2att_info.html)
have a chance to create a thread, let's share our experiences with the LineageOS 14 Nightlies here
Latest LineageOS 14 Nightlies
https://download.lineageos.org/d2att
i am just a novice but.......I did a clean install of the 1/23 rom with the mini gapps and everything went well as expected. Wifi, calls/data, bluetooth, battery life, camera all work perfectly for my limited needs.
The only hiccup I had was in doing the the 1/30 update. When doing the update using settings, Lineage will download the update and boot to TWRP, but will not automatically install the update. Easy enough though, as I performed the update manually.
I can't complain. I have a five year old device with up to date software and security patch. All I can say is thanks to these amazing developers.
yoshkapundrick said:
i am just a novice but.......I did a clean install of the 1/23 rom with the mini gapps and everything went well as expected. Wifi, calls/data, bluetooth, battery life, camera all work perfectly for my limited needs.
The only hiccup I had was in doing the the 1/30 update. When doing the update using settings, Lineage will download the update and boot to TWRP, but will not automatically install the update. Easy enough though, as I performed the update manually.
I can't complain. I have a five year old device with up to date software and security patch. All I can say is thanks to these amazing developers.
Click to expand...
Click to collapse
Did you use the addonsu*.zip file (https://download.lineageos.org/extras) to root the device. If so, did you have any problems?
No I didn't. I was only changing roms from cyanogenmod to lineage.
With 2017-02-13 nightly installed, I was able to finally performed a successful backup and restore in TWRP 3.0.2-0.
Phone was setup with a clean install using the following:
lineage-14.1-20170213-nightly-d2att-signed.zip
addonsu-arm-signed.zip
open_gapps-arm-7.1-nano-20170213.zip
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Other people I know have had this problem and some of them are on different cell providers.
I had to turn off the automatic settings and set the date and time manually.
tjensen said:
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Other people I know have had this problem and some of them are on different cell providers.
I had to turn off the automatic settings and set the date and time manually.
Click to expand...
Click to collapse
Same problem here. Also home button wake the device regardless of the setting under buttons sub menu and a very erratic compass after several attempts to calibrate.
Anyone getting "Updater process ended with ERROR 7" error with installing 20170220 update?
yoshkapundrick said:
Anyone getting "Updater process ended with ERROR 7" error with installing 20170220 update?
Click to expand...
Click to collapse
I did, so downloaded again and still the same... Wiped everything and flashed it anew; working great.... simply can't update existing rom... or so it seems...
nextmouk said:
I did, so downloaded again and still the same... Wiped everything and flashed it anew; working great.... simply can't update existing rom... or so it seems...
Click to expand...
Click to collapse
Yep, previous nightlies I could dirty flash. However, 2017-02-20 nightly I could only clean flash to install.
In TWRP:
Dalvik/ART Cache - Wipe
System - Wipe
Data - Leave
Internal Storage - Leave
Cache - Wipe
Micro SDCard - Leave
USB OTG - Leave
Dirty flash produces error
Dalvik/ART Cache - Wipe
System - Wipe
Data - Wipe
Internal Storage - Leave
Cache - Wipe
Micro SDCard - Leave
USB OTG - Leave
Clean flash produces no error
UPDATE: 2017-02-21 nightly can be dirty flashed
20170221 update works nicely in updating previous versions.
tjensen said:
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Click to expand...
Click to collapse
This is still problematic int the 2017-02-27 nightly. At least on my device, it's a time zone issue. That is, the automatic time zone setting isn't working. So, the minutes are right, but the device shows GMT instead of CST/CDT.
Everything else seems to be working, and I find Lineage OS a bit "snappier" than Oct-OS - probably because of the absence of add-ons. But, hey, it's a 4.5-year-old phone.
New TWRP version 3.1.0-0 released!
https://dl.twrp.me/d2att/
Anyone notice a moderate improvement of the compass (I had not checked in months since cm). My readings used to be wildly variable, however now it seems to be consistently off 20 degrees.
FYI: After encrypting the phone with 20170320 nightly installed, the sim card is not recognized.
First I did a CLEAN install of 20170320 nightly; sim recognized.
Next I did not make any changes except encrypted the phone; sim NOT recognized.
SIM not recognized
After the first boot on 20170328 the SIM card is recognized but once the device is rebooted the SIM card is not recognized anymore, the same with 20170320.
FYI: Posted over on reddit an inquiry on the status of the compass accuracy on our D2att LineageOS device.
https://www.reddit.com/r/LineageOS/comments/64v74o/d2att_compass_accuracy/
The d2att does not appear to be supported anymore by LineageOS.
There are no maintainers listed at https://wiki.lineageos.org/devices/d2att anymore.
And then there is this in blazing red on the page:
"The Samsung Galaxy S III (AT&T) is either unmaintained or does not meet the criteria needed for official LineageOS support status. A build guide is available for developers that would like to make private builds, or even restart official support."
If anyone has any news it would be appreciated.
tjensen said:
The d2att does not appear to be supported anymore by LineageOS.
There are no maintainers listed at https://wiki.lineageos.org/devices/d2att anymore.
And then there is this in blazing red on the page:
"The Samsung Galaxy S III (AT&T) is either unmaintained or does not meet the criteria needed for official LineageOS support status. A build guide is available for developers that would like to make private builds, or even restart official support."
If anyone has any news it would be appreciated.
Click to expand...
Click to collapse
Thanks to tjensen For posting this.
For those wondering, Yesterday (04/14/2017), I posted the following on reddit:
Samsung Galaxy S3 not supported anymore?
https://www.lineageoslog.com/14.1/d2att Unless I'm incorrect Lineage 14.1 support for d2att, d2spr, d2tmo and d2vzw has been discontinued. Can anyone confirm this?
Link to reddit post: https://www.reddit.com/r/LineageOS/comments/65diqo/samsung_galaxy_s3_not_supported_anymore/
Chuckles5150 said:
Thanks to tjensen For posting this.
For those wondering, Yesterday (04/14/2017), I posted the following on reddit:
Samsung Galaxy S3 not supported anymore?
https://www.lineageoslog.com/14.1/d2att Unless I'm incorrect Lineage 14.1 support for d2att, d2spr, d2tmo and d2vzw has been discontinued. Can anyone confirm this?
Link to reddit post: https://www.reddit.com/r/LineageOS/comments/65diqo/samsung_galaxy_s3_not_supported_anymore/
Click to expand...
Click to collapse
Just last week the d2att was ranked 89th out of 1,254 devices for the most installs of the LinageOS (according to LinageOS stats page).
With that kind of popularity and interest I thought it was safe and would always have maintainers wanting to continue the builds. :crying:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.
Hi, I have the latest CM12 installed in my tablet, but I have a lot of issues, especially when installing multiple apps or if I try to change the Launcher. It gets into boot loop and there is nothing one can do but re-flash the rom, which is pretty annoying. It has happened to me already 3 times in a short while and I am thinking of flashing LineageOS. However, I hear it is still very buggy, especially the issues with wifi. So I would like to ask which is the least buggy Rom for 7.0 v410 or if there is a way to avoid CM12 from getting the problem with boot loop.
Boot loop has been caused when trying to change Launcher (because trebuchet regularly crashes), when installing x-plore file manager and in a clean flash when I attempted to install multiple apps at the same time. In all cases it got stack in boot loop, or would start only to restart after a while, endlessly.
Finally, I opted for LineageOS 14.1.
I had the 11-11 Nightly for some time and seemed fine. Today I updated to 25-11 Nightly. It feels maybe slightly laggy, but still checking it.
I have also installed "Best WiFi Keeper" app from play store and it generally keeps me connected. However, if connection is lost (e.g at restart or if I get out of range), I have to reconnect manually. I tried few apps for reconnecting but nothing worked. It appears that although the WiFi network is seen, the tablet cannot really re-establish the connection automatically.
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Tesla works great for me. I'm running a lollipop version that's still on androidfilehost; I'm not sure if GZR ever got updated beyond 5.1 for V410.
I've had CM 14.1 (long enough ago it was still CM and not LOS) on the tablet, and it felt like it would get laggy. That could just be from junk my kid installs though, but I don't seem to have that problem with Tesla.
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
kingzones said:
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
Click to expand...
Click to collapse
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
jason2678 said:
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
Click to expand...
Click to collapse
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
xdause said:
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
Click to expand...
Click to collapse
I'm on Tesla, but it has the same base as Tipsy. I don't have data on the tablet so it isn't a 100% conclusive test, but it doesn't seem to work. The switch for USB tethering never turns on. Wifi turns on but never connects properly. My laptop does briefly show connection then disconnects with both USB and wifi tethering. It could be because there is no data connection on my tablet, but looking through dmesg on the laptop gives me the impression that something on the tablet isn't working right.
kingzones said:
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Click to expand...
Click to collapse
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
nicospanas said:
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
Click to expand...
Click to collapse
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
KLit75 said:
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
Click to expand...
Click to collapse
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
nicospanas said:
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
Click to expand...
Click to collapse
Thanks. That's more or less what I thought. From what I'm hearing there are some bugs in the roms that no doubt aren't being maintained at this late stage so I think I'll stick with stock (would be nice to have a custom recovery though.)
Not that it matters (a year later) but lots of people root with Kingroot when there isn't another option and there's several ways to remove all the bits left behind and switch it to supersu.
Thanks again!
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
kingzones said:
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
Click to expand...
Click to collapse
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
nicospanas said:
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
Click to expand...
Click to collapse
That would be great.. I shall try.. if successful, I shall post results.
I have a uk410, the US Cellular variant of the v410. I tried the CM12.1 "stable" release cm-12.1-20151117-SNAPSHOT-YOG7DAO1K5-v410.zip found here (archive.org/download/cmarchive_snapshots), along with Open GApps nano for 5.1 (opengapps.org/?api=5.1), and quickly got the infinite rebooting issue.
I then switched to the Telsa ROM mentioned earlier in this thread (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip) found at androidfilehost.com/?fid=24052804347807214, again with Open GApps nano for 5.1 (build open_gapps-arm-5.1-nano-20180922.zip), and have been running it with no issues for two days. My wifi is connected, and stays connected (tested two different routers), Play Store and apps have been working fine, and no crashes so far.
I'm using TWRP 3.1 (twrp-3.1.0-0-v410.img).
Thanks for mentioning Tesla, @jason2678 !
So like all of you I was looking for a rom to install on this v410 7" tablet, and it looks like I should just give up or stick with 4.4.2 stock if I want to go through the rooting process.
Basically all the development roms end with the same problems, wifi dropping, hostspot not working, no ir blaster, volume problems, bluetooth errors, and several hundred posts about lolipop memory leaks crippling the tablet because of only 1gb mem.
So, I am asking all of you, is there any real reason to root it, besides going back to stock 4.4.2?
And lastly, is the stock 4.4.2 kdz image that is floating around a test version, and if so is there an actual official kdz image somewhere that isn't a test image?
Thanks...
CrDroid by far in my opinion. Lineage based, 7.1.2.
Also, e/ os has been unofficially released. No Google anything...an entirely new Google list operating system by lineage. It's lightning fast and runs magisk perfectly. It's basically like nothing you've ever seen before and if you look under LG g pad 7.0 on Android file host, go to the second page and click on the last user who goes by the name anonymous and you'll find the ROM there. I had no idea what it was until my g pad boot it up and I saw the e logo. I pretty much **** myself in excitement