Database Users

Android Nougat nbd90z (flashable & image, no encryption, no dm verification)

** DISCLAIMER: APPLY AT YOUR OWN RISK **​** The following are instructions for installing Android Nougat released by Google on 10/4/2016. **​Always backup your data before flashing stuff you download from the internet!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP 3.0.2-0 or higher installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to Nougat. If your internal storage is unencrypted before flashing it remains unencrypted.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and flashes TWRP 3.0.2-0)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to Nougat with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.78 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703.
Some of your apps may be too old to work properly under 7.0 so if they act up you may need to uninstall them and install the newer versions. If some of your old settings like wifi calling don't work properly, especially if you upgrade from a custom ROM, it is not because of this flashable zip, the reason is that Nougat is having trouble converting your settings and a factory reset will solve all of your problems.

was waiting for this to drop, awesome, downloading now
Sent from my Nexus 6 using Tapatalk

Thanks!

so i can just flash this if im on franco kernel r19 runing andro 5.1.1?
---------- Post added at 10:25 AM ---------- Previous post was at 10:18 AM ----------
how do i flash twrp3.02? can i just use flashify app?

Works great and as advertised. Thanks!

flash-all.bat contains a typo.
fastboot flash boot shamu-npd90g-boot-NoEncNoVerify.img
should be
fastboot flash boot shamu-nbd90z-boot-NoEncNoVerify.img

So can we still flash this over yesterday's nougat update or have to go back to M?

This is what I have been waiting for, najoor I have been using your NDP5 since July, thank you for your work downloading now.

yudumcan said:
So can we still flash this over yesterday's nougat update or have to go back to M?
Click to expand...
Click to collapse
Yes, no need to go back to M.

najoor said:
Yes, no need to go back to M.
Click to expand...
Click to collapse
Thanks mate. So what's the difference than this release http://forum.xda-developers.com/nex...ightromstock-lmy47e-03-19-2015-t3059493/page4
Edit: what if I'm encrypted?

Works great. If you are a Verizon customer with an unlimited data plan, you can use root explorer to add net.tethering.noprovisioning=true to your build prop to unlock tethering. (Must be rooted to use root explorer.)

Thanks op! Will this flash bootloader and radios too? I'm coming from MM custom ROM. Also, why the modified kernel and what is different from stock?
Sent from my Nexus 6 using Tapatalk

xt926 said:
Thanks op! Will this flash bootloader and radios too? I'm coming from MM custom ROM. Also, why the modified kernel and what is different from stock?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes it will flash everything. The kernel is modified so that you can change the OS through recovery without getting a bootloop. Unmodified kernels after lollipop check for system integrity at every boot up and generate a panic signal if something is changed. Also the modified kernel does not force encryption so your system remains unencrypted if it already is.

I presume this bootloader is backwards compatible with M ROMs as was the previous one?

Well I was hoping the official build would've fixed my Wifi disconnection problems but unfortunately I'm still having them. Anyone else? Mine started on P5 and I've done everything as far as turning on and off different settings on my phone, to resetting my router to see if that was the problem and it's still continuing to do the same thing.

Flashed this over najoor's NDP5 and added ElementalX 4.08 and superSu 2.78, works perfectly. No issues, all root apps still working, very smooth and stable.
Thank you najoor nice work.
Nexus 6

jk8260 said:
Flashed this over najoor's NDP5 and added ElementalX 4.08 and superSu 2.78, works perfectly. No issues, all root apps still working, very smooth and stable.
Thank you najoor nice work.
Nexus 6
Click to expand...
Click to collapse
Can u post a link for that superSU 2.78. TIA
So far so good. Tmo Nexus.
Sent from my SM-G935T using XDA-Developers mobile app

Thanks for this! How come no Nougat boot animation?

info[]box1 said:
Can u post a link for that superSU 2.78. TIA
So far so good. Tmo Nexus.
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Direct URL
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
XDA page
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Nexus 6

kxs783kms said:
Well I was hoping the official build would've fixed my Wifi disconnection problems but unfortunately I'm still having them. Anyone else? Mine started on P5 and I've done everything as far as turning on and off different settings on my phone, to resetting my router to see if that was the problem and it's still continuing to do the same thing.
Click to expand...
Click to collapse
Do a clean install then. Dirty flashing over DP5 caused it to others too.
Sent from my Nexus 6 running cyosp using Tapatalk

Correct Way Of Rooting A Moto Z Play As Of Feb/ 17

Ok folks you're here because you have the need to root​MM 6 or Nougat 7.0 Only
As of February 2017 you need 3 things
Unlocked Bootloader
Motorola Device Manger (drivers):Download
1) TWRP ( Recovery)
2) Modified kernel (F2FS fixes)
3) SuperSu 2.79 R3 systemless root
TWRP can be found Here: TWRP
Modified Kernel can be found here:TWRP & Modified kernel
Download both the modified kernel, either the MM one Or Nougat 7.0, depending on which OS you are using and download the modified kernel to your internal sd card ( Our external sdcard can't be read by TWRP, so all flashable zips must be in your internal sdcard)
Flash recovery through fastboot Code: fastboot flash recovery (name of recovery).img
Do not reboot but use the volume buttons on the phone to select recovery from the menu on the fastboot screen.
Now we can flash the Modified Kernel which you have previously downloaded to your internal sd card.
Flash the Kernel.
Now download SuperSu
SuperSu:SuperSu 2.79 R3
NEW FOR NOUGAT 7.1.1 ONLY
Unlocked bootloader
Motorola device manager Download:Download["]Moto Device Manager
Twrp recovery downloaded into the same folder as fastboot
Gaining root differs from 7.0 or 6.0, you can only root with magisks 13 or above if you are running any stock based rom or custom based rom that doesn't have built in root, you no longer need to flash the F2FS fixed kernel on 7.1.1
Magisks Thread :Magisks Thread
You need to flash Magisks to disable dm-verity otherwise your phone will not boot this is because the stock kernel checks for any modifications to the system
That's it
Thanks to @Alberto97 & @tomparr

Will be useful for noobies
Enviado desde mi XT1635-02 mediante Tapatalk

Do you suggest disabling force encryption. I'm rooted but encrypted currently. If disabling would make significant speed boost I'm willing to take the pain of setting-up apps and stuff from scratch and format userdata

Nil253259 said:
Do you suggest disabling force encryption. I'm rooted but encrypted currently. If disabling would make significant speed boost I'm willing to take the pain of setting-up apps and stuff from scratch and format userdata
Click to expand...
Click to collapse
I'm unecrytped and see real no gain, I think it's more of a placebo effect.

is that superSU better than Magisk?

Do you still need official bootloader unlocking ? aka no more warranty ? Thanks

razorsbk said:
Do you still need official bootloader unlocking ? aka no more warranty ? Thanks
Click to expand...
Click to collapse
Yes

Thank you.
Sent from my XT1635-02 using Tapatalk

Will all this work with Windows 10?

shawnsac2000 said:
Will all this work with Windows 10?
Click to expand...
Click to collapse
It will if you have the right drivers installed

punkerEVO said:
is that superSU better than Magisk?
Click to expand...
Click to collapse
It's confirmed that you'll have root with SuperSu 2.79 R3, Magisk's may cause Issues under certain circumstances.
I'ver tried to keep as simple as possible because there's 2 other threads with root method's that are not up to date.

Thanks

dedraks said:
Thanks
Click to expand...
Click to collapse
Lol OK I can see where this could get confusing now.

Thanks flashallthetime.
I misread your instructions though and I am in trouble. I misread the bit about copying the modified kernel to internal SD card; instead I copied to external SD card (as I have always done with previous devices). I now can't flash the modified kernel because the newly flashed TWRP 3.0.2 doesn't have access to the external SD card.
The current state of the device is that it is stuck at the unlocked warning screen. It says "ID: bad key", but after flashing a recovery, it says "ID: N/A".
Is this consistent with the kernel not being flashed, or do I have another issue?
If I get an OTG cable, can I flash the modified kernel that way with TWRP? Can this version of TWRP access an OTG USB device on Moto Z Play?
Anyone? Thanks so much!!

You can use fastboot to flash boot.img.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
punkerEVO said:
Lol OK I can see where this could get confusing now.
Click to expand...
Click to collapse
How?

dedraks said:
You can use fastboot to flash boot.img.
Click to expand...
Click to collapse
Is that to me? Which boot.img, where do I find it? Thanks!

raymosaurus said:
Is that to me? Which boot.img, where do I find it? Thanks!
Click to expand...
Click to collapse
Yes.
Extract from the ROM in this post:
https://forum.xda-developers.com/moto-z-play/development/rom-stock-7-0-t3553213

raymosaurus said:
If I get an OTG cable, can I flash the modified kernel that way with TWRP? Can this version of TWRP access an OTG USB device on Moto Z Play?
Click to expand...
Click to collapse
Should do fine. Did not test with this version, but using Chinese twrp I could mount and afterwards access OTG partition. Don't see a reason why this one should behave differently.
If you want to use fastboot, the command should be (from memory): fastboot flash boot boot.img

tag68 said:
Should do fine. Did not test with this version, but using Chinese twrp I could mount and afterwards access OTG partition. Don't see a reason why this one should behave differently.
If you want to use fastboot, the command should be (from memory): fastboot flash boot boot.img
Click to expand...
Click to collapse
For God's sake people , don't use the Chinese TWRP. 2 people that I know have mistakenly wiped their IMEI with that junk.

dedraks said:
You can use fastboot to flash boot.img.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
How?
Click to expand...
Click to collapse
I have a flashable zip of the Nougat stock boot.img
Here https://www.androidfilehost.com/?fid=457095661767138793

Flyme official beta 6.0 released

Finally flyme 6.0 beta official is released
link :- http://www.flyme.cn/firmwarelist-76.html#8

i just install this flyme 6.0 beta...seems to be great...dont know yet if it could be used as a daily...feedback later...thanks

So any reviews?

My review for the previous version of flyme 6, was this:
"Just flashed.. Great animations, graphics, sounds and a unique feeling in general.
BUT! This rom asks for every single app for internet and location permissions! from calendar to gallery and notes, in music app and so on.. And if you don't to give permissions there is only an "exit" option and you can't use the app! Maybe it's safe but it seems to me a little shady.
There are many chinese apps preinstalled which explains the size of the rom.
Furthermore some notifications are in chinese and you can't understand what they say.
I flashed opengapps after flashing the rom with no success, so I used a google installer from their store and it worked just fine..
Photos from the camera are stretched and Gallery doesn't show anything as mentioned..
wifi/bluetooth/data works fine."
(I don't know if any of these changed in this version)

Mchasard said:
i just install this flyme 6.0 beta...seems to be great...dont know yet if it could be used as a daily...feedback later...thanks
Click to expand...
Click to collapse
can you please mirror it because it seems like the official link is not working. I really want to download but not able to download from anywhere

download worked for me but failed to flash with status 7 error !! what's causing that anybody??

intoxicated.mad said:
download worked for me but failed to flash with status 7 error !! what's causing that anybody??
Click to expand...
Click to collapse
First flash oos 3.1.4 then wipe only dalvik cache/data don't wipe system.

ajmcklosky said:
First flash oos 3.1.4 then wipe only dalvik cache/data don't wipe system.
Click to expand...
Click to collapse
Thanked .... worked perfectly

intoxicated.mad said:
download worked for me but failed to flash with status 7 error !! what's causing that anybody??
Click to expand...
Click to collapse
please can you share zip with me on google drive or any where else ?
download link is not working for i tried many times

tapanrgohil said:
please can you share zip with me on google drive or any where else ?
download link is not working for i tried many times
Click to expand...
Click to collapse
Try this link: http://openrom-dl.flyme.cn/111732199/20170704/1499109120027/flyme_ONE-E1001_xs_6.7.6.30R-beta.zip

Did anyone flash it? I was stuck at TWRP. It wont boot to rom.

sundhar88 said:
Did anyone flash it? I was stuck at TWRP. It wont boot to rom.
Click to expand...
Click to collapse
First flash oos 3.1.4 then wipe only dalvik cache/data, don't wipe system.

ajmcklosky said:
First flash oos 3.1.4 then wipe only dalvik cache/data, don't wipe system.
Click to expand...
Click to collapse
I did that. nothing helped.
did you flashed successfully?
what version of twrp do you have?
It flashes its own twrp

sundhar88 said:
I did that. nothing helped.
did you flashed successfully?
what version of twrp do you have?
It flashes its own twrp
Click to expand...
Click to collapse
Yes, it worked perfectly on twrp 3.0.2-2 bluespark v41.
try flashing any other ROM or try downloading the ROM again.
Check if you can access the downloaded ROM files in winRAR or any zip extractor.

sundhar88 said:
I did that. nothing helped.
did you flashed successfully?
what version of twrp do you have?
It flashes its own twrp
Click to expand...
Click to collapse
I guess this ROM is for old boot loader.

How are y'all finding the ROM? How stable is it?
EDIT: I just flashed it and I really hate it. Prefer to use stock android

sundhar88 said:
I did that. nothing helped.
did you flashed successfully?
what version of twrp do you have?
It flashes its own twrp
Click to expand...
Click to collapse
Got a workaround just unmount system and then flash.

Project deleted.

Projector permanently suspended.

reserved for updated links.

Sands207 said:
I just made a ROM for Boost/Sprint SM-J327P J3 Emerge that should be flashable in TWRP. I have 2 versions, One that should be Odin flashable and the other being a zip that should be easily flashed in TWRP once we work out the kinks ... I worked primarily on LG's before this and Samsungs long before that. Anyway these are the features I've added so far:
Deodexed
Pre-rooted
Deknoxed
Busybox included
init enabled
Csc debloated (not exactly sure what to remove for bloat but I need feedback on what can be kept etc...
zip aligned on boot
xposed
links coming later today....
lemme know if I missed anything!!
I need testers! Chime in if you would like to help, we have a way to unbrick easily via Odin
*Update* 7.11.17 Flashed it on my phone but may have gotten steps CONFUSED? Installs perfectly... No loops just either takes forever to load initially or hangs on my device. I got sick of waiting but I'm curious if others know, when we flash a new pre rooted stock rom do we need to wipe data, then supersu & dm verity patch? Will removing csc stuff brick this device?
*FLASH AT YOUR OWN RISK!* I am not responsible for ANY damage to your device. ALWAYS MAKE A BACKUP FIRST, I can link to Odin and firmware files if needed til we get this right.
Flash rom
Mount DATA
Format data in TWRP this will wipe internal storage
Reboot recovery
Flash Supersu
Flash dm verity patch and *possibly* Xposed?
Credit goes to @[email protected]@[email protected] for TWRP Recovery and Root https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Wait for device to boot first boot may take awhile!!
Initial Alpha Release: https://drive.google.com/file/d/0Bz99NuhE3Xwmd2c4d3ZDV3dPcTA/view?usp=drivesdk
Signed Version
https://drive.google.com/file/d/0Bz99NuhE3XwmWXZHdWxCalBNcWM/view?usp=drivesdk
Please Report back with failure, success or bugs or feature requests.
Click to expand...
Click to collapse
Ill download and get back to you with sucess/failure or w.e i might encounter that can be tweakes.
Regards
Doctur

I'm downloading it now, I'll flash it as soon as I'm done. I just wiped my J327P after having root, no more knox, and Xposed running smooth. It accidentally had a pocket party with my keys and some of the seedier Xposed modules one night and then after that, it was never the same. I think I pretty got no more USB besides Odin. TWRP can't even use it.
But hey, listen Sands. This better not be some bull****. Don't you ever **** me Sands. You hear me? Don't you ever **** me. :good:

IdealInShade said:
I'm downloading it now, I'll flash it as soon as I'm done. I just wiped my J327P after having root, no more knox, and Xposed running smooth. It accidentally had a pocket party with my keys and some of the seedier Xposed modules one night and then after that, it was never the same. I think I pretty got no more USB besides Odin. TWRP can't even use it.
But hey, listen Sands. This better not be some bull****. Don't you ever **** me Sands. You hear me? Don't you ever **** me. :good:
Click to expand...
Click to collapse
ANYTHING

Sands207 said:
I just made a ROM for Boost/Sprint SM-J327P J3 Emerge that should be flashable in TWRP. I have 2 versions, One that should be Odin flashable and the other being a zip that should be easily flashed in TWRP once we work out the kinks ... I worked primarily on LG's before this and Samsungs long before that. Anyway these are the features I've added so far:
Deodexed
Pre-rooted
Deknoxed
Busybox included
init enabled
Csc debloated (not exactly sure what to remove for bloat but I need feedback on what can be kept etc...
zip aligned on boot
xposed
links coming later today....
lemme know if I missed anything!!
I need testers! Chime in if you would like to help, we have a way to unbrick easily via Odin
*Update* 7.11.17 Flashed it on my phone but may have gotten steps CONFUSED? Installs perfectly... No loops just either takes forever to load initially or hangs on my device. I got sick of waiting but I'm curious if others know, when we flash a new pre rooted stock rom do we need to wipe data, then supersu & dm verity patch? Will removing csc stuff brick this device?
*FLASH AT YOUR OWN RISK!* I am not responsible for ANY damage to your device. ALWAYS MAKE A BACKUP FIRST, I can link to Odin and firmware files if needed til we get this right.
Flash rom
Mount DATA
Format data in TWRP this will wipe internal storage
Reboot recovery
Flash Supersu
Flash dm verity patch and *possibly* Xposed?
Credit goes to @[email protected]@[email protected] for TWRP Recovery and Root https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Wait for device to boot first boot may take awhile!!
Initial Alpha Release: https://drive.google.com/file/d/0Bz99NuhE3Xwmd2c4d3ZDV3dPcTA/view?usp=drivesdk
Signed Version
https://drive.google.com/file/d/0Bz99NuhE3XwmWXZHdWxCalBNcWM/view?usp=drivesdk
Please Report back with failure, success or bugs or feature requests.
Click to expand...
Click to collapse
DM Verity is better if you flash it before instead of after root method. Instead of flashing SuperSU use magisk because a lot of apps are starting to reject rooted devices using SuperSU. After flashing magisk, wipe cache and dalvik

SonderTech said:
DM Verity is better if you flash it before instead of after root method. Instead of flashing SuperSU use magisk because a lot of apps are starting to reject rooted devices using SuperSU. After flashing magisk, wipe cache and dalvik
Click to expand...
Click to collapse
Should i make a new build with magisk incorporated? I've never used it before but my lady uses snapchat and will likely need this to root hers as well. i didn't update mine but she did so has the second to newest ota build on hers, i can use her system dump for an update. Can you link me to the recommended version for ours? xposed seems ok too but seems limited. thanks for your input
Sent from my SM-J327P using Tapatalk

Sands207 said:
Should i make a new build with magisk incorporated? I've never used it before but my lady uses snapchat and will likely need this to root hers as well. i didn't update mine but she did so has the second to newest ota build on hers, i can use her system dump for an update. Can you link me to the recommended version for ours? xposed seems ok too but seems limited. thanks for your input
Click to expand...
Click to collapse
She definitely will need magisk then, they are all the way on 13.2 . I could try to help you through the installation if you would like.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3

SonderTech said:
She definitely will need magisk then, they are all the way on 13.2 . I could try to help you through the installation if you would like.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3
Click to expand...
Click to collapse
Definitely, ill be back at my pc tonight or tomorrow i really appreciate it. hoping to make the next one smoother magisk sounds pretty interesting, do we have a safe list of what we can remove? or what needs to be flashed w the rom?

Sands207 said:
Definitely, ill be back at my pc tonight or tomorrow i really appreciate it. hoping to make the next one smoother magisk sounds pretty interesting, do we have a safe list of what we can remove? or what needs to be flashed w the rom?
Click to expand...
Click to collapse
Knox files are good to remove. Samsung device manager and samsung+ is a no go. That's all I know at the moment. Before I forget, if your gonna flash gapps do it before rooting but after DM Verity

SonderTech said:
Knox files
are good to remove. Samsung device manager and samsung+ is a no go. That's all I know at the moment. Before I forget, if your gonna flash gapps do it before rooting but after DM Verity
Click to expand...
Click to collapse
Cool, so from what ive gathered so far im going to make the next rom unrooted but deodexed as as debloated as i possibly can safely and we will flash the newest MM gapps first, then dm verity and a reboot to recovery per the directions, then magisk and finally xposed and clear cache and dalvik at the end... sound about right? I did try flashing magisk on my device as is but it failed because the boot image was already patched and stock was needed instead. Is dm verity absolutely needed or could magisk accomplish in theory what our patch does?

Sands207 said:
Cool, so from what ive gathered so far im going to make the next rom unrooted but deodexed and we will flash the newest MM gapps first, then dm verity and a reboot to recovery per the directions, then magisk and finally xposed and clear cache and dalvik at the end... sound about right? I did try flashing magisk on my device as is but it failed because the boot image was already patched and stock was needed instead. Is dm verity absolutely needed or could magisk accomplish in theory what our patch does?
Click to expand...
Click to collapse
I think it's better to flash Dm Verity and you would do it before you flash gapps because to flash Dm Verity you have to format data so you can mount the data partition

SonderTech said:
I think it's better to flash Dm Verity and you would do it before you flash gapps because to flash Dm Verity you have to format data so you can mount the data partition
Click to expand...
Click to collapse
ok excellent. I appreciate your help ?
Sent from my SM-J327P using Tapatalk

Sands207 said:
ok excellent. I appreciate your help ?
Click to expand...
Click to collapse
No problem, and when your flashing it on your device just flash stock ROM flash twrp recovery and then do the Dev mode and OEM unlock setup and then wipe data once again flash Dm Verity and clear cache and dalvik and then setup your device and then flash magisk and then wipe cache and dalvik once again

SonderTech said:
No problem, and when your flashing it on your device just flash stock ROM flash twrp recovery and then do the Dev mode and OEM unlock setup and then wipe data once again flash Dm Verity and clear cache and dalvik and then setup your device and then flash magisk and then wipe cache and dalvik once again
Click to expand...
Click to collapse
Excellent. I'll update the OP when i post the second build.

Sands207 said:
Excellent. I'll update the OP when i post the second build.
Click to expand...
Click to collapse
Coolio and if you need a boot animation just pm me. I have a couple zips that need converting and resizing.

SonderTech said:
Coolio and if you need a boot animation just pm me. I have a couple zips that need converting and resizing.
Click to expand...
Click to collapse
Awesome, I just finished the second build. My upload speed is insanely slow so it may take all night for me but i did manage to cut the size down considerably ? im sure there will be stuff to remove still but everyone is different. Definitely about a new boot animation tho stock is pretty blah lol

Sands207 said:
Awesome, I just finished the second build. My upload speed is insanely slow so it may take all night for me but i did manage to cut the size down considerably ? im sure there will be stuff to remove still but everyone is different. Definitely about a new boot animation tho stock is pretty blah lol
Click to expand...
Click to collapse
I have a batman sonar animation I got from bhoot.co.uk that I converted to a QMG for our device, just need to upload it to the drive with the rest of them

Alpha 2 released: https://drive.google.com/folderview?id=0Bz99NuhE3XwmWGN5ejBqMDlNUVU
Will update OP in a few to reflect changes ?

Is it going to be possible to port Lineage OS to this device ?

Magisk on Oreo

I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.

I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...

GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?

+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)

+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?

kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!

+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?

GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.

kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)

I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.

kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?

GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good: