Database Develop

last update binary couse a lot of problems

OnePlus cm12.1 - yesterday update to S1K2.
after intalltion everything works great UNTIL...
"su binary needs to update".
regular update passed ok.
and then:
1. tasker fail to perform a few actions that demand root (such as "sceencap -p \sdcard\folder\pic.png").
2. Titanume backup fail to backup . "rom storgage full" or somthing like this.
reintall old su zip 2.46 from recovery fixed the problems , reupdate su binary return the problems.

use one of these: http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (same install process as 2.46)

Xmaster24 said:
use one of these: http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (same install process as 2.46)
Click to expand...
Click to collapse
same problems.
flashed back to 2.46..

this is your device correct?: https://download.cyanogenmod.org/?device=bacon What build number are you on?

Xmaster24 said:
this is your device correct?:-- What build number are you on?
Click to expand...
Click to collapse
this is the device with last stable cm12.1 version:
Build number : LMY48Y
Cyanogen OS : 12.1.1-YOG7DAS2K1

bouhady said:
this is the device with last stable cm12.1 version:
Build number : LMY48Y
Cyanogen OS : 12.1.1-YOG7DAS2K1
Click to expand...
Click to collapse
Ah you are using Cyanogen OS cm's most despised OS. Seems to be they just updated to android 5.1.1. The Quality of this ROM is nowhere near the same as Cyanogenmod, could just be some broken port of 5.1.1
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
You are not running cm 12.1 you are running COS 12.1

Xmaster24 said:
Ah you are using Cyanogen OS cm's most despised OS. Seems to be they just updated to android 5.1.1. The Quality of this ROM is nowhere near the same as Cyanogenmod, could just be some broken port of 5.1.1
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
You are not running cm 12.1 you are running COS 12.1
Click to expand...
Click to collapse
But this is the official last version for OPO. isn't it suppoed to be supported?

Well technically OPO has no "official ROM" See they provide COS by default but they themselves also support other ROMs like Cyanogenmod. I highly recommend you get cm 13 it's well worth it
---------- Post added at 03:08 PM ---------- Previous post was at 03:02 PM ----------
cyanogen OS is managed by a different sector in Cyanongen Inc than Cyanogenmod which is mainly managed by independent developers and they are well known for making awful ROM's (that sector is)

Got a question to everyone, who changed their touchscreen...

After changing my touchscreen, when i flash any Adrian's builds or Helium kernel 6.1 my phone can't access recovery and touchscreen doesn't work. But when i use any Adrian's builds with Helium Kernel lower than 6.0 - everything works fine.
P.s. stock CM 12.1 Nightlies with CM kernel also work without issues
Using Adrian's AICP and Helium 5.0 - everything works good.
Any ideas?

The safest answer would be the kernel apparently doesn't support the newer touchscreen you installed. I suspect driver issues but I may be wrong

wuarx said:
After changing my touchscreen, when i flash any Adrian's builds or Helium kernel 6.1 my phone can't access recovery and touchscreen doesn't work. But when i use any Adrian's builds with Helium Kernel lower than 6.0 - everything works fine.
P.s. stock CM 12.1 Nightlies with CM kernel also work without issues
Using Adrian's AICP and Helium 5.0 - everything works good.
Any ideas?
Click to expand...
Click to collapse
Starting from Helium 6 I cleaned up the config file of the kernel to match Adrian's. This removed a lot of unnecessary drivers but it might have removed some options that made your touchscreen work properly. Previously I used a very old config file. I'll compare the two configs and try to build another kernel that supports your touchscreen.

Same issue here, in TWRP i cannot use my touchscreen. (I changed 2 digitizer, last one give this problem)
F*** ! Digitizer not working on cm12.1 :'(
2.attempt : CM14.0 - Digitizer not working
---------- Post added at 12:13 PM ---------- Previous post was at 11:46 AM ----------
Have you solved this problem ?
---------- Post added at 01:01 PM ---------- Previous post was at 12:13 PM ----------
Tomoms said:
Starting from Helium 6 I cleaned up the config file of the kernel to match Adrian's. This removed a lot of unnecessary drivers but it might have removed some options that made your touchscreen work properly. Previously I used a very old config file. I'll compare the two configs and try to build another kernel that supports your touchscreen.
Click to expand...
Click to collapse
Is there any solution for this ?

Iekuta said:
Is there any solution for this ?
Click to expand...
Click to collapse
This issue has been fixed by Adrian ages ago.

Tomoms said:
This issue has been fixed by Adrian ages ago.
Click to expand...
Click to collapse
i wonder what the heck is going on with my screen.
I was on 4.1.2 , waiting STRYFLEX 2.0.
I changed my digitizer 3 days ago. No problems in 3 days.
But this morning, the screen go a little crazy (touched 3-4 times itself randomly ), but i did not care so much.
After that, i reboot to recovery /to install and try Sailfish OS.
But after Fastboot flash TWRP 3.0.2 /// BAMM BOOM %#$!!
The screen is not working anymore. I will try to reflash the stock with Flashtool.
and thanks for the reply
---------- Post added at 03:19 PM ---------- Previous post was at 02:41 PM ----------
I tried 4.3 but again, no response from digitizer.
Will flash 4.1.2 and make sure that the screen is completely gone

Lineage 15.1 update for Moto Z2 Force

Just saw this on the xda front page, thought I'd post it here:
https://www.xda-developers.com/lineageos-15-1-supports-a-b-devices-moto-z2-force/
Sent from my Moto Z (2) using Tapatalk

Yes. Also: erfan has almost completely got treble working for our device. Twrp had an overhaul as well

@Uzephi do you have downloads for twrp?

this is great news i was playing with the vendor partition on these phone and was not able to get the gsi to load until i started modding the version of twrp i was running with red wolf recovery additions. it booted but was not usable as the device did not like something in my work around and gave up on it i was just going to wait for the Z3 but now i think this phone will stay in my pocket even longer.

cervantesjc said:
@Uzephi do you have downloads for twrp?
Click to expand...
Click to collapse
Check erfanoabdi's AFH. All his experimental releases are there. There is a treble one (a bunch of stuff broken, on back burner for now) and one that supports password decryption. Cannot flash current builds with it though.
Edit: warning. Experimental means no support and most likely things are broken, like flashing ROMs explained for the test twrp. It does decrypt 8.1 ROMs correctly though

Looks like an experimental build has been posted.
https://download.lineageos.org/nash

nightly 15.1
https://download.lineageos.org/nash

...
if I flash these roms I will not have problems with the imei when returning to stock?
---------- Post added at 06:13 PM ---------- Previous post was at 06:08 PM ----------
Is this rom better than the stock? because the stock is incredible and it works perfectly for me. I'm only interested in installing this rom since it's the only way I can get rid of the bloatware and make it work in sprint.

EddiePR said:
if I flash these roms I will not have problems with the imei when returning to stock?
---------- Post added at 06:13 PM ---------- Previous post was at 06:08 PM ----------
Is this rom better than the stock? because the stock is incredible and it works perfectly for me. I'm only interested in installing this rom since it's the only way I can get rid of the bloatware and make it work in sprint.
Click to expand...
Click to collapse
I've been using LOS for quite a bit now, and it's great, and to answer your question, YES, it is better than stock, battery life is better, smooth and responsive, the only drawback for some people, is that audio motomods don't work on the ROM and probably never will, but highly recommended if you want a clean android experience.

cervantesjc said:
I've been using LOS for quite a bit now, and it's great, and to answer your question, YES, it is better than stock, battery life is better, smooth and responsive, the only drawback for some people, is that audio motomods don't work on the ROM and probably never will, but highly recommended if you want a clean android experience.
Click to expand...
Click to collapse
I would not be so pessimistic on that. There's a small but possible chance, once they force the Treble on, that someone else may be able to figure out the Audio Motomods.

Flashed Nightly 15.1 following steps in their official website and ended up with a brick....But I found a blankflash through port 9008 to recover.
It`s possible that I missed the fastboot -w step.

Unseeablething said:
I would not be so pessimistic on that. There's a small but possible chance, once they force the Treble on, that someone else may be able to figure out the Audio Motomods.
Click to expand...
Click to collapse
Unless motorola releases the audio drivers for their motomods, I find it kinda impossible, because it seems that those drivers are closed source, treble will help with future development but I really doubt we'll see audio mods working.

I was using the last nightly until yesterday when I found out that the microphone on video calls was not working, so I had to come back to stock.

Is this the newest update?? i'm still on June 18th. i usually get notified on my phone but for some reason not getting any and when i check for updates it fails????

HugeUFO said:
Flashed Nightly 15.1 following steps in their official website and ended up with a brick....But I found a blankflash through port 9008 to recover.
It`s possible that I missed the fastboot -w step.
Click to expand...
Click to collapse
Me too, but I got it working following other AOSP installs.
Flashall
Bootloader and then Fastboot into TWRP
Wipe Cache, Data, System
Install to A
Install to B
Reboot to Bootloader, run the fastboot -w
(optional) Fastboot into TWRP, Install GAPPs
(optional Magisk)
Boot into the system, do not add your accounts or anything.
Skip past everything, only selecting the reporting and bug logs you want on.
Boot back into the Bootloader, and fastboot TWRP
Install Magisk, and preferably go to Magisk Manager and Magiskhide Google Play Store and Google Framework Services before adding accounts.
---------- Post added at 11:09 AM ---------- Previous post was at 11:07 AM ----------
blake .l said:
Is this the newest update?? i'm still on June 18th. i usually get notified on my phone but for some reason not getting any and when i check for updates it fails????
Click to expand...
Click to collapse
Well, that might've been an experiment release? I know the July 3rd one is a nightly.

Anyone able to get volte working on the latest nightly (20180703)?

[discussion] reducing risks when trying treble

Hi,
It seems noone so far tryed to flash a treble GSI to the redmi 6. Im courious in doing this, but would like to discuss potential risks. What could go wrong?
After some reading i found the possibility that devices get problems running Google Apps, since they we're not certified.
To prevent this, you can register your Google Services ID in your Google Account.
1) Install the App "device ID" from Playstore, run it and copy the GSF.
2) Open this Page and paste your GSF. Click register, and your done.
Another thing is that there are two types of GSI Updates.
Type A/B and Type A. I ran the App "treble Check" from Playstore and it tells me that the redmi 6 ist treble supported and that I need the Type A GSI
Then it seems necessary to remove magisk/superSu/xposed to have a clean boot Image.
Loosing data is no problem for me.
Anyone any suggestions?

Tell us what works and what doesn't work.
---------- Post added at 12:16 PM ---------- Previous post was at 12:15 PM ----------
You use the TWRP in test ?

..i will not flash until i'm pretty Sure, nothing will go wrong.
I would like to understand what ist technicaly done.
After what i've read, its a normal fastboot flash, of the system partition. So, am I still able to run TWRP If anything goes wrong?
I guess the way to go, is to do a clean Fastboot flash of the official MiUi10 in advance to make sure my boot/ramdisk is clean. Then I would reflash TWRP and last the GSI.
What do you think?
(beside from 'let others risk their phone')

use this link for reference:
https://youtu.be/YI2CtIIPVaI

please, which treble GSI AOSP rom (8.1 or 9.0) advised with the most things working (calls, camera, fingerprint, sound...)??
thanks

i think Android 8.1 gsi rom is more stable as of now.
if u want to flash gsi rom
1. unlock bootloader by official way
2. flash twrp
3. do a factory reset in twrp
4. flash rom.
that's all.

nobody has tested yet?
no feed back on what's working and what doesn't?

I think i am gonna test soon, just gotta get some info... i was flashing intesively lot of phones in past, but now i had pause few years... seems lot of things changed - treble?! whaat?!
I just got this redmi 6, although i wanted 5, and seems it was big mistake, but nonetheless im gonna try and see. I dont remember any phone with 0 info and 0 feedback few years back.

snoerme said:
..i will not flash until i'm pretty Sure, nothing will go wrong.
I would like to understand what ist technicaly done.
After what i've read, its a normal fastboot flash, of the system partition. So, am I still able to run TWRP If anything goes wrong?
I guess the way to go, is to do a clean Fastboot flash of the official MiUi10 in advance to make sure my boot/ramdisk is clean. Then I would reflash TWRP and last the GSI.
What do you think?
(beside from 'let others risk their phone')
Click to expand...
Click to collapse
I Android world, if you experience like this, always something goes wrong. It's about testing what works, what doesn't. If you do things like these, you can't rely on stability anymore

snoerme said:
It seems noone so far tryed to flash a treble GSI to the redmi 6. What could go wrong?
Click to expand...
Click to collapse
Hey there everyone!
Since there are no custom ROM's currently available for our Redmi 6, i decided to give GSI ROM's a try. I tried los 15.1, and it worked! Wifi, bt, and even camera work. The only problem: The radio's don't work, so you cant make calls / sms /data. Other then that, the ROM is super fast and speedy. Also, there are no GApps and its not certified, so we gotta certify it I've tried only Lineage, but you can also try RR, HavocOS etc.
BTW, the Redmi 6 is ARM and A only.

Feedback from GSI Lineage OS
Hey Everyone!
I recently tried Lineage OS 15.1 GSI, and I've made a thread with all you wanna know here:
https://forum.xda-developers.com/redmi-6/how-to/rom-gsi-lineage-os-redmi-6-t3915146
---------- Post added at 12:41 PM ---------- Previous post was at 12:36 PM ----------
bilatche said:
Tell us what works and what doesn't work.
---------- Post added at 12:16 PM ---------- Previous post was at 12:15 PM ----------
You use the TWRP in test ?
Click to expand...
Click to collapse
Hey there !
Since there are no custom ROM's currently available for our Redmi 6, i decided to give GSI ROM's a try. I tried los 15.1, and it worked! Wifi, bt, and even camera work. The only problem: The radio's don't work, so you cant make calls / sms /data. Other then that, the ROM is super fast and speedy. Also, there are no GApps and its not certified, so we gotta certify it I've tried only Lineage, but you can also try RR, HavocOS etc.
https://forum.xda-developers.com/redmi-6/how-to/rom-gsi-lineage-os-redmi-6-t3915146
---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
snoerme said:
..i will not flash until i'm pretty Sure, nothing will go wrong.
I would like to understand what ist technicaly done.
After what i've read, its a normal fastboot flash, of the system partition. So, am I still able to run TWRP If anything goes wrong?
I guess the way to go, is to do a clean Fastboot flash of the official MiUi10 in advance to make sure my boot/ramdisk is clean. Then I would reflash TWRP and last the GSI.
What do you think?
(beside from 'let others risk their phone')
Click to expand...
Click to collapse
You don't need to fastboot flash the img, you can use TWRP too. And yes, TWRP works if anything goes wrong and worst case use Mi flash and rescue your phone. I tried los 15.1, here are my thoughts: https://forum.xda-developers.com/redmi-6/how-to/rom-gsi-lineage-os-redmi-6-t3915146
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
bilatche said:
please, which treble GSI AOSP rom (8.1 or 9.0) advised with the most things working (calls, camera, fingerprint, sound...)??
thanks
Click to expand...
Click to collapse
Imo, this (https://forum.xda-developers.com/redmi-6/how-to/rom-gsi-lineage-os-redmi-6-t3915146) boots and works, but no calls :crying: If you want calls you'll need cereus's drivers. Don't expect everything to work with GSI.
---------- Post added at 12:49 PM ---------- Previous post was at 12:47 PM ----------
bilatche said:
nobody has tested yet?
no feed back on what's working and what doesn't?
Click to expand...
Click to collapse
Hey there !
Since there are no custom ROM's currently available for our Redmi 6, i decided to give GSI ROM's a try. I tried los 15.1, and it worked! Wifi, bt, and even camera work. The only problem: The radio's don't work, so you cant make calls / sms /data. Other then that, the ROM is super fast and speedy. Also, there are no GApps and its not certified, so we gotta certify it I've tried only Lineage, but you can also try RR, HavocOS etc.
https://forum.xda-developers.com/red...dmi-6-t3915146
---------- Post added at 12:51 PM ---------- Previous post was at 12:49 PM ----------
vasillek said:
I think i am gonna test soon, just gotta get some info... i was flashing intesively lot of phones in past, but now i had pause few years... seems lot of things changed - treble?! whaat?!
I just got this redmi 6, although i wanted 5, and seems it was big mistake, but nonetheless im gonna try and see. I dont remember any phone with 0 info and 0 feedback few years back.
Click to expand...
Click to collapse
Hey there !
Since there are no custom ROM's currently available for our Redmi 6, i decided to give GSI ROM's a try. I tried los 15.1, and it worked! Wifi, bt, and even camera work. The only problem: The radio's don't work, so you cant make calls / sms /data. Other then that, the ROM is super fast and speedy. Also, there are no GApps and its not certified, so we gotta certify it I've tried only Lineage, but you can also try RR, HavocOS etc.
https://forum.xda-developers.com/red...dmi-6-t3915146 Btw, the Redmi 5 is better. Bigger screen, faster Snapdragon gpu, ir blaster etc
---------- Post added at 01:01 PM ---------- Previous post was at 12:51 PM ----------
anish sk said:
i think Android 8.1 gsi rom is more stable as of now.
if u want to flash gsi rom
1. unlock bootloader by official way
2. flash twrp
3. do a factory reset in twrp
4. flash rom.
that's all.
Click to expand...
Click to collapse
Hey which gsi rom is the best in your opinion?

snoerme said:
Hi,
It seems noone so far tryed to flash a treble GSI to the redmi 6. Im courious in doing this, but would like to discuss potential risks. What could go wrong?
After some reading i found the possibility that devices get problems running Google Apps, since they we're not certified.
To prevent this, you can register your Google Services ID in your Google Account.
1) Install the App "device ID" from Playstore, run it and copy the GSF.
2) Open this Page and paste your GSF. Click register, and your done.
Another thing is that there are two types of GSI Updates.
Type A/B and Type A. I ran the App "treble Check" from Playstore and it tells me that the redmi 6 ist treble supported and that I need the Type A GSI
Then it seems necessary to remove magisk/superSu/xposed to have a clean boot Image.
Loosing data is no problem for me.
Anyone any suggestions?
Click to expand...
Click to collapse
Don't know bro, since your post was 5 years old but here it is showing arm32_binder64_ab_system.img or a64_system_ab.img will work fine...
i.e in short Android 13 gsi will definitely gonna work

killerboychetan said:
Don't know bro, since your post was 5 years old but here it is showing arm32_binder64_ab_system.img or a64_system_ab.img will work fine...
i.e in short Android 13 gsi will definitely gonna work
Click to expand...
Click to collapse
I actually still Use this phone and am happy about your reply. Waited for IT about 5 years These days i will not find time to give it a try, but i will report if this changes.. Hopefully not in 5 years "

How do I update Lineage OS?

Hi,
can anyone tell me how I can update Lineage OS and the custom google apps?
I'm on the 20191214 Build and want to update to the new build and updated custom google apps.
If I do it like in the OP on the Rom section on xda, google apps and play store don't work anymore.
Thanks in advance.

I tell you not to use this lineage. It's just a bugged and patched GSI, use a pure gsi that's better, it could be havoc or arrowOS. Or better yet, use miui.eu.

NaassomDourado said:
I tell you not to use this lineage. It's just a bugged and patched GSI, use a pure gsi that's better, it could be havoc or arrowOS. Or better yet, use miui.eu.
Click to expand...
Click to collapse
That is your opinion and does not help anyone here.
Further, I have updated to the latest version myself and am now facing issues with google play services and SELinux, that I haven't had before.
Perphaps someone that managed to updated successfully can give a short how-to or step-by-step guide ?

LMAO
NaassomDourado said:
I tell you not to use this lineage. It's just a bugged and patched GSI, use a pure gsi that's better, it could be havoc or arrowOS. Or better yet, use miui.eu.
Click to expand...
Click to collapse
Just FYI :
Patch = Device Tree
I created the full device tree for pyxis (100%) from day 0, but i will never share it with anyone here because most of users are ungrateful and disrespectful !
Cheers
---------- Post added at 09:29 PM ---------- Previous post was at 08:54 PM ----------
druschlan said:
That is your opinion and does not help anyone here.
Further, I have updated to the latest version myself and am now facing issues with google play services and SELinux, that I haven't had before.
Perphaps someone that managed to updated successfully can give a short how-to or step-by-step guide ?
Click to expand...
Click to collapse
If you see SELinux (red) disabled in Trust option, it's because the kernel is permissive. It's normal, don't worry !
For Google Services, if you are using titanium backup or a decrypt.zip you will have errors : always use a TWRP crypted backup for your data ! If you are not using TB, check permissions for GServices on the app manager (give all authorizations !)
This is for my help, if you need more, grab a logcat !

gringo80 said:
Just FYI :
Patch = Device Tree
I created the full device tree for pyxis (100%) from day 0, but i will never share it with anyone here because most of users are ungrateful and disrespectful !
Cheers
---------- Post added at 09:29 PM ---------- Previous post was at 08:54 PM ----------
If you see SELinux (red) disabled in Trust option, it's because the kernel is permissive. It's normal, don't worry !
For Google Services, if you are using titanium backup or a decrypt.zip you will have errors : always use a TWRP crypted backup for your data ! If you are not using TB, check permissions for GServices on the app manager (give all authorizations !)
This is for my help, if you need more, grab a logcat !
Click to expand...
Click to collapse
In regard to logcat, what line/info do you need here?