Stock Pixel/PixelXL Kernel + SafetyNet Patch
Current version: android-msm-marlin-3.18-nougat-mr1
Suitable for build: NMF26U
Security patch level: January 5, 2017
I compiled the stock kernel for the Pixel/PixelXL (they both use the same kernel) and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the stock builds, except with the addition of the SafetyNet patch.
Installation:
- Download attached .zip and unzip into a folder
- Reboot device into bootloader (power down device, then Power + Volume down)
- Connect device to computer
- Verify connection by typing 'fastboot devices'. Your device should show up (check serial number)
- Enter command: fastboot flash kernel <kernel_image>
- Once flashing is complete, enter command: fastboot reboot
- Disconnect device and wait for reboot sequence to complete.
- You now have a stock Pixel with an unlocked bootloader that can use Android Pay
**WARNING**
If flashing this kernel for whatever reason ruins your device, please don't hold me accountable. Use this at your own risk!
And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future (am running a Verizon Pixel). I will try to maintain this kernel with each new release until I lose interest
Downloads:
NMF26U
All versions
If one wants to stay completely stock wouldn't they just keep bootloader locked?
Edit: nevermind seems like this will cater to Verizon pixel owners since you can't unlock the bootloader on latest build. Good job!
Sent from my Pixel using Tapatalk
joetheshmo said:
If one wants to stay completely stock wouldn't they just keep bootloader locked?
Edit: nevermind seems like this will cater to Verizon pixel owners since you can't unlock the bootloader on latest build. Good job!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yep, let's us unlock the bootloader in case we need it in the future, without committing to any mods or losing Android Pay just yet.
Stock + Safetynet patch.... Finally.
Thank you
Thanks for sharing your work, OP.
Sent from my Pixel using Tapatalk
Any chance of you turning this into a flashable TWRP zip? Then I could run ElementalX and root when I want to, and flash back to stock if I want to, all from my phone, in a single reboot.
Just want to confirm that this is for Sailfish also. The name of the file is marlin and just want to make sure. Thanks
@Sakete, I appreciate your attitude.... You need something, you just make it.
jay661972 said:
Just want to confirm that this is for Sailfish also. The name of the file is marlin and just want to make sure. Thanks
Click to expand...
Click to collapse
Yes, it will also work on sailfish. Sailfish and marlin both use the same kernel. I installed it last night on my own Pixel (sailfish) and it works great, no issues so far (and am not expecting any since it's just stock + safety net bypass patch)
Sent from my Pixel using Tapatalk
Your Verizon Pixel can be unlocked and rooted, yet Android Pay works. What else can you want, right?
Sakete said:
Yes, it will also work on sailfish. Sailfish and marlin both use the same kernel. I installed it last night on my own Pixel (sailfish) and it works great, no issues so far (and am not expecting any since it's just stock + safety net bypass patch)
Click to expand...
Click to collapse
You are right there should have no issues at all since the change was the safetynet patch.
Thanks for this..
quangtran1 said:
Your Verizon Pixel can be unlocked and rooted, yet Android Pay works. What else can you want, right?
Click to expand...
Click to collapse
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.
Sakete said:
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.
Click to expand...
Click to collapse
Sure it does. AP works on both of my Pixel and Pixel XL. Here's the trick. Well, actually, it's no trick, but it's something I remembered from 6.0. With 6.0, you could temporarily unroot, add cards in AP, then resume root. You have to add your credit cards in AP prior to rooting.
In the beginning, I rooted first, then AP couldn't get past the Add Card screen. I flashed back to 7.1.1 stock, install your (or any) SafetyNet-bypassing kernel. That gets AP working (allows me to add cards). Then re-root.
If screenshots are needed to demonstrate this, I can do that, but that seems rather childish.
---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------
Sakete said:
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.
Click to expand...
Click to collapse
Here goes, unlocked BL + rooted + Android Pay. Screenshot of my multitask screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
quangtran1 said:
Sure it does. AP works on both of my Pixel and Pixel XL. Here's the trick. Well, actually, it's no trick, but it's something I remembered from 6.0. With 6.0, you could temporarily unroot, add cards in AP, then resume root. You have to add your credit cards in AP prior to rooting.
In the beginning, I rooted first, then AP couldn't get past the Add A Card screen. I flashed back to 7.1.1 stock, install your (or any) SafetyNet-bypassing kernel. That gets AP working (allows me to add cards). Then re-root.
If screenshots are needed to demonstrate this, I can do that, but that seems rather childish.
---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------
Here goes, unlocked BL + rooted + Android Pay. Screenshot of my multitask screen.
Click to expand...
Click to collapse
That's good to know. If I ever decide to root my device, this will be my workaround (and since I already added my card I should now be able to root it without incident regarding Android Pay).
Thanks for sharing!
Sakete said:
That's good to know. If I ever decide to root my device, this will be my workaround (and since I already added my card I should now be able to root it without incident regarding Android Pay).
Thanks for sharing!
Click to expand...
Click to collapse
No, thank YOU for the kernel.
One item I must mention. That is, AP will break if you disable login security, or even just changing from PIN to password, or anything that would normally require a reactivation of your Android Pay credit cards. Then you just need to reflash the kernel, which in essence kills root. Add back AP, then reroot.
... Of course, Google can always implement another layer to circumvent this workaround in the future. But that's what makes Android fun.
thank you for this kind sir.
*next on my list is a deodexed stock 7.1 so i can start themeing this device...
time to bring BuuF back
Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...
pigmoose said:
Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...
Click to expand...
Click to collapse
Odd... that isn't supposed to happen. Were you rooted when you flashed?
And did you by chance take the OTA for NMF26Q? This kernel is for NMF26O, might not be compatible with the Q build. Haven't created a new kernel yet, will probably just wait for the January update.
pigmoose said:
Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...
Click to expand...
Click to collapse
Sakete said:
Odd... that isn't supposed to happen. Were you rooted when you flashed?
And did you by chance take the OTA for NMF26Q? This kernel is for NMF26O, might not be compatible with the Q build. Haven't created a new kernel yet, will probably just wait for the January update.
Click to expand...
Click to collapse
almost sounds like the active slot got swapped from A to B or B to A. When that happens the previous update boots instead of the current build.
the active slot can be changed in bootloader w/fastboot.
I believe the command for that is:
1. fastboot set_active _a
or
2. fastboot set_active _b
depending on which slot you want active.
I assume that we can flash this over a custom kernel no problem in order to go back to stock?
Related
I decided to create a Thread because there were to many people asking how to Install a Custom ROM using the engineered bootloader and not tripping knox. (I Will not provide links to the Bootloader i already provided the MD5 number to compare so search on google)
I used to have Rapture 2.0 that is based on COF8(I UPDATED to Rapture 2.1 Have wificalling but didn't have time to UPLOAD pictures because i changed to XtreStolite 2.2) and i still have this method. KNOX 0x000.
I don't own any of this files, i just recompiled from the forum. All thanks to the developers and their respective work. (Aou's, g.lewarne and iB4STiD and Others). I REPEAT i don't own any of the files so don't ask for files if they get removed.
Flash it at your own Risk, I am not responsible if you damage your phone or don't follow instructions. Just tested on 920T and 925T tmobile variant and it works. YOU MUST use the engineer bootloader or you will trip knox. Fingerprint and Miracast not working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used this Method:
DOWNLOAD These first:
Download ODIN3 3.10.6 from Here
Download Samsung USB Drivers from HERE
IF you are on 5.0.2 AOCG you must first UPDATE to COF6 from here and not FULL COF8 so you can get back to COF6 if needed. COF8 have more benefits but you still don't know.
STEPS:
1. OPEN ODIN and select AP and choose the 5.1.1 COF6 mentioned before.(Make sure RE-Partition is not selected in options. ONLY Auto Reboot and F. Reset Time) Wait until it verify.
2. Click on START and wait until your PHONE reboot(Never turn it off before it finishes)
3. After phone reboot continue bellow.
Before you do this make sure to ENABLE OEM Unlocking ON, on the Developer Options. (To enable Developer Options, go to Settings/About Device and After tapping the build number 7+ times, you will be notified you are a developer and the option will be there Settings/Developer Options)
1. Flash sboot.bin for you model. (Odin Select BL) Search on Google
S6 920T MD5: 6F8D0372CDF94A5B95B8034B7641E132
S6 925T MD5: 528F23A8138BF6570D1BAE0857B916E4
2. Flash Latest Unikernel from here (AP Odin , To give SE permisive) (Thanks to g.lewarne) Have the In Audio call fixed.
3. Odin-flashable TWRP recovery that Aou's put together (AP Odin) (Original Thread Here) (Thanks to Aou's)
4. Make a full Backup on TWRP just in Case. (Beware Touch screen will be Inverted on TWRP)(Right is left and left is right)
5. Go to REBOOT on TWRP and select DOWNLOAD , Open ODIN Select CP and Flash the G920T_UVU2COF8_BASEBAND.tar.md5. (Original Thread here) (Thanks to iB4STiD)
6. Go into TWRP WIPE/Advance WIPE and select dalvik cache, cache, data, system r/w (DON'T Select Internal Storage) Swipe to wipe.
7. Install Rapture 2.1 from Here. (Original Thread here) (Thanks to iB4STiD)
8. WIPE, Swipe Factory Reset
9. Wait 5-10 minutes first boot.
10. MAKE SURE to ENABLE AGAIN OEM Unlocking like you did the first time before you started the process so you don't have a problem later on with FRP LOCK.
11. ENJOY !!
It is recommended to Charge your phone to 100% and use a Battery Calibration, Restart your phone wait until it boots and remove the charger. Let it discharge until it turns off. Charge it again without interruption up to 100% and remove the charger and use it normally so the battery and system adapts.
In case of any problems you can Wipe and Restore from TWRP or ODIN STOCK 5.1.1 COF8 from HERE to fix any problems.
If you are on firmware COF6 with ONLY COF8 MODEM use the COF6 Odin from here.
Thanks for the write-up! Could you add how you updated from 5.0.2 to COF6? Its too bad fingerprint scanner doesn't work.
Billyvnilly said:
Thanks for the write-up! Could you add how you updated from 5.0.2 to COF6? Its too bad fingerprint scanner doesn't work.
Click to expand...
Click to collapse
Srry for the delay, i added it today the steps. I have been very busy lately creating a Custom ROM and kernel testing it.
Am I able to flash any custom rom using this method and still retain my warranty?
I flashed the ROM in the OP but now I have no sound making phone calls or receiving them.
GeorgeNYer said:
Am I able to flash any custom rom using this method and still retain my warranty?
Click to expand...
Click to collapse
Did you read the OP?
sent from my Hyperdrive powered G Note 10.1
The Apostle said:
Did you read the OP?
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
I'm just double checking, so can I?
Deleted
GeorgeNYer said:
I'm just double checking, so can I?
Click to expand...
Click to collapse
Did you flashed the Unikernel or Unistock latest? If not that is the audio problem.Yes it works with any released Custom rom. Currently i am using latest XtreStoLite Deo-Mod Edition 2.2 [478MB ○ BOGG](Thanks to edgarf18) and if you care for wifi calling xtrestolie doesnt have it. But you can install talkatone(example) can be any app that give you a US number and call fowarding to it when you dont have signal and have wifi and works the same.
Remember sboot or engi bootloader is for 920t or 925t.
It works now after flashing unikernel v6-0001rb. Thank you for finding a way go install custom roms without tripping Knox!!! Now there's still no way no make the fingerprint scanner to work?
GeorgeNYer said:
It works now after flashing unikernel v6-0001rb. Thank you for finding a way go install custom roms without tripping Knox!!! Now there's still no way no make the fingerprint scanner to work?
Click to expand...
Click to collapse
Nop there is no way. I am currently making a hybrid custom rom sometimes it works and sometime cratches... The problem lies in the bootloader invoking it a little diferent because its a 5.0.2 bootloader.
[MY SCREEN IS OPPOSITE] I may have installed something for the Edge variant, although I got lost in trying to get back to stock, which I currently am back at. (5.1.1)
So.... hoping this gets seen, I might xpost over to another thread, but here it goes.....
Notes: 5.1.1
920T model
Ultimately I am trying to get Alliance on my S6 (920T), and no I don't care if the know counter gets tripped (*spoiler* already done)
I started trying to get root for alliance ROM, and got the samsung splash lock after using odin to root. After re-loading the 5.1.1 firmware everything was working again, so I tried this *example* thread on how to install alliance again. After following things around and now have bizzaro phone, to where the opposite sides of the screen need to be pressed for the corresponding action, I am looking for help.....
What about aroma installer roms, can I flash them using this method without tripping the Knox counter?
So I'm all good running a custom ROM with Knox untripped, if I want to flash a different ROM I can just flash normally in twrp and it won't trip Knox?
GeorgeNYer said:
What about aroma installer roms, can I flash them using this method without tripping the Knox counter?
Click to expand...
Click to collapse
Not sure... alliance hasnt worked for me with this... Im going to try another tomorrow. I'll let you know....
If you need call audio or fingerprint scanner working just flash back to the stock F8 bootloader. You can always reflash to the engineering bootloader to flash more things down the line.
Edit: My mistake, seems this is not possible without tripping it.
Calnyx said:
If you need call audio or fingerprint scanner working just flash back to the stock F8 bootloader. You can always reflash to the engineering bootloader to flash more things down the line.
Click to expand...
Click to collapse
Just to make sure i am understanding right - after step 11, i can flash back a stock COF6/8 bootloader, and retain everything (root, custom ROM, etc) without tripping knox, so long as i dont try to flash anything further? I value my fingerprint scanner, and would love to not lose it and knox if at all possible. For future flashing, go back to the eng bootloader, flash, and then reflash the stock again?
If u flash Stock bootloader it will trip knox.
For the screen problem make sure you have unikernel v6.0001. If it doesnt work maybe you have the Aou twrp. Find the Twrp that is for 920t variant. If not fixed try *#2663# and select TSP FW UPDATE AND IT WILL get fixed.
Call audio gets fixed with unikernel... v6.0001
It will work for unified and 920/5t custom roms. I have tried them all and knox still 0x000 never flash stock bootloader with anything that is custom
... or u will trip knox.
Well, thats a bummer, but i figured as much; if it was as simple as flashing back, i figured people would have been doing it.
Still, thank you for the excellent guide. Followed it on my rooted 5.0.2, and everything worked as advertised. Have root, knox, and only fingerprint reader of course is busted (no huge loss)..
is this verified to work with COH8 without tripping KNOX?
I'm creating this thread since we're not allowed to discuss a kernel patch for LOS 14.1 to make Android Pay work on the official thread. From my understanding the biggest issue right now is that Android Pay does not work on LOS because it cannot pass SafetyNet because of unlocked bootloader. We cannot lock the bootloader because we risk hard-bricking the device.
Some (most?) banking apps can still work by flashing Magisk 10.2 and then using Magisk Hide on the banking app, however Android Pay cannot.
Anyone who has any work-in-progress on a kernel patch feel free to post or let us know of any updates. Thank you.
edit: SOLUTION: https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Please try this patch
https://review.lineageos.org/#/c/152083/
josephjdrew said:
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Click to expand...
Click to collapse
deathscythemeng said:
Please try this patch
https://review.lineageos.org/#/c/152083/
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
AfouToPatisa said:
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Click to expand...
Click to collapse
Following the directions in that post I:
Flashed the Lineage addonsu-remove package because I was rooted the Lineage way
reboot
Flash the gemini-safetynetpass package
Reboot
That didn't work (Android Pay still rejected my device).
So I wiped System, Cache, Dalvik, then reinstalled latest LOS.
Reboot and reinstall the gemini-safetynet pass zip.
Still Android Pay won't work.
What is going wrong?
My final intention is to root the device with Magisk. If I install it now, will it help at all?
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MI 5 using Tapatalk
p8pepe said:
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
Click to expand...
Click to collapse
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
AaronWhiting said:
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
Click to expand...
Click to collapse
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
AfouToPatisa said:
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
Click to expand...
Click to collapse
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
It's very weird. Seems like you do everything right. I'm very new to this, so maybe wait for an advanced user to answer. If I was you, I might try to play with the developer options (disable debugging, enable oem unlock etc) or reflash the patch zip or flash magisk zip (and then open magisk app and enable magisk hide).
AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
Please try to downgrage TWRP to official 3.0.2-3 and install Lineage once again. Maybe that will help.
BTW, I've made first payment today on Mi 5 and it works flawlessly, so many thanks for the patch! [emoji1]
Sent from my MI 5 using Tapatalk
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
p8pepe said:
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
No. The only users I know who have it working are using TWRP 3.0.3 as well. I don't want to downgrade it.
My patch install dialogue all looks good, but nevermind. I wasted a day on this. Can't afford any more time, so I've restored my backup.
Maybe I'll try another time.
I have TWRP 3.0.2-3 and Android Pay is working fine. I've advised you to temporarily downgrade to official, because 3.0.3 is not perfect yet. Personally I had major problem with booting on encrypted device so I had to do that. You can upgrade again to 3.0.3 at any time, but it's your choice.
Regards!
Sent from my MI 5 using Tapatalk
AaronWhiting said:
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
Click to expand...
Click to collapse
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
AfouToPatisa said:
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
Click to expand...
Click to collapse
Its ok. I'm over it.
I definitely didn't have root. I'm sure that wasn't the problem.
I even tried it with super clean install. No gapps, no other apps restored, just one to check safety net.
Thanks anyway. I'd still rather carry a credit card than go back to MIUI or waste more time trying.
Me too...
I tried that patch on my Mi5 32GB running RR v5.8.1 after unrooting it and found the device in a bootloop. Just like @AaronWhiting, I'm also flashing from TWRP v3.0.3 stable (but unofficial). Now that would be an entirely new case in itself (since he didn't have any bootloop), but I don't think RR could be an issue since it is also LOS-based, and in fact, I used the 'addonsu-remove-arm64-signed.zip' from LOS extras section to unroot the ROM (RR has built-in root enabled by default) and it worked. Just wanted to ask you guys @p8pepe and @AfouToPatisa , what setup did you have to get a positive result, like say the LOS/other ROM version on which you flashed the safetynetpass zip, device encryption state, and of course the TWRP version as well? Though I understand that you @AaronWhiting have stopped trying to get this thing working, I request you to post your device state as well.
As for me, I am presently on RR v5.8.1 official, GApps micro, no encryption and TWRP 3.0.3. Please add any other important parameter that I may have missed. Let us see if we can solve this out...:fingers-crossed:
Hey,
I have official TWRP 3.0.2-3, LOS 20170131 (clean install - no experimental migration used), opengapps nano. The device is encrypted.
I also had bootloops on TWRP 3.0.3 (probably due to encryption), so downgraded to official.
Sent from my MI 5 using Tapatalk
I'm also using TWRP 3.0.3 & LOS 20170131. Ext partitions all around. Nothing encrypted.
I have been with CM and now LOS since early days of Mi5. Used experimental migration to LOS originally, but went straight to latest version when I did the recent clean flash.
I suspect it's something to do with Bootloader / boot partition but don't have the know-how to troubleshoot further.
I sent @kyasu a PM asking him to check out this thread and help if he can since its his mod were talking about and he'll have the expertise, but haven't heard back yet.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Also, I'm surprised about your troubles with encryption on 3.0.3 @p8pepe since it was specifically meant to FIX those issues.
What this thread is for:
Booting into TWRP Recovery for the Moto Z2 Play Retus Variant
Rooting the Z2 Play Retus Variant with Magisk
Things you will need:
IMPORTANT: You WILL need a USB C OTG cable and USB Thumbdrive (or a USB C Thumbdrive)
Magisk Zip 13.3 Mod uploaded by Junior Passos: https://www.androidfilehost.com/?fid=889764386195922735
Magisk Manager v5.1.1 apk: https://github.com/topjohnwu/MagiskManager/releases/download/v5.1.1/MagiskManager-v5.1.1.apk
DM Verity and Forced Encryption Disabler v5.1: https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
My modified TWRP: https://www.androidfilehost.com/?fid=673368273298983327 md5: ebcecfaf2e00725561555dd398f883dc
Magisk ZIP and DM Verity ZIP must be put on a thumbdrive. Installing from (external) SD Card will not work with this version of TWRP.
Things you will need to keep in mind:
Make sure you fully update your device before unlocking and rooting as it likely will break OTAs. You'll likely have to rely on stock images posted by users to this forum from now on.
In order to be able to do what you need to do in TWRP, you will need to format data due to forced encryption. You won't be able to root and boot your device otherwise.
My version of TWRP is a hacky build. It works, but one feature in particular does not work: External SD card mounting. Until an updated build is made to fix this issue (of which I will require the assistance of people MUCH better at this than I am), you will need to use a USB C OTG cable and a thumbdrive to be able to back up your device and to flash ZIPs.
Try booting (not flashing) the TWRP build here first: https://forum.xda-developers.com/z2-play/development/twrp-3-1-1-0-moto-g5-plus-albus-t3622593 - If it doesn't work (hangs on logo), then try mine.
DO NOT install SuperSU from within TWRP.
These instructions assume you know how to use ADB and Fastboot Android tools. If you need the utilities, you can download the Windows versions from here: https://forum.xda-developers.com/showthread.php?t=2317790
How to boot into TWRP, make backups and root your device:
0) Your device must already be bootloader unlocked.
0a) DO NOT install SuperSU from within TWRP!!
1) Boot into Fastboot (powered off, hold down Power and Vol Down)
2) Plug your USB C cable into your computer and phone, make sure you have the Android tools installed.
3) Use fastboot command to boot into TWRP (NOT flash): fastboot boot albus_twrp.img
3a) I do not recommend flashing this version of recovery to the device because, as I said before, it's a hacky build. I don't want people to rely on it as their permanent recovery in case issues are found and fixed later.
4) Swipe to allow modification, click Cancel when it asks for passphrase to read encrypted partition.
5) Press Wipe on main screen, slide to wipe. This will wipe Data, Cache and Dalvik partitions. You will need to do this because the partitions will have to remain unencrypted after you flash DMVerity and Encryption Disabler.
5a) Yes, you have to wipe. DM Verity and forced encryption will cause your device to fail to boot if you don't disable them.
6) Back up your device. Attempting to back up System Image may fail because the partition is over 4GB and nearly every thumbdrive will be formatted in Fat32. Back up System, Boot and Recovery.
7) Install DM-Verity ZIP.
8) Install Magisk ZIP linked in this thread.
9) Reboot into system. Anticipate a longer first boot.
10) Sideload Magisk Manager.
Magisk running on Z2 Play:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What I did:
Extracted kernel, img_info and dt.img from the retus albus system image and dumped it into a harpia twrp build. I suspect the other version of TWRP was built against a different AOSP version, triggering a SELinux boot block. In my version of TWRP, fstab paths are correct but for some reason MicroSD won't mount. I'll leave that to the professionals. Everything else that I did (as described above) worked and was my exact method for doing so.
Finally:
Special thanks to Dees_Troy for TWRP. Without you, devices would suck.
Here's the Moto Z2 Play Albus boot.img for anyone who wants to take on the task of doing an official TWRP build for the device. https://www.androidfilehost.com/?fid=889764386195927416
You're the man. I'll give this a shot today and report back.
Great tutorial! One question: Does your device pass the "SafetyNet check"?
romhippo.com said:
Great tutorial! One question: Does your device pass the "SafetyNet check"?
Click to expand...
Click to collapse
In my case... it does not fully pass. Passes Safetynet Request and Response Signature... but fails on the Basic Integrity and CTS Profile Match tests. I also did modify /system (ad away, removed bootanimation.zip, moved Magisk apk and Substratum apk into /system) so that could be why.
https://i.imgur.com/u9OVkUq.png
Followed the directions to the letter and everything is working for me. Thanks a lot, twelfth!
Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.
Just a heads up guys. Flashed Magisk 14.0. Passed safetynet. Can't download/install modules though, gives Parse Error or something. Haven't tried installing modules through TWRP to see if it works.
atheart said:
Can't download/install modules though, gives Parse Error or something.
Click to expand...
Click to collapse
I have had the same issue with Magisk 13.3 ...
This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....
cantsingh said:
Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.
Click to expand...
Click to collapse
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
cmjester6421 said:
This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....
Click to expand...
Click to collapse
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.
twelfth said:
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.
Click to expand...
Click to collapse
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:
Cameras not working post root
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.
Can you make this alittle more simple like in steps, I recently got this phone and I want to root it
cantsingh said:
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:
Click to expand...
Click to collapse
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!
ihatevz said:
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!
Click to expand...
Click to collapse
Haha, we've all been there! :good:
Alabamajackhammer said:
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.
Click to expand...
Click to collapse
What's wrong with the camera, after root?
Are there no images to restore out yet?
Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?
Pooper22 said:
Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?
Click to expand...
Click to collapse
Yes. I'm surprised that this surprises you.
Is there a specific reason why op says not to flash SuperSU? Will it not work or damage something?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sony AOSP project
Disclaimer
I'm not liable for anything YOU do to YOUR device, YOU are doing it and it's YOUR device.
What is it?
It's a project developed and maintained by Sony Xperia Developers team.
You can get more informations here: https://developer.sony.com/develop/open-devices/
Can I build it by myself?
Sure, just follow these instructions and have patience!
What works and what doesn't?
According to this official page, almost everything seems to be fine.
How can I flash it?
Follow these steps:
Unlock the bootloader (this will erase your data and will void warranty): https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Setup fastboot on your PC (there are many guides for this step)
Download and unpack the zip archive
Open a shell into the folder containing unpacked files
Run these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (it’s not necessary to flash userdata every time)
Download and unpack the corresponding vendor image from here: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open a shell into the folder containing unpacked image
Run this command:
fastboot flash oem SW_binaries_for_Xperia_xxxxx.img (where "xxxxx" varies depending on the file)
(optional) In case you want to flash GApps, Magisk or other mods, you can use TWRP: https://forum.xda-developers.com/xa2-ultra/development/recovery-twrp-3-2-1-0-touch-recovery-t3774193
Reboot the device and enjoy!
Download link
You can get the builds from my AFH folder: https://androidfilehost.com/?w=files&flid=269497.
I haven't done any change to Sony's source code, these are vanilla builds.
Credits
All credits go to Sony and Google.
XDA:DevDB Information
Sony AOSP, ROM for the Sony XA2 Ultra
Contributors
axxx007xxxz
Source Code: https://github.com/sonyxperiadev
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-05-08
Last Updated 2018-05-08
Reserved
NOTE: I'm in no way associated with Sony, these are unofficial builds and are made for pesonal usage.
Also, these builds are untested so I can't assure they're going to work!
Reserved 2
Post reserved for future usage.
Reserved 3
Post reserved for future usage.
Reserved 4
Post reserved for future usage.
New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r20
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 81032020581dd636ab9d7f8414609bad07332288
Last commit of sonyxperiadev/kernel: 1df958f2943c6c5cae31018e42d2f42e8a55c4b3
Last commit of sonyxperiadev/device-sony-nile: c775da101d57377979cdcb79b1ba1b5bbd3739a4
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=818222786056029296.
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying. And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it.
Click to expand...
Click to collapse
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
roirraW "edor" ehT said:
I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Casserole said:
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Click to expand...
Click to collapse
You're welcome! I'm not suggesting that you flashing Magisk or anything is the cause of this on this ROM, it's just related to changes in Android 8.1 and that it doesn't really necessarily mean there's something wrong. I'm sure there are ways around it, but since I'm not a developer and I don't know what triggers it, I don't know.
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
tombassi said:
cool down dude !! XDA is not the correct please for these bad words. if you don't know what you are doing that is not the Developer fault and if you need no bugs stay with the stock ROM.
Click to expand...
Click to collapse
Thanks! With "almost everything seems to be fine", I meant that most of the main parts (should) work.
Camera is a known problem on Sony devices due to DRM keys getting erased on bootloader unlock.
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Click to expand...
Click to collapse
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
then reboot the phone and test.
These come directly from H4113 makefile, I can't assure you everything will be fine after this, but you can give it a try.
As per the fingerprint, it's currently broken on all variants, I'm sorry.
mirco_pa said:
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
Click to expand...
Click to collapse
Sony website reports it as currently not working on AOSP, I'm sorry.
axxx007xxxz said:
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Click to expand...
Click to collapse
I think SD card problem was related to something else, because it started working after reformatting.
But there were also problems with SIM card, it worked on first boot, but after removing and inserting it again device shown that there were no signal, so your solution may be helpful in this situation. I can't test it due to limited amount of time, though.
New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r26
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 1c992d7f3f2ef8d0b53397e23227e10489e40bec
Last commit of sonyxperiadev/kernel: ab6fd5b1a4126cfdd4391eefe8eba17eb6626781
Last commit of sonyxperiadev/device-sony-nile: 7d57c76da9ce47849429347e77e013781e63db2f
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=890278863836285554.
Can you build one for H4113? You shood have files for it too
Thanks axxx007xxxz for sharing these builds! They helped me recover Android on my completely wiped h3113 pioneer. Both the 8.0 and 8.1 build work for me. Downloading them to my PC was the hardest part, for some reason the download often fails.
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Thank you!
roirraW "edor" ehT said:
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I get the same error message right after booting, also without root. It's annoying, but I guess I can live with it.
P.S. As I'm a new user, I cannot use links yet. Please use these footnotes instead:
*: https[colon]//developer[dot]sony[dot]com/develop/open-devices/downloads/software-binaries
**: https[colon]//developer[dot]sony[dot]com/develop/open-devices/guides/aosp-build-instructions/build-aosp-nougat-8-1-oreo-4-4/#tutorial-step-6
1. parts of android which are closed source, graphics driver for example. you won't see them.
2. eng should give you more debugging options, like working adb logcat without enabling developer options which is sometimes needed while you're porting android to new device and there's just black screen on the phone for example. correct me if i'm wrong.
3. flashing worked through twrp for me but i had to build unsingned zip.
regarding the internal problem message, just ignore it.
davidhozic said:
Can you build one for H4113? You shood have files for it too
Click to expand...
Click to collapse
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Nonstop decay said:
Downloading them to my PC was the hardest part, for some reason the download often fails.
Click to expand...
Click to collapse
Unfortunately, Android File Host is problematic sometime.
Nonstop decay said:
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Click to expand...
Click to collapse
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
axxx007xxxz said:
I can make a H4113 build if you want to test it though.
Click to expand...
Click to collapse
Just wondering aside from not being supported in Sony's open device program what exactly is needed to get the H3223 from getting AOSP 8.1 built for it? I can't imagine the kernel being much different on the H3223 from any of the other XA2 Ultra single sim models, right?
axxx007xxxz said:
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Unfortunately, Android File Host is problematic sometime.
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
Click to expand...
Click to collapse
Yes plese make a build for H4413, i get so many random errors and every time i fix an error there appears another. And is the build for this model supposed to work with h4113? Aren't the boot images incompatible?
I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse
ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro
Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page
there is already something new on this topic?
not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse
some good news
good news
Rooted on 9.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my CLT-L04 using Tapatalk
Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root
Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls
mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent
mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)
Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...