Related
Last Update : August, 19, 2014
Hi,
I'm still try to bypass the MMU protection.
I have fixe a lot of bug, like memory misalignment, bad adresses allocation, dtb correction, etc...
Last sources and binaries here :
kexec-tools V11.zip : http://forum.xda-developers.com/attachment.php?attachmentid=2902912&stc=1&d=1408401794
kexec-tools binaries V11.zip : http://forum.xda-developers.com/attachment.php?attachmentid=2902913&stc=1&d=1408401794
Sorry, i have always 13 sec reboot after new kernel boot.
"cpu_proc_fin" use a "mcr p15" to init cache and proc that cause freeze.
I try to find solution for that.
Last Update : June, 22, 2014
Hi,
My sources are horrible... but i give something new.
This kexec is for stock kernel only (tested on .757). I thinks theses sources work on other kernel too.
In "kexec-tools V10.zip", you have all my sources. It's highly recommended to mod them to have something OK.
In "kexec binaries.zip", you have binaries to install
=> "kexec_load.ko" and "procfs_rw.ko" must be placed in "/system/lib/modules" folder with "chmod 777"
=> "kexec" must be placed in /system/bin" folder with "chmod 777"
=> cd /system/lib/modules
=> insmod kexec_load.ko
For sources :
Mod and adapt all you want, it's free.
You have 2 scripts in Zip : "./compil-kexec" in "kexec-tools" folder to rebuild and send in device directly (install Adbtcp on device and send by tcp with : adb connect xxx.xxx.xxx.xxx) = work perfectly with me.
"scriptZ1" is for compil stock kernel or another kernel (doomlord kernel for eg)
You must rename "custom_final_files" folder after compil to "final_file" manually ; You can have guest kernel in "custom_final_files" and stock kernel in "final_files" for "kexec-tools" path ... Don't mix a guest and host kernel please ^^
I am tired... i let you test and say if it's ok for you...
Thank a lot to munjeni for his help.
kexec-tools V10.zip : http://forum.xda-developers.com/attachment.php?attachmentid=2811994&stc=1&d=1403456181
kexec binaries.zip : http://forum.xda-developers.com/attachment.php?attachmentid=2811995&stc=1&d=1403456181
Last Update : November, 23, 2013
Hi,
For few days now, i haven't no more kernel panic with my kexec.
I have fixed few stuffs into sources, and add a lot.
These adds are, to include a "dt.img" image file into kexec load process.
This image file is a "device_tree" image to match hardware to software.
So, i assume to don't include atags into boot process, but pass bootloader informations by this DT.
I have programmed a little scan memory to found dynamicly all magic tags, because i found 3 device_tree into memory (magic is "0xd00dfeed").
These 2 device_tree are echo from first and nice structure.
The boot process need to have informations from this DT, and need all informations to initialize hardware (no HDW initialisation by the kernel)
I must first fix issues ; Regroup zImage and dt.img into memory to load a solid bloc to kexec_load module to boot into, and second, fix an offset i can't explain, 0x800 in memory causing misalignment memory
Keep tuned..
Last Update : November, 17, 2013
Hi everybody,
My kexec-tools work for Sony Xperia Z1 stock kernel "3.4.0-perf"
This tools can work on all locked bootloader for all locked device, not only Sony or Z1 models.
This kexec-tools add a kexec_load kernel module (LKM) and use a driver to grant a communication between "kexec" user program and kexec_load.ko module
what is for ?
"kexec" user program load in memory a custom kernel in zImage format, but can load ".tar" image too
This user tool load ramdisk in memory if necessary
This tool is for this purpose only, and don't keep in memory the custom kernel at device reboot.
It is a "user" program, not a "kernel" extension... So, to really do the magic, we need the host kernel (stock sony locked kernel) have a kexec_load capability to reboot in a new gest kernel (custom kernel).
Infortuntly, stock kernel don't have kexec_load capability.
Sony have compiled his stock kernel without this option, and "standard" kexec-tools "need" this option to work.
To see all system call capability of kernel, you can run theses command :
Code:
echo 0 > /proc/sys/kernel/dmesg_restrict
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms
Do all grep you want here.
The "echo 0" "restrict" is here to unmask logical adresses to "system calls"
Like you can see, "__NR_kexec_load" capability isn't here.
To add kexec_load capability in stock locked kernel, we need to add manualy a kernel module wich add this function into the kernel.
Why ? Because the way to keep in memory a custom kernel need to know a lot of parameters, and keep a specific memory range alive at reboot.
Only kernel can do this.
All user program will be terminated at reboot.
"Standard" kexec_load.ko module use a method to implement the "__NR_kexec_load" function in system call table.
Since 2.6.0 kernel, linux for security reason, have locked in memory the "system_call_table" ; No more add or modification is authorized.
If kexec tool try to add a value, "kexec_load" for us, we causes a kernel panic, and reboot device.
For this reason, i have modify kexec user program and kexec_load module to implement a driver to talk to each other.
this driver replace syscall method, and we no more need to use a system call table.
For this reason, this tool is now compatible with modern kernel like our "3.4.0"
For this reason, this tool must work for other device (Xperia X, P, S, etc...) and another brand
For this reason, if kernel is locked, we can bootstrap to run a new kernel.
Installation
First, you can compil your own kexec tool
Here, sources : http://forum.xda-developers.com/attachment.php?attachmentid=2397299&stc=1&d=1384689174
And here, the binaries : http://forum.xda-developers.com/attachment.php?attachmentid=2397305&stc=1&d=1384689406
(it's not a cwm zip, i have no time to create an installer for now ; use "./compil-kexec" if you want an automatic install)
Install *.ko in /system/lib/modules
Install kexec and kdump in /system/bin
Grant with "chmod 777"
Unzip in kexec-tools folder
Install a toolchain (sudo apt-get install gcc-arm-linux-gnueabi)
launch => ./compil-kexec
what's all
This script can do everythinks for you
- Compilation of tools
- Compilation of modules
- installation in device
This script can compil for every brand you have.
Except you must remove or adapt the patch (see below why)
Patch ??
This patch is because a module must be compiled in the same time the kernel himself.
For this reason a "vermagic", an identifier, is used by system to block every module not compil with kernel
Some custom kernel bypass this to authorize every modules.
But for stock kernel, it is not allowed.
You can easely strapp this by busybox.
"busybox modprobe" for help
"-f" to force load without vermagic
To see this vermagic :
Code:
# uname -r
This "uname -r" must be the same that
Code:
# strings kexec_load.ko | grep vermagic
vermagic=3.4.0-perf-g66807d4-02450-g9a218f1 SMP preempt mod_unload modversions ARMv7
If you want use automaticaly this vermagic, you can modify into the custom kernel this file :
Code:
"include/config/kernel.release" and add :
"3.4.0-perf-g66807d4-02450-g9a218f1"
This file will be use at module compil to match the vermagic.
Infortunatly, it is not enought. :silly:
The infamous "no symbol version for module_layout"
When a module compil is created, it use symbols link to system call function, translate by adresses
Theses symbols are not at same physical adresses in stock kernel and modules (compiled from DooMLoRD kernel).
So, theses adresses must be convert into modules itself to match with stock symbols adress.
A patch is needed.
If you use my script, modules are automatically patched.
Here patches :
Code:
sed -i 's/\x32\x76\x86\x29/\x72\xFF\x5E\x20/' procfs_rw.ko
sed -i 's/\x32\x76\x86\x29/\x72\xFF\x5E\x20/' kexec_load.ko
sed -i 's/\xBB\xD0\xF8\x4D/\x0E\x1C\x63\x77/' kexec_load.ko
sed -i 's/\xA6\x26\x81\x1A/\xD4\x56\x02\x7E/' kexec_load.ko
sed -i 's/\xA3\xD1\xEC\x96/\xEC\x43\x28\x1A/' kexec_load.ko
sed -i 's/\x8C\xE6\x6A\x5F/\x3D\xDF\x02\xF2/' kexec_load.ko
sed -i 's/\x3E\xF3\xEF\xE9/\x18\x7F\xA6\x8A/' kexec_load.ko
sed -i 's/\x8B\xD2\x92\x10/\xC8\x19\x08\x9C/' kexec_load.ko
sed -i 's/\x1C\xE8\x18\xE1/\x7C\x71\x9E\xEF/' kexec_load.ko
sed -i 's/\xAB\x2C\x2F\x8B/\x8E\xD7\x63\xC0/' kexec_load.ko
sed -i 's/\xF5\x62\xAA\x4B/\x34\x80\x1B\x74/' kexec_load.ko
sed -i 's/\x00\x52\xD6\xD7/\x6F\x80\x91\x20/' kexec_load.ko
sed -i 's/\x4F\x77\x57\x6A/\x0C\x57\xC7\x63/' kexec_load.ko
sed -i 's/\xCA\x2F\x65\x71/\x92\xB8\x7F\x53/' kexec_load.ko
sed -i 's/\x0F\xD0\xA0\x91/\xFA\x80\x15\xB4/' kexec_load.ko
sed -i 's/\x29\xA0\x6D\x48/\x6C\x6B\x96\x54/' kexec_load.ko
sed -i 's/\x6D\x1F\x1F\x37/\xCC\x5E\x79\x8B/' kexec_load.ko
sed -i 's/\xFD\x23\xD0\xFB/\xE3\xE3\x68\x52/' kexec_load.ko
You can use hexedit or hexdump to see these adresses :
Code:
hexdump kexec_load.ko | grep ff72
0003d50 b0b0 80ac ff72 205e 6f6d 7564 656c 6c5f
how does it work ?
# kexec --help
For kexec help... nothing more to say.
# lsmod
List loaded modules... You must see
kexec_load 31369 0 - Live 0x00000000 (O)
# rmmod kexec_load.ko
Remove kexec_load module from memory.
# grep kexec /proc/device
To see installed driver.
You must see :
100 kexec_driver
First number is "major" number to identify your driver in system.
# mknod /dev/kexec_driver c 100 0
Install driver.
Major number (here 100), is important for module.
This Major must be the same between module and driver.
By default, 100 is used.
# insmod kexec_load.ko
To install "LKM", kexec_load kernel module.
If another Major is needed, you can use "insmod kexec_load.ko 101" for Major 101
You can use "modprob" if you want, but you must configure the module folder.
How kexec and module exchange informations ?
By the driver.
Normal output for a kernel module is to write in "dmsg" file.
To see kernel output, launch this command :
Code:
# dmesg
To see last kernel log, see in :
Code:
# cat /proc/last_kmsg
For kexec module, this normal way still exist, and give a lot of informations, but to speak with, you must use the driver.
/dev/kexec_driver
You can yourself test communication:
Code:
# cat /dev/kexec_driver
You can send kernel by this communication channel.
Type following commands for help
=> echo help >/dev/kexec_driver
=> dmesg | grep Kexec
Code:
# echo help >/dev/kexec_driver
# cat /dev/kexec_driver
Last command : 'help'
Please type following command :
=> dmesg|grep Kexec
Every command send into driver is receive by kexec_load.ko module and running into the kernel.
The answer can by read thru the driver
Here, you can see that normal way to see messages is allway dmesg.
Code:
# dmesg|grep Kexec
<4>[15050.521628] Kexec: Starting kexec_module...
<6>[15050.521656] Kexec: kexec_driver_contener allocation
<6>[15050.521673] Kexec: kexec_memory_buffer allocation
<4>[15050.521691] Kexec:----------------------------------------------------
<4>[15050.521710] Kexec: kexec_driver created with major : '100'
<4>[15050.521728] Kexec: Please, prepare by typing the following commands :
<4>[15050.521746] Kexec: => mknod /dev/kexec_driver c 100 0
<4>[15050.521761] Kexec: => cat /dev/kexec_driver
<4>[15050.521775] Kexec:-----------------------------------------------------
<4>[15050.521791] Kexec: For help
<4>[15050.521803] Kexec: => echo help >/dev/kexec_driver
(...)
I have add a lot of informations to help to configure kexec.
rdtags, atags ??
Not sure for this part of kernel.
"atags" is the most used method to bootloader to parse commands and informations to kernel at boot.
"atags" is a form of structure in memory to organise informations.
At boot, a address chain is created and can be compulse in /proc/atags file.
This file is read only system.
"rdtags" is another way to bootloader to parse information to kernel.
"rdtags" is not stocked in "/proc"
But, as i see, stock kernel can use "atags" from bootloader.
kexec can substitute bootloader function to create fromscratch a atags chain, and parse to new kernel.
I have change this part to stock atags in "/data/atags", and reuse or change if need.
If this don't work, i must create a rdtags chain to replace atags ; It's not a hard work.
Status
For the moment, kexec tools works.
=> Phase one OK.
I can start Phase Two : new kernel patch.
If you want to help me...
Actually, load a custom kernel and boot into with kexec tools work.
But at boot into, a kernel panic occurs.
It seems, a part of kexec patch is missing in custom kernel.
Hi new thread created for kernel kexec development.
Status: not working: wrong values for mem defines under the kernel is giving segmentation fault as its attempting to write to memory areas that are currently being used byyyyy the system
Instructions:
Make kernel compatible?:
1. Download kernel diff patch from below
2. Terminal - diff patch > diff.txt
How to use:
1. Download kexec-tools (kexec binary) from below
2. Copy into system/bin directory and give it executable permission
3. Download compatible kernel
4. Terminal - kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x20000000 --command-line="$(cat /proc/cmdline)"
kexec -e
Download links:
Kexec tool- https://db.tt/8DZXQ9eV
Ramdisk firmware 1.548 : https://db.tt/8DZXQ9eV
zImage (kernel):
Source code:
Kernel diff patch: https://db.tt/Xi2htT7Q (currently contains wrong values for mem defines)
Kexec-tools: https://db.tt/I22ofr3b
Special thanks: @delewer @krabappel2548
Reserved
Please move this thread to Xda Devdb, then I can also edit first post etc if I find new stuff
Sent from my C6903 using xda app-developers app
krabappel2548 said:
Please move this thread to Xda Devdb, then I can also edit first post etc if I find new stuff
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Devdb?
Pm me i dont know what Devdb is lol
Recieved segmentation fault with delewers calculated mem values too
We need to write to memory where we have write access to, maybe lockedbootloader is not allowing us to write? Orrr we are just writing to wrong area of memory
If kexec works on the Z1, can it be ported over to Xperia Z/ZL/T/Ultra? I believe they don't all share the same processor.
Shaky156 said:
Devdb?
Pm me i dont know what Devdb is lol
Click to expand...
Click to collapse
Shaky156 said:
Recieved segmentation fault with delewers calculated mem values too
We need to write to memory where we have write access to, maybe lockedbootloader is not allowing us to write? Orrr we are just writing to wrong area of memory
Click to expand...
Click to collapse
I'll discuss with Kali- today if he's available.
Knucklessg1 said:
If kexec works on the Z1, can it be ported over to Xperia Z/ZL/T/Ultra? I believe they don't all share the same processor.
Click to expand...
Click to collapse
Doesn't need to be same processor, can be ported
Sent from my C6903 using xda app-developers app
Knucklessg1 said:
If kexec works on the Z1, can it be ported over to Xperia Z/ZL/T/Ultra? I believe they don't all share the same processor.
Click to expand...
Click to collapse
Yes it wont matter much, since its not s800 it should be easier for you guys , take the kexec-tool use that, implement the patch write to the correct mem addresses which is free, it should boot if you guys have issues let me know,
I need to calculate the correct addresses.
Ive noticed s800 uses a dt.img, might need to modify kexec-tool to support dt.img, not sure what dt.img does yet, only know it holds values
Shaky156 said:
I need to calculate the correct addresses.
Ive noticed s800 uses a dt.img, might need to modify kexec-tool to support dt.img, not sure what dt.img does yet, only know it holds values
Click to expand...
Click to collapse
the dt.img is needed by the kernel to boot, so I guess we need to load that too in kexec.
EDIT: people that wanna try add kexec patch to their kernel, check github: android_kernel_sony_msm8974/commits/kexec
krabappel2548, i have compil your kernel by my script (fromscratch)
My script (instruction in "DoomLord Build kernel thread" : scriptZ1 http://forum.xda-developers.com/attachment.php?attachmentid=2346163&d=1382568778
(for thoses who want to help us...)
You have a little mod to do here (bad compil) :
In "sound/soc/msm/qdsp6v2/rtac.c"
you must change
#include <q6voice.h>
by
#include "q6voice.h"
btw : no more ideas to load kexec for the moment ...
delewer said:
krabappel2548, i have compil your kernel by my script (fromscratch)
My script (instruction in "DoomLord Build kernel thread" : scriptZ1 http://forum.xda-developers.com/attachment.php?attachmentid=2346163&d=1382568778
(for thoses who want to help us...)
You have a little mod to do here (bad compil) :
In "sound/soc/msm/qdsp6v2/rtac.c"
you must change
#include <q6voice.h>
by
#include "q6voice.h"
btw : no more ideas to load kexec for the moment ...
Click to expand...
Click to collapse
Sorry, I'm trying to get caught up on the forum, but what seems to be the current standing issue to get kexec working?
Knucklessg1 said:
Sorry, I'm trying to get caught up on the forum, but what seems to be the current standing issue to get kexec working?
Click to expand...
Click to collapse
Read the OP
Status paragraph
Memory regions
00000000-07afffff : System RAM
00008000-00b79383 : Kernel code
00d04000-00f0cddb : Kernel data
0ff00000-779fffff : System RAM
7ff00000-7ff3ffff : rdtags_mem
7ff80000-7ffa0fff : last_kmsg
7ffa1000-7ffa5fff : last_amsslog
System RAM MEM = 00000000
So --min-mem=0x20000000
Now need to find a free memory area thatll allow us to write and hopefully the mmu/pmu on locked bootloader wont cancel it
@delewer? @DooMLoRD @kali @Bin4ry
I know I shouldn't disturb, but i must ask: if You achieve Your goal, would it be possible to port it to devices like Xperia P, S, T, U and other NXT? It would be great, many ppl are ready to give a prize for it. Thanks in advance, good luck and sorry again.
Sent from my LT22i using xda app-developers app
king960 said:
I know I shouldn't disturb, but i must ask: if You achieve Your goal, would it be possible to port it to devices like Xperia P, S, T, U and other NXT? It would be great, many ppl are ready to give a prize for it. Thanks in advance, good luck and sorry again.
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
These devices are not 2013 devices, they arent s800 socs, so they are much easier to do, simply take the kexec-tools from op, implement the patch in your kernel, write the correct memory values for your specific device and execute in terminal via the command in op, minmem depends on your device too, good luck
I think some1 tried it already, but it works only for unlocked devices... Anyway, thanks for help.
Sent from my LT22i using xda app-developers app
king960 said:
I know I shouldn't disturb, but i must ask: if You achieve Your goal, would it be possible to port it to devices like Xperia P, S, T, U and other NXT? It would be great, many ppl are ready to give a prize for it. Thanks in advance, good luck and sorry again.
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
Does doing this require having an Unlocked Boot loader prior to implementation?
Sent from my C6603 using xda app-developers app
A few informations about kexec-tools debug
in kexec.c
Fonction :
if (file_type.load(argc, argv, kernel_buf,
kernel_size, &info) < 0) {
fprintf(stderr, "Cannot load %s\n", kernel);
return -1;
}
With a forced execution of kexec (bypass error to see...)
--mem-min=0x90000000
kernel: 0xb6b9d008 kernel_size: 3e9340
debug: 1 - after get memory range
debug: 2 - after type test
debug: 3 - after type test
debug: 4 - after info.kexec
debug: Focus 1 - argc '5' ; argv 'be856774' ; kernel_buf 'b6b9d008' ; kernel_size '3e9340' ; info 'be856548' ; i '1' ; file_type.name 'zImage'
Could not find a free area of memory of 3f1340 bytes...
Cannot load zImage
debug: 10 - before trampoline
debug: 11 - after trampoline
debug: 12 - before segment load
debug: 13 - after segment load
debug: 8 - before sort_segment
debug: 9 - after sort_segment
debug: 6 - before purgatory
debug: 7 - after purgatory
kexec_load: entry = (nil) flags = 280004
nr_segments = 0
kexec_load failed: Function not implemented
entry = (nil) flags = 280004
nr_segments = 0
debug: 5 - return result : ffffffff
With a forced bypass on file_type.load , we have this :
--mem-min=0x20000000
debug: Focus 1 - argc '5' ; argv 'bef18774' ; kernel_buf 'b6bc7008' ; kernel_size '3e9340' ; info 'bef18548' ; i '1' ; file_type.name 'zImage'
Segmentation fault
delewer said:
A few informations about kexec-tools debug
in kexec.c
Fonction :
if (file_type.load(argc, argv, kernel_buf,
kernel_size, &info) < 0) {
fprintf(stderr, "Cannot load %s\n", kernel);
return -1;
}
With a forced execution of kexec (bypass error to see...)
--mem-min=0x90000000
kernel: 0xb6b9d008 kernel_size: 3e9340
debug: 1 - after get memory range
debug: 2 - after type test
debug: 3 - after type test
debug: 4 - after info.kexec
debug: Focus 1 - argc '5' ; argv 'be856774' ; kernel_buf 'b6b9d008' ; kernel_size '3e9340' ; info 'be856548' ; i '1' ; file_type.name 'zImage'
Could not find a free area of memory of 3f1340 bytes...
Cannot load zImage
debug: 10 - before trampoline
debug: 11 - after trampoline
debug: 12 - before segment load
debug: 13 - after segment load
debug: 8 - before sort_segment
debug: 9 - after sort_segment
debug: 6 - before purgatory
debug: 7 - after purgatory
kexec_load: entry = (nil) flags = 280004
nr_segments = 0
kexec_load failed: Function not implemented
entry = (nil) flags = 280004
nr_segments = 0
debug: 5 - return result : ffffffff
With a forced bypass on file_type.load , we have this :
--mem-min=0x20000000
debug: Focus 1 - argc '5' ; argv 'bef18774' ; kernel_buf 'b6bc7008' ; kernel_size '3e9340' ; info 'bef18548' ; i '1' ; file_type.name 'zImage'
Segmentation fault
Click to expand...
Click to collapse
Did you compile this kexec yourself? Or did you get this from krapabbel? I issued krapabbel to compile a new debug version have gave him the code but never heard back from him :/
Anywayz so cannot find free memory is the issue
Here is a TWRP flashable B581 ROM. The rom is completely stock for you stock lovers with only a few addons.
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TUTO
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Features:
-Pre-Rooted with SuperSU
-Alpha (NEVER TESTED)
Instructions:
-You must be on stock B5xx (Nougat) to flash this
-Make BACKUP BACKUP BACKUP via TWRP
-Boot into TWRP
-Factory Reset
-Flash ROM
-Profit
--------------------------------------------------------------------
Download link(s):
-NXT-L29-B581-STOCK-ROOTED-ALPHA-1-17/05/24
--------------------------------------------------------------------
--------------------------------------------------------------------
update_data_full_public.zip link if necessary (missing apps):
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v84296/f1/full/public/update_data_full_public.zip
--------------------------------------------------------------------
Changelogs:
Code:
ALPHA-1-17/05/24
* Based on [URL="https://forum.xda-developers.com/mate-8/development/rom-stock-b162-rooted-t3336931"]this one[/URL] (a bit)
* Integrated [URL="https://forum.xda-developers.com/mate-8/general/how-to-root-nxt-l29c432b560-official-t3555364"]this modified boot[/URL] in order to root fine
* Integrated supersu Emui5.0
Last big constraint:
Code:
I would like to start with a test for seasoned people
* Able to restore without being obliged paying tools
* Being on the B580/ B581 to begin
* People not affraid mishaps
* Of course.. Who does not reproach me for any worries that can happen to them
I ask that because like I said above... IT IS NOT TESTED
Information:
Status: ALPHA 1
Created: 2017-05-24
Last Updated: 2017-05-24
If you like that, hit the THANKS button below !
The download in progress gives us the time to reflect if YES or NO I have to continue this thread!
Will gps work in canada with this rom?can we add kang vip b587 to this ? What firmware cyst should we be on? I'm on dl0017 ...
why not continuing this rom? nice idea
I would test it ^^
c|nder said:
Will gps work in canada with this rom?can we add kang vip b587 to this ? What firmware cyst should we be on? I'm on dl0017 ...
Click to expand...
Click to collapse
I've not tested it, it's why I said it is for seasoned testers to begin. So I don't know.
B. R
harryhase said:
why not continuing this rom? nice idea
Click to expand...
Click to collapse
The upload has to be finished. I put the link soon. When I'm on my PC.
Thanks
plzhelpimannob said:
I would test it ^^
Click to expand...
Click to collapse
Same like above.
ROM AVAILABLE IN THE OP POST!!!!
Little reminder:
Have the TWRP, this one is better because it's for this firmware.
Be a SEASONED tester, I prefer to begin
Make a backup of your system via TWRP or Hisuite to be sure in the case
I will prefer that the first tester(s) is, at least, with a C432B580+
Does not reproach me if the first test is wrong
Finally, that you know what you do!
Thanks for comprehension!
If you're not sure... Please abstain!
B.R
Thanks!
Edit:
I removed "international" in the title because I noticed, unlike the B320, that I had only put that package to the C432. So for the moment, it's only for the NXT-L29C432 testers.
Sorry for the others!
Edit 2:
Possible too some apps is missing, so need others, install this in addition.
update_data_full_public.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v84296/f1/full/public/update_data_full_public.zip
I will work on more complete version.
I would like to ask if @ajsmsg78 can help and explain me how make an international version. How he made the B320 international rooted. What files he used.
I'm unable to boot this ROM. Stuck on "Your device is booting..." screen (tried the zip from OP and also tried to flash stock boot.img over it).
Boosik said:
I'm unable to boot this ROM. Stuck on "Your device is booting..." screen (tried the zip from OP and also tried to flash stock boot.img over it).
Click to expand...
Click to collapse
Thanks to have tried! :good:
Can you explain me what you made?
What firmware do you have before?
If you made the wipes. What wipes?
If you saw some errors during the installation process.
And all others things that you have noticed.
Thanks! :good:
franzyroy said:
Thanks to have tried! :good:
Can you explain me what you made?
What firmware do you have before?
If you made the wipes. What wipes?
If you saw some errors during the installation process.
And all others things that you have noticed.
Thanks! :good:
Click to expand...
Click to collapse
I had B560, flashed this ROM and got stuck on that screen with "Your phone was unlocked and can't be trusted". I wiped cache and dalvik cache and installation process was without any error.
Boosik said:
I had B560, flashed this ROM and got stuck on that screen with "Your phone was unlocked and can't be trusted". I wiped cache and dalvik cache.
Click to expand...
Click to collapse
So you didn't make the wipe factory reset?! Maybe the cause even if you are already on Nougat.
What if you try to factory reset the phone ? Will it keep root ?
c|nder said:
What if you try to factory reset the phone ? Will it keep root ?
Click to expand...
Click to collapse
No but this rom is supposed to be rooted.:laugh: Of course, the factory reset is before installation. I preconize the installation of update data public also for that... because, there is a keyboard in the rom but like never installed, I prefer to take the precautions with people.
In addition, like you know, I can help you to root again.
Can someone send me the GPSCONFIG files and all other gps files for this international rom ? I will work on this too , as of EVER I have always never had gps ,,, I live in canada thou , but should not matter , please uload gps files , franzeroy should know what I am looking for
---------- Post added at 06:00 PM ---------- Previous post was at 05:53 PM ----------
Franzroy , what did u do that makes this rom international ? Please explain , is it just google service or is it satalite and cell tower altered. I wanna help if i can understand it.
c|nder said:
Can someone send me the GPSCONFIG files and all other gps files for this international rom ? I will work on this too , as of EVER I have always never had gps ,,, I live in canada thou , but should not matter , please uload gps files , franzeroy should know what I am looking for
---------- Post added at 06:00 PM ---------- Previous post was at 05:53 PM ----------
Franzroy , what did u do that makes this rom international ? Please explain , is it just google service or is it satalite and cell tower altered. I wanna help if i can understand it.
Click to expand...
Click to collapse
No, there are lots of other things in order to make an international rom.
For the GPS, the file that you have to modify, it's gps.conf in /system/etc folder. You can do it after installation if you are rooted or even via TWRP. You have to find the configuration for this file for your country. You can find it on Google. I made a version for the Europe. If you want, I can send you the file that you see how it is.
This one works for several countries
Code:
#Uncommenting these urls would only enable
#the power up auto injection and force injection(test case).
XTRA_SERVER_1=http://xtrapath1.izatcloud.net/xtra2.bin
XTRA_SERVER_2=http://xtrapath2.izatcloud.net/xtra2.bin
XTRA_SERVER_3=http://xtrapath3.izatcloud.net/xtra2.bin
#Version check for XTRA
#DISABLE = 0
#AUTO = 1
#XTRA2 = 2
#XTRA3 = 3
XTRA_VERSION_CHECK=0
# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0
#Test
NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
# NTP_SERVER=north-america.pool.ntp.org
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
# If DEBUG_LEVEL is commented, Android's logging levels will be used
DEBUG_LEVEL = 4
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# Below bit mask configures how GPS functionalities
# should be locked when user turns off GPS on Settings
# Set bit 0x1 if MO GPS functionalities are to be locked
# Set bit 0x2 if NI GPS functionalities are to be locked
# default - non is locked for backward compatibility
#GPS_LOCK = 0
# supl version 1.0
SUPL_VER=0x10000
# Emergency SUPL, 1=enable, 0=disable
SUPL_ES=1
#Choose PDN for Emergency SUPL
#1 - Use emergency PDN
#0 - Use regular SUPL PDN for Emergency SUPL
USE_EMERGENCY_PDN_FOR_EMERGENCY_SUPL=1
#SUPL_MODE is a bit mask set in config.xml per carrier by default.
#If it is uncommented here, this value will over write the value from
#config.xml.
#MSA=0X2
#MSB=0X1
#SUPL_MODE=
# GPS Capabilities bit mask
# SCHEDULING = 0x01
# MSB = 0x02
# MSA = 0x04
# ON_DEMAND_TIME = 0x10
# GEOFENCE = 0x20
# default = ON_DEMAND_TIME | MSA | MSB | SCHEDULING | GEOFENCE
CAPABILITIES=0x37
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=5000
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.host.com or IP
# SUPL_PORT=1234
# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234
# Bitmask of slots that are available
# for write/install to, where 1s indicate writable,
# and the default value is 0 where no slots
# are writable. For example, AGPS_CERT_WRITABLE_MASK
# of b1000001010 makes 3 slots available
# and the remaining 7 slots unwritable.
#AGPS_CERT_WRITABLE_MASK=0
####################################
# LTE Positioning Profile Settings
####################################
# 0: Enable RRLP on LTE(Default)
# 1: Enable LPP_User_Plane on LTE
# 2: Enable LPP_Control_Plane
# 3: Enable both LPP_User_Plane and LPP_Control_Plane
LPP_PROFILE = 0 # Sensor R&D : This will not be injected to MODEM
################################
# EXTRA SETTINGS
################################
# NMEA provider (1=Modem Processor, 0=Application Processor)
NMEA_PROVIDER=1
# Mark if it is a SGLTE target (1=SGLTE, 0=nonSGLTE)
SGLTE_TARGET=0
##################################################
# Select Positioning Protocol on A-GLONASS system
##################################################
# 0x1: RRC CPlane
# 0x2: RRLP UPlane
# 0x4: LLP Uplane
A_GLONASS_POS_PROTOCOL_SELECT = 0 #Sensor R&D : This will not be injected to MODEM
-Asia
-Europe
-North America
When I will be on my PC, I could send you the file to install via TWRP.
Edit:
Like you're rooted, recover your current file in /system/etc in order to have a backup in the case where mine doesn't work correctly for you. I've not the time to make a script to backup it.
@franzyroy unfortunatelly I can't factory reset just now.
beginning of main
I( 1996: 1996) Magisk v14.0(1400) daemon started
I( 1996: 1998) ** post-fs mode running
--------- beginning of system
I( 1996: 2071) ** post-fs-data mode running
I( 1996: 2071) * Mounting mirrors
I( 1996: 2071) mount: /dev/block/mmcblk0p13 -> /dev/magisk/mirror/system
I( 1996: 2071) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
I( 1996: 2071) bind_mount: /dev/magisk/mirror/bin
I( 1996: 2071) * Mounting /data/magisk.img
I( 1996: 2071) * Running post-fs-data.d scripts
I( 1996: 2092) * Starting MagiskHide
I( 1996: 2092) hide_utils: Hiding sensitive props
I( 1996: 2092) hide_list: [com.google.android.gms.unstable]
E( 1996: 2092) proc_monitor: Your kernel doesn't support mount namespace ?
I( 1996: 2177) ** late_start service mode running
installed lineage os and magisk version 14. but able to bypass safetynet your kernal doesn't support mount namespace in log file help me
There's nothing you can do. Magisk cannot pass SafetyNet on our device because there is no kernel for our device that supports the necessary functionality (i.e. mount namespace) in order for MagiskHide to work properly. The only solution is if a dev backports the necessary functionality. The only way to pass SafetyNet on our device is to use Lineage Su and iSu.
h_maharaj said:
There's nothing you can do. Magisk cannot pass SafetyNet on our device because there is no kernel for our device that supports the necessary functionality (i.e. mount namespace) in order for MagiskHide to work properly. The only solution is if a dev backports the necessary functionality. The only way to pass SafetyNet on our device is to use Lineage Su and iSu.
Click to expand...
Click to collapse
HOW TO do that please explain step by step procedure bro will be very thankful to you
vijayfb said:
HOW TO do that please explain step by step procedure bro will be very thankful to you
Click to expand...
Click to collapse
If you already have Magisk then you need to uninstall it.
Flash Lineage Su for root (use the one that says "addonsu-14.1-arm-signed.zip").
Download the latest version of iSu from here and install as you would a normal apk.
Follow these instructions to set up. If you have questions/issues then I suggest asking in the iSu thread.
no idea if your still around h_maharaj do you need to be running Lineage to use Lineage Su and iSu???
I am not.
James
Build 24/03/2019 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r34 13.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
SafetyNet changes to pass
WireGuard Support
Expanded volume rocker ( thanks to @agentfabulous )
Direct unlock with face unlock enabled, lock screen options
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 13.0
Added expanded volume rocker (thanks to AgentFabulous)
Added option to disable the direct unlock with face unlock enabled
Project name: proprietary_vendor_oneplus
msm8998: add missing blobs
Project name: android_kernel_oneplus_msm8998
tri-state-key: send proper input when updating keycodes from userspace
Revert "tri_state_key: import driver from msm8996"
tri_state_key: import driver from msm8996
Project name: android_device_oneplus_msm8998-common
msm8998-common: set project_name prop via init
msm8998-common: Add missing blobs
msm8998-common: add missing libmm-omxcore
msm8998-common: set perms on tri-state-key nodes
Project name: android_frameworks_base
Prevent NFE in SystemUI when parsing invalid int
Prevent NFE in SystemUI when parsing invalid int (2)
Prevent NFE in SystemUI when parsing invalid int
SystemUI: Fix FORCE_SHOW_NAVBAR handling on user switch
Clean up screenshot if nothing selected
IMMS should preserve selected IME upon boot
Add bluetooth icon.
Project name: android_frameworks_av
Request to reset effect buffer in clearInputBuffer
Revert "effects: fix volume burst on pause/resume with AudioFX"
Project name: android_frameworks_native
Respect source crop when capturing layers.
libgui: add docs to geometry states and captureScreen
surfaceflinger: fix captureScreen for landscape LCM
surfaceflinger: improve RenderArea needsFiltering
surfaceflinger: respect install orientation in DisplayRenderArea
surfaceflinger: add install orientation to DisplayDevice
surfaceflinger: make mPrimaryDisplayOrientation static
surfaceflinger: clean up captureScreen
surfaceflinger: silence some RenderArea errors
surfaceflinger: fix race conditions in captureScreen
surfaceflinger: remove ISurfaceComposer.h from RenderArea
surfaceflinger: reorder width and height in RenderArea ctor
surfaceflinger: documents RenderArea
Revert "Revert screenshot changes to exclude black cutout"
Revert "APP may display abnormally in landscape LCM"
Project name: android_vendor_lineage
Add APN ION Mobile & APN for Roaming
config: Remove duplicate keyguard.no_require_sim prop
overlay: Move managed profiles overlay to frameworks/base
kernel: Use build-image-kernel-modules instead of copying it
kernel: Use a macro for kernel build targets
kernel: Detect kernel module usage better
kernel: Move kernel module dir cleanup/creation to module install target
kernel: Move full kernel build guard flag below all targets
kernel: Add more threads to kernel build process
Project name: android_packages_apps_Snap
Snap: Fix picture size preference
Project name: android_packages_apps_Trebuchet
Lint fix: Invalid vector path in horizontal_ellipsis
Project name: android_packages_apps_Bluetooth
Update Bluetooth to use adaptive icon.
Project name: android_packages_apps_Nfc
NfcNci: make T3T/Nfc-F HCE optional
Project name: android_hardware_qcom_display
hwc: Handle validateAndSet failures in AD prepare call
Project name: android_hardware_qcom_display
display-hals: Allow building libdisplayconfig
Project name: android_hardware_qcom_audio
msm8960: Add SND_DEVICE_OUT_VOICE_MUSIC_TX
Project name: android_system_core
Fix path for treble default prop
storaged: change log level for health HAL calls
Project name: android_system_vold
increase timeout for waiting on block device
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP13_OP5.zip
MD5: 6872d0b9526c59fe125cb253bf5d6d72
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.4_OP5.zip
Please dont mirror for now the roms zips, thanks
Sources :
Rom:- https://github.com/LineageOS
Device:- https://github.com/LineageOS/android_device_oneplus_cheeseburger
Kernel:- https://github.com/LineageOS/android_kernel_oneplus_msm8998
Reserved
1st
Added to the OnePlus 5 Index Thread here.
Build 17/02/2018 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r31 10.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
WireGuard Support
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 10.0
Magisk included is now stable version
Project name: proprietary_vendor_oneplus
msm8998-common: add missing blobs
Project name: android_device_oneplus_msm8998-common
msm8998-common: add missing blobs
msm8998-common: selinux: fix some denials
Project name: android_packages_apps_SetupWizard
SUW: Change WizardManager activity default state to disabled
Project name: android_external_chromium-webview
Update x86/x64 Chromium Webviews to 71.0.3578.99
Project name: android_packages_apps_Settings
Settings: Add back summary_collapsed_preference_list for zh-rCN
Project name: android_packages_apps_LineageParts
parts: don't allow clock and network traffic to be enabled at the same time
StatusBarSettings: Hide network traffic settings if device has a notch
Project name: android_packages_services_Telephony
set config_enabled_lte to true by default
Project name: android_frameworks_av
effects: fix volume burst on pause/resume with AudioFX
Project name: android_frameworks_base
Informing app idle listeners on enabled state changes.
Fix for CTS testAllowWhileIdleJobInTempwhitelist
Null locale causing the VTS fail.
SettingsProvider: Allow accessing LineageSettings via settings command
Camera: Simplify code for Aux/Mono white and black lists
Camera: Force HAL1 for predefined package list.
SystemUI: Network Traffic [1/3]
SystemUI: Add Lineage statusbar item holder
fonts: Build different fonts.xml if EXCLUDE_SERIF_FONTS is true
Project name: android_device_qcom_sepolicy
sepolicy: Label vendor.camera.hal1.packagelist
Project name: android_device_lineage_sepolicy
Make backuptool permissive only in non user builds
Make sysinit permissive
lineage: Use set_prop() macro for setting adb tcp property
Project name: android_hardware_ril
Encode the Number of MNC Digits in CellIdentity
Project name: android_hardware_qcom_wlan
wcnss-service: Opt-in to disable copying WCNSS_qcom_cfg.ini to userdata
Project name: android_hardware_qcom_media
Revert "media: Avoid collision with FFMPEG plugin"
Project name: android_hardware_qcom_display
Make memtrack build with the VNDK.
Add missing includes.
libmemtrack: Add open method for apq8084.memtrack
display: Use generated kernel headers
hal: Added LOCAL_VENDOR_MODULE to set output path of the binaries
Use header lib instead of using global include path
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP10_OP5.zip
MD5: d44bee63f45eecdc0db9c8186e20d9eb
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.3_oneplus5.zip
Please dont mirror for now the roms zips, thanks
Build 09/03/2019 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r34 12.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
SafetyNet changes to pass
WireGuard Support
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 12.0
Project name: proprietary_vendor_oneplus
msm8998-common: update blobs from 9.0.4
msm8998-common: add binhaxxed camera libs to fix front cam
Project name: android_kernel_oneplus_msm8998
block: Fix BFQ not being built
Project name: android_device_oneplus_msm8998-common
msm8998-common: update props for wfd
msm8998-common: pin camera blobs (front cam fix)
Project name: android_device_oneplus_cheeseburger
cheeseburger: require 9.0.4 firmware
Project name: android
5 March Security Patch
Project name: android_build_soong
Fix formatting
Project name: android_packages_apps_SetupWizard
SUW: Don't make google suw use material_light
SUW: Update wizard scripts for Pie
Project name: android_packages_apps_Settings
Update the timestamp used for time zone filtering
Project name: android_packages_services_Telephony
Stop generating ids in android namespace.
Fix resource warnings.
Project name: android_frameworks_base
Show mobile icons with left-to-right in order of slot index
Revert "SystemUI: Sort subscriptions in reversed order"
Project name: android_device_qcom_sepolicy
sepolicy: Fix video4linux "name" node labeling
sepolicy: Label persist.nfc.hci_network_reset_req
Project name: android_vendor_lineage
sensitive_pn: New United Kingdom helplines
Project name: android_hardware_qcom_display
display-hals: Expose c2d2.h even if TARGET_DISABLE_DISPLAY is set
Project name: android_system_extras_su
su: Add back mistakenly removed code
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP12_OP5.zip
MD5: 4593674d66a2040a50b11cbd6927f33d
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.4_OP5.zip
Please dont mirror for now the roms zips, thanks
danieldmm said:
Build 09/03/2019 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r34 12.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
SafetyNet changes to pass
WireGuard Support
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 12.0
Project name: proprietary_vendor_oneplus
msm8998-common: update blobs from 9.0.4
msm8998-common: add binhaxxed camera libs to fix front cam
Project name: android_kernel_oneplus_msm8998
block: Fix BFQ not being built
Project name: android_device_oneplus_msm8998-common
msm8998-common: update props for wfd
msm8998-common: pin camera blobs (front cam fix)
Project name: android_device_oneplus_cheeseburger
cheeseburger: require 9.0.4 firmware
Project name: android
5 March Security Patch
Project name: android_build_soong
Fix formatting
Project name: android_packages_apps_SetupWizard
SUW: Don't make google suw use material_light
SUW: Update wizard scripts for Pie
Project name: android_packages_apps_Settings
Update the timestamp used for time zone filtering
Project name: android_packages_services_Telephony
Stop generating ids in android namespace.
Fix resource warnings.
Project name: android_frameworks_base
Show mobile icons with left-to-right in order of slot index
Revert "SystemUI: Sort subscriptions in reversed order"
Project name: android_device_qcom_sepolicy
sepolicy: Fix video4linux "name" node labeling
sepolicy: Label persist.nfc.hci_network_reset_req
Project name: android_vendor_lineage
sensitive_pn: New United Kingdom helplines
Project name: android_hardware_qcom_display
display-hals: Expose c2d2.h even if TARGET_DISABLE_DISPLAY is set
Project name: android_system_extras_su
su: Add back mistakenly removed code
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP12_OP5.zip
MD5: 4593674d66a2040a50b11cbd6927f33d
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.4_OP5.zip
Please dont mirror for now the roms zips, thanks
Click to expand...
Click to collapse
Does rom force encryption after flash?
Build 24/03/2019 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r34 13.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
SafetyNet changes to pass
WireGuard Support
Expanded volume rocker ( thanks to @agentfabulous )
Direct unlock with face unlock enabled, lock screen options
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 13.0
Added expanded volume rocker (thanks to AgentFabulous)
Added option to disable the direct unlock with face unlock enabled
Project name: proprietary_vendor_oneplus
msm8998: add missing blobs
Project name: android_kernel_oneplus_msm8998
tri-state-key: send proper input when updating keycodes from userspace
Revert "tri_state_key: import driver from msm8996"
tri_state_key: import driver from msm8996
Project name: android_device_oneplus_msm8998-common
msm8998-common: set project_name prop via init
msm8998-common: Add missing blobs
msm8998-common: add missing libmm-omxcore
msm8998-common: set perms on tri-state-key nodes
Project name: android_frameworks_base
Prevent NFE in SystemUI when parsing invalid int
Prevent NFE in SystemUI when parsing invalid int (2)
Prevent NFE in SystemUI when parsing invalid int
SystemUI: Fix FORCE_SHOW_NAVBAR handling on user switch
Clean up screenshot if nothing selected
IMMS should preserve selected IME upon boot
Add bluetooth icon.
Project name: android_frameworks_av
Request to reset effect buffer in clearInputBuffer
Revert "effects: fix volume burst on pause/resume with AudioFX"
Project name: android_frameworks_native
Respect source crop when capturing layers.
libgui: add docs to geometry states and captureScreen
surfaceflinger: fix captureScreen for landscape LCM
surfaceflinger: improve RenderArea needsFiltering
surfaceflinger: respect install orientation in DisplayRenderArea
surfaceflinger: add install orientation to DisplayDevice
surfaceflinger: make mPrimaryDisplayOrientation static
surfaceflinger: clean up captureScreen
surfaceflinger: silence some RenderArea errors
surfaceflinger: fix race conditions in captureScreen
surfaceflinger: remove ISurfaceComposer.h from RenderArea
surfaceflinger: reorder width and height in RenderArea ctor
surfaceflinger: documents RenderArea
Revert "Revert screenshot changes to exclude black cutout"
Revert "APP may display abnormally in landscape LCM"
Project name: android_vendor_lineage
Add APN ION Mobile & APN for Roaming
config: Remove duplicate keyguard.no_require_sim prop
overlay: Move managed profiles overlay to frameworks/base
kernel: Use build-image-kernel-modules instead of copying it
kernel: Use a macro for kernel build targets
kernel: Detect kernel module usage better
kernel: Move kernel module dir cleanup/creation to module install target
kernel: Move full kernel build guard flag below all targets
kernel: Add more threads to kernel build process
Project name: android_packages_apps_Snap
Snap: Fix picture size preference
Project name: android_packages_apps_Trebuchet
Lint fix: Invalid vector path in horizontal_ellipsis
Project name: android_packages_apps_Bluetooth
Update Bluetooth to use adaptive icon.
Project name: android_packages_apps_Nfc
NfcNci: make T3T/Nfc-F HCE optional
Project name: android_hardware_qcom_display
hwc: Handle validateAndSet failures in AD prepare call
Project name: android_hardware_qcom_display
display-hals: Allow building libdisplayconfig
Project name: android_hardware_qcom_audio
msm8960: Add SND_DEVICE_OUT_VOICE_MUSIC_TX
Project name: android_system_core
Fix path for treble default prop
storaged: change log level for health HAL calls
Project name: android_system_vold
increase timeout for waiting on block device
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP13_OP5.zip
MD5: 6872d0b9526c59fe125cb253bf5d6d72
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.4_OP5.zip
Please dont mirror for now the roms zips, thanks
For those searching along: The ROM is still maintained and currently up to Version P23. Downloads can be found at https://tugapower.net/?dir=TP/OP5/PIE
Currently you'll need to install firmware 9.0.6 which isn't hosted over there (yet?) but can be found in the OP5 OOS thread at https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8
I'm receiving error 255 for flashing the 9.0.6 firmware as well as the ROM. Is this because I haven't formatted? I'm on the Android 7 version of TugaPower.
Where are the ROM sources mate? Would you kindly provide, or is it closed?
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_xiaomi_scorpio
Kernel source code: LineageOS/android_device_xiaomi_msm8996-common
Broken / not yet supported:
Tell Me
Downloads:
LineageOS Downloads
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Reboot to recovery (TWRP recovery for Mi Note 2 - Direct link)
Format /system, /data and /cache
Install LineageOS zip package
Install [optional] the LineageOS su addon to get root (there are obviously other root methods, but this is the recommended one as it survives to OTA updates)
Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
Credits & collaborations:
joe2k01
.
Finally, all LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Device wiki:
Official wiki link
Contributors
joe2k01
ROM OS Version: 10.x
ROM Kernel: Linux 3.x
ROM Firmware Required: MIUI 8.8.30 Beta
Version Information
Status: Stable
Created 2021-01-19
Last Updated 2021-02-09
I installed lineage 18.1. But no Volte support. Any way to enable it?
There's a bug when opening Settings > System > Buttons. Here's the logcat I found:
Code:
HidlServiceManagement: Waited one second for [email protected]::IKeySwapper/default
hwservicemanager: Since [email protected]::IKeySwapper/default is not registered, trying to start it as a lazy HAL.
HidlServiceManagement: getService: Trying again for [email protected]::IKeySwapper/default...
libc : Unable to set property "ctl.interface_start" to "[email protected]::IKeySwapper/default": error code: 0x20
chatty : uid=0(root) logd identical 10 lines
init : Control message: Could not find '[email protected]::IKeySwapper/default' for ctl.interface_start from pid: 451 (/system/bin/hwservicemanager)
logd : logdr: UID=2000 GID=2000 PID=7072 n tail=0 logMask=99 pid=0 start=0ns timeout=0ns
cc: @fernandodtg @joe2k01
ChessPiece said:
There's a bug when opening Settings > System > Buttons. Here's the logcat I found:
Code:
HidlServiceManagement: Waited one second for [email protected]::IKeySwapper/default
hwservicemanager: Since [email protected]::IKeySwapper/default is not registered, trying to start it as a lazy HAL.
HidlServiceManagement: getService: Trying again for [email protected]::IKeySwapper/default...
libc : Unable to set property "ctl.interface_start" to "[email protected]::IKeySwapper/default": error code: 0x20
chatty : uid=0(root) logd identical 10 lines
init : Control message: Could not find '[email protected]::IKeySwapper/default' for ctl.interface_start from pid: 451 (/system/bin/hwservicemanager)
logd : logdr: UID=2000 GID=2000 PID=7072 n tail=0 logMask=99 pid=0 start=0ns timeout=0ns
cc: @fernandodtg @joe2k01
Click to expand...
Click to collapse
Just flash this vendor in TWRP (install - install image - vendor partition). One of the 4pda's user had corrected buttons settings + google camera fix.
vendor_fix.img
drive.google.com
The
ChessPiece said:
There's a bug when opening Settings > System > Buttons. Here's the logcat I found:
Code:
HidlServiceManagement: Waited one second for [email protected]::IKeySwapper/default
hwservicemanager: Since [email protected]::IKeySwapper/default is not registered, trying to start it as a lazy HAL.
HidlServiceManagement: getService: Trying again for [email protected]::IKeySwapper/default...
libc : Unable to set property "ctl.interface_start" to "[email protected]::IKeySwapper/default": error code: 0x20
chatty : uid=0(root) logd identical 10 lines
init : Control message: Could not find '[email protected]::IKeySwapper/default' for ctl.interface_start from pid: 451 (/system/bin/hwservicemanager)
logd : logdr: UID=2000 GID=2000 PID=7072 n tail=0 logMask=99 pid=0 start=0ns timeout=0ns
cc: @fernandodtg @joe2k01
Click to expand...
Click to collapse
This bug has been fixed in the official build.
Thanks @Wiwern and @LuK1337
Wow, updated my old phone. Love it
Can someone post the build pls, the link of the OP doesn't have any file for the Mi Note 2.
thanks
I took this guide and built a fresh LOS 18.1 for scorpio
Build for scorpio | LineageOS Wiki
wiki.lineageos.org
It was not easy (2 hrs on my i7 12700/64Gb/970Evo+) but succesuful....
Everyone can take it here (or make their own build)
lineage-18.1-20230327-UNOFFICIAL-scorpio.zip
drive.google.com
The only hint is to edit roomservice.py, make it first line #!/usr/bin/env python3 and you can extract proprietary blobs for scorpio.