Develop Bugs

Installed CM 12.1 everything went fine, went to flash gapps, getting UID error

Coming from stock rooted / unlocked Touchwiz KitKat
Cm12.1 installed just fine but when I rebooted and went to flash gapps I get a non-stop error saying "there's an internal problem with your device, and it may be unstable until you factory data reset."
So I factory reset the device and even installed CM 12.1 without gapps and it still gives me this error.
Factory reset again, try my recovery and I get an error mentoning UID's being messed up (I did this and it did not help http://forum.xda-developers.com/and...on-finally-t3151579/post61729442#post61729442 ) . So I factory reset again and flashed CM 12.1 without gapps and everything is fine.
Boot into recovery and flash gapps and boom the error again. Seems like the only way to get rid of the error (After many trials and errors) is to Restore recovery -> factory reset -> flash rom. The only problem is when I also flash gapps the error comes back.
Now here is the part where I can use YOUR help, in TWRP I keep saying red text that says
"E:error opening '/data/data/com/google.android.gms/files/images/games/de7f5650'
E:error: Not a directory"
on everything I do, from formating the system to flashing a rom. I think this is where my problem lies.
Other notes: No sd card,
when CM is working, I am getting no reception (Looks like a full but has ! next to it)
When CM is working, the messaging app does not even open and just instantly closes

OK I'll break into parts I see 1: gapps 2 signal 3:msg app.
1: GAPPS
cm 12.1 is android 5.1.* so you need to verify you have correct gapps. Use gapps for 5.1 hopefully that will fix problem. Factory reset, flash cm 12.1, flash gapps 5.1, wipe dev/cache, and reboot. Should be working fine after.
2: Signal is due to rom bugs but usually due to bad/wrong apn settings or bad efs/modem pretty much all the time from my experience. So I'll break that down from easiest to the latter and hopefully we'll fix it.
a: check you apn settings and see the attachments. I'm on lte tmo so if you aren't the Google apn setting for your carrier.
b: flash back up of moden/efs
3: msg app might be fixed since gapps was installed but if not only thing I can think of is clear data/cache for msg app.
Hope I could help

these days I'd use LineageOS for the Note 3/SM-N900T (I use nightlies and my note 3 used on wifi only) I can't test the normal 2g 3g 4g or lte cuz I dont have a compatible sim card (I have a nano sim in my j7 prime so it won't fit) it takes a bigger sim so yeah......I have gapps installed for my android version and they work fine for me

BsB5068 said:
N900TUVUCNB4
Click to expand...
Click to collapse
Rolatnor said:
these days I'd use LineageOS for the Note 3/SM-N900T (I use nightlies and my note 3 used on wifi only) I can't test the normal 2g 3g 4g or lte cuz I dont have a compatible sim card (I have a nano sim in my j7 prime so it won't fit) it takes a bigger sim so yeah......I have gapps installed for my android version and they work fine for me
Click to expand...
Click to collapse
lineageos 16.0 is what I've been running on it, i needed a newer os cuz stock 5.0 was the last official version, and pokemon go was dropping support for the note 3 with stock roms, now switching to LineageOS 17.1 on my note 3 i'll update whether gapps works so you know
LineageOS Downloads
download.lineageos.org
LineageOS 17.1 is android 10

btw I have sd cards in all my spare phones 8gb normally, so I am recommending a small sd card 4gb-16gb because it makes it easier to flash roms with twrp

google play works, gmail works, yt works, sound works, flashlight works, and camera works on LineageOS 17.1
note 3 sm-n900t
i used the nano gapps from opengapps
the newest file version of lineageos 17.1 on their site

LineageOS 14 Nightlies

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:

Rooting the phone breaks cellular network

Hello.
I'm experiencing some issues with rooting. My objective: stay stock, but gain root to flash franco kernel in order to get the best out of my device
All this is happening on OOS Open Beta 12 (Android 7.1.1). I was originally on OOS 4.1.1 and done everything I listed below, and then sideloaded OOS Open Beta 12 in hopes that it would resolve the issue.
What I've done: unlock bl > reboot into android> reboot to fastboot> flash twrp> reboot to twrp> reboot to system> reboot to recovery> i notice that the twrp recovery got overriden by the stock one
i then reboot to fastboot> flash twrp again> reboot to twrp> flash supersu> reboot to system
i have root and it works perfectly, but i lose cellular network.
Flashing franco kernel didn't bring the cellular network back. My device is not encrypted as far as I can see, even though the "Encrypt phone" tooltip in settings says "Encrypted". I'm not required to enter a PIN to start booting android nor did I not need to enter it to decrpyt the phone in TWRP.
Root zip I used is: BETA-SuperSU-v2.74-2-20160519174328-forced-systemless.zip
TWRP used: official 3.1.0-0 from official TWRP site, not the one from this guide
TL;DR: As soon as I get root, I lose cellular network. Right now I can't regain cellular network unless I reflash stock OOS.
Any clues on why this is happening and how can I resolve the issue?

Nevermind, resolved the issue using these steps:
Unroot > reflash twrp > flash SuperSU-v2.79-201612051815 > reboot. Also reflashed FrancoKernel and everything seems to be working fine now.

Although everything seems to be working fine, I can't seem to get LTE. 3G is max I can get. My G3 can pick up LTE with no problems. I was able to pick up LTE with OnePlus 3 yesterday, but nothing today. I'm not sure if this is due to root + kernel change.
Is this a known issue?
Edit: I just randomly got back LTE. It was probably just a temporary issue on my side.

I know you have to allow system modifications in order for twrp to stick or flash something besides an ota.
Glad your problem was fixed!

Moto Z2 Force Lineage 17.0

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?

LineageOS/RR: AddonSU slows down device over time, Magisk messes up Wi-Fi

I tried flashing a superuser that works without side-effects, I have tried multiple. Magisk screws up the Wi-Fi, SuperSU just refuses to work, and AddonSU seems to slow down the device until it becomes unusable. I have found threads elsewhere which address the issue about Magisk messing up the Wi-Fi in one way or another, nothing on SuperSU, nor on AddonSU. I’d be really happy if I could get Magisk working properly, but I at least want one of these packages to work. I have tried all three both on LineageOS and Resurrection Remix, same results each time. Can I fix these problems?

Hey UTNT. Same boat. I've not tried as many things as you. I really don't get how this seems to have gone un-noticed. Not like WIFI is some sort of obscure use scenario lol. I'm going to try older versions of magisk.

Lineage 16 or 17?

SnowFuhrer said:
Lineage 16 or 17?
Click to expand...
Click to collapse
Hi. Lineage 16. Not sure about 17 because I've not been able to get this installed following all instructions I just get a stuck Lineage boot logo (nothing to do with MAGISK as not installed at that point.) Last night I ODIN > stock 8.0 build 5 and MAGISK does the same thing... WIFI not enableable.
Thanks!

nonsub said:
Hi. Lineage 16. Not sure about 17 because I've not been able to get this installed following all instructions I just get a stuck Lineage boot logo (nothing to do with MAGISK as not installed at that point.) Last night I ODIN > stock 8.0 build 5 and MAGISK does the same thing... WIFI not enableable.
Thanks!
Click to expand...
Click to collapse
Never had problems.
Just keep force rebooting los 17 until it boots.