Database Users

Android N Preview npc56p (flashable & image with no encryption and dm verification)

Android N Preview npc56p (flashable & image with no encryption and dm verification)
This thread is for the first Android N Preview.
For Android N Preview 2 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview image released by Google on 3/9/2016. After the installation you will have TWRP recovery 3.0.0-1 and the data partition will be erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery
1- You need to have TWRP 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 N. If your internal storage is unencrypted before flashing it remains unencrypted. Your TWRP is also upgraded to 3.0.0-1.
Method 2: Flash update using a computer
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 N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.0-1.
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
To obtain root after installing this update you should flash SuperSU 2.70 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726. Note that at least at the moment (as of SuperSU 2.70) the root method is a hack solution which requires a lot of further refinement. Many programs are still unable to acquire root and mount the system partition for R/W. However, it is possible to install the android terminal emulator, do an su, mount /system as rw, and do all the modifications within the terminal emulator. Of course you can always use TWRP to modify the system, for which you don't even need to root the device.

Hot dog! First for once... Thanks!
Sent from my Nexus 6 using Tapatalk

#2

will this wipe internal storage ? or only data partition?

For anyone interested...
I enrolled in the Developer Beta program and the OTA worked for me even though I was rooted with SuperSU v2.68.
However, despite installing TWRP 3.0.1 and then SuperSU v2.68 again, root doesn't stick. Fortunately the only critical previously-root-only app I want is a firewall, and Netguard doesn't need root. I can live for a while without Double Tap To Wake, Wakelock detector, Quick Reboot, etc. And the only app that seems to crash is BBC Radio Player, though BBC News and iPlayer still seem ok (warning about libraries, but still plays). And Battery Bot Pro seems to have lost its status bar display...
So it does pretty much what the warnings say - it's stable but not everything will work.

so if i flash this i will still have twrp once rebooted?

kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.

It would be nice moving forward if Google just made SuperSU/root part of their factory image under developer options. So once you enable developer option, there's a little toggle next to OEM unlock that says "root/SuperSU".
Would make life much easier.

simms22 said:
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
Click to expand...
Click to collapse
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
The zip doesn't include stock recovery so if you flash everything according to the instructions you will have twrp at the first reboot.

This kernel worked great thanks. I'm still decrypted and didn't have to wipe internal storage. I didn't run the .bat I manually flashed the img files. Wiped data with TWRP.

so can we flash this via twrp?

omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
no, those are IMG format, flash via fastboot.
I'd wait for root ready then flash...

omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
It literally says right next to the link, "Note that it is NOT a flashable zip."

PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
it says twrp recovery in title, so I was wondering....

what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721

chapelfreak said:
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
Click to expand...
Click to collapse
I flashed that boot img and now i am encrypted and boot-looping. No access to SD card.

Does this build have new bootloader and radio? If so, is it backward compatible to Marshmallow roms or do we need to flash back M bootloader and radio to get M roms work?
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
I lold at this. :laugh::laugh::laugh::laugh:

Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.

kclive said:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
Click to expand...
Click to collapse
Toggle on and off airplane mode. Turn off wifi and see if it works. I was at work and had to do this a few times

Flashed phh kernel (su-noverity - 3rd one) and installed this superuser. I now have root working.

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)
This thread is for the second Android N Preview.
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview 2 image released by Google on 4/13/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP 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 N Preview 2. If your internal storage is unencrypted before flashing it remains unencrypted.
For some people this didn't work. It seems to be the case when you have been encrypted by your previous Android N installation, in which case TWRP seems to have difficulty reading the file, and that seemingly Preview 2 doesn't play nice with TWRP. It works best when you are unencrypted and your recovery is 3.0.2-0. Thanks to @gammaxgoblin, @blitzerking1, @Michael in ATL, @HueyT, and @PhillyFlyer for debugging and hints.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
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 N 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.71 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133. Despite the fact that SuperSU 2.71 is supposedly re-written for Android N, there are still some apps that seem to have a problem obtaining root. The commonest complaint on this thread so far has been about Adaway. If you want to block Ads just manually do what Adaway does. Download a hosts file from any ad block list server such as http://winhelp2002.mvps.org/hosts.htm, copy the files on your sdcard, boot the phone into recovery, and using the TWRP file manager replace the file /system/etc/hosts with this file and set its permissions to 644 (rw-r--r--).

wouldnt flash first go. redl now
no flash again

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Same happened to me. It would not flash, same error

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
Same error for me as well. I can extract the zip and view the file it is talking about. I also tried on TWRP 3.0.1-0 and TWRP 3.0.2-0
Everything is working perfect for me with the new zip. I have a unencrypted phone and used 3.0.2 TWRP.

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
i tried 3.0.1 and 3.0.2 and i can also see the file

Method 2 works great

Method two works I used it myself

Shall I flash preview 2 directly from marshmallow?

Seems like TWRP is having a lot of troubles with each version of N Preview's encryption. I have same problem with both N6 and N6P, as do others in that forum too....:/

i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.

marius987 said:
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
Click to expand...
Click to collapse
Sorry for the stupid question. What do you mean for TB?

cerico76 said:
Sorry for the stupid question. What do you mean for TB?
Click to expand...
Click to collapse
I'm going to assume it stands for Titanium Backup.

Waiting for fixed method #1

outkastz said:
I'm going to assume it stands for Titanium Backup.
Click to expand...
Click to collapse
Ah,yes! Thanx!

Can someone please provide a link to the desktop website for the flashable zip?

Just to help with the installation of method 2, holding shift and right clicking a blank space in your unzipped folder, you can click open command window here. That will save you having to CD all the way to it.
Sent from my Nexus 6 using XDA-Developers mobile app

I did method 1. It upgraded fine. All my data remained. It killed root (expected this) and my TWRP. I was unencrypted before attempting.
I went and downloaded the latest TWRP and flashed via fastboot. Then downloaded latest SuperSU from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and flashed it via my newly installed TWRP. Root confirmed and all is well.
Good to go Thanks!

I've got an "Invalid boot image" issue :
Any tought ?

outpox said:
I've got an "Invalid boot image" issue :
Any tought ?
Click to expand...
Click to collapse
You may have to flash a previous stable release of marshmallow or lollipop from Google first and then try this because something seems to be corrupted in your system.

[TUTORIAL][Tethering]+[Android Pay] How to have your Nougat, and eat it too!

Obviously I'm not responsible for your mom exploding or your phone disowning you, but.....
I got tethering and Android Pay working on stock Nougat - that's Android N, folks - on a Nexus.
(confirmed will work on Marshmallow and up on 5, 5x, 6, 6p...etc.)
Thanks to @Chainfire, @ManHands and @interloper, and you!
click thanks if this helps, or buy me a beer or something.
prerequisites:
working adb and fastboot (from platform-tools in the Android SDK if you don't know where to find it)
twrp .img for your device
latest stable systemless supersu
1. be on Marshmallow or Nougat obviously
2. flash twrp
(volume down + power on nexus gets you into bootloader, then after flashing recovery, use volume buttons to scroll and power button to select recovery mode)
3. flash systemless root while booted into twrp (unsure if .supersu SYSTEMLESS=true in /data is still needed, but can't hurt - mine is still there from earlier.)
4. while still in twrp, go to mount and check system. Make sure you allow changes.
5. from your computer, do this
Code:
adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop
6. reboot into Android.
7. Install Terminal Emulator from the Play Store.
8. Launch it, and in Terminal Emulator, do this
Code:
su
settings put global tether_dun_required 0
exit
9. go into Supersu, expert, scroll to the bottom and hit full unroot. No, you don't want it to patch you back to the stock boot image or recovery*. If it hangs, just reboot and try doing it again.
10. ????
11. Profit! You should have tethering unlocked, be unrooted, and have full Android Pay goodness working.
To take an OTA, do this, because Flashfire gets confused after you've done build.prop edits -
1. go to About Phone, scroll down. Find your build number.
2. download that Nexus Factory Image.
3. Unzip it all. ALL OF IT.
4. Make sure you have Android SDK & platform-tools (or just a working Fastboot and ADB)
5. just flash boot, system, and recovery - you can now OTA with no problems. Then repeat the above guide on your new OTA. Confirmed working 10 minutes ago, OTA'ing from Marshmallow to Nougat and then getting tethering working again
ALTERNATE IF YOU PREFER FLASHFIRE:
All the above steps, but you only have to flash the System image to fix the build.prop hash fail then flashfire should work for you. Wouldn't necessarily recommend upgrading version numbers (6.0.1 to 7.0.0) with Flashfire, but who knows, it might work great! Chainfire is a wizard.
*you can do this if you want, but when I let it patch my boot image I got the dreaded "device corrupt!!!!1" message at boot. Did not try letting it flash stock recovery image.

You're mentioning to do a systemless root but enable read/write on the system partition. Isnt't that counter-intuitive?

codycook said:
You're mentioning to do a systemless root but enable read/write on the system partition. Isnt't that counter-intuitive?
Click to expand...
Click to collapse
Nope! rw system is only for the build.prop echo, other than that you don't touch /system

Have you been able to get this to work with the latest factory Nougat images from Google's website?
I successfully did your process above when I was on an older version of Nougat for Nexus 6 (beta release), but when I try now with NBD90Z Google Pay won't work after rooting after a full unroot.

Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .

cal028 said:
Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .
Click to expand...
Click to collapse
Hmm. Bummer. For a split second, I felt like I finally had a fully functioning Android
Almost regret upgrading to NBD90Z, but figured it would be less buggy. If anyone has figured out how to get AP and NBD90Z to work with a slightly modified build.prop file (to allow tethering), please update this thread!

cal028 said:
Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .
Click to expand...
Click to collapse
same for me too. Pulled build.prop and verified net.tethering.noprovisioning=true and settings put global tether_dun_required 0
still no luck on NBD90Z

w8291 said:
same for me too. Pulled build.prop and verified net.tethering.noprovisioning=true and settings put global tether_dun_required 0
still no luck on NBD90Z
Click to expand...
Click to collapse
Flashed back down to NRD90S and the method works again.

Where did you download that version?
The stock Nexus 6 images on the official Google site do not list that version as valid for the Nexus 6.
Are you using the Nexus 6P image?

May be a dumb question but I have a Moto X Pure running Ressurection Remix nougat ROM and I don't have WiFi tethering in my settings. Would this method work on it?

worked, thanks

n8onXDA said:
Have you been able to get this to work with the latest factory Nougat images from Google's website?
I successfully did your process above when I was on an older version of Nougat for Nexus 6 (beta release), but when I try now with NBD90Z Google Pay won't work after rooting after a full unroot.
Click to expand...
Click to collapse
With the current build, no methods work. SafetyNet check fails with the last 2 builds

Safety net now requires OEM lock, even fully stock with open bootloader never rooted fails
Sent from my Nexus 6 using Tapatalk

Ok great! Well at least I know I'm not missing some clever workaround. Isn't there a way to bypass SafetyNet and/or OEM lock? I thought someone was trying or working on something like this...

wrecklesswun said:
With the current build, no methods work. SafetyNet check fails with the last 2 builds
Click to expand...
Click to collapse
So I read that the March 2017 7.1.1 Update for Nexus 6 broke Android Pay even on non-rooted devices so Google released images with SafetyNet disabled. Would that version allow us to root AND use Android Pay since SafetyNet is disabled to make it work for regular users?

Had to do this but gaining root was going to be tricky (encrypted partition), and I didn't need root for any other reason. I unlocked the bootloaded, flashed twrp, and used adb to pull build.prop, added the line in (net.tethering.noprovisioning=true), pushed it back using adb (with twrp still running), and rebooted. Tethering is working fine now.
By the way -- this is so infuriating. When tethering does not work it asks your provider's permission even in airplane mode (which fails, it's airplane mode), so you can't use the phone to provide wifi to other devices. Such an amateurish disrespect for my rights as an owner of an unlocked device.

I flashed Vanilla rom 7.1.2, then flash stock recovery and locked bootloader and Android pay, Netflix and Snapchat etc all work. After I flashed Vanilla rom Android pay wasn't working stating I had a root, so I locked bootloader but was bootlooping into twrp. After flashing stock recovery it worked just fine

I discovered that you can you can have TWRP recovery and still use android pay so long as you have your bootloader locked. I am pretty sure you can still flash roms w/ locked bootloader in recovery but I am not positive

[Discussion] DualBootPatcher

I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.

Got now rr as primary rom and will try later on to flash some roms on the second space... Let you know if that works out.

Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk

superior8888 said:
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
Click to expand...
Click to collapse
I have also rr as primary but second rom install ended in error 1 in twrp. Maybe you can try to reset data of second rom with the dualboot patcher zip.

It might be helpful to read the Dual Boot Patcher thread for the OP5, as there may be some important info there that is relevant for getting it to work on the 5T.

I tried rr as primary, no problem. Tried adding 2nd rom as secondary, as data slot 1, and no dice. Even tried removing assert lines in the updater script as suggested in op5 with rr as 2nd rom but that didn't work either; either booted back to twrp or booted to a black screen. If anyone makes it work please document and share your work. I'm encrypted by the way, even though you're "supposed" to be decrypted I was able to switch between primary and the non-booting rom just fine.

Anyone having any luck with this?

matteosaeed said:
Anyone having any luck with this?
Click to expand...
Click to collapse
Nope primary install goes good with a oos rom not stock. But when you try to install a second rom it gives error 1 in twrp and rom don't boot up.

That's great! Old MultiROM user here!

Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?

superior888 said:
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Click to expand...
Click to collapse
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN ?
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.

cubandanger05 said:
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
Click to expand...
Click to collapse
Thanks for updating us, I'm an old multirom user as well and I'm going to keep my eye on this.

cubandanger05 said:
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
Click to expand...
Click to collapse
Thanks! I'll try this next days.

Thanks. Nothing works with Oreo as of yet i suppose :/

superior888 said:
Thanks. Nothing works with Oreo as of yet i suppose :/
Click to expand...
Click to collapse
It may be possible to have oreo as primary and flash Nougat as data slot roms. I tried with Phoenix as primary and I could boot into rr Nougat in data slot but Phoenix wouldnt boot. If someone can try rr oreo as primary and report back. I'm tempted to try with otg and see if I can install secondary roms using extsd option

*Quick update*
I was able to keep latest Phoenix oreo ROM as primary and install and boot Nougat RR as data-slot and as secondary using the latest dualbootpatcher app which may have fixed the "failed to update mbtool" error I was getting on Phoenix ROM. Also I used Magisk 14.0 for root as the latest version 16.0 kept booting back to recovery on non primary ROMs.
I'm still unable to flash Oreo ROMs as data-slot or secondary. At least we're able to keep Oreo as primary and test Nougat ROMs until dualbootpatcher app is compatible with Oreo or until some other fix is released.
Internal storage/data is still encrypted and unreadable on all non-primary ROMs; you must be decrypted prior to installing additional ROMs to have access to it, which I haven't tested yet.
See screenshots

Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.

es0tericcha0s said:
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
Click to expand...
Click to collapse
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Edit: Now that it's working almost as intended we should make an official "how to" thread

cubandanger05 said:
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Click to expand...
Click to collapse
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.

es0tericcha0s said:
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
Click to expand...
Click to collapse
? understandable

Updating Android on SM-T560

I got a brand new Samsung Tab E 9.6" (SM-T560). Shame on me, I didn't notice before it comes with Android 4.4.4
As many apps require newer OS, I'm wondering if I can upgrade it to Android 6.0.
Plase note:
1. I'm not an expert, so please explain me as easy as possible how to do it, if it can be done;
2. please tell me, in case,if it's 100% legal and/or if it can void warrant.
Thank you.

Samsung Tab E
Check again --- Just picked up the same thing this week at Walmart for $129.00 + $25 Google Play credits - it came with 7.1.1. - Take it back sounds like you got some real old stock..

They do come with Android 4.4, however if you go to Samsungs web page you can find a crispy 7.1.1 image you can flash with Odin. Then if you wish you can unlock bootloader and flash a custom recovery like CWM or TWRP and then chainfires systemless root. Cheers! Upgrading to just 7.1.1 with Odin will not void your warranty, anything else that involves unlocking the bootloader will and is will trip samsungs knox security feature. If warranty is important only flash the 7.1.1 image using Odin.

Hello,
I'm searching forsuch an update, too. But It seems, that it was only released for USA and CA. But I'm from Germany. @xSLAYERx do you have a link to the ROM?

xSLAYERx said:
They do come with Android 4.4, however if you go to Samsungs web page you can find a crispy 7.1.1 image you can flash with Odin. Then if you wish you can unlock bootloader and flash a custom recovery like CWM or TWRP and then chainfires systemless root. Cheers! Upgrading to just 7.1.1 with Odin will not void your warranty, anything else that involves unlocking the bootloader will and is will trip samsungs knox security feature. If warranty is important only flash the 7.1.1 image using Odin.
Click to expand...
Click to collapse
heya, could you please share a link of this 7.1.1 with me? or the image itself, I can't find it anywhere and I'm stuck with 4.4.4
thank you!

hurkagyurka123 said:
heya, could you please share a link of this 7.1.1 with me? or the image itself, I can't find it anywhere and I'm stuck with 4.4.4
thank you!
Click to expand...
Click to collapse
Hi, I was with the same problem, and I posted here in XDA, I'm from Brazil, i have the model SM-T560, and now i'm using nougt, from Lineageos 14.1, and this was only possible, because someone from Xda, gave me the following link:
http://www.gearappsnap.com/2018/03/14/how-to-install-android-nougat-on-the-galaxy-tab-e-sm-t561/
The rom is of the SM-T561 model, but also works on the SM-T560, read everything before doing anything. When installing TWRP, you can install the version of the SM-t560, which will not make any difference.
One more thing, I advise you to see some YouTube tutorials how to install TWRP. Just in case.

Thank You for your help!

hurkagyurka123 said:
Thank You for your help!
Click to expand...
Click to collapse
For nothing, follow step by step that will work perfectly. Except this will end your warranty, but it's the only way to install an update. If you need any help, just talk.

gearappsnap site is not really good made.. The download links behind text which look like a normal one and also that it says, flash boot.img only when the memory is wrong..
Well, CM14.1 did not work for me.. I had to flash boot.img before EVERYTHING else, then rebooted again to TWRP and THEN install cm14.1.

Um, did you follow step by step?
I followed what was written, and for me it worked normal, The boot.img file is to fit just the memory of the table because it had some problem with the rom, without installing it, has tablet that got locked in infinite loop. And the links were working normal for me.
Links that i download:
ROM: https://drive.google.com/file/d/1D0wrGM4XyZMo-t3ll4trvJ93Pl1KEZ1V/view
Boot.img: https://drive.google.com/file/d/1bqGmu4NTlEeKdsFPGjIY9lnPqujjazr4/view
softkeys: https://drive.google.com/file/d/1ddSB28g1xTd0J7sl8V6QmlPZA1aX77ot/view
Gaps: https://opengapps.org/
First the TWRP is installed, with the battery above 70%, then restarts the tablet.
Within the TWRP:
1) Wibe-> advanced wibe-> selects almost anything but not microSD and OTC. and Wibe.
2) Back to the home page-> Install-> select the external storage (the files must be saved on the SD card).
3) The first file to be installed is the rom.
4) Once installed, go back to the files and at the bottom of the page you will click install image and install boot.img.
5) After Boot.img is installed, switch back to Install Zip, and Install the Softkeys.
6) After installing the softkeys go back and install the Gaps. (I used the ARM-7.1-Pico) and restart the tablet.
In my case I did not install superSU. That's what I did. This rom has some flaws but better than Kitkat, that's what I think.

thE_29 said:
gearappsnap site is not really good made.. The download links behind text which look like a normal one and also that it says, flash boot.img only when the memory is wrong..
Well, CM14.1 did not work for me.. I had to flash boot.img before EVERYTHING else, then rebooted again to TWRP and THEN install cm14.1.
Click to expand...
Click to collapse
HEY!
download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow steps.
1-install TWRP 3.0.2-1 via odin
2- copy ALL files of .zip in one folder in storage (mem stick)
3- power off and then power on IN TWRP (vol + + home + power button)
4- make full wipes except externar storage
5- install zip (first choice lineage -14, then choice open gapps, next choice key.zip)
6- install img (choice boot.img)
7- WIPE (Dalvik, cache)
enjoy android 7.1 in your tab e T560

63or63 said:
HEY!
download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow steps.
1-install TWRP 3.0.2-1 via odin
2- copy ALL files of .zip in one folder in storage (mem stick)
3- power off and then power on IN TWRP (vol + + home + power button)
4- make full wipes except externar storage
5- install zip (first choice lineage -14, then choice open gapps, next choice key.zip)
6- install img (choice boot.img)
7- WIPE (Dalvik, cache)
enjoy android 7.1 in your tab e T560
Click to expand...
Click to collapse
In reality you have to install boot.img and softkeys before, the reason is because they are modified for the T56X, otherwise install themselves after the gaps will give error when to use. At least it is what was written on the site, and so far I have been using no defect at all.

marcelo010 said:
In reality you have to install boot.img and softkeys before, the reason is because they are modified for the T56X, otherwise install themselves after the gaps will give error when to use. At least it is what was written on the site, and so far I have been using no defect at all.
Click to expand...
Click to collapse
I do not think that is effective. if you come from 4.4.4 and install it before the lineage ROM (BASE 7.1 for example) it will be erased again because with the new base everything is overwritten.

63or63 said:
I do not think that is effective. if you come from 4.4.4 and install it before the lineage ROM (BASE 7.1 for example) it will be erased again because with the new base everything is overwritten.
Click to expand...
Click to collapse
Well that didnt work for me.. Was coming from Stock 4.4 ROM. Flashed the CM14.1 AND softkeys, but NOT the boot.img, because you cannot flash zip and img files at the same time. Then I booted it and it crashed 10-60secs after it booted. Sometimes it had a boot loop.
Then I tried CM 13 which worked fine and in a german board, someone wrote (based on the gearappsnap site) that the boot.img has to be the first thing to flash and even reboot into twrp again and then flash CM14.1 + softkeys + gapps.

If you could install it, that's what matters, in my case it worked the way it was on the site, there are some bug's, but it's a lot better than the stock rom, and I was already using a custom rom on the T560 before installing this LineageOS 14.1,and it was this link:
https://forum.xda-developers.com/galaxy-tab-e/development/rom-lightning-t3716039

Szia!
did the upgrade work for You For galaxy tab e?

Done this and it worked but.........
The tablet is really slow, not netflix compatible with this version, and so on....
I think I just might downgrade again

After I have tried step 3, it didnt open in twrp mode. My tab stucks in black screen with "Samsung galaxt tab e " text in background.Please let me know how to proceed.

[QUOTE = "63or63, Post: 78613279, Mitglied: 4438103"]
HI THERE!
Download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow the steps.
1-install TWRP 3.0.2-1 through odin
2- Copy ALL .zip files to a folder in memory (mem stick).
3- turn off and then turn on IN TWRP (vol + + home + power button)
4- Make full towels except for external storage
5- install zip (first choice line -14, then select open gaps, next choice key.zip)
6- install img (choose boot.img)
7- WIPE (Dalvik, Cache)
enjoy Android 7.1 in your Tab e T560
[/ZITAT]
1000 tanks BR
.

1000 x danke es hat funktioniert
Translation: 1000 x thank you it worked