Galaxy Tab A 10.5 SM-T590/SM-T595/SM-T597
TWRP and Lineage 16/17.1 for (SM-T590/SM-T595/SM-T597)!!!!!!!!!!!!!!!!!!!!!
BROUGHT TO YOU BY: MrHomebrew
BIG CREDIT TO: Rupansh (For his time, work: dedication and discovery on how to achieve TWRP on these devices).
THANK YOU TO: Cale (For his time, findings and testing).
READ ENTIRE POST!!!!!!!!
READ ENTIRE POST!!!!!!!!
READ ENTIRE POST!!!!!!!!
THIS IS AT YOUR OWN DESCRETION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT COULD GO WRONG (for example a BRICKED DEVICE)!!!!!!!!
EXPECIALLY IF YOU CAN NOT FALLOW INSTRUCTIONS PROPERLY!!!!!!!!
THIS IS SIMPLY A GUIDE AND IF YOU ARE WILLING TO ATTEMPT ON YOUR OWN DEVICE THAT IS FULLY YOUR CHOICE, RESPONSIBILY and DESCRETION!!!!!!!!
IF YOU ARE STUCK IN A BOOTLOOP REBOOT TO DOWNLOAD MODE AND FLASH STOCK SAMSUNG ROM IN ODIN AND IF YOU WOULD LIKE, TRY AGAIN!!!!
1.
Download stock/unmodded Odin:
https://forum.xda-developers.com/attachment.php?attachmentid=4946889&d=1581302091
Install stock SM-T590/T595/T597 PIE rom with stock/unmodded Odin in download mode
(POWER OFF TABLET AND BOOT WITH VOLUME UP, DOWN AND POWER BUTTON WELL PLUGGED IN TO YOUR PC THROUGH USB).
2.
Finish setup SKIP ALL and enable OEM UNLOCK in developer options/settings.
(If developer options/settings is not viewable tap build number in settings/about a bunch of times)
(Then go back and you should see developer options in settings and ENABLE OEM UNLOCK).
3.
Download patched/modded Odin:
https://forum.xda-developers.com/attachment.php?attachmentid=4952061&d=1581888388
Reboot to recovery (POWER OFF TABLET AND BOOT WITH VOLUME UP AND POWER BUTTON).
Select wipe data/factory reset in recovery (THIS WILL WIPE THE TABLET).
THEN SELECT REBOOT TO BOOTLOADER (DO NOT REBOOT THE DEVICE TO THE SYSTEM, STRAIGHT TO THE BOOTLOADER/DOWNLOAD MODE)
(BLACK LOOKING SCREEN THIS TIME).
4.
Download TWRP:
(SM-T590)
Mega - https://mega.nz/#!nVIknQrB!-Zb_xBWy2_Ruj0TBMHPQGvND1uA_LtOvwdRkmV9sFnQ
Zippyshare - https://www15.zippyshare.com/v/dLVoxicq/file.html
(SM-T595/SM-T597)
Mega - https://mega.nz/#!GQQWnASY!T0oJEkwu9m2rviVYFHy_E5tfithsqLYUTjcIW04iGzw
Zippyshare - https://www45.zippyshare.com/v/2VGMIYyb/file.html
Well in download mode open patched/modded Odin.
Select options in patched/modded odin and UNCHECK Auto Reboot and F. Reset Time.
Select recovery.tar.md5 (SPECIFIC FOR YOUR DEVICE MODEL SM-T590 or SM-T595/SM-T597) in the AP tab of patched/modded odin.
Flash recovery.tar.md5 to your tablet.
WHEN FINISHED MAKE SURE TO REBOOT TO RECOVERY MODE/TWRP(STEPS BELOW).
HOLD (VOLUME DOWN AND POWER BUTTON) AND AS SOON AS THE TABLET TURNS OFF HOLD (VOLUME UP AND THE POWER BUTTON) TO FORCE RECOVERY MODE/TWRP
(DO NOT REBOOT THE DEVICE TO THE SYSTEM, STRAIGHT TO RECOVERY MODE/TWRP).
5.
Download Lineage 16 Download Lineage 16 and unpack the .xz so you are left with a .img file (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
(SM-T590/SM-T595/SM-T597)
Sourceforge - https://sourceforge.net/projects/an...017-UNOFFICIAL-treble_a64_avN.img.xz/download
Download Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
Mega - https://mega.nz/#!eUpj3AAR!B-3_dgBX9nEj4PJufCnCl7FsiS5bJXy-XvNsBg2KQXg
Zippyshare - https://www120.zippyshare.com/v/fDpBrVte/file.html
Download open_gapps-arm-9.0-nano (SELECT AND DOWNLOAD ARM, 9.0 nano VARIANT) (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
https://opengapps.org/
Unmount your micro sd in TWRP, remove CURRENT/MAIN micro sd card from your tablet and replace with the SECONDARY micro sd.
In recovery/twrp select wipe tab, then format data and type yes fallowed by enter (THIS WILL FORMAT/ERASE ALL DATA ON THE TABLET).
Go back to main TWRP menu, select reboot and then REBOOT TO RECOVERY.
Once Rebooted to RECOVERY/TWRP select install and at the bottom select install img.
Find the lineage-16.0-20191017-UNOFFICIAL-treble_a64_avN.img select and install it to SYSTEM IMAGE (MAKE SURE YOU SELECT SYSTEM IMAGE FOR INSTALL LOCATION!!!!).
Go back and select wipe then advanced wipe. Toggle System partition, select repair or change partition and then Resize File System.
(Swipe to resize).
Go back select install and at the bottom select install zip.
Then install open_gapps-arm-9.0-nano zip file in TWRP (AND THEN WIPE CACHE/DALVIK).
Go back select install and install Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip in TWRP.
Unmount your micro sd in TWRP, remove SECONDARY micro sd from your tablet and replace it with the MAIN micro sd card.
6.
REBOOT TO SYSTEM AND SEE THE MAGIC HAPPEN (NOT DONE YET IF YOU WANT ANDROID 10 ALONG WITH ADOPTABLE STORAGE!!!!).
Setup device
FORMAT your MAIN micro sd card in android (SHOULD SEE A NOTIFICATION TO FORMAT MICRO SD CARD).
Select the formatting notification, dismiss the first popup and select adoptable/internal storage. (Be Patient and let it finish formatting).
(IF LINEAGE 16 DOES NOT ASK TO FORMAT MICRO SD CARD EJECT THEN PLACE IT IN A WINDOWS COMPUTER AND FORMAT TO SOMETHING ANDROID DOES NOT LIKE AND TRY AGAIN)
(FALLOWING INSTRUCTIONS BELOW)!!!!
Then insert your MAIN micro sd card (THAT IS FORMATTED IN A WAY THAT FORCES YOU TO HAVE TO REFORMAT) the MAIN micro sd card in Lineage 16
(SHOULD SEE A NOTIFICATION TO FORMAT MICRO SD CARD).
Select the formatting notification, dismiss the first popup and select adoptable/internal storage. (Be Patient and let it finish formatting).
7.
Download Lineage 17.1 and unpack the .xz so you are left with a .img file (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
(SM-T590/SM-T595/SM-T597)
Sourceforge - https://sourceforge.net/projects/an...111-UNOFFICIAL-treble_a64_avN.img.xz/download
Download open_gapps-arm-10.0-nano (SELECT AND DOWNLOAD ARM, 10.0 nano VARIANT) (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
https://opengapps.org/
Download PHH-Magisk (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD)
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
Power off or reboot to twrp (VOLUME UP AND THE POWER BUTTON).
Unmount your micro sd in TWRP, remove MAIN micro sd card (NOW USED AS ADOPTABLE STORAGE) from your tablet and replace with the SECONDARY micro sd.
Now select install and at the bottom select install img.
Find the lineage-17.1-20200111-UNOFFICIAL-treble_a64_avN.img select and install it to SYSTEM IMAGE (MAKE SURE YOU SELECT SYSTEM IMAGE FOR INSTALL LOCATION!!!!).
Go back and select wipe then advanced wipe. Toggle System partition, select repair or change partition and then Resize File System.
(Swipe to resize).
Go back select install and at the bottom select install zip.
Then install open_gapps-arm-10.0-nano zip file in TWRP (AND THEN WIPE CACHE/DALVIK).
Go back select install and YOU MUST INSTALL Magisk-v20.2-b29f0ca4-phh.zip (OR ELSE LINEAGE 17.1 WILL NOT BOOT).
Go back select install and install Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip in TWRP.
Unmount your micro sd in TWRP, remove SECONDARY micro sd from your tablet and replace it with the MAIN micro sd card (STILL USED AS ADOPTABLE STORAGE).
8.
(VERY IMPORTANT YOU CAN UPDATE (MAGISK MANAGER) BUT NOT (MAGISK) ITSELF!!!! DO NOT UPDATE MAGISK!!!!) YOU WILL END UP IN A BOOT LOOP).
(VERY IMPORTANT) REBOOT TO SYSTEM AND GO IN TO MAGISK MANAGER.
Go to modules in Magisk Manager and install Busybox for Android NDK (DO NOT REBOOT) and also install MagiskHide Props Config (NOW REBOOT).
After reboot go to developer options/settings (System/Advanced/Developer options) and enable Local terminal.
(If developer options is not viewable tap build number in settings/about a bunch of times till it enables)
(Then go back and you should see developer options in settings).
9.
Return to home screen and launch terminal app.
In terminal app type "su" (WITHOUT QUOTES) and hit enter (ALWAYS HIT ENTER TO EXECUTE THE COMMAND).
Accept Magisk/Superuser popup for terminal.
(If you accidentally deny/miss permission go to Magisk a enable Superuser for terminal).
In terminal app type "props" (WITHOUT QUOTES).
Select option "1" (WITHOUT QUOTES), then select option "f" (WITHOUT QUOTES) and then select option "23" (WITHOUT QUOTES).
Now select (ONE OF THESE 3) options "45" (WITHOUT QUOTES) for SM-T590 / option "46" (WITHOUT QUOTES) for SM-T595 / or option "47" (WITHOUT QUOTES) for SM-T597.
Finally select "y" (WITHOUT QUOTES) to accept and then select "y" (WITHOUT QUOTES) to restart.
FINISHED!!!!
YOU ARE DONE!!!!
Hope you enjoy, a lot of work has gone in to making this possible on the Galaxy Tab A 10.5 SM-T590/SM-T595/SM-T597.
BUGS/ISSUES:
Encryption
Lockscreen password NOT WORKING (DO NOT SET A PASSWORD)
MTP not working in TWRP
Two out of four speakers WORKING
Can only enable adoptable storage in Lineage 16 and carry it over to Lineage 17.1
DEMONSTRATION/REVIEW VIDEO COMING SOON!!!!
BROUGHT TO YOU BY THE ONE AND ONLY: MrHomebrew
Contributors: MrHomebrew, Rupansh and Cale.
Source Code Used To Help Build TWRP For SM-T590/SM-T595/SM-T597
https://github.com/rupansh/android_kernel_samsung_gta2xl
Magisk_PHH and Lineage 16/17.1 GSI: AndyYan
XDA:DevDB Information
[RECOVERY][ROM][ROOT][UNOFFICAL] TWRP 3.3.1-0 + Lineage [SM-T590/SM-T595/SM-T597], Kernel for the Samsung Galaxy Tab A series
Contributors
Leonidas87, rupanshji, AndyYan, Cale
Source Code: https://github.com/rupansh/android_kernel_samsung_gta2xl
Kernel Special Features:
Version Information
Status: Stable
Created 2020-02-20
Last Updated 2020-02-20
confirmed working on sm - t590.
many thanks !
supelele said:
confirmed working on sm - t590.
many thanks !
Click to expand...
Click to collapse
You are welcome, thanks for confirming you had success on your end :good:
One issue. Wifi does not stay enabled.
Connection gets disconnected here.
supelele said:
One issue. Wifi does not stay enabled.
Connection gets disconnected here.
Click to expand...
Click to collapse
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
MrHomebrew said:
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
Click to expand...
Click to collapse
Did try that. It keeps remembered and after a resstart it is connected. But after 2 Minutes it goes to disconnected and stays there.
Tried 2 wifis. Tried aswell reflashing line 17.
No success :/
MrHomebrew said:
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
Click to expand...
Click to collapse
Disableing location did the trick
Want to try but...
Firstly, thank you for this. I can only imagine the time and effort to figure this out.
How the hell you guys do this I'll never know. Kudos.
Now, what if I want to install LineageOS 16 without the adoptable storage and get root? Is there a reason one needs adoptable storage for this process?
Nervous about having an eventually-to-fail sd card in there and no spare sd card slot to add storage.
All I really want (sorry, would like) right now is root so I can fiddle with my device. It seems all other attempts at pure root result in bootloop and having to reflash stock. I know, I tried https://forum.xda-developers.com/showthread.php?p=81286251#post81286251 and posted my results.
Is there a method to just install LlineageOS/Gapps, Magisk, Busybox/su?
Not wanting to knock your efforts, but a slimmed down LinOS16 with root installation instr. will be fantastic!
Is there a benefit to having to do the system install with adoptable storage?
Thanks again.
T
TrinityTrip54 said:
Is there a method to just install LlineageOS/Gapps, Magisk, Busybox/su?
Not wanting to knock your efforts, but a slimmed down LinOS16 with root installation instr. will be fantastic!
Is there a benefit to having to do the system install with adoptable storage?
Thanks again.
T
Click to expand...
Click to collapse
You don't have to use adoptable storage it's just an option really. If you want to use lineage 16 you can just fine with even magisk canary builds, might want try out some other GSI a64a ( ARM 32-bit with 64-bit binder, A-only) builds with an AOSP base and see what works. The only benefit would be having extra install space for loads of apps and full access to storage. As far as lineage 17 goes you must flash the magisk-phh for it to even boot but adoptable storage you don't need. Still follow the instructions minus adoptable storage and you'll achieve root in no time. As of right now there's been weekly builds of lineage GSI. Hopefully we'll get a real build of lineage 17 eventually.
Highly recommend orange fox recovery.
whenever i try to flash the recovery i get an error only official released binaries are allowed to be flashed how do i resolve this problem?
Mikxx said:
whenever i try to flash the recovery i get an error only official released binaries are allowed to be flashed how do i resolve this problem?
Click to expand...
Click to collapse
https://www.the***********.com/prenormal-rmm-state-on-samsung-galaxy-guide/
dm.homelinux.com said:
https://www.the***********.com/prenormal-rmm-state-on-samsung-galaxy-guide/
Click to expand...
Click to collapse
link broken but it still helped me out thanks
Boot loop after installing Busybox for Android NDK and MagiskHide Props Config
8.
(VERY IMPORTANT YOU CAN UPDATE (MAGISK MANAGER) BUT NOT (MAGISK) ITSELF!!!! DO NOT UPDATE MAGISK!!!!) YOU WILL END UP IN A BOOT LOOP).
(VERY IMPORTANT) REBOOT TO SYSTEM AND GO IN TO MAGISK MANAGER.
Go to modules in Magisk Manager and install Busybox for Android NDK (DO NOT REBOOT) and also install MagiskHide Props Config (NOW REBOOT).
After reboot go to developer options/settings (System/Advanced/Developer options) and enable Local terminal.
(If developer options is not viewable tap build number in settings/about a bunch of times till it enables)
(Then go back and you should see developer options in settings).
Click to expand...
Click to collapse
Hello community,
I am now at this point. I have installed just Linage 17, without Linage 16 without gapps, because i dont need them.
So, lineage 17 is starting, now I have to prepare Magisk.
I have updated _JUST_ Magisk Manager (see screenshot) and installed two recommended modules (Busybox for Android NDK and MagiskHide Props Config)
After reboot ends up in a boot loop. Interim solution is start to recovery and make factory reset. In this case is Magisk not available. After Magisk installation there is again a loop. I tried this 3 times. What I am doing wrong?
dm.homelinux.com said:
Hello community,
I am now at this point. I have installed just Linage 17, without Linage 16 without gapps, because i dont need them.
So, lineage 17 is starting, now I have to prepare Magisk.
I have updated _JUST_ Magisk Manager (see screenshot) and installed two recommended modules (Busybox for Android NDK and MagiskHide Props Config)
After reboot ends up in a boot loop. Interim solution is start to recovery and make factory reset. In this case is Magisk not available. After Magisk installation there is again a loop. I tried this 3 times. What I am doing wrong?
Click to expand...
Click to collapse
Are you using magisk-phh? Also try using magisk manager Canary
Yes. Step 7
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
What ist Magisk Manager canary?
Edit: many thx
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
It semms to be stable, after I installed this apk. Magisk is now available as app, i can see the installed modules and the system starts correctly.
Do I ned the next steps with su?
The rom works great, but one question, is it possible to get the assistant ambient mode on this device when i place it in my pogodock?
Mikxx said:
The rom works great, but one question, is it possible to get the assistant ambient mode on this device when i place it in my pogodock?
Click to expand...
Click to collapse
As far as I know probably not. These are GSI builds and are not exactly fully supported for our devices but still function pretty good.
---------- Post added at 08:53 AM ---------- Previous post was at 08:53 AM ----------
dm.homelinux.com said:
Yes. Step 7
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
What ist Magisk Manager canary?
Edit: many thx
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
It semms to be stable, after I installed this apk. Magisk is now available as app, i can see the installed modules and the system starts correctly.
Do I ned the next steps with su?
Click to expand...
Click to collapse
Next steps for su? Which steps are you referring too? As soon as you have magisk-phh flashed with Canary manager on 17 you have SU. As far as 17 goes do not update magisk just manager. 16 you can use any magisk up to Canary
koobie777 said:
Next steps for su? Which steps are you referring too? As soon as you have magisk-phh flashed with Canary manager on 17 you have SU. As far as 17 goes do not update magisk just manager. 16 you can use any magisk up to Canary
Click to expand...
Click to collapse
I refer to step 9 in this manual on page 1.
But su is indeed over Magisk configuration. ROM works very well
Magisk also working with LineageOS 16 ?
jb44 said:
Magisk also working with LineageOS 16 ?
Click to expand...
Click to collapse
Yes up to Canary. Use magisk-phh for 17
---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------
dm.homelinux.com said:
I refer to step 9 in this manual on page 1.
But su is indeed over Magisk configuration. ROM works very well
Click to expand...
Click to collapse
Step 9 is recommended for safteynet
Related
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Someone posted a tutorial on YouTube, the title of video is "MIBOX 3 MDZ-16-aa ROOT + Install Android TV English".
@[email protected], did you get Netflix to work on it?
dummyaccount said:
Someone posted a tutorial on YouTube, the title of video is "MIBOX 3 MDZ-16-aa ROOT + Install Android TV English".
@[email protected], did you get Netflix to work on it?
Click to expand...
Click to collapse
I tried all the steps.
No google play videos, no voice search and most of all no netflix.
=(
I hate the ****ing Chinese that sold me MDZ-16-aa saying it was the international version.
dont work password androidtv rom....... is Mibox2015?
mdz 16-AA
I faced the same issue.Wrong password.
Thanx for your post [email protected] I am going to use this method for my Mi box3.
As I am going to root any device for the first time, what precautions should I take
that I don't brick it?
Does the Microphone and and Ok button on Remote work normally after rooting by your method ?
Thx in advance....
[email protected] said:
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Click to expand...
Click to collapse
I tried to downgrade my MDZ-16-AA device with the MiBOX3_jurassicpark_gitv_1.3.106.386 file ... but it brings it down only to 1. 3. 114 and not to 1. 3. 106.
Secondly I do not get "ADB Debugging" option. Hence I cannot connect my Mi Box to my laptop.
Can anyone help ?
the correct password is : '@'mibox2015
the quotes are only to avoid mention to xda user "mibo" in xda forum...u don't have to write it in...
mibox v1.5.1
I've troubles to root my mibox, I've the 1.5.1 version.
Can you help me, please ?
Mi box 3C v 1.5.1
Can it possible to do the same for version 1.5.1?
I have Mi box 3C v 1.5.1 and I can't even boot into recovery yet.
Add widevine drm in MDZ-16-AA
To complete your notice, I found a way to launch MyCanal and molotov.tv (not tested for netflix yet).
As you know these apps requires widevine drm.
First download
extractor 4.0 and Xiomi 3S official rom
Then extract update.zip and add in root folder of extractor: system.new.dat + system.transfert.list.file_context
Use Extractor.bat to uncompact system.new
On folder go on system\vendor and copy paste lib folder on USB key.
Does anybody know how to go to recovery mode?
HOLD Back + OK and Home + Option doesn't work for my MDZ-16-AA
the system has been automatically updated yesterday.. :crying:
Thank you so much, I got it installed.
Step 1 can be hard because of the chinese language therefor I used this link:
https://www dot cnx-software dot com/2016/04/12/how-to-change-language-to-english-and-install-apps-remotely-on-xiaomi-mi-box-3-enhanced/
at step 2 I made the mistake that I extracted the update.zip aswell. while I needed to keep it zipped.
I used the app RUFUS to make the usbdrive a FAT32 drive.
at step 3 Kingoroot worked for me, although I needed to restart several times to make the ADB debugging connection work.
at step 4 sending the TWRP files, was a bit of a hurdle. It wwas not possible for me to copt them from the USB stick with ES file manager to the device. I needed to use the USB cable to my computer (ADB off) password: "@mibox2015"
At point 5 I was not able to use my remote or keyboard, I needed to turn off ADB!
At the end allot works, but there is still some bugs:
- MIUI still present. eg. when connecting an usb stick you get a chinese menu. and you are able to get into the old system menu
- unable to get NETFLIX to work
- allot of bloatware, apps I can not disable or delete.
- im unable to disable search by microphone in the UI, which is not supported by the remote of the 16-AA
- im unable to edit the tiles in the homescreen to eg. hide the supersu, market etc. and to put PLEX of KODI more in front
Thanks!!!!
I have rooted my mibox 3c and installed TWRP app
I copied img to device and flash drive, but I can't choose any img in TWRP app...
any method to replace custom recovery?? THX
weiabroad said:
I have rooted my mibox 3c and installed TWRP app
I copied img to device and flash drive, but I can't choose any img in TWRP app...
any method to replace custom recovery?? THX
Click to expand...
Click to collapse
Go through each step carefully, if stuck be clear about what you have done
Sent from my A0001 using Tapatalk
Arquivo converter ROM chinesa para global 3C-16AA
Olá, gostaria dos arquivos para converter a ROM 3C-16AA, você tem whats para contato?
Hey,
Im' trying to get mycanal to work on my mibox MDZ-16-AA.
I copied the lib folder on my usb stick.
it's still not working, isn't any steps missing ?
Thanks.
Secure Check failed error while downgrading
I Got "secure check failed." error while downgrading. What did i do wrong ?
[email protected] said:
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Click to expand...
Click to collapse
I successfully rooted my mibox 3c (MDZ-16-AA) and installed TWRP app and Android TV.
Now I want to go back to the Xiaomi Original Firmware (1.5.25). I tried to use TWRP and the Update.zip, but it did not work. How can I do it? Many thanks!
---------- Post added at 09:59 AM ---------- Previous post was at 09:53 AM ----------
I read from a Chinese forum that the 1.4.32 can also be rooted. As far as I know the Android TV is based on the 1.3.106. Does it make any sense to root the MDZ-16-AA with the firmware 1.4.32 and install the Android TV then?
[HOW-TO] Installing AOSP Android 7.0 "Nougat" Internally on the 16 GB Nook Tablet
Edit 2-5-23: I recently revisited my installation and found it had become sluggish to the point of being more or less useless. Google Play service updates had taken their toll. So I decided to start over and use microG instead. I also found that the original rooting method no longer worked for some unknown reason, so I resorted to Magisk. Seems like a good time for an update to the instructions!
[shamelessly adapted from peerless instructions for other NT installs by @digixmax, and information from @mikeataol that is scattered through the CM 13.0 thread.]
Disclaimer: Neither I nor any other user mentioned here, real or imaginary, is responsible if you brick your device following these instructions. The only stupid question is the one you didn't ask right before you ruined your tablet.
By following these instructions you can install an AOSP Android 7.0 ROM from @amaces internally (into emmc) on a 16 GB Nook Tablet running either stock, CM 10.x, CM 11.x, CM 12.x, or CM 13.x, assuming you have done no special repartitioning (it may also work if you have done special repartitioning, but I do not know). If you have previously installed CM 14.x and have repartitioned, you can return to those installation instructions where there may be a description of how to revert to the regular partitioning. This ROM does not require any special partitioning.
The AOSP ROM is a bare-bones, very responsive build. It runs rings around my former CM 12.1 install without any freezes or shutdowns. Using microG to spoof Google Services Framework signature frees you from the relentless pressure of GApps as Play Services are always updating and always expanding. I originally used a pico GApps package on my first install. At the time the package was 77 MB. The current package as of this editing is 184 MB--too much for the device. You can start with my original package but it won't stay that size. Still, some people will want to try so I have provided instructions for both microG and GApps.
If you have a bootable SD card made for installing CM 10.x-13.x, you can skip to step 2b.
1. Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on the SD card a Primary FAT32 partition, set the partition ID type for the partition to 0x0C FAT32 LBA, and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
2. Obtain and copy to the SD card the following files:
a. first MLO, then next u-boot.bin, and finally flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
b. TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
c. the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
d. the zip file of the AOSP Android 7.0 ROM by @amaces, i.e., aosp_acclaim-ota-NBD90Z.161020.zip from https://www.mediafire.com/?5vcw8l603d3r5sc or https://mega.nz/#!nQwiEILS!dm7i-4AOUzYW5yP0LaqcZ5EAUsxeh-Qr8DULB4BGYZ8 [this ROM is no longer in the repository maintained by @amaces] (alternate link provided by @mikeataol)
e. Magisk for the Nook Tablet: https://forum.xda-developers.com/attachments/magisk-v16-0_patched2-zip.4427362/ (credits to member @fddm)
OPTIONAL:
f. the zip file of the GApps package (corresponding to Android 7.0): https://www.mediafire.com/file/po12x99lg47p4oj/open_gapps-arm-7.0-pico-20170310.zip/file
3. Put the SD card into the NT and boot from its power off by inserting a powered USB cable. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display.
a. Select SDC Recovery.
b. [Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
c. Return to TWRP opening screen and select Install. From the external SD card install flashable_TWRP_3.0.2-0.zip
(my experience with TWRP is that it is very cranky, at least on my tablet; if you have trouble with it not recognizing the external SD card, try rebooting into recovery again....or again....)
d. Reboot. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery (note that from here on all installation is done using the internal TWRP 3.0.2-0)
e. Select Wipe (data & factory reset) OR, using Advanced Wipe, wipe system, data, cache, dalvik.
f. [Optional] Select Advanced Wipe, Repair or Change file system; select "data" (only) and change file system from ext4s to f2fs (supposedly a faster format--if you decide to undo all this, you should probably reformat "data" to ext4s)
g. Reboot to internal (emmc) recovery as in 3d. (ignore warnings about "no system" if you see any)
h. Select Install. From the external SD card install aosp_acclaim-ota-NBD90Z.161020.zip (ignore E: unknown command errors)
i. Reboot to internal (emmc) recovery as in 3d.
j. Select Install. From the external SD card install magisk-v16-0_patched2-zip
OPTIONAL:
k. Reboot to internal (emmc) recovery as in 3d.
l. Select Install. From the external SD card install appropriate opengapps zip
Continue here from either step j or step l
m. Remove SD card and select reboot.
For GApps
n. Wait for first boot to complete and sign in.
After first boot and the usual stuff, check Magisk Manager to see if root is enabled. You will be asked to update Magisk Manager. You can say "yes" ONCE. It will ask every time you open the app, but don't say "yes" again. The next update will render it inoperable., you'll lose root, curse me, etc. You've been warned.
Done!
[Don't you want to make a baseline backup right now?]
microG (for those skipping GApps)
Spoiler
You've skipped GApps if you're looking at this. There are all kinds of packages available for Magisk to do all the microG stuff in one fell swoop. But there's a lot of contradictory information out there and many of the packages include other stuff you may not want. Also, this old version of Magisk may not work with some of the packages. In the end I decided to try setting up microG the way I learned to do it: manually. It's not that difficult and you get only what you want.
To work, microG requires that signature spoofing be enabled on the ROM. On this ROM you need to use Xposed for that. So let's get started!
4.
a. Download the Xposed installer zip for Magisk and SDK 24 (Android 7.0): https://www.mediafire.com/file/v6zkpj4n3rbi11t/xposed-sdk24-topjohnwu.zip/file. Copy the file to the bootable SD card you used for the ROM installation.
OPTIONAL
b. Download the flashable maps zip file and copy it to the SD card (you only want this if you wish to use Location services or might want to run Tasker): https://www.mediafire.com/file/7y8cmr4obydo35d/mapsv1.flashable.zip/file
c. You'll need some kind of root file manager for this process (you could use adb, but it's cumbersome). I've attached an old version of ES File Explorer that I like. You'll have to adb install that since the meager sort of "file manager" in the ROM doesn't work with the package installer.
d. You'll also need the Xposed installer app and the Fake GApps module which enables signature spoofing. I've attached both below.
e. Finally, you need the microG component apps. You can get them here: https://microg.org/download.html. You want Services Core, Services Framework Proxy, and Store. If you want to use Location services, you will also need the UnifiedNLP app.
The tools are now assembled!
f. Shut down your tablet and place the bootable SD card in the slot. Power up.
g. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery
h. Select Install. From the external SD card install xposed-sdk24-topjohnwu.zip
OPTIONAL
i. If you want to use Location services, also install mapsv1.flashable.zip
j. Remove the SD card and reboot. The process may take a little longer due to the new Xposed framework (first time only).
k. Transfer the apps you collected in steps d and e above to the internal Download folder. Use the root file manager you installed to install the Xposed installer app and the Fake GApps app. Open the installer app and check anything that needs checking then reboot. Check the installer app once more to see that the Fake GApps app has been installed and enabled.
l. Using the root file manager create the folder /system/priv-app/Phonesky. Set folder permissions to rwx-rx-rx. Use the root file manager to move fake "Store" app (com.android.vending-16.apk) into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
m. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core and Services Framework Proxy for this step). Reboot.
n. Check microG Settings to be sure spoofing is enabled and other permissions are granted. You don't need to enable any of the other Google stuff at this point unless you want to.
OPTIONAL
o. If you want Location services install the UnifiedNLP app then return to microG settings to configure (check regular settings for "Location" also--you'll see that the microG settings have been inserted into the general Settings app)
OK, you now have microG running at its lowest service level. Without doing anything else it should provide signature spoofing for apps that are looking for Google Services Framework. If you want higher levels of service (say, an actual Google account) you can make those selections in the settings. Generally, apps that require a Google account will call up microG to initiate a Google login (slow, but it works).
It is theoretically possible to run the PlayStore with the right configuration, but I would not recommend it. The Aurora Store (F-droid) runs really well on the device and can provide you with PlayStore access without GApps (or more demanding levels of microG service). You can use the anonymous login.
Calendar and Contacts will not sync with Google using microG. There's a lot of old stuff online about this working and how to set it up, but it does not work any more, so don't waste your time. If you MUST have synced contacts and calendar, you can use DavX (F-droid) (configuration--start with Calendar!) . Otherwise you can export a vcard file (*.vcf) of your contacts and load them in as a local set on the tablet. For a contacts app I extracted the Contacts.apk from a CM 13 ROM and placed it in /system/app/Contacts (permissions rw-r-r). Likewise the Calendar.apk in /system/app/Calendar. I've attached these apps below.
For email I tried using the AOSP client from a CM 13 ROM. The system recognized it but crashed on opening. Eventually I settled on an older version of K-9 mail (6.20). I had problems with Google 2-factor verification with the more current versions.
I've attached a screenshot of my system below. More discussion on individual apps and issues in the following post.
My thanks to @digixmax for his many, many excellent how-to's and for the help he has given me in the past. He is also responsible for providing the flashable TWRP that avoids the need for fastboot in this install. I'm grateful to @mikeataol for his patient responses to my probably lame questions in the CM 13.0 thread concerning this ROM and, of course, really thankful that @amaces turned out this excellent version of AOSP Android 7.0 for our devices.
See post immediately below for a discussion of known issues and app options.
Updated 2-16-23
Issues and Apps
Every custom (and stock) ROM has some issues. This one seems to have very few and they are easily addressed.
1. The stock browser is "broken", at least to the extent that it cannot save bookmarks.
Here's a fix for the bookmark issue. Use a root file manager to navigate to /system/app/BookmarkProvider. In that folder you will find an apk file of the same name. Tap to install (actually update, I guess). Then reboot.
A good alternative browser that works well with this ROM is Via.
2. The stock launcher is pretty basic. After a lot of fooling around with display and font size in Settings I found no combination that significantly affected the rather large (for my taste) icon size without otherwise distorting the display in some way.
I ended up restoring the display to defaults and installing Nova Launcher.
3. There's no Gallery?! Yep. For awhile I was using a Gallery from my old CM 10.2.1 install, but it didn't work very well. Then I discovered that @theportal2 had worked up a Lineage Gallery app with the necessary libraries for install on other ROMs. It works great and includes a ton of features, even photo editing. You can get it here: https://forum.xda-developers.com/an...lineage-os-gallery-apk-photo-editing-t3664460
4. The MTP file transfer setting in Settings>Developer options>Networking>Select USB Configuration is not effective and selecting it in Settings seems to encourage the MTP host to whine with system messages occasionally.
Leave setting on "charging" (default) and when you connect via USB, use the pull-down notification to select MTP transfer for that session.
Better yet, you can disable the MTP Host app with no apparent repercussions. Just go into Settings>Apps (show system) and disable it. I was sort of surprised that this had no effect on file transfer protocol.
5. The swipe-to-unlock screen is tenacious and its use may result in repetitive motion injury.
OK, so maybe this is a "feature?". If you touch anywhere on the swipe-to-unlock screen the little "Swipe to unlock" bounces up from the bottom. With that visible, the screen swipes effortlessly. Who knew?
6. The system throws up two notifications when you connect to USB (if you have debugging enabled). Just a minor annoyance. If you don't like seeing those two "N"s either, you can see just one (for the connection type: charge, transfer, etc.) with a simple addition to /system/build.prop:
Code:
persist.adb.notify=0
7. Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I recommend off-loading a copy and editing with something like Notepad++. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
Replace the file on the device with the edited version and reboot. This change will be overwritten if the app updates, so you might want to keep that in mind.
8. I am partial to the version of ES File Explorer which is attached to the first post. It's not too bloated and works well with the device, the package installer, etc.
9. Generally speaking I would gravitate toward older versions of apps which may be easier on the system. As an example, I'm using version 1.8.6 of MX Player, long before all the streaming nonsense took over. TuneIn Radio and Pandora are so old they will run on Android 2.1! Sometimes enough is just right.
Apps that don't work
1. The NPR News app currently in the PlayStore at this writing crashes repeatedly just after starting.
Version 2.6.1 works fine. Interestingly, when the PlayStore version installs, the icon background color is black. On another Nook Tablet (HD) running CM 11, the same version installs with a white icon background and runs fine. Version 2.6.1 also installs on this AOSP ROM with a white icon background. Hmm.
Xposed
Oh yes, even I eventually missed a feature or two from my last CM install The good news is that the Nougat version of Xposed runs well on this ROM, at least to the extent of using Gravity Box (I just had to have the extended power menu back.....)
Alternative apps for microG
I've included some of the more common ones (Contacts, Calendar, Email) in the previous post. If you've set up Location service you might want Maps. I've not had much luck with newer versions of Maps on my various devices. Too greedy for system resources. But I have found an older version of the app which still runs, includes Places, and allows you to cache map areas which do not expire.
YouTube is another real resource hog. I'm not a big YouTube fan, but there are times when I want something and a browser like Via or the stock one is so-so (it works, but you have to be patient). I looked around and decided NewPipe would meet most of my needs. It's not perfect. The full-screen player crashes on all the custom ROMs I've tried. However, you can set it to use an external player (like MX Player) and that works fine with full screen. I really like the ability to download videos (or just the audio) in a recognizable format--and even to the SD card!
And don't forget the Aurora Store (F-Droid) for PlayStore access.
nmyshkin said:
[shamelessly adapted from peerless instructions for other NT installs by @digixmax, and information from @mikeataol that is scattered through the CM 13.0 thread.]
Disclaimer: Neither I nor any other user mentioned here, real or imaginary, is responsible if you brick your device following these instructions. The only stupid question is the one you didn't ask right before you ruined your tablet.
By following these instructions you can install an AOSP Android 7.0 ROM from @amaces internally (into emmc) on a 16 GB Nook Tablet running either stock, CM 10.x, CM 11.x, CM 12.x, or CM 13.x, assuming you have done no special repartitioning (it may also work if you have done special repartitioning, but I do not know). If you have previously installed CM 14.x and have repartitioned, you can return to those installation instructions where there may be a description of how to revert to the regular partitioning. This ROM does not require any special partitioning.
The AOSP ROM is a bare-bones, very responsive build. It runs rings around my former CM 12.1 install without any freezes or shutdowns. Adding a pico Google Apps package keeps the ROM mean and lean while giving you PlayStore access to add just what you want.
If you have a bootable SD card made for installing CM 10.x-12.x, you can skip to step 2b.
1. Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on the SD card a Primary FAT32 partition, set the partition ID type for the partition to 0x0C FAT32 LBA, and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
2. Obtain and copy to the SD card the following files:
a. first MLO, then next u-boot.bin, and finally flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
b. TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
c. the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
d. the zip file of the AOSP Android 7.0 ROM by @amaces, i.e., aosp_acclaim-ota-NBD90Z.161020.zip from my Dropbox: https://www.dropbox.com/s/b7zc8d56z2gl69m/aosp_acclaim-ota-NBD90Z.161020.zip?dl=0 (alternative link provided by @mikeataol: https://mega.nz/#!nQwiEILS!dm7i-4AOUzYW5yP0LaqcZ5EAUsxeh-Qr8DULB4BGYZ8) [this ROM is no longer in the repository maintained by @amaces]
e. the zip file of the Gapps package (corresponding to Android 7.0) from http://opengapps.org/
3. Put the SD card into the NT and boot from its power off by inserting a powered USB cable. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display.
a. Select SDC Recovery.
b. [Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
c. Return to TWRP opening screen and select Install. From the external SD card install flashable_TWRP_3.0.2-0.zip
(my experience with TWRP is that it is very cranky, at least on my tablet; if you have trouble with it not recognizing the external SD card, try rebooting into recovery again....or again....)
d. Reboot. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery (note that from here on all installation is done using the internal TWRP 3.0.2-0)
e. Select Wipe (data & factory reset) OR, using Advanced Wipe, wipe system, data, cache, dalvik.
f. [Optional] Select Advanced Wipe, Repair or Change file system; select "data" (only) and change file system from ext4s to f2fs (supposedly a faster format--if you decide to undo all this, you should probably reformat "data" to ext4s)
g. Reboot to internal (emmc) recovery as in 3d. (ignore warnings about "no system" if you see any)
h. Select Install. From the external SD card install aosp_acclaim-ota-NBD90Z.161020.zip (ignore E: unknown command errors)
i. Reboot to internal (emmc) recovery as in 3d.
j. Select Install. From the external SD card install appropriate opengapps zip
k. Remove SD card and select reboot.
Wait for first boot to complete and sign in. To fully enable root access for ADB and apps you must install the opensource version of the SU interface from the PlayStore: https://play.google.com/store/search?q=phh superuser&c=apps. Search for "phh superuser".
Done!
[Don't you want to make a baseline backup right now?]
My thanks to @digixmax for his many, many excellent how-to's and for the help he has given me in the past. He is also responsible for providing the flashable TWRP that avoids the need for fastboot in this install. I'm grateful to @mikeataol for his patient responses to my probably lame questions in the CM 13.0 thread concerning this ROM and, of course, really thankful that @amaces turned out this excellent version of AOSP Android 7.0 for our devices.
See post immediately below for a discussion of known issues.
Click to expand...
Click to collapse
I have cm 11 installed with 12 gb system and 1 gb media partition . and twrp 2.8.6... Installed . can i flash rom and g apps straight away ? Without foolowing other instructions
ehtisham ali said:
I have cm 11 installed with 12 gb system and 1 gb media partition . and twrp 2.8.6... Installed . can i flash rom and g apps straight away ? Without foolowing other instructions
Click to expand...
Click to collapse
You can try, but I think you'll need to update the internal TWRP at least.
Is anyone able to install any of the recent AOSP/LNOS builds of Amaces on a 16G NT that still uses the original partition format PLUS any recent opengapps TOGETHER successfully???
For me any builds from Amaces since 2017 can install successfully ... BUT ran out of /system space after that and cannot install OpenGapps. I use/tried PICO opengapps only always.
When I open file manager from TWRP 3100 there is nothing inside /system .... so was not able to clean up anything inside ....
Amaces: If you see this can you please help?? I know your focus is on the Ovation (I use it too) but I really want to try your LNOS for the NT on my original partitioned one.
Just FYI on the 16G NT that has the newer CM14.1 repartitioned format -> None of Amaces' ROM for Acclaim can install. Can only use dmarble's new LNOS builds or the old remaining CM14.1 builds on those.
If anyone has a good and easy solution to get around the /system out of space issue to install Gapps please share. I want to keep one acclaim on the original partition format. My other acclaim is running dmarble's ROM happily.
nsfgp said:
Is anyone able to install any of the recent AOSP/LNOS builds of Amaces on a 16G NT that still uses the original partition format PLUS any recent opengapps TOGETHER successfully???
For me any builds from Amaces since 2017 can install successfully ... BUT ran out of /system space after that and cannot install OpenGapps. I use/tried PICO opengapps only always.
When I open file manager from TWRP 3100 there is nothing inside /system .... so was not able to clean up anything inside ....
Amaces: If you see this can you please help?? I know your focus is on the Ovation (I use it too) but I really want to try your LNOS for the NT on my original partitioned one.
Just FYI on the 16G NT that has the newer CM14.1 repartitioned format -> None of Amaces' ROM for Acclaim can install. Can only use dmarble's new LNOS builds or the old remaining CM14.1 builds on those.
If anyone has a good and easy solution to get around the /system out of space issue to install Gapps please share. I want to keep one acclaim on the original partition format. My other acclaim is running dmarble's ROM happily.
Click to expand...
Click to collapse
Yes, have done many times.
make sure you have mounted /system in TWRP
Try a reboot after ROM install, and before gapps install.
The latest LNOS in experimental (lnos_acclaim-ota-N2G47E.170416) installs a fresh pico gapps of about 80MB with no manipulation.
in the past if I have had to make room, I copy and delete /system/media to /emmc before gapps install, and copy it back after
mikeataol said:
Yes, have done many times.
make sure you have mounted /system in TWRP
Try a reboot after ROM install, and before gapps install.
The latest LNOS in experimental (lnos_acclaim-ota-N2G47E.170416) installs a fresh pico gapps of about 80MB with no manipulation.
in the past if I have had to make room, I copy and delete /system/media to /emmc before gapps install, and copy it back after
Click to expand...
Click to collapse
Thank you Mike!!! It is the /system mounting .... I never thought it would have to be mounted .... since it complaint not enough space instead of not found/mounted. But anyway .... I mounted /system in TWRP after ROM install+reboot into recovery. Now I can see stuff inside /system.
But it still complaint about not enough /system space and cannot install Gapps. I just copied off /system/media and deleted it. And now the Gapps installed ok. I am rebooting into LNOS now.
Do I really need those stuff in /system/media and have to copy it back?? If no use I want to keep it lean.
Thanks again!!! (I am using the exact LNOS ROM in A's experimental folder as you mentioned)
Just a heads-up that I don't actually have the hardware, so everything that I upload for acclaim is not really tested, but I try to not to break things.
nsfgp said:
But it still complaint about not enough /system space and cannot install Gapps. I just copied off /system/media and deleted it. And now the Gapps installed ok. I am rebooting into LNOS now.
Click to expand...
Click to collapse
I'll put something like this on the list, so a larger /system (upstream Lineage, or via REPIT) is usable with these builds (Lineage/AOSP would still need manual resize).
So far this build (7.0) works much better than 6.0. Thanks!
Hi, thank you very much for the tutorial, I have followed the guide step by step but I can't get the tablet to boot the cyanoboot, I turned off and plug the power cable from the adapter and it boots normally, my tablet model is BNTV250 16 GB version, runing stock OS and it has not been rooted before or anything, I have tried flash the sd with older methods in order to root it and haven't had any success, that's how I ended up here, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
killerkalmah said:
Hi, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
Click to expand...
Click to collapse
there is a certain percentage of Nook tablets that wont boot from a card unless you power down, insert the card, then power up by inserting the USB cable, not by pressing the on/off switch. (about 15% of nooks I've seen are like this)
if even that doesn't work, you should make another card . Class 4 is best, faster isn't better in this case.
killerkalmah said:
Hi, thank you very much for the tutorial, I have followed the guide step by step but I can't get the tablet to boot the cyanoboot, I turned off and plug the power cable from the adapter and it boots normally, my tablet model is BNTV250 16 GB version, runing stock OS and it has not been rooted before or anything, I have tried flash the sd with older methods in order to root it and haven't had any success, that's how I ended up here, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
Click to expand...
Click to collapse
If the tablet won't boot from the SD card it's likely that there is either something wrong with the boot files, i.e., those files first placed on the card in step 2a, or with the formatting of the card (step 1). You might want to download a fresh set of files and try making the card again. Corrupt files will make this task impossible.
It's also possible that your particular SD card just won't do it. It's been known to happen.
mikeataol said:
there is a certain percentage of Nook tablets that wont boot from a card unless you power down, insert the card, then power up by inserting the USB cable, not by pressing the on/off switch. (about 15% of nooks I've seen are like this)
if even that doesn't work, you should make another card . Class 4 is best, faster isn't better in this case.
Click to expand...
Click to collapse
That's they way I've tried, inserting the USB cable, the sd is class 4 indeed, so I don't know what it could be.
nmyshkin said:
If the tablet won't boot from the SD card it's likely that there is either something wrong with the boot files, i.e., those files first placed on the card in step 2a, or with the formatting of the card (step 1). You might want to download a fresh set of files and try making the card again. Corrupt files will make this task impossible.
It's also possible that your particular SD card just won't do it. It's been known to happen.
Click to expand...
Click to collapse
Is it possible that the SD card can be read it, explorer and formated from the tablet and unable to do the boot? cuz the tablet appear to recognize evrything on the SD
killerkalmah said:
Is it possible that the SD card can be read it, explorer and formated from the tablet and unable to do the boot? cuz the tablet appear to recognize evrything on the SD
Click to expand...
Click to collapse
Unfortunately, yes. I'm not saying your card is defective but this whole business of booting from the card contains a minor but distinct element of voodoo
So....download those files from step 2a again, reformat the card (again....), and prepare it as before (again....). If it still does not work, I'd look for a different card to try this process. Don't be discouraged. I did a lot of "again..." when I first did anything like this. It will work for you.
nmyshkin said:
Unfortunately, yes. I'm not saying your card is defective but this whole business of booting from the card contains a minor but distinct element of voodoo
So....download those files from step 2a again, reformat the card (again....), and prepare it as before (again....). If it still does not work, I'd look for a different card to try this process. Don't be discouraged. I did a lot of "again..." when I first did anything like this. It will work for you.
Click to expand...
Click to collapse
I downloaded those files again, re-do the sd card and prepare it again, it still don't boot lol
This is the link I'm following for the TWRP image; https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img, i don't know if I have to use that or the one that comes in the suculent boot folder?
Another thing is that I've been using an SD card adapter and have tried trough the nook too, and also downloaded the mini gaaps file for android 7 ARM, but I'm pretty sure that has nothing to do with the boot stuff, so I'm gonna fallow your suggestion and try with an old 1 gb or 2 gb card, and see what happens, everything related on formating the SD via partition tool mini has done correctly, my Internet security blocks a menace while I attemp to download the files from media fire, you think that could be corrupting the files? I get the download and the menace blocked by Iinternet Security so I'm not sure, if you have any other suggestion I will be glad to read, meanwhile I will search for those damn cards, and I can't thank you enough for you time helping a noob here! thanks!!
killerkalmah said:
I downloaded those files again, re-do the sd card and prepare it again, it still don't boot lol
This is the link I'm following for the TWRP image; https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img, i don't know if I have to use that or the one that comes in the suculent boot folder?
Another thing is that I've been using an SD card adapter and have tried trough the nook too, and also downloaded the mini gaaps file for android 7 ARM, but I'm pretty sure that has nothing to do with the boot stuff, so I'm gonna fallow your suggestion and try with an old 1 gb or 2 gb card, and see what happens, everything related on formating the SD via partition tool mini has done correctly, my Internet security blocks a menace while I attemp to download the files from media fire, you think that could be corrupting the files? I get the download and the menace blocked by Iinternet Security so I'm not sure, if you have any other suggestion I will be glad to read, meanwhile I will search for those damn cards, and I can't thank you enough for you time helping a noob here! thanks!!
Click to expand...
Click to collapse
You are downloading the correct TWRP. The other one is too old. I don't know about any warnings from MediaFire. I just downloaded the succulent_boot.zip myself and saw no warnings, but that may be browser/configuration dependent. I'm using Firefox with a double layer of ad-blocking.
Generally speaking you want to download the files on your PC, then insert the SD card into the adapter, into the SDHC slot, and do all the work on the PC before inserting the card into the tablet.
If you have a way to verify the MD5 checksums of your boot files (winmd5free), this is what I get:
MLO: 979fa71c9ee33ca9690df809c71e1991
u-boot.bin: 1070cd90b3d57a47cdc8c22b00243ff7
flashing_boot.img: 3a626c102ef4324a163d54751ef680f1
I think you might run into size issues with the mini GApps.
nmyshkin said:
You are downloading the correct TWRP. The other one is too old. I don't know about any warnings from MediaFire. I just downloaded the succulent_boot.zip myself and saw no warnings, but that may be browser/configuration dependent. I'm using Firefox with a double layer of ad-blocking.
Generally speaking you want to download the files on your PC, then insert the SD card into the adapter, into the SDHC slot, and do all the work on the PC before inserting the card into the tablet.
If you have a way to verify the MD5 checksums of your boot files (winmd5free), this is what I get:
MLO: 979fa71c9ee33ca9690df809c71e1991
u-boot.bin: 1070cd90b3d57a47cdc8c22b00243ff7
flashing_boot.img: 3a626c102ef4324a163d54751ef680f1
I think you might run into size issues with the mini GApps.
Click to expand...
Click to collapse
Alright! I found 3 sd cards each of them with a 2gb capacity, that should the incompatibilty, each three are different brands, and I found a better SD adapter, I will re-do all the steps in building the SD and if that does not work will download the files again with jdownloader to avoid menace pop outs, and if that doesn't do I will check the MD5 :fingers-crossed: I will update here, and thank you again!.
Update: it was the SD, I manage to do all the steps except for the gapps file, I couldn't install it, which you will recomend to download, I download the ARM android 7.0 mini, and more importantly my tablet loops on the "android" screen, with or without the SD inside, am I missing something? I did not installed supersu even though I got asked a few times during tutorial, any suggestion?
Have you tried clearing the cache? That worked for me the first time I did this.
Also, which OS image are you using? When I tried to reinstall a newer version mine would not boot after copying gapps over, presumably due to space.
nosborm said:
Have you tried clearing the cache? That worked for me the first time I did this.
Also, which OS image are you using? When I tried to reinstall a newer version mine would not boot after copying gapps over, presumably due to space.
Click to expand...
Click to collapse
I'm a little bit lose regarding memory space on this tablet, I reinstall the OS that was in this tutorial and finally booted to menu, but I can't connect to wifi, I don't know why, I might install another OS, which gapps file you reccomend to download? the stock, full version or mini?
The phone must be installed stock rom Android 9 Pie and installed TWRP recovery. For downloading files I can not send direct link for our respect to dev. For complete tutorial you can watch video below.
Download:
TWRP Recovery for M30s Android 9 Pie
Havoc-OS-v3.1-20200111-ARM64AB-GSI.img
open_gapps-arm64-10.0-nano-20200408.zip
Follow this steps to flash it:
Enter TWRP Recovery Mode
Select Wipe - Format Data
Select Reboot - Power off
Enter TWRP Recovery
Copy GSI ROM and GAPPS to your phone
Install - Install Image - select Havoc-OS-v3.1-20200111-ARM64AB-GSI.img - select System Image
Select Reboot - Power off
Enter TWRP Recovery Mode
Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System
Select Mount - select "System" & "Vendor"
Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
Reboot - Recovery
Setup the phone - Done!
Watch this video for complete tutorial include installing TWRP:
Thx its working
Hi, after some trial error I was able to install Havoc 3.1 on my SM-M307FN dual sim model, but unfortunately there is no dual sim support in this version of Havoc, or am I missing something? Didn't find any related settings in Havoc settings so far... please confirm...
Thanks
no dual sim support here
hm, so i went a little wild and tested successfully these five GSI images, all listed bellow booted on my phone, but only one SIM card was enabled/presented and i didn't find a way how to access both my SIM cards, so for now I am going to back to stock firmware... if anyone wants to try be my guest, you can safely skip "power off" steps from OP steps to flash to save some time (or not its your choice - worked for me) also if you get error after first try to resize system - just try again it will work on second try (tested several times)...
I didn't tested much, but none of tested system images had working auto brightness, dual sim support and maybe several broken things which i didn't noticed, you can find for yourself ... if you have b***s
happy testing (name of the system image + size after unpacking):
EvolutionX-4.1.69-20200329-GSI-ARM64-AB.img 3*118*272*792
Havoc-OS-v3.1-20200111-ARM64AB-GSI.img 1*851*064*600
Havoc-OS-v3.3-20200402-arm64-ab-vanilla-nosu.img 1*824*542*976
PixelExperience-10.0-20200328-GSI-ARM64-AB.img 2*779*201*792
ExtendedUI_1.0.2_ARM64AB-10.0-20200207-2204-GSI.img 2*780*713*216
Any major bugs, except Volte or auto brightness?
I've got the Indian Phone, but I live in Australia, so Volte doesn't matter for me. But please let me know if there are any other bugs that could create issues for daily usage?
error 8 in twrp while resize or repair
no os installed no resize and no repair
after flashed my stock rom 9.0 and i flashed twrp for 9.0 its shows my internal 16 gb but its 128gb varient plz help
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here.
Boot with AB only. Seems this was due to some ROM compatibility issue and the FW of Samsung that time. Any Treble based ROM, based on our partition structure works now.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Thanks for your guide. I appreciate your persistence.
We must try relentlessly to get working stuff!
Incredible work testing GSI's, I might flash myself to test out
Snapshots!
Attaching few snapshots for the build and successful flash.
Akhil99 said:
Thanks for your guide. I appreciate your persistence.
We must try relentlessly to get working stuff!
Incredible work testing GSI's, I might flash myself to test out
Click to expand...
Click to collapse
Thanks mate. This guide should work on M30 all variants, ideally.
I will post once PHH gives an update and see how it goes with Dirty Flash or if I need to flash it again. Hopefully dirty flash should work.
vdbhb59 said:
Thanks mate. This guide should work on M30 all variants, ideally.
I will post once PHH gives an update and see how it goes with Dirty Flash or if I need to flash it again. Hopefully dirty flash should work.
Click to expand...
Click to collapse
Which gsi did you flash? I will flash the same for first boot for safety...
And also make a telegram group for samsung m30, so others can post their problems.
nareshfree said:
Which gsi did you flash? I will flash the same for first boot for safety...
And also make a telegram group for samsung m30, so others can post their problems.
Click to expand...
Click to collapse
I flashed the GSI by PHH (phhusson), the FLOSS one.
https://github.com/phhusson/treble_experimentations/releases
There are few groups on TG. I am no longer on TG (left a week/2 ago). I am available here for anything.
System partition or System image?
veekay said:
System partition or System image?
Click to expand...
Click to collapse
Flash as /system image.. By system partition I meant the /system portion of the OS.
Any chance you would be able to take a screenshot of the partition list that is shown after you select the image? I am trying to do this on another Samsung device and am wondering if the issue comes down to the TWRP options shown as I don't have just System - only System Image
veekay said:
Any chance you would be able to take a screenshot of the partition list that is shown after you select the image? I am trying to do this on another Samsung device and am wondering if the issue comes down to the TWRP options shown as I don't have just System - only System Image
Click to expand...
Click to collapse
It is the system image. Dont have Samsung turned on or fully setup to give snap.
There you go.. /system image..
One suggestion. Even with GSI do not try to flash any experimental zips from say Android 9 on Android 10. I just landed on bootloop and had to reflash system Magisk and DM again.
I switched to Havoc. Much more stable and has loads of features..
Couple of Havoc snaps..
vdbhb59 said:
Couple of Havoc snaps..
Click to expand...
Click to collapse
How is your use at hovac ?? Is the lock screen working?
Can you make and receive calls normally?
MiyamuraNEET said:
How is your use at hovac ?? Is the lock screen working?
Can you make and receive calls normally?
Click to expand...
Click to collapse
Nope for both. Calls only on 2G, not even 3G. Audio on speakers is not working. SMS on LTE does not work, but works only on 3G or 2G.
If anything is moved manually to /priv-app or /etc it bootloops on the next reboot.
vdbhb59 said:
Nope for both. Calls only on 2G, not even 3G. Audio on speakers is not working. SMS on LTE does not work, but works only on 3G or 2G.
If anything is moved manually to /priv-app or /etc it bootloops on the next reboot.
Click to expand...
Click to collapse
This is a matter of time soon customs will appear!
MiyamuraNEET said:
This is a matter of time soon customs will appear!
Click to expand...
Click to collapse
True. Just waiting for it. Will see if I can get to help Akhil, Sahil and Aditya.
Flashing the GAPPS build works only until one reboot after which the phone goes into boot loop. also, VOLTE does not work.
thvardhan said:
Flashing the GAPPS build works only until one reboot after which the phone goes into boot loop. also, VOLTE does not work.
Click to expand...
Click to collapse
I do not use gaaps, so not sure, but it does stick around on several reboots as well. Only time it will go to bootloop if you try to manually place any file within "/system/app" and "/system/priv-app" folders. Somehow, it ticks boot and does not start beyond Android logo.
could you please tell which phh to download exactly
vdbhb59 said:
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here. Boot with AB only.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Click to expand...
Click to collapse
It would be very kind of you if yould could tell me exactly which phh to download from github?
---------- Post added at 09:34 AM ---------- Previous post was at 08:46 AM ----------
vdbhb59 said:
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here. Boot with AB only.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Click to expand...
Click to collapse
when I am installing twrp and then formating data and the rebooting to system it is causing bootloop.Please help
Note
Before getting started, I'm not a developer and I'm not on that level yet but being an enthusiast of Android ROMs especially my favorite ROM Pixel Experience (PE). However what I can contribute (as of now) is to guide newbies and answer people who is confusing with flashing PE ROM, any custom kernels, mods, Gcam and help you out from problems while trying these things.
Tons credits to @jhenrique09, without his great effort there is no born of Pixel Experience project, and we would not have a taste of stock and pure Pixel ROM without having an actual Pixel phone.
It is good that you attempt new things and seek into the freedom of pure Android experience, and the whole world of Android development, though there's some risk when you try something new.
!!! Warning: I am not responsible for any bricked devices, it is your choice to modify your device software.
Pixel Experience ROM official thread - by Henrique Silva @jhenrique09
How to unlock bootloader?
https://xiaomiwiki.github.io/wiki/Unlock_the_bootloader.html
Official ROM downloads:
Download from Pixel Experience website
Screenshots
Check telegraph here!
Pixel Experience Official Wiki Page for Redmi K20 Pro/Mi 9T Pro - Info about raphael & raphaelin
Appreciation to
@jhenrique09, founder and lead developer of Pixel Experience, and maintainer for raphael & raphaelin (Redmi K20 Pro & Mi 9T Pro Series).
@WasikFahim, a friend of mine who assists me for creating this thread.
Thanks to all developers I have been know so far.
And all developers and original creators of the attached files below and for all of the following posts.
Special thanks to @Sandeeep Kiran (TG handle @ sandeeep, due to request from him), who has proposed the idea of creating this new thread for me.
Reserved.
Nice Thread ?
How To Flash Custom Kernels
Hello Guys Hope You're Fine, Today We're Going To Learn How To Flash Custom Kernels In Recovery, So Without Further Due Let's Jump Into It:
I'm Using PitchBlack Recovery
Prerequisite:
*Backup Stock Kernel [Boot.img & Dtbo(Optional)] Image=> 1 & 2
Steps For Flashing Custom Kernels:
1.Go To Recovery.
2.For OF(Go To Files) For TWRP/PBRP(Go To Install). Image=> 3
3.Select Kernel And Swipe to Install. Image=> 4 & 5
4.Wipe Dalvic/Cache.(Optional)
5.Reboot To System.
Enjoy!!!!!! :good::fingers-crossed:
Here Are Some Recommended Kernels:
We Use LOS FOD Implementation.
Gaming & Decent Battery = F1xy
Battery Backup & Decent Gaming = Immensity
Decent Performance + Battery = Englezos (Less gaming)
Mods tutorials
ANX Camera
ANX Camera TWRP
ANX Camera magisk
Working version of ANX magisk: 185
48MP fix for ANX camera magisk module: 181
Which ones should I download? Check attached screenshots below this post.
How to install and setup MIUI camera on PE?
* For ANX Camera TWRP
1. Save zip file to internal storage (/sdcard) and reboot to recovery.
2. For orangefox go to "files", for TWRP or Pitchblack recovery go to "install".
3. Swipe button to install.
4. Reboot to system.
5. Give all permissions to ANX camera, launch and quit app for at least 3 times.
6. You're all done.
* For ANX Camera magisk modules
1. Save both camera and 48MP fix modules to internal storage (/sdcard).
2. Open magisk manager, hamburger icon on top left corner, modules, tap on "+" icon and find ANX camera zip.
3. Same goes with 48MP fix module.
4. Reboot, give all permissions to ANX camera app, then launch & quit app for at least 3 times.
5. You're all done.
* 48MP fix is already included in ANX Camera TWRP, do NOT flash the 48MP fix magisk module.
* No root needed.
+ Credits to ANX developers and contributors, @HSgod, @nuub1k, for porting and debugging MIUI camera to AOSP ROMs.
Custom boot logo
MS drive Downloads
Head to XDA thread for more info, credits for @mouhannadsukkar creating boot logo collection.
Disable force encryption
Force Encrytion and difference compared with decrypted storage
1. All ROMs have force encryption by default for now, which should be enabled while booting the device for the first time.
2. Therefore DFE, also known as "disable force encryption", which shall force the device to be decrypted (Use #-dfe to get the DFE file).
3. If you format data, it will decrypt the encrypted storage, while everything on data partition including internal storage, also known as /sdcard directory, will be erased.
4. However if you already got a decrypted storage, simply wipe data and internal storage won't have any effects, unless you do a format.
5. To keep the storage decrypted, if you want, you will need to flash DFE for every ROM and vendor update.
6. Format data only if you flash custom ROM from stock MIUI, if you want to keep your storage decrypted or you want encrypted without flashing DFE while flashing custom ROMs and vendors (if the ROM uses MIUI vendor).
7. In short formatting data is to remove encryption for an encrypted device.
How to flash DFE?
IMPORTANT: Please make sure you perform a data FORMAT (NOT wipe) via recovery before flashing DFE, otherwise device may end up with bootloop or stuck in bootloader! Everything including all files on internal storage will lost so please backup everything to elsewhere. You have been warned, I am not responsible for data loss.
1. Go to recovery and format data (NOT wiping it, the place where you will type "yes" and confirm formatting).
2. Since internal storage is purged too, copy DFE from your PC or OTG storage etc., flash via recovery.
3. The recovery console will ask you to press volume buttons for picking options, so the recommended key combination is:
+ (vol up)
- (vol down)
- (vol down)
+ (vol up)
4. Done, reboot to system and see if storage is decrypted.
F2FS
What is F2FS?
F2FS, which stands for "Flash-Friendly File System", it was invented by Samsung coorperation, mainly focus on improving random read/write efficiency of flash storage and somewhat extends its lifespan.
Notice!!!
Currently, almost all known custom ROMs support F2FS on cache and data partitions but not system for compatibility and disk quota reasons, usually there's no writing actions to system partitions except flashing/updating ROM or using root access to modify it so keep system partition as EXT4.
How to enable F2FS?
You will lose all of your data including internal storage.
1. In recovery, convert data partition to F2FS via advanced wipe, same for cache partition (Do not convert system partition to F2FS to avoid some possible problems).
2. Flash f2fs-patched-fstab.zip (attached below) via recovery.
3. Reboot.
Note: You will have to flash patch again whenever flashing/wiping vendor, otherwise you will stuck at boot animation.
Fix low microphone problem (magisk needed)
Description
Sometimes, you might feel the microphone sensitivity isn't good enough on AOSP ROMs including Pixel Experience, this might related to device tree (or source code) of K20 Pro/9T Pro series. For instance you make or pick a phone call, using voice call of some IM apps the other side might not hear you clearly, that's the time when you can have a workaround if you have magisk installed.
How to fix?
Same as you install any magisk modules via magisk manager.
magisk_iem_mic_gain_0.3.zip attached below.
Magisk manager recovery mode
What to do if my device stuck at boot animation?
Sometimes, your device might stuck at boot animation because you flashed a buggy magisk module, for obvious reasons you have to delete that for letting your device boot into OS, so what about removing it via recovery? That's how this zip comes - Magisk Manager Recovery Mode.
How?
1. Boot your device to recovery, flash provided zip file.
2. Go to advanced => terminal.
3. Type this command to launch program:
sh /sdcard/mm
4. Type l to list all installed magisk modules, locate the one which might causes the problem.
5. Type r, enter, then the name of module name as the output shown, case-sensitive!
For example:
module[]
You should type:
module
Then enter.
6. If you see there's an X inside brackets like:
module[X]
Then you're good to go.
7. Reboot your phone and that's it.
Troubleshoot and advanced guides
Stuck at bootloader
Sometimes when you flashed ROM, custom recoveries, or updating vendor and try rebooting your device thereafter, your device does not boot into system or recovery but fall into bootloader (fastboot) screen. This is due to verified boot of our device being triggered, so flashing a custom vbmeta will usually get the problem solved.
How to flash vbmeta?
You need a working PC or laptop, USB cable and install fastboot driver if you are using Windows.
1. Download attached vbmeta file to your PC, connect your phone with USB cable, make sure PC has detected the phone and it's connected properly.
2. Open CMD (if using Windows) or terminal (Linux/Mac).
3. Type the following command:
Code:
fastboot flash --disable-verity --disable-verification vbmeta fake_vbmeta_williamfeng.img
4. Reboot your device to either recovery or system, it should work fine now.
Upgrade vendor
Note: You will not lose your data so you don't need to wipe anything, just flash vendor on top of current one, no matter if device is encrypted
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Reboot to system.
Downgrade vendor
Note: Before you downgrade your vendor you're suggested to backup all your data (including internal storage) elsewhere in case you lose them while doing so.
If your device is decrypted (NOT encrypted), the steps are same as you upgrade vendor.
Otherwise:
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Format data partition in your recovery (the place where you'll type "yes" and confirm formatting).
5. Reboot to system.
How to update PE ROM?
You don't need to download full zip file on PE, it gives small OTA which can be downloaded from "settings => system => system updater". After downloading simply tap on 'apply/install update', then the device will boot into recovery, update and reboot back into system.
WARNING: Make sure your device always have enough charge (30% or more is suggested) for updating process.
* The update file will be downloaded to /data/system_updates
Error 7 when updating PE
- If you see updating ROM doesn't work and the recovery shows you error 7, please make sure you update vendor to correct one first.
- Try updating your recovery (TWRP/OFOX).
If it still happens, try flashing full ROM zip of latest build instead of using built-in updater from ROM.
Miscellaneous info of Pixel Experience
Changing animation of Pixel Experience - just like you have a real Pixel device!
Power-off your phone and plug into changer, you'll see that.
Video link