Related
Hello all,
as you may know installing systemless SuperSU for Z2 stock roms was not possible until now due to the ELF format of the boot image. As a workaround one was required to install SuperSU in system mode, but support for this installation type seems to fade away...
In order to have convenient solution to enable systemless installation for elf boot image files, @adriandC created a tool called boot_bridge that works around the limitations caused by the ELF format. Up to now, only Xperia SP and similar device have been supported.
But, due to the recent efforts to support ELF images in libbootimg (backend library used by MultiRom) and which are found in Z2 and similar devices, the boot_bridge tool now supports the Z2 as well (boot_bridge also uses the libbootimg library). This is a result of a collaborative effort of AdrainDC and me wherby the main portion of the work on the boot_bridge was done by AdrainDC (I focussed on the Z2 ELF support, where AdrainDC fixed may changes such that the Xperia SP support is no broken )
You can find the tools here:
boot_bridge
Regards,
Diewi
P.S: I am posting this here to raise awareness of this useful tool, since this update may be easily missed in the cross-device dev section).
very interesting and saw this in Cross Dev section . will try and let u know
Do i have to come from clean install of the ROm ? currently im on stock .291 with super su
Dilesh Perera said:
very interesting and saw this in Cross Dev section . will try and let u know
Do i have to come from clean install of the ROm ? currently im on stock .291 with super su
Click to expand...
Click to collapse
To be safe, uninstall supersu before. Either via a the uninstaller or by flashing stock.
Does this mean that we can now use Magisk, for example?
Vic. said:
Does this mean that we can now use Magisk, for example?
Click to expand...
Click to collapse
I have this exactly same doubt. I was using Magisk on my Z2 with @Gustavo RD78 amazing Advanced Stock Kernel, but after Magisk 6.0 i always got a bootloop when i try to use then
Hmmm I have Sony Xperia Z2 with Elite Kernel v3, Xposed, SuperSU, and Magisk V8 installed and everything is working fine for me
Custom kernels are not using the ELF format. The boot_bridge is for the stock kernel, not custom kernels compiled from stock sources.
Diewi said:
Custom kernels are not using the ELF format. The boot_bridge is for the stock kernel, not custom kernels compiled from stock sources.
Click to expand...
Click to collapse
So bootbridge will help us with e.g android pay? (systemless root on stock kernel?)
UBL only?
EugenStanis said:
So bootbridge will help us with e.g android pay? (systemless root on stock kernel?)
Click to expand...
Click to collapse
IF you need stock for that then: probably yes. But I am not into this android pay stuff (which has even more scurity mechanisms AFAIK to even detect systemless root), so at least I can't give you an answer to this. Anyone?
vandiaz_sairavinz said:
UBL only?
Click to expand...
Click to collapse
Yep.
Please provide the download link for kcal.zip file which can be used for screen color adjustments in kernel auditor.
I accidently deleted that file, if anyone here has it please share it.
ch3tan007 said:
Please provide the download link for kcal.zip file which can be used for screen color adjustments in kernel auditor.
I accidently deleted that file, if anyone here has it please share it.
Click to expand...
Click to collapse
Kcal is actually the hardware's display settings exposed by a sysfs interface
What zip? You need to compile a kernel with the patch to get this feature
anupritaisno1 said:
Kcal is actually the hardware's display settings exposed by a sysfs interface
What zip? You need to compile a kernel with the patch to get this feature
Click to expand...
Click to collapse
I somewhere found the kcal zip file which i flashed over h20s stock rom for color adjustments. But yesterday i accidently formatted my phone so need that file again.
ch3tan007 said:
I somewhere found the kcal zip file which i flashed over h20s stock rom for color adjustments. But yesterday i accidently formatted my phone so need that file again.
Click to expand...
Click to collapse
Are you sure you didn't unknowingly flash a kernel?
Because what you're saying is impossible without touching boot.img
anupritaisno1 said:
Are you sure you didn't unknowingly flash a kernel?
Because what you're saying is impossible without touching boot.img
Click to expand...
Click to collapse
Donno mate but when i checked kernel version in about pbone all were stock and i could see screen options in kernel auditor
ch3tan007 said:
Donno mate but when i checked kernel version in about pbone all were stock and i could see screen options in kernel auditor
Click to expand...
Click to collapse
I can make the kernel show perf+ too
Just need to change one variable in the defconfig and 2 exported variables in the shell
Why don't you try a ROM that comes with kcal, like seraph's build or try out something like halogenos
Or maybe you can find my thread in the development session and flash my ROM and custom kernel from there?
Anyways if you want kcal on hydrogenos, boeffla kernel, I'm not going to say it again
anupritaisno1 said:
I can make the kernel show perf+ too
Just need to change one variable in the defconfig and 2 exported variables in the shell
Why don't you try a ROM that comes with kcal, like seraph's build or try out something like halogenos
Or maybe you can find my thread in the development session and flash my ROM and custom kernel from there?
Anyways if you want kcal on hydrogenos, boeffla kernel, I'm not going to say it again
Click to expand...
Click to collapse
I have tried seraph's and other cm14.1 based rom, yes sure will give a try to ur rom too microg looks useful feature.:good:
Thanks for ur replies.
The first builds of Lineage are out for the shamu finally!
download.lineageos.org
How do I get rid of the ugly watermark across my screen?
The link to the nightly version doesn't work
Link to nightly worked fine for me. Haven't flashed yet, but it downloaded, albeit slowly.
https://download.lineageos.org/shamu
How to remove this cm to lineage migration build background ?
People who have the watermark did you flash the nighly or experimental?
From my understanding the experimental build is only used for migration from CM and will have that watermark no matter what, the nightly build should have no water mark. I believe they posted this info on their site.
You're supposed to flash nightly over experimental. Just read the instructions...
Dopamin3 said:
People who have the watermark did you flash the nighly or experimental?
From my understanding the experimental build is only used for migration from CM and will have that watermark no matter what, the nightly build should have no water mark. I believe they posted this info on their site.
Click to expand...
Click to collapse
can confirm - no watermark at nightly building!
Strange how everytime I try to download the nightly it fails. No matter what browser I use
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
MartinN6 said:
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
Click to expand...
Click to collapse
You mean permissive, but you can use stock kernel enforced, a bit tricky, you need to root with supersu, latest beta sr3 runs fine. Superuser from los page doesn't recognize viper4a for root at all. I flashed latest arise and supersu, reboot, viper4a still not recognized for root, uninstall viper4a driver, supersu recognize viper4a now, confirm it. Reboot to recovery and reflash latest arise. Now it's working.
If you want Dolby too you have to use blackbird kernel and stay permissive.
coremania said:
You mean permissive, but you can use stock kernel enforced, a bit tricky, you need to root with supersu, latest beta sr3 runs fine. Superuser from los page doesn't recognize viper4a for root at all. I flashed latest arise and supersu, reboot, viper4a still not recognized for root, uninstall viper4a driver, supersu recognize viper4a now, confirm it. Reboot to recovery and reflash latest arise. Now it's working.
If you want Dolby too you have to use blackbird kernel and stay permissive.
Click to expand...
Click to collapse
Thanks for advice!!
And yes of course - sorry - I mean "permissive"
I flashed "Viper4Android_Cleaner_v1_3_Android_7x.zip" and than "ViPER4Android_2.5.0.5_guitardedhero.zip"
... and it works without any trouble ...
MartinN6 said:
Thanks for advice!!
And yes of course - sorry - I mean "permissive"
I flashed "Viper4Android_Cleaner_v1_3_Android_7x.zip" and than "ViPER4Android_2.5.0.5_guitardedhero.zip"
... and it works witout any trouble ...
Click to expand...
Click to collapse
Good, if it works that easy, but there was something about the cleaner, don't remember right now exactly, but it breaks something. May it was dolby.
Edit: using the cleaner always kills cast connection, that's why I didn't use it anymore
MartinN6 said:
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
Click to expand...
Click to collapse
Kernel Adiutor Mod should let you toggle that (requires root) under the Misc Controls tab. I would imagine the ad-filled subpar original Kernel Adiutor from the Play Store would too but I wouldn't recommend using that.
Is there an updater built in or do we flash all updates? Reading in other threads that ppl get a update notification when a new build is available. I'm on experimental cuz the nightly link didn't work when I tried last night
Dopamin3 said:
Kernel Adiutor Mod should let you toggle that (requires root) under the Misc Controls tab. I would imagine the ad-filled subpar original Kernel Adiutor from the Play Store would too but I wouldn't recommend using that.
Click to expand...
Click to collapse
Thanks!
I got it and it (Kernel Adiutor mod) works great!
Now AdAway works again (need SElinux permissiv) - that's very good!
Guys, whats your baseband or radio? My proximity sensor isn't working properly on LineageOS...
MartinN6 said:
Thanks!
I got it and it (Kernel Adiutor mod) works great!
Now AdAway works again (need SElinux permissiv) - that's very good!
Click to expand...
Click to collapse
How did you get those SOFT keys from. Pixel
hashtag_harsh said:
How did you get those SOFT keys from. Pixel
Click to expand...
Click to collapse
sorry I don´t understand what you mean with "SOFT keys" ?
Edit: Aah now I know!
Yes, it's from the mod - link next post! ->
hashtag_harsh said:
How did you get those SOFT keys from. Pixel
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/themes-apps/cool-pixel-mod-android-7-1-1-t3532951
Here you go
---------- Post added at 19:57 ---------- Previous post was at 19:54 ----------
LeroViten said:
Guys, whats your baseband or radio? My proximity sensor isn't working properly on LineageOS...
Click to expand...
Click to collapse
Latest
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
I am creating this guide for Magisk v13 and working modules. Please let me know if there are additional ROMs that this guide works with, but I am trying to keep the steps as simple as possible.
Magisk Installation Instructions:
Download Latest PureNexus / PA ROM and follow those instructions
Boot into the ROM and go through the initial set up, at this point verify that SafetyNet is passing. If it is not you may need to factory reset and re-install your ROM.
Reboot into TWRP
Flash the attached modified Magisk-v13-Pixel (from Goodwin_c)
Flash the attached verified boot signer (from Chainfire)
Reboot the System
Uninstall the version of Magisk Manager that shows up in the drawer
Install the attached version of MagiskManager_v13_new5.apk (from Goodwin_c)
Open Magisk Manager (you may need to wait a bit, I had to clear it from my recents a few times before it launched and asked for file system permissions)
Go to the app settings and tick on Magisk Hide
Re-run SafetyNet and verify it's passing
Working Modules
I will create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
Modules I have modified to work with Pixel:
Emoji One - systemlessly replaces emojie font with Emoji One.
Tethering Enabler - enables tethering on phones where it is disabled by the manufacturer/provider.
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
mac796 said:
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
Click to expand...
Click to collapse
These still looks like the ones @goodwin_c created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
uodii said:
These still looks like the ones @goodwin_c created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
Click to expand...
Click to collapse
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
mac796 said:
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
Click to expand...
Click to collapse
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
chadgauth said:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
Click to expand...
Click to collapse
That's cool maybe I'll give it another shot.
chadgauth said:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
Click to expand...
Click to collapse
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?
It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
uodii said:
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?
It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
Click to expand...
Click to collapse
Yeah, I haven't tried Titanium backup, I'm using Solid Explorer and Greenify with root and they seem to work alright. I am still using new1, I will update to new5 and play with Titanium to see if I can get it to backup and reinstall an app
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
I'm very interessted about how to modify modules to work with Pixel device !
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
Only custom rom? Anyone tried on stock image?
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?
I just want to keep updated to his modification.
I have been using his modified Magisk v12, but finding it from RR thread.
There is no way to know if it is updated or not.
The zip failed to flash for me. Couldn't unpack boot image.
Pixel running PN 7.1.1, twrp RC1.
maflin18 said:
The zip failed to flash for me. Couldn't unpack boot image.
Pixel running PN 7.1.1, twrp RC1.
Click to expand...
Click to collapse
Try TWRP RC2
TENN3R said:
Only custom rom? Anyone tried on stock image?
Click to expand...
Click to collapse
The stock image should most likely work, if it works for you or someone else in this thread let me know and I'll update the OP.
y2kbugleung said:
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?
I just want to keep updated to his modification.
I have been using his modified Magisk v12, but finding it from RR thread.
There is no way to know if it is updated or not.
Click to expand...
Click to collapse
I'll update the post date in brackets when I make updates here. Goodwin_c does not have his own thread, so I've just been monitoring his android file host account. The original poster has not updated or maintained his guide from the RR thread, so I created a new one to be as up-to-date as possible and include modules as I modify them.
foski said:
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
Click to expand...
Click to collapse
I've included both of those. I basically have been using beyond compare to compare the arise module that works with pixel to other modules and re-zipping them and testing with my device.
I see. Thanks.
Btw do you know the difference between v1 and v5 apk?
It seems MagiskHide is gone on v5?
I have tried Magisk-V13 on Pixel-XL with stock ROM.
I haven't tried it with stock kernel, since SafetyNet won't pass (as far as I understand).
Tested with Elemental-X + MagiskManager-v1, SafetyNet does not pass. App always says "cannot use Play service"
Tested with Kirisakura-Rebase-1.36 + MagiskManager-v1, SafetyNet passes.
MagiskManager-v5 does not come with MagiskHide, so I assume it cannot handle SafetyNet.
Both MagiskManager v1 and v5 loads very slowly.
Before the UI could be used normally (it means Magisk is loaded?), ROOT cannot be obtained.
So those boot-up root-required action would probably fail.
newbie question this so forgive me being so niave.
i have a samsung galaxy note 4...its my old phone i have as a spare.
at one stage i had lineage os on it and it was fantastic, slick, fast, clean with superb battery life....but the lineage os for the note 4 was unofficial and was pre-rooted...which meant some apps dont work... snapchat an obvious one.
so... what are my options on roms that are stock android like...which wont be rooted and be stable ?
thanks in advance for any replies.
Sent from my SM-G955F using Tapatalk
dougm1970 said:
newbie question this so forgive me being so niave.
i have a samsung galaxy note 4...its my old phone i have as a spare.
at one stage i had lineage os on it and it was fantastic, slick, fast, clean with superb battery life....but the lineage os for the note 4 was unofficial and was pre-rooted...which meant some apps dont work... snapchat an obvious one.
so... what are my options on roms that are stock android like...which wont be rooted and be stable ?
thanks in advance for any replies.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
U have on this site SuperDeodexedRom that isnt rooted by default: https://forum.xda-developers.com/note-4/development/rom-t3768967
... And U have also Like Stok based if U choose A5 system UI, fast and smooth:
https://forum.xda-developers.com/note-4/development/air-rom-v1-0-t3630284
And so one... Using both on both N4,,, Great roms Stock to near Stock based...
RamHa said:
U have on this site SuperDeodexedRom that isnt rooted by default: https://forum.xda-developers.com/note-4/development/rom-t3768967
... And U have also Like Stok based if U choose A5 system UI, fast and smooth:
https://forum.xda-developers.com/note-4/development/air-rom-v1-0-t3630284
And so one... Using both on both N4,,, Great roms Stock to near Stock based...
Click to expand...
Click to collapse
Air rom unfortunately you can't use some apps due to prerooted rom.
The first rom I used it but if you use any note 7 port the old ui seems outdated. I wish I could unroot someway the Air Rom which I use for daily driver but unfortunately I can't use an app that I need because it's prerooted.
ioannis_m said:
Air rom unfortunately you can't use some apps due to prerooted rom.
The first rom I used it but if you use any note 7 port the old ui seems outdated. I wish I could unroot someway the Air Rom which I use for daily driver but unfortunately I can't use an app that I need because it's prerooted.
Click to expand...
Click to collapse
Why dont U ask dev to Unroot it 4 u???? Give it a try. And as always U can unroot it by installing non rooted kernel after installing rom or inject non rooted kernel into Rom.zip. But, ask Dev, rom is great.
And, Note 7 Ports 4 me r better than s8 etc ports
RamHa said:
Why dont U ask dev to Unroot it 4 u???? Give it a try. And as always U can unroot it by installing non rooted kernel after installing rom or inject non rooted kernel into Rom.zip. But, ask Dev, rom is great.
And, Note 7 Ports 4 me r better than s8 etc ports
Click to expand...
Click to collapse
I already tried to unroot the rom with spacelemon non root version but still the app can't play at the device due to root existance. I
ioannis_m said:
I already tried to unroot the rom with spacelemon non root version but still the app can't play at the device due to root existance. I
Click to expand...
Click to collapse
When you are saying some apps are you talking about safetynet getting tripped? Why not just flash Spacelemon non-rooted and flash latest magisk with prop hide module to get it to work. I was able to pass safetynet with the latest version of AirRom at the time.
dougm1970 said:
newbie question this so forgive me being so niave.
i have a samsung galaxy note 4...its my old phone i have as a spare.
at one stage i had lineage os on it and it was fantastic, slick, fast, clean with superb battery life....but the lineage os for the note 4 was unofficial and was pre-rooted...which meant some apps dont work... snapchat an obvious one.
so... what are my options on roms that are stock android like...which wont be rooted and be stable ?
thanks in advance for any replies.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
No worries for you being a newbie, but I just wanted to clarify that you can actually use restricted apps like Snapchat (created a burner account since I don't use it), Netflix, and Android Pay, etc.
Requirements:
- Lastest build from Bonuzzz (Mar.)
- Some basic knowledge on working Magisk
- Download Terminal app
- Possibly a third party file manager (ex. Solid Explorer, ES Files Explorer, etc.)
Steps:
- You need to download this and flash it in your recovery to remove pre-root from your device. https://mirrorbits.lineageos.org/su/addonsu-remove-15.1-arm-signed.zip
- Head over to the Magisk thread and download the latest version of Magisk (16.0). https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- Flash Magisk in your recovery and and open the Magisk Manager and update it when prompted.
- Head over back to the Magisk thread and download the MagiskHide Props Config module. https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199
- Open back up Magisk Manager click on the three dashes on the top left and click on the modules tab. Press the button that shows a plus sign and locate the module that you downloaded/saved on your device.
- It should then start flashing through the manager and prompt you to reboot.
- After reboot, download any terminal app (preferably Termux) and open it.
- Type in "Su" and grant it root access. Next, type "props" and it should open up onto an interface.
- Type in "1" to change your device fingerprint and type in "f" to pick a certified fingerprint.
- From here, you can choose whichever certified fingerprint your device wants to be recognized as (I used Samsung Note 5).
- After choosing your certified fingerprint, it will ask you to reboot.
- After reboot, head back into Magisk Manager and click on the SafetyNet Check (It might prompt you to download something). Eventually you should get the same test like in my picture.
- (Optional) Head back into recovery and wipe dalvik cache/cache.
Hopefully this helps out on your problem on apps not working or not letting you install them. Also, this can work for others too that don't use lineage but other Custom ROMs (AirRom, Nemesis, etc.). All you need to do is just install the latest SpaceLemon Non-rooted Kernel or manually unroot and continue with the steps on "Heading over to Magisk Threads". I do hope that this worked for others, and sorry if the instructions are either too long or really complicated on following.
RetroSpect_17 said:
When you are saying some apps are you talking about safetynet getting tripped? Why not just flash Spacelemon non-rooted and flash latest magisk with prop hide module to get it to work. I was able to pass safetynet with the latest version of AirRom at the time.
Click to expand...
Click to collapse
True, and yes, that is solution! :highfive:
RetroSpect_17 said:
When you are saying some apps are you talking about safetynet getting tripped? Why not just flash Spacelemon non-rooted and flash latest magisk with prop hide module to get it to work. I was able to pass safetynet with the latest version of AirRom at the time.
Click to expand...
Click to collapse
No even with non rooted kernel and magisk hide props and safetynet passes correctly the app does not start due to root existance.I don't know what else to do.
RamHa said:
True, and yes, that is solution! :highfive:
Click to expand...
Click to collapse
For me the only solution was to flash the no root stock deodexed rom you wrote above earlier today. With air rom and doing every step to pass safetynet correctly the app recognises root whatever I do.
Just saying, but please don't create a thread like this on the Android Development page again.
Quoted from the rules post: https://forum.xda-developers.com/note-4/development/rules-posting-development-t2868781
"Only the following topics are allowed in DEVELOPMENT area:
[DEV] - Development for any special projects or Apps
[ROM] - Custom ROMs
[KERNEL] - Custom Kernels (usually found in Original Development)
[MOD] - Hack & Modifications for the phone with code only, zips go in themes and apps
[FIX] - Fixes for known issues & bugs
[R&D] - Research & Development for Devs only, when gathering data for a new projects
[HOWTO] / [GUIDE] - How to instructions and Guides (Most of the time should be in General)"