Dirty flashed lineage-14.1-20170116-UNOFFICIAL-oneplus3 over cm-14.1-20161225-NIGHTLY-oneplus3 with recommended Unofficial TWRP 3.0.3-0 touch recovery for OnePlus 3. So far no problems.
I assume the UNOFFICIAL in the zip name is uncorrect for the thread is named OFFICIAL. [ROM][Official] LineageOS 14.1 for OnePlus 3
*edit* It's unofficial because the builds are dianlujitao's personal builds and not yet the official weeklies.
Is this build has SU/root enabled? I saw the latest changelog that SU is now disabled by default.
After dirty flashing another nightly build I lost root totally. Trying to flash SuperSU doesn't help (failed at "Extracting ramdisk")
sunng87 said:
Is this build has SU/root enabled? I saw the latest changelog that SU is now disabled by default.
After dirty flashing another nightly build I lost root totally. Trying to flash SuperSU doesn't help (failed at "Extracting ramdisk")
Click to expand...
Click to collapse
There's still the "Root access" option in Developer options and I can do "su -" in a terminal. So yes, root is still enabled but I never flashed SuperSU, I'm using the built in root manager.
Will any ROM, other than stock, ever offer VoWiFi and VoLTE? Stock has these features.
magic242 said:
There's still the "Root access" option in Developer options and I can do "su -" in a terminal. So yes, root is still enabled but I never flashed SuperSU, I'm using the built in root manager.
Click to expand...
Click to collapse
Maybe the change will comes to jianlujitao's build tomorrow (or never, because su can be enabled at build time)
Update: I updated my twrp to dianlujitao's 3.0.3 and I can successfully flash SuperSU. Now root is back! YAY!
No LTE after second boot
All,
I have a really weird problem with lineageOS lately. I clean flashed jianlujitao's (20170120) and flo017's (20170116) built, both show the same issue: after the first boot and doing the initial setup, the phone connects to LTE without problems. If I reboot directly after the initial setup, I don't touch any settings or do anything else, just reboot directly, the phone doesn't connect to LTE anymore. It only connects to H+.
Nothing else flashed but clean lineage, no gapps, no SuperSU or anything.
Tried to force LTE in the settings by choosing LTE only, but then it doesn't connect to cellular network at all. Deleted the APN, no change.
With Experience ROM by jamal2367 (OOS based) everything works fine!
What could be wrong here? I hope someone has an idea. I want to go back to lineage! :crying:
Cheers
I figured a workaround today. Changed Sim Card Slots to have the one for Data in Slot 1. Doesn't solve the root cause, but works now. :good:
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
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
ZeitgeistGlee said:
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
Click to expand...
Click to collapse
Try this:
https://forums.oneplus.com/threads/...-3-3t-and-go-back-completely-to-stock.456232/
ZeitgeistGlee said:
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Read his second post. Wrong TWRP version may lead to this. 3.2.3.1 encryption issues.
Is had the same issue, i ended up with a fastboot installation. Al is working again.
I decided to install LineageOS 16.0 on my Galaxy A3 2017 (SM-A320FL). However, after flashing it, OpenGApps, and the SU addon, I could no longer access the Wi-Fi. When I turned it on, it would turn itself back off. After a reboot, it worked fine. After another reboot, it wouldn't work again. Rebooting it more times wouldn't fix it. I tried reflashing it, same results. I tried reflashing it again, but no difference. How can I fix it?
EDIT: I also noticed that occasionally, I get an issue that when the device is put into sleep mode, after a few minutes of standby it will refuse to wake up. Could this be a related problem?
EDIT 2: I discovered that it was Magisk causing the issue (flashing Magisk instead of AddonSU allowed me to replicate the issue, the build where the bug occured had Magisk embedded), but I'd quite like to be able to use Magisk instead of AddonSU. Any way to make it compatible?
Has anyone tried Lineage 17.0 with Android 10.0? I have seen on lolinet
But I don't pretty sure if it's working actually,
Actually I can't test it but I wonder that someone here could prove and tell us how is working this rom
mirrors.lolinet. com/firmware/moto/nash/custom/lineage/ l
Just got done installing it, and reinstalling twrp and magisk. It works. I had to sideload it and then when rebooting to recovery, it took me to stock android recovery. I tried to reboot system and it wouldn't- it took me back to stock recoverty. I factory reset and then it booted lineage 17. Right now I'm trying to get a compatible gapps installed. Overall looks promising. New features available in developer options
Edit: Gapps nano installed, this rom has good 3d graphics- 4120 on passmark 3d test. Not sure what kernel it uses but so far no complaints. Cellular radio and wifi both work. Cricket network shows as ATT (which it actually is) and getting LTE speeds.
way2aware said:
Just got done installing it, and reinstalling twrp and magisk. It works. I had to sideload it and then when rebooting to recovery, it took me to stock android recovery. I tried to reboot system and it wouldn't- it took me back to stock recoverty. I factory reset and then it booted lineage 17. Right now I'm trying to get a compatible gapps installed. Overall looks promising. New features available in developer options
Edit: Gapps nano installed, this rom has good 3d graphics- 4120 on passmark 3d test. Not sure what kernel it uses but so far no complaints. Cellular radio and wifi both work. Cricket network shows as ATT (which it actually is) and getting LTE speeds.
Click to expand...
Click to collapse
Awesome! I'll be testing it too, had you installed from another Lineage rom?
I'm on stock rom (I've been trying another's based on Lineage rom but actually came back to stock)
Danniel_GR said:
Awesome! I'll be testing it too, had you installed from another Lineage rom?
I'm on stock rom (I've been trying another's based on Lineage rom but actually came back to stock)
Click to expand...
Click to collapse
I was coming from the stock tmobile rom. latest firmware. And like you, had a custom rom installed previous to that, it was crDroid, I believe.
way2aware said:
I was coming from the stock tmobile rom. latest firmware. And like you, had a custom rom installed previous to that, it was crDroid, I believe.
Click to expand...
Click to collapse
I decided to go back to stock, everything worked except Bluetooth, well, Bluetooth was partially functional, the only problem was that I couldn't listen to music with my Bluetooth headphones, it was a little disappointing Jaja ):
way2aware said:
Just got done installing it, and reinstalling twrp and magisk. It works. I had to sideload it and then when rebooting to recovery, it took me to stock android recovery. I tried to reboot system and it wouldn't- it took me back to stock recoverty. I factory reset and then it booted lineage 17. Right now I'm trying to get a compatible gapps installed. Overall looks promising. New features available in developer options
Edit: Gapps nano installed, this rom has good 3d graphics- 4120 on passmark 3d test. Not sure what kernel it uses but so far no complaints. Cellular radio and wifi both work. Cricket network shows as ATT (which it actually is) and getting LTE speeds.
Click to expand...
Click to collapse
can you explain the step for installation with gapps? did you just install rom then restart recovery then install nano gapps? and gapps for 9 o 10 android?