Related
Hello folks at xda
i think it's better to ask our questions that are not helping developers to make stable cm12 here,and not post spams on dev thread.
i just want to say : leave developer threads for developers.:good:
ask general questions here.so devs can focus on important things.
Download rom from this mirror link if you can't download it from mega
Also you can try Resurrection remix [Lollipop 5.0.2] [Credit : @Furrydaus]
[*]USB Charging : Ok
[*]USB ADB : Ok
[*]USB MTP : Ok
[*]Video : Ok
[*]Audio : Ok
[*]Sensors : Ok
[*]Screen rotation : Ok
[*]WLAN : Ok
[*]Wifi hotspot : seems to be working ( Fix! [credit : @MrSteve555] )
[*]GPS : Ok
[*]GSM : Ok
[*]GSM Data : (Fix! [credit : @Sylvester lobo] || or this => A comprehensive Mobile Data fix)
[*]GSM Voice : Ok ( Fix! [credit : @MrSteve555] )
[*]GSM SMS : OK
[*]Bluetooth : Ok
[*]NFC : Ok
[*]Camera : Ok
[*]FM Radio : Not work
[*]Keyboard : Ok
[*]MHL : Not tested
[*]OTG : Ok ( this post )
[*]VPN : Doesn't work
[*]...
How to install cm12 (mrsteve) on sp . by @[SIZE="5"]Dammer Martins[/SIZE]
Small tutorial for instalation of the steves build with working camera and wifi:
1-Download the ROM , ramdix fix, stock kernel and root fix
2-Open the ROM zip an push the ramdisk fiz in to system/bin folder
3-Now, put the ROM zip fixed, stock kernel and the root fix in your sdcard
4-Reboot in recovery, wipe data, cache and dalvik cache
5-Install the ROM, the stock kernel and then the root fix
6-Now reboot the system and wait the phone boot up (this take a veeery long time, trust me )
Tips: don't flash the gapps with the ROM instalation and disable the adaptive brightness to make the auto reboots stop.
Click to expand...
Click to collapse
Fix hot reboots by turning off adaptive brightness(settings->display->adaptive brightness)
Fix connectivity problem on CM12.by @noahvt
Hello,
Finally a fix has arrived for android 5.0 which will allow wi-fi data, outgoing calls, ... to work again
Steps:
1: Make sure your device is running android 5.0 by mrsteve555: http://forum.xda-developers.com/xper...8#post56946968
2: root the device by flashing this file: http://download.chainfire.eu/589/Sup...erSU-v2.16.zip
3: Reboot your device and open up terminal emulator
4: type su, press enter and give it root acces
5: type setenforce 0 and press enter
6: WAIT untill the device asks you to enter your sim pin (this means that it worked)
7: turn on wi-fi (it might take a little long to turn on wi-fi though)
8: that's it
9: well not yet there is one step you can do to make it easier to change the selinux state, Download and install this app:https://play.google.com/store/apps/d....selinux&hl=en
10: again make sure your device is rooted
11: open the app and now you can switch between permissive (this mode is the one that fixed the issues) and enforcing (default mode: wi-fi, ... don't work on this mode)
FAQ:
What is not affected (what doesn't work): The camera (can't connect to camera or hot reboot when launching camera app), more?
What is affected (what is fixed): WI-FI, Data (LTE too) Outgoing calls, more?
Do i have to do this everytime i boot my device: Yes for now you do
On what build does it run: mrsteve555's build, there were 2 reports of it not working on bagy's build
Credits:
Mrsteve555 and bagyusz for the amazing rom
Click to expand...
Click to collapse
just update titanium backup to latest version in case of super user access error.like this : can't aquire root provileges....this attemtp was made using the "/system/xbin/su" command.
Fix wifi hotspot => credit : MrSteve555
setup zram in android 5[credit : Mrsteve555]
Code:
#!/system/bin/sh
sleep 30
echo xM > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
Replace x with your desired value(in MB)
And zram doesn't make phone "much faster", it just allows more multitasking while slowing the phone a bit.
Click to expand...
Click to collapse
fix sdcard mount problem [credit : Mrsteve555]
Code:
su
depmod
rmmod texfat
modprobe exfat_core
modprobe exfat_fs
These commands will try to load different exfat modules, I didn't test it myself, though.
Click to expand...
Click to collapse
Fix for unresponsive touch screen[credit : Mrsteve555]
Code:
#!/system/bin/sh
echo 20 > /sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/finger_threshold
chmod 666 /sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/signal_disparity
echo 0 > /sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/signal_disparity
Fix for music file not playing when you uncheck nuplayer in developer options
The solution to that will be installing viper audio. There is a different version for lollipop. You have to flash 3 zips. They need nuplayer off so you can play music and videos easily with nuplayer off
Click to expand...
Click to collapse
Download from this post [Thanks@pranavthombare]
r 3
and-roid007 said:
Fix hot reboots by turning off adaptive brightness(settings->display->adaptive brightness)
Fix connectivity problem on CM12.by @noahvt
Click to expand...
Click to collapse
Really thks ;D
Youve stated that GSM voice hasnt been tested - This is voice calls. Are they working on MrSteves build with the latest fixes or not as there seems to be mixed reports.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Also your link to the https://play.google.com/store/apps/d....selinux&hl=en doesnt work
I assume its this app? https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en_GB
and-roid007 said:
Fix hot reboots by turning off adaptive brightness(settings->display->adaptive brightness)
Fix connectivity problem on CM12.by @noahvt
Click to expand...
Click to collapse
The fix isn't working for me
@Oblox
you are right about both.corrected
Sorry the pin code doesn't apear because i don't have set any pin code ... IM REALLYYYYYYY NOOOOOB! xD
Edit: But i can't send call, i recieve
bobslesbricoleurs said:
Sorry the pin code doesn't apear because i don't have set any pin code ... IM REALLYYYYYYY NOOOOOB! xD
Edit: But i can't send call, i recieve
Click to expand...
Click to collapse
just open terminal : type su-> type setenforce 0,hit enter.if no dialog appears dont worry,it's ok.
go to settings-> about phone-> make sure that SELinux status = premissive.
see the bug list :
GSM Voice : doesn't works (Only can recieve calls)
Click to expand...
Click to collapse
and-roid007 said:
How to install cm12 (mrsteve) on sp . by @Dammer Martins
Click to expand...
Click to collapse
What's the problem if I flash GApps with the ROM?
sohan3421 said:
What's the problem if I flash GApps with the ROM?
Click to expand...
Click to collapse
The problem will occur if you do this on first flash as itll take a lot longer to boot and the auto brightness forced reboot will kick in before it finishes. Once system is in and auto brightness disabled then install gapps.
No new about calls?
Sent from my Xperia SP using XDA Premium 4 mobile app
Navigation bar and Pie controls
I know when I moved from 4.4 to 5.0 most things that I could get from xposed or custom roms were gone such as pie controls. I've been looking around for ages and I've managed to remove navigation bar using build.prop and adding a highly customizable pie controls app. If anyone wants a tutorial made to hide navigation bar and get pie controls just ask and ill do it
Pie
Keep Pie In Memory
1. Search root explorer in Google play 3rd one down.
2. Open it and press mount R/W ( top of app)
3. Go into root directory and open the folder data.
4. Create new file and name it local.prop
5. Long hold the newly created app and press open in text editor.
6. Add com.android.lmt
This is to prevent android removing the service from memory when it is low.
Remove Navigation Bar
1. Open build.prop located on /system
2. Add qemu.hw .mainkeys = 1 Remember to add a space between either side of the equals or it won't work
3.Do not reboot until you have downloaded LMT launcher
Add Pie Controls
LMT Launcher ( PIe Controls (Not an actual launcher like nova or apex its just called that) )
1. Download the latest apk from here http://forum.xda-developers.com/showthread.php?t=1330150
2. Open the app make sure autostart is selected
3. Swipe right until you get to Pie.
4.Use these settings ( navigate to the screenshots) it will get rid of the unneeded two extra slots of pie controls
Finally Reboot
If you have titanium backup convert lmt launcher into a system app to integrate the pie controls more into the system
and-roid007 said:
How to install cm12 (mrsteve) on sp . by @[SIZE="5"]Dammer Martins[/SIZE]
Click to expand...
Click to collapse
Why should I add ramdisk fix?
sohan3421 said:
Why should I add ramdisk fix?
Click to expand...
Click to collapse
Why not?
Because the ramdisk inside the zip is either corrupt or incomplete, resulting in bootloop if flashed.
sohan3421 said:
Why should I add ramdisk fix?
Click to expand...
Click to collapse
Coz it'll go in a bootloop if you don't and then clog this thread too, by begging for a link and a guide which was clearly given and posted by many users.
gapps working fine?
shahrukhqasim said:
gapps working fine?
Click to expand...
Click to collapse
yes.i think
Hi guys!
I'm from Brazil and in the last two days I was reading about the Android 9 Pie update to our Mi A2.
I also read that today it started to roll out to India and some European countries.
For curiosity I installed ExpressVPN, conected to an Holland server and tried to download the OTA. It worked flawlessly.
I flashed via fastboot the Magisk patched boot of 10.0.1 build and got the Magisk also working flawlessly.
For the Camera2 API, I just edited the Magisk module and added the line "persist.vendor.camera.HAL3.enabled=1". Then I installed it through Magisk module screen. It also worked.
These are the steps I did:
1 - Obviously you will need to be on Android 9 Pie
(Try to download the OTA via VPN or wait to get it in your country)
2 - Download this file and extract it: https: // drive.google.com/open?id=1b9jRc1gZuPJatds5RkuCiJtuE7UCH5wh
(Remove the spaces)
3 - Turn your phone off and boot it in Fastboot Mode by pressing and holding Power + Vol Down and then, plug into the USB;
4 - In the extracted files, open the folder "Plataform Tools" and then open the Power Shell window.
(Inside this folder I added the original "boot.img" and the "patched_boot.img", all from 10.0.1 build)
5 - In PowerShell, just type: fastboot boot patched_boot.img
(It should boot with Magisk installed)
6 - Open Magisk, tap Install and chose to install directly. Reboot
(It will prevent Magisk get uninstalled after reboot)
7 - Transfer the files "Camera 2 API Enabler - Pie.zip" and "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk" to your phone memory.
8 - Open Magisk, go to "Modules", then tap the yellow buttom, search for the "Camera 2 API Enabler - Pie.zip" file and then install it. Reboot
9 - Once the phone rebooted, install the "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk".
(Go to Developer Options and unchek "camera.enable_micro", so you can use 5MP on front camera)
10 - Done! You're now on Android Pie with Magisk and Google Camera
Ricardo Guariento said:
Hi guys!
I'm from Brazil and in the last two days I was reading about the Android 9 Pie update to our Mi A2.
I also read that today it started to roll out to India and some European countries.
For curiosity I installed ExpressVPN, conected to an Holland server and tried to download the OTA. It worked flawlessly.
I flashed via fastboot the Magisk patched boot of 10.0.1 build and got the Magisk also working flawlessly.
For the Camera2 API, I just edited the Magisk module and added the line "persist.vendor.camera.HAL3.enabled=1". Then I installed it through Magisk module screen. It also worked.
These are the steps I did:
1 - Obviously you will need to be on Android 9 Pie
(Try to download the OTA via VPN or wait to get it in your country)
2 - Download this file and extract it: https: // drive.google.com/open?id=1b9jRc1gZuPJatds5RkuCiJtuE7UCH5wh
(Remove the spaces)
3 - Turn your phone off and boot it in Fastboot Mode by pressing and holding Power + Vol Down and then, plug into the USB;
4 - In the extracted files, open the folder "Plataform Tools" and then open the Power Shell window.
(Inside this folder I added the original "boot.img" and the "patched_boot.img", all from 10.0.1 build)
5 - In PowerShell, just type: fastboot boot patched_boot.img
(It should boot with Magisk installed)
6 - Open Magisk, tap Install and chose to install directly. Reboot
(It will prevent Magisk get uninstalled after reboot)
7 - Transfer the files "Camera 2 API Enabler - Pie.zip" and "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk" to your phone memory.
8 - Open Magisk, go to "Modules", then tap the yellow buttom, search for the "Camera 2 API Enabler - Pie.zip" file and then install it. Reboot
9 - Once the phone rebooted, install the "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk".
(Frontal camera will only work with 3MP)
10 - Done! You're now on Android Pie with Magisk and Google Camera
Click to expand...
Click to collapse
I downloaded ExpressVPN and changed to Holland, I still don't get the update.
Yepi69 said:
I downloaded ExpressVPN and changed to Holland, I still don't get the update.
Click to expand...
Click to collapse
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Amigo, tem que ser Power Shell mesmo? Aqui me dá opção do Prompt de comando apenas.
OTA
After using this method can I update normally without VPN?
Ricardo Guariento said:
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Click to expand...
Click to collapse
Ricardo Guariento said:
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Click to expand...
Click to collapse
This one worked like a charm, it is downloading now.
Ricardo Guariento said:
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Click to expand...
Click to collapse
It worked flawlessly, damn you Brazilians and your ''Brasileirices'' kkkkk
Hmm After doing this, will I loose ota update?
Ricardo Guariento said:
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Click to expand...
Click to collapse
Duude, big thanks to you, worked for me too. Only I used Nord VPN, as Express said that Trial is not available.
You've made my Day.
Works the download boot in reboot, bootlop 9 times, and starts and says "couldn't update".
Ricardo Guariento said:
Hi guys!
I'm from Brazil and in the last two days I was reading about the Android 9 Pie update to our Mi A2.
I also read that today it started to roll out to India and some European countries.
For curiosity I installed ExpressVPN, conected to an Holland server and tried to download the OTA. It worked flawlessly.
I flashed via fastboot the Magisk patched boot of 10.0.1 build and got the Magisk also working flawlessly.
For the Camera2 API, I just edited the Magisk module and added the line "persist.vendor.camera.HAL3.enabled=1". Then I installed it through Magisk module screen. It also worked.
These are the steps I did:
1 - Obviously you will need to be on Android 9 Pie
(Try to download the OTA via VPN or wait to get it in your country)
2 - Download this file and extract it: https: // drive.google.com/open?id=1b9jRc1gZuPJatds5RkuCiJtuE7UCH5wh
(Remove the spaces)
3 - Turn your phone off and boot it in Fastboot Mode by pressing and holding Power + Vol Down and then, plug into the USB;
4 - In the extracted files, open the folder "Plataform Tools" and then open the Power Shell window.
(Inside this folder I added the original "boot.img" and the "patched_boot.img", all from 10.0.1 build)
5 - In PowerShell, just type: fastboot boot patched_boot.img
(It should boot with Magisk installed)
6 - Open Magisk, tap Install and chose to install directly. Reboot
(It will prevent Magisk get uninstalled after reboot)
7 - Transfer the files "Camera 2 API Enabler - Pie.zip" and "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk" to your phone memory.
8 - Open Magisk, go to "Modules", then tap the yellow buttom, search for the "Camera 2 API Enabler - Pie.zip" file and then install it. Reboot
9 - Once the phone rebooted, install the "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk".
(Frontal camera will only work with 3MP)
10 - Done! You're now on Android Pie with Magisk and Google Camera
Click to expand...
Click to collapse
will my phone will get ota updates after unlocking bootloader and enabling camera2api ???
miillerjr said:
Amigo, tem que ser Power Shell mesmo? Aqui me dá opção do Prompt de comando apenas.
Click to expand...
Click to collapse
Pode ser, não tem problema.
RubenPCA said:
After using this method can I update normally without VPN?
Click to expand...
Click to collapse
I think so!
You just faked your region, the OTA file will be the same for everyone.
In my case, the phone was fully set up (with Google Account and all the stuffs) and I managed to get the OTA. It has no sign of a Netherlands-like phone at all.
ClownIndo said:
Hmm After doing this, will I loose ota update?
Click to expand...
Click to collapse
No, this is a legit OTA.
You will lose OTA if you screwed up with system partition.
If you install Magisk and use its modules, you still be able to get the OTA.
Hemant Dhillan said:
will my phone will get ota updates after unlocking bootloader and enabling camera2api ???
Click to expand...
Click to collapse
You still get the OTA with unlocked bootloader.
Follow the instructions on OP and you will enable Camera2 API without touch the system partition, so you will have no problem with future OTA's.
Does the ROM remain rooted after following this procedure?
Does rooting with magisk loses ota?
Without editing build prop and other stuffs
Using magisk modules only
bidhu said:
Does the ROM remain rooted after following this procedure?
Click to expand...
Click to collapse
Follow all the steps and you will be on Pie, with Magisk and GCam.
johnsci911 said:
Does rooting with magisk loses ota?
Without editing build prop and other stuffs
Using magisk modules only
Click to expand...
Click to collapse
If you use Magisk Modules you will be able to get OTA's.
do i need to have bootloader unlocked for this?
[Guide] Root Pixel XL Android 11 (R) Unlock/Lock Bootloader + Install Custom ROMS + Update Magisk/Systemless Root
Introduction
This Guide is for Google Pixel XL owners that want to Install/Flash Custom ROMs, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimers
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel XL phone with an unlocked bootloader.
An Android 11 (R) Custom ROM(s) (Update(s) 9. below).
A Computer with the latest working SDK Platform-tools r. 34.0.3 installed.
Important Notes:
If you use the Linux or Windows version of SDK Platform- tools r. 34.0.3 you must set the environment variable - See Note(s) for instructions on setting the enviroment Variable
If you have any problems with SDK Platform-tools 34.0.3. You can get SDK Platform-tools 33.0.3 here.
Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
Update Platform Tools, regularly, for optimal performance.
Need Google's USB Drivers for your Pixel Phone?
NEW
"...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
Updates
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Alpha
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta - app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
TWRP - TWRP Android 9 for marlin
Waiting for T.W.R.P. for Android 11 (R). (Q)
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.2 14Feb
SDK Platform-tools - r34.0.3 May 22, 2023
Custom Kernels
Google Pixel XL ROMs, Kernels, Recoveries, & Other
ElementalX Kernel Manager
My other guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Credits/Thanks/Recognitions
@topjohnwu - Magisk
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Open a Command Prompt/Boot Bootloader/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt to test ADB.
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Backup your data/Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Tap Build Number 7 times or until you see you're a Developer.
Tap back > Developer Options and toogle OEM Unlock on and, toggle USB Debugging on.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
This will erase all user data from the device!
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll see a warning: Your device software can't be checked for corruption. Please lock the bootloader. You will see this warning until, you relock the bootloader.
Important: Do not relock your bootloader until you have returned the device to Stock..
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Important: Do not relock your bootloader until you have returned the device to Stock..
Boot bootloader
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Set up your phone.
Enable Developer Options: Settings > System > About phone > Tap Build number 7 times or until you see'You are a Developer. Tap Back > Developer options and toggle OEM Unlock off.
Install/Flash Custom ROM with @badabing2003 PixelFlasher
PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones. by badabing2003
Install/Update Magisk Modules
Download Modules
Fox Magisk Module Manager Releases
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Fox2Code/FoxMagiskModuleManager
Open Fox2Code/FoxMagiskModuleManager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Fox2Code/FoxMagiskModuleManager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs for Pixel XL
Need help with a Custom ROM?
If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMS
Google Pixel XL ROMs, Kernels, Recoveries, & Other
Other Custom ROMs
[OFFICIAL] LineageOS 18.1 for the Google Pixel XL by npjohnson
[ROM][11.0] crDroid 9.99 [UNOFFICIAL][marlin/sailfish] By blckbear
Themes, Apps, and Mods
Google Pixel XL Themes, Apps, and Mods
Other: TWRP Backup
TWRP Android 9 for marlin
Waiting for T.W.R.P. for Android 11 (R).
Has anyone tried using the current TWRP and Magisk?
I don't think those steps for rooting with canary give us full root, I was able to install adaway, but if i try to use a root uninstaller to remove Chrome (system app) it shows "Rooted, but cannot grant RW permissions on /system"
It seems no app can obtain root access to /System, i tested it with Root Explorer and the "mount /R/W" button does nothing when trying to mount the /System folder.
shiodooru said:
Has anyone tried using the current TWRP and Magisk?
Click to expand...
Click to collapse
Yes. Didn't work, just rebooted twice (I think) then booted directly into android.
Therev86 said:
I don't think those steps for rooting with canary give us full root, I was able to install adaway, but if i try to use a root uninstaller to remove Chrome (system app) it shows "Rooted, but cannot grant RW permissions on /system"
It seems no app can obtain root access to /System, i tested it with Root Explorer and the "mount /R/W" button does nothing when trying to mount the /System folder.
Click to expand...
Click to collapse
I have the same problem with AdAway too. I'm guessing that we don't have write access.
Trylr said:
I have the same problem with AdAway too. I'm guessing that we don't have write access.
Click to expand...
Click to collapse
I got Adaway to work, you have to open Magisk Manager, tap Settings and then tap
"Systemless Hosts" then reboot and run Adaway again
Therev86 said:
I got Adaway to work, you have to open Magisk Manager, tap Settings and then tap
"Systemless Hosts" then reboot and run Adaway again
Click to expand...
Click to collapse
Hey that worked. Thanks.
I have 10 on my phone. I just took the OTA a few hours ago. This may be a bit off topic but I can't get picture to play on Amazon video or Google movies only audio and captions. Hulu YouTube and Netflix work fine.
EDIT: AFTER A RESTART ALL VIDEO APPS WORK FINE. I'M THE dumbass ?
Useless without twrp
There is an installer for TWRP, "twrp-installer-3.3.1-0-marlin.zip" but because it doesn't follow the naming convention for all the previous releases "twrp-pixel-installer-marlin X.X.X" it appears at the bottom of the list of installers instead of the top.
Is anyone having good results with the battery life? It sucks for me.
H0wdy said:
Is anyone having good results with the battery life? It sucks for me.
Click to expand...
Click to collapse
I'm on Android 10, rooted with Magisk and I don't notice any bad battery life. Might be time for a battery replacement. I just got my battery replaced about 2 weeks ago.
Hi
Why the pixel imprint suddenly gone from my pixel xl?
I used your guide to unlock bootloader and get root on Android 10 and it worked perfectly. Thanks.
Trylr said:
I'm on Android 10, rooted with Magisk and I don't notice any bad battery life. Might be time for a battery replacement. I just got my battery replaced about 2 weeks ago.
Click to expand...
Click to collapse
The battery life only got bad after I upgraded, so I doubt it's hardware.
H0wdy said:
The battery life only got bad after I upgraded, so I doubt it's hardware.
Click to expand...
Click to collapse
How long have you been on Android 10? It always takes a few days at least for everything to settle down. More battery usage early.
salpsuc said:
There is an installer for TWRP, "twrp-installer-3.3.1-0-marlin.zip" but because it doesn't follow the naming convention for all the previous releases "twrp-pixel-installer-marlin X.X.X" it appears at the bottom of the list of installers instead of the top.
Click to expand...
Click to collapse
Wait, so that newest version of twrp does work with 10 on pixel XL?
Sent from my Pixel XL using XDA Labs
It works but it cannot decrypt. You will have to remove any passwords/patterns before booting into it
AP2FTW said:
Wait, so that newest version of twrp does work with 10 on pixel XL?
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
No, sadly we're still waiting. I was just offering a correction.
so i did the magisk patched method but i still don't have root in magisk? i took the boot.img out of the factory image and did it as i was told to...
anything i'm missing?
it's flashing it to boot_a, is it supposed to do something else?
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 Stock to Android 13
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 LTE/deb or Wi-Fi-only/flo to Android 13 / LineageOS 20 with Netflix/Disney+ working
This detailed step-by-step guide helps you transform your Google Nexus 7 (4G or wifi) with Android 6 to a fresher one with Android 13.
### I'll make a few notes using this style: PLEASE READ THEM.
Before going further, make sure you have the correct model.
Go to Settings > About tablet > Model number: Nexus 7
And on tablet's back cover: Nexus is written vertically (horizontally on 2012 model)
### See here if not clear: https://android.stackexchange.com/questions/58273/how-to-distinguish-nexus-7-2012-and-nexus-7-2013
If you have a SIM card slot on the side, it is a LTE model (codename deb), if not, Wi-Fi only alias flo.
Make sure you have latest official updates.
Connect tab to Wi-Fi network.
Go to Settings > About tablet > System updates. Download if update is available.
### WARNING. I'm not sure banking apps will work. Office Lens and Adobe Scan don't work.
### See all my tutorials at https://github.com/djibe/Android-tutorials
### Buy me a coffee: https://ko-fi.com/djibe
CHANGELOG
v10. BitGApps v2, Lanchon repit cited
v9. Android 13, TWRP 3.7 (both by @followmsi)
v8. Back to BitGApps
v7. Hack GApps for Android 12.1/12L (thx to @JamesTanner)
v6. Android 12.1/LOS 19.1
v5. Stick to 12/19 (not 12L/19.1) to wait for compatible BitGApps
v4. Move to Android 12, improve fastboot errors, update Magisk to 24.3 + Netflix access
v3. Move to BitGApps, TWRP 3.6 by @followmsi, repartition script 1380/20 by @k23m
v2. Netflix and Disney+ with Magisk 23 + updated pack, improve readability
v1. Initial release
1) DOWNLOAD
- djibe Nexus 7 2013 pack: https://drive.google.com/file/d/1gPo8YGO-5b6mqugCDyi7T3k94uecwbfZ/view?usp=sharing
(contains USB drivers r13 + fastboot & adb + TWRP recovery 3.7.0_9-0 flo & deb by followmsi + Magisk root + repartition zip sysrepart_1380_20 by @k23m).
### Use Incognito web browser mode if needed to download pack.
Unzip pack on Windows desktop.
For both LTE model/deb & Wi-Fi model re-partitionned/flox
- ROM LineageOS 20 Unofficial by @followmsi (Android 13): https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-20-0.3569067/
Download latest build: See top link in thread above
### You may also want LineageOS 18.1 Official (Android 11): https://download.lineageos.org/flox (download according BitGApps version)
+ BitGApps ARM 13 v2+ CORE: https://github.com/BiTGApps/BiTGApps-Release/releases/
+ Tablet must be fully charged.
2) INSTALL WINDOWS DRIVERS AND BACKUP
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect tab to PC and retrieve data.
3) UNLOCK BOOTLOADER OF GOOGLE NEXUS 7 2013
In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a notification confirms Developer menu is unlocked.
Go to Settings > Developer options and switch USB debugging ON.
Go to my /djibe folder you unziped earlier. In Windows address bar (ie E:\root\Google Nexus 7 2013\djibe\flash), type cmd and hit Enter
to open a Windows Command.
Connect tablet to PC.
Enter command
Code:
adb devices
Command starts adb and returns
Code:
077955f1 unauthorized
ADB (Android Debug Bridge) has started but tab is waiting for authorization.
On tablet, authorize adb commands from Allow USB debugging dialog: tap on OK.
Then enter command
Code:
adb reboot bootloader
Tab restarts and displays a droid, lowest message is: LOCK STATE - locked
Enter command
Code:
fastboot oem unlock
Using Volume+, select Yes - Unlock bootloader, confirm by pressing Power.
Lowest message is now: LOCK STATE - unlocked
### Unable to run fastboot commands: < waiting for device > ? Go to Windows Device Manager
### While in ADB, driver for Android Device should be named Android Composite ADB Interface. In Fastboot: Android Bootloader Interface
### Click on View > Display hidden devices, right click on Nexus 7 > Uninstall. Reinstall drivers. No success ? Try from another computer
Use Volume keys to select Start and Power to confirm.
Tablet is unlocked.
Configure Android quickly, reactivate Developer options and USB debugging.
Then restart tablet to bootloader using once again
Code:
adb reboot bootloader
4) FLASH TWRP 3.7 RECOVERY
Tablet displays the droid logo.
From Windows command, enter:
Code:
fastboot flash recovery twrp-3.7.0_9-0-flo_followmsi.img
### Or for LTE model:
Code:
fastboot flash recovery twrp-3.7.0_9-0-deb_followmsi.img
Command returns Finished. Total time: 0.995s
Back to tablet, use Volume keys to select Recovery mode, confirm with Power.
### You may experience lagginess within the Recovery.
Welcome to TWRP recovery.
Check Never show this screen during boot again and Swip to Allow Modifications.
Go straight to Backup > select Boot, System, Data partitions.
Swipe to Backup and wait during backup.
Back to home screen > Mount (tablet still connected to PC).
You can access tablet's storage folders from Windows Explorer if Data partition is checked and bottom right button show Disable MTP (within TWRP Mount menu).
From Windows Explorer, navigate to Nexus 7 > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) FORMAT PARTITIONS
On tablet, now go to Wipe > Format data.
Type yes and confirm with bottom right check icon.
Now go to Wipe > Advanced Wipe. Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and Swipe to Wipe.
We cannot flash on wiped partitions. Go to Reboot > Recovery and Swipe to Reboot.
Back to Mount menu.
From Windows Explorer, now copy sysrepart_1380_20.zip on Internal Storage.
Disconnect tab.
Back to tablet, go to Install > tap on sysrepart_1380_20.zip and Swipe to flash.
Go to Reboot > Recovery and Swipe to Reboot.
### Repartitioned Wi-Fi model is called flox (instead of flo)
### If you lack space, you should go there: https://forum.xda-developers.com/t/tool-unofficial-port-repit-for-nexus-7-2013-deb-flo.4237183/
6) FLASH ANDROID + GAPPS (+ MAGISK)
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Connect tab to PC.
Back to Mount menu.
Copy ROM + GAPPS (+ Magisk) to Internal storage with Windows Explorer.
Go to TWRP Home > Install.
Select lineage-*.zip,
then Add more zips: bitgapps*.zip and Swipe to Install
(for root, needed for Netflix : and Add More Zips, then Magisk.zip)
### If you get Error 70, don't be scared. Tablet doesn't know the System partition was increased.
### Go to Wipe > Advanced Wipe > Resize File System > Swipe to Resize and flash GApps.
(Repeat Reboot to Recovery with Magisk v25.2 if you need root).
Android 13 is installed !
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (a few minutes).
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magisk via TWRP recovery
Do not connect to Android account.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
Open Files app > Install Magisk.apk.
Then in Magisk goto Settings > Hide magisk app and give it a name, switch Zygisk option ON.
Go to Modules Tab > Install from Storage: MagiskHidePropsConfig and safetynet.
Go to Developer options to disable Android debugging (ADB).
Reboot phone.
You can use yasnac app to check Safetynet passes.
Then with Files App: install netflix and disney+ if needed.
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About tablet.
Tap 7 times on build number.
Back to Settings > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x (or disabled)
Tablet not seen by Windows or Can't access tablet from Windows Explorer ?
Activate Developer options.
Go to Settings > System > Developer options > Default USB configuration > File transfer
11) NETFLIX AND DISNEY+
You may try both apps without more manipulations.
If they don't work, go back to recovery and flash Magisk.
That's it.
Enjoy ;-)
Thanks: @followmsi, @k23m, @nbehary, @DevSwift1, @flex1911, @yattodettaman, @emmett.tsai, TopJohnWu, TWRP team, LineageOS team, BitGApps team
------------------------------------------------------------------------------------------
BOOT TO RECOVERY
Hold Power + Volume- until Droid logo appears and release buttons, this is Bootloader.
Press Volume- twice to show Recovery mode and confirm with Power
Amazing guide. Start to finish in just under an hour. Zero issues.
DefconZero said:
Amazing guide. Start to finish in just under an hour. Zero issues.
Click to expand...
Click to collapse
Hi, glad you like it !
This tab is awesome.
djibe89 said:
Hi, glad you like it !
This tab is awesome.
Click to expand...
Click to collapse
Indeed!
Forgot to add - THANKS to you and all the contributors you mentioned for all the support in keeping this device and the android community alive!
Easy guide, everything seems working just fine except gps not working how do I fix that?
Thanks to you and all the contributors you mentioned for all the support in keeping this device alive
After many unsuccessful attempts (Win64, Linux) I followed these instructions to the letter and it was successful. Thanks!
amem said:
Easy guide, everything seems working just fine except gps not working how do I fix that?
Thanks to you and all the contributors you mentioned for all the support in keeping this device alive
Click to expand...
Click to collapse
Hi,
I don't remember to have GPS failing.
I'm sorry I can't help on this.
I'll try to buy a new tab one day to test it again.
djibe89 said:
Hi,
I don't remember to have GPS failing.
I'm sorry I can't help on this.
I'll try to buy a new tab one day to test it again.
Click to expand...
Click to collapse
Hi
Thanks for taking the time to read my post after reboot It is working fine thanks again
Finally there is a guide which I can refer to as a newbie. Thank you so much!
Not sure why can't boot to recovery mode though...but resolved by manual long hold vol up + power button
andycyc said:
Finally there is a guide which I can refer to as a newbie. Thank you so much!
Not sure why can't boot to recovery mode though...but resolved by manual long hold vol up + power button
Click to expand...
Click to collapse
Hi,
thx for your post.
I'm glad it's useful.
Hi, been running my Nexus 7 rooted and on custom Android 6 based ROM and kernal for probably the last 6 years. Admittedly used very little, but still runs like a champ, if not a little sluggish. So I just decided to check back in to XDA and so happy to find this and try it out. However, GApps link not working for me. "File requested does not exist" Any possibility to fix link?
Thanks very much to OP!!
Edit: wow, pardon the banner, haven't been on XDA like I said for maybe six years, or more!
Edit 2: I believe I found the same GApps from another link djibe89 posted in LG G3 tutorial for the same process. Here:
[GUIDE/TUTORIAL/HOWTO] LG G3 D855 Stock to Android 11
[GUIDE/TUTORIAL/HOWTO] LG G3 D855 Stock to Android 11 [GUIDE/TUTORIAL/HOWTO] LG G3 LG-D855 (Unlocked/Europe) Stock to Android 11 R/LineageOS 18.1 with all files included, Netflix and Disney+ working This detailed step-by-step guide helps you...
forum.xda-developers.com
mookdawg7 said:
Hi, been running my Nexus 7 rooted and on custom Android 6 based ROM and kernal for probably the last 6 years. Admittedly used very little, but still runs like a champ, if not a little sluggish. So I just decided to check back in to XDA and so happy to find this and try it out. However, GApps link not working for me. "File requested does not exist" Any possibility to fix link?
Thanks very much to OP!!
Edit: wow, pardon the banner, haven't been on XDA like I said for maybe six years, or more!
Edit 2: I believe I found the same GApps from another link djibe89 posted in LG G3 tutorial for the same process. Here:
[GUIDE/TUTORIAL/HOWTO] LG G3 D855 Stock to Android 11
[GUIDE/TUTORIAL/HOWTO] LG G3 D855 Stock to Android 11 [GUIDE/TUTORIAL/HOWTO] LG G3 LG-D855 (Unlocked/Europe) Stock to Android 11 R/LineageOS 18.1 with all files included, Netflix and Disney+ working This detailed step-by-step guide helps you...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, you can use Bitgapps:
BiTGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
Clean Flash ROM > restart recovery > flash Gapps > reboot
I'm updating tutorial
djibe89 said:
Hi, you can use Bitgapps:
BiTGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
Clean Flash ROM > restart recovery > flash Gapps > reboot
I'm updating tutorial
Click to expand...
Click to collapse
Fantastic! Everything was going smoothly. But the GApps kept failing on install (Unsupported SDK version, and Install config not found). Thought it might be the version I downloaded, but I came back here and found your reply, so rebooted recovery after Lineage 19 install, installed GApps package, wiped Dalvik/Cache, installed Magisk, wiped dalvik/cache, and rebooted system. Joy! Now appears to be up and running. Seems as though reboot>recovery after ROM flash made the difference. Haven't rooted yet, but I am having a lot of fun. Huge gratitude to you for this tutorial and development work, as well as quick reply. Thank you!
Edit: Ahh, I'm pretty rusty. Realized now Lineage 19 is based off of Android 12, instead of 11. So I installed GApps for 11, not 12. Maybe something to do with it...?
mookdawg7 said:
Fantastic! Everything was going smoothly. But the GApps kept failing on install (Unsupported SDK version, and Install config not found). Thought it might be the version I downloaded, but I came back here and found your reply, so rebooted recovery after Lineage 19 install, installed GApps package, wiped Dalvik/Cache, installed Magisk, wiped dalvik/cache, and rebooted system. Joy! Now appears to be up and running. Seems as though reboot>recovery after ROM flash made the difference. Haven't rooted yet, but I am having a lot of fun. Huge gratitude to you for this tutorial and development work, as well as quick reply. Thank you!
Edit: Ahh, I'm pretty rusty. Realized now Lineage 19 is based off of Android 12, instead of 11. So I installed GApps for 11, not 12. Maybe something to do with it...?
Click to expand...
Click to collapse
Well, I updated tuto for 12.
Choose GApps package accordingly
I'm looking to buy a new one to try 12
And test flashing errors after repartition
djibe89 said:
Well, I updated tuto for 12.
Choose GApps package accordingly
I'm looking to buy a new one to try 12
And test flashing errors after repartition
Click to expand...
Click to collapse
Thanks, worked great for me running unofficial Lineage 19/Android 12! I wasn't able to install official Lineage 18.1. TWRP rejected install because it did not recognize my device as flox. I thought that the repartition package renamed it to this, but anyway that is what I ran into.
mookdawg7 said:
Thanks, worked great for me running unofficial Lineage 19/Android 12! I wasn't able to install official Lineage 18.1. TWRP rejected install because it did not recognize my device as flox. I thought that the repartition package renamed it to this, but anyway that is what I ran into.
Click to expand...
Click to collapse
If you need to force flash one day, you can edit updater-script in ROM archive
djibe89 said:
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 stock to Android 11 or 12
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 LTE/deb or Wi-Fi-only/flo to Android 11 or 12 / LineageOS 18.1 or 19 with Netflix/Disney+ working
This detailed step-by-step guide helps you transform your Google Nexus 7 (4G or wifi) with Android 6 to a powerful one with Android 11 R.
### I'll make a few notes using this style: PLEASE READ THEM.
Before going further, make sure you have the correct model.
Go to Settings > About tablet > Model number: Nexus 7
And on tablet's back cover: Nexus is written vertically (horizontally on 2012 model)
### See here if not clear: https://android.stackexchange.com/questions/58273/how-to-distinguish-nexus-7-2012-and-nexus-7-2013
If you have a SIM card slot on the side, it is a LTE model (codename deb), if not, Wi-Fi only alias flo.
Make sure you have latest official updates.
Connect tab to Wi-Fi network.
Go to Settings > About tablet > System updates. Download if update is available.
### WARNING. I'm not sure banking apps will work.
CHANGELOG
v3. Move to BitGApps, TWRP 3.6 by @followmsi, repartition script 1380/20 by @k23m
v2. Netflix and Disney+ with Magisk 23 + updated pack, improve readability
v1. Initial release
1) DOWNLOAD
- djibe Nexus 7 2013 pack: https://drive.google.com/file/d/1gPo8YGO-5b6mqugCDyi7T3k94uecwbfZ/view?usp=sharing
(contains USB drivers r13 + fastboot & adb + TWRP recovery 3.6.0_9-1 flo & deb by followmsi + Magisk root + repartition zip sysrepart_1380_20 by @k23m).
### Use Incognito web browser mode if needed to download pack.
Unzip pack on Windows desktop.
For both LTE model/deb & Wi-Fi model re-partitionned/flox
- ROM LineageOS 18.1 Unofficial: https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-05-06.3569067/
Download latest build: See top link in thread above
### You may also use LineageOS 18.1 Official: https://download.lineageos.org/flox
### Want Android 12 (maybe not yet fully stable) ? Enjoy https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-19-0-2022-01-07.3569067/
+ BiTGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
+ Tablet must be fully charged to 100%.
2) INSTALL WINDOWS DRIVERS AND BACKUP
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect tab to PC and retrieve data.
3) UNLOCK BOOTLOADER OF GOOGLE NEXUS 7 2013
In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a notification confirms Developer menu is unlocked.
Go to Settings > Developer options and switch USB debugging ON.
Open a Windows command prompt on the /djibe pack folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
Connect tablet to PC.
Enter command
Code:
adb devices
Command starts adb and returns
Code:
077955f1 unauthorized
ADB (Android Debug Bridge) has started but tab is waiting for authorization.
On tablet, authorize adb commands from Allow USB debugging dialog: tap on OK.
Then enter command
Code:
adb reboot bootloader
Tab restarts and displays a droid, lowest message is: LOCK STATE - locked
Enter command
Code:
fastboot oem unlock
Using Volume+, select Yes - Unlock bootloader, confirm by pressing Power.
Lowest message is now: LOCK STATE - unlocked
Use Volume keys to select Start and Power to confirm.
Tablet is unlocked.
Configure Android fast, reactivate Developer options and USB debugging.
Then restart tablet to bootloader using once again
Code:
adb reboot bootloader
4) FLASH TWRP 3.5/3.6 RECOVERY
Tablet displays the droid logo.
Enter this command
Code:
fastboot flash recovery twrp-3.6.0_9-1-flo_followmsi.img
### Or for LTE model:
Code:
fastboot flash recovery twrp-3.6.0_9-1-deb_followmsi.img
Command returns Finished. Total time: 0.995s
Use Volume keys to select Recovery mode, confirm with Power.
### You may experience lagginess within the Recovery.
Welcome to TWRP recovery.
Check Never show this screen during boot again and Swip to Allow Modifications.
Go straight to Backup > select Boot, System, Data partitions.
Swipe to Backup and wait during backup.
Back to home screen > Mount.
You can access folders from PC if Data partition is checked and bottom right button show Disable MTP.
From Windows Explorer, navigate to Nexus 7 > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) FORMAT PARTITIONS
Now go to Wipe > Format data.
Type yes and confirm with bottom right check icon.
Now go to Wipe > Advanced Wipe, select Dalvik / ART Cache, System, Data, Internal Storage, Cache and Swipe to Wipe.
We cannot flash on wiped partitions. Go to Reboot > Recovery and Swipe to Reboot.
Back to Mount.
Copy sysrepart_1280_120.zip on Internal Storage.
Disconnect tab.
Go to Install > tap on sysrepart_1380_20.zip and Swipe to flash.
Go to Reboot > Recovery and Swipe to Reboot.
### Repartitioned Wi-Fi model is called flox (instead of flo)
6) FLASH ANDROID + BITGAPPS (+ MAGISK)
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Connect tab to PC.
Back to Mount menu.
Copy ROM + GAPPS (+ Magisk) to Internal storage with Windows Explorer.
Go to TWRP Home > then Install.
Select lineage-*.zip,
(for root: and Add More Zips, then Magisk.zip)
and Swipe to force install.
After flash, go to Reboot > Recovery
After TWRP reboot, go to Install > BiTGApps*.zip and Swipe to Install.
### If you get Error 70, don't be scared. Tablet doesn't know the System partition was increased.
### Go to Wipe > Advanced Wipe > Resize File System > Swipe to Resize and flash BitGApps.
Android 11 (or 12) is installed !
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (a few minutes).
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magish via TWRP recovery.
Configure Android as you like.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
If Magisk Manager doesn't download apk. Download official apk here: https://github.com/topjohnwu/Magisk/releases
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About tablet.
Tap 7 times on build number.
Back to Settings > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
11) NETFLIX AND DISNEY+
You may try both apps without more manipulations.
If they don't work, go back to recovery anf flash Magisk.
Open Magisk app (v23+).
Go to Settings > go to App Rename app to Godmode to hide hide.
Below, switch MagiskHide ON.
Now go to Magisk Modules tab > install liboemcrypto disabler and MagiskHide Props Config.
Connect to your Google account, download from Play Store Netflix and Disney+.
### If you are already connected to Google account.
Clear cache (Settings > Apps > All apps > Google Play Store > Storage > Clear storage) and restart tab.
Relaunch Play Store, Netflix and Disney+ will be available in SD.
That's it.
Enjoy ;-)
Thanks: @followmsi, @k23m, @nbehary, @DevSwift1, @flex1911, @yattodettaman, @emmett.tsai, TopJohnWu, TWRP team, LineageOS team, BitGApps team
Click to expand...
Click to collapse
I followed the instructions and successfully installed the OS. It was working fine, but after some time touchscreen became unresponsive and now I can't do anything. I tried restarting using the power button and got into recovery, even in recovery, the touch screen is not responding. Someone, Please help.
moneyrockers said:
I followed the instructions and successfully installed the OS. It was working fine, but after some time touchscreen became unresponsive and now I can't do anything. I tried restarting using the power button and got into recovery, even in recovery, the touch screen is not responding. Someone, Please help.
Click to expand...
Click to collapse
Hi, is ADB active ?
djibe89 said:
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 stock to Android 11 or 12
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 LTE/deb or Wi-Fi-only/flo to Android 11 or 12 / LineageOS 18.1 or 19 with Netflix/Disney+ working
This detailed step-by-step guide helps you transform your Google Nexus 7 (4G or wifi) with Android 6 to a powerful one with Android 11 R.
### I'll make a few notes using this style: PLEASE READ THEM.
Before going further, make sure you have the correct model.
Go to Settings > About tablet > Model number: Nexus 7
And on tablet's back cover: Nexus is written vertically (horizontally on 2012 model)
### See here if not clear: https://android.stackexchange.com/questions/58273/how-to-distinguish-nexus-7-2012-and-nexus-7-2013
If you have a SIM card slot on the side, it is a LTE model (codename deb), if not, Wi-Fi only alias flo.
Make sure you have latest official updates.
Connect tab to Wi-Fi network.
Go to Settings > About tablet > System updates. Download if update is available.
### WARNING. I'm not sure banking apps will work.
CHANGELOG
v3. Move to BitGApps, TWRP 3.6 by @followmsi, repartition script 1380/20 by @k23m
v2. Netflix and Disney+ with Magisk 23 + updated pack, improve readability
v1. Initial release
1) DOWNLOAD
- djibe Nexus 7 2013 pack: https://drive.google.com/file/d/1gPo8YGO-5b6mqugCDyi7T3k94uecwbfZ/view?usp=sharing
(contains USB drivers r13 + fastboot & adb + TWRP recovery 3.6.0_9-1 flo & deb by followmsi + Magisk root + repartition zip sysrepart_1380_20 by @k23m).
### Use Incognito web browser mode if needed to download pack.
Unzip pack on Windows desktop.
For both LTE model/deb & Wi-Fi model re-partitionned/flox
- ROM LineageOS 18.1 Unofficial: https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-05-06.3569067/
Download latest build: See top link in thread above
### You may also use LineageOS 18.1 Official: https://download.lineageos.org/flox
### Want Android 12 (maybe not yet fully stable) ? Enjoy https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-19-0-2022-01-07.3569067/
+ BiTGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
+ Tablet must be fully charged to 100%.
2) INSTALL WINDOWS DRIVERS AND BACKUP
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect tab to PC and retrieve data.
3) UNLOCK BOOTLOADER OF GOOGLE NEXUS 7 2013
In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a notification confirms Developer menu is unlocked.
Go to Settings > Developer options and switch USB debugging ON.
Open a Windows command prompt on the /djibe pack folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
Connect tablet to PC.
Enter command
Code:
adb devices
Command starts adb and returns
Code:
077955f1 unauthorized
ADB (Android Debug Bridge) has started but tab is waiting for authorization.
On tablet, authorize adb commands from Allow USB debugging dialog: tap on OK.
Then enter command
Code:
adb reboot bootloader
Tab restarts and displays a droid, lowest message is: LOCK STATE - locked
Enter command
Code:
fastboot oem unlock
Using Volume+, select Yes - Unlock bootloader, confirm by pressing Power.
Lowest message is now: LOCK STATE - unlocked
Use Volume keys to select Start and Power to confirm.
Tablet is unlocked.
Configure Android fast, reactivate Developer options and USB debugging.
Then restart tablet to bootloader using once again
Code:
adb reboot bootloader
4) FLASH TWRP 3.5/3.6 RECOVERY
Tablet displays the droid logo.
Enter this command
Code:
fastboot flash recovery twrp-3.6.0_9-1-flo_followmsi.img
### Or for LTE model:
Code:
fastboot flash recovery twrp-3.6.0_9-1-deb_followmsi.img
Command returns Finished. Total time: 0.995s
Use Volume keys to select Recovery mode, confirm with Power.
### You may experience lagginess within the Recovery.
Welcome to TWRP recovery.
Check Never show this screen during boot again and Swip to Allow Modifications.
Go straight to Backup > select Boot, System, Data partitions.
Swipe to Backup and wait during backup.
Back to home screen > Mount.
You can access folders from PC if Data partition is checked and bottom right button show Disable MTP.
From Windows Explorer, navigate to Nexus 7 > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) FORMAT PARTITIONS
Now go to Wipe > Format data.
Type yes and confirm with bottom right check icon.
Now go to Wipe > Advanced Wipe, select Dalvik / ART Cache, System, Data, Internal Storage, Cache and Swipe to Wipe.
We cannot flash on wiped partitions. Go to Reboot > Recovery and Swipe to Reboot.
Back to Mount.
Copy sysrepart_1280_120.zip on Internal Storage.
Disconnect tab.
Go to Install > tap on sysrepart_1380_20.zip and Swipe to flash.
Go to Reboot > Recovery and Swipe to Reboot.
### Repartitioned Wi-Fi model is called flox (instead of flo)
6) FLASH ANDROID + BITGAPPS (+ MAGISK)
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Connect tab to PC.
Back to Mount menu.
Copy ROM + GAPPS (+ Magisk) to Internal storage with Windows Explorer.
Go to TWRP Home > then Install.
Select lineage-*.zip,
(for root: and Add More Zips, then Magisk.zip)
and Swipe to force install.
After flash, go to Reboot > Recovery
After TWRP reboot, go to Install > BiTGApps*.zip and Swipe to Install.
### If you get Error 70, don't be scared. Tablet doesn't know the System partition was increased.
### Go to Wipe > Advanced Wipe > Resize File System > Swipe to Resize and flash BitGApps.
Android 11 (or 12) is installed !
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (a few minutes).
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magish via TWRP recovery.
Configure Android as you like.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
If Magisk Manager doesn't download apk. Download official apk here: https://github.com/topjohnwu/Magisk/releases
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About tablet.
Tap 7 times on build number.
Back to Settings > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
11) NETFLIX AND DISNEY+
You may try both apps without more manipulations.
If they don't work, go back to recovery anf flash Magisk.
Open Magisk app (v23+).
Go to Settings > go to App Rename app to Godmode to hide hide.
Below, switch MagiskHide ON.
Now go to Magisk Modules tab > install liboemcrypto disabler and MagiskHide Props Config.
Connect to your Google account, download from Play Store Netflix and Disney+.
### If you are already connected to Google account.
Clear cache (Settings > Apps > All apps > Google Play Store > Storage > Clear storage) and restart tab.
Relaunch Play Store, Netflix and Disney+ will be available in SD.
That's it.
Enjoy ;-)
Thanks: @followmsi, @k23m, @nbehary, @DevSwift1, @flex1911, @yattodettaman, @emmett.tsai, TopJohnWu, TWRP team, LineageOS team, BitGApps team
Click to expand...
Click to collapse
hi i followed the tutorial but when i flash twrp recovery then the touch is not working inside the recovery.its really annoying, can you please help me with this im using nexus 7 2013 LTE version
ShivaRK666 said:
hi i followed the tutorial but when i flash twrp recovery then the touch is not working inside the recovery.its really annoying, can you please help me with this im using nexus 7 2013 LTE version
Click to expand...
Click to collapse
Hi, can you try with suitable 3.5 TWRP ?
[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]
LineageOS 20.0 lineage-20.0-20230507-UNOFFICIAL-flo.zip lineage-20.0-20230507-UNOFFICIAL-deb.zip Known issues: - We are still Permissive (SELinux) - Encryption is not working .. Pls do NOT encrypt your /data partition! - Camera is not fully...
forum.xda-developers.com
W.I.P. - UPDATED on 21.05.2023Assumptions of reader,PRIOR to following this guide:
You understand that you follow anything seen here of your own volition.
Your Bootloader is unlocked.
Able to troubleshoot your device, setups, installs, unlocking, rooting, etc.
Capable of searching on XDA/Github/Telegram/Google for missing information and files.
This guide outlines the process I used to clean install the following:TWRP-3.7.0_12-v7.8_A13_FBEv2-lmi-skkk.img
CrDroid v9.5/ A13/build-02.06.2023
NikGapps-T FULL package, 09.06.2023
ROOT/Magisk DELTA - fdac22ba-delta(25210)
Pass SafetyNet Basic Attestation - Universal SafetyNet Fix 2.4.0 by kdrag0n
LSPosed v1.8.6 (6712) ZYGISK and Hide My Apps List
Test root detection, Pass SafetyNet Basic Attestation
PIXEL LAUNCHER ISSUE;
On CrDroid ROMs :
Due to CrDroid Home/Stock Launcher having its own QuickStep built-in, it cannot be installed alongside Pixel Launcher, nor vice versa.
This concerns the Pixel Launcher included in some NikGApps package AND the Pixel Launcher addon.
Therefore, you/we can ONLY use CrDroid Home/Stock Launcher OR Pixel Launcher,
The Pixel Launcher section of your nikgapps.config should look like this to avoid any issues with CrDroid Home Launcher ;
PixelLauncher=1
# Pixel Launcher set to 0 to skip its installation over CrDroid Home Launcher
PixelLauncher=0
DevicePersonalizationServices=1
QuickAccessWallet=1
GoogleWallpaper=1
SettingsServices=1
PrivateComputeServices=1
#Pixel Themes set to 0 to avoid issues with CrDroid Home Launcher
PixelThemes=0
#For Live Captions to work, the follwing must be enabled, i.e. set to 1.
DevicePersonalizationServices=1
SettingsServices=1
PrivateComputeServices=1
More details on using the NikGApps config file can be found here.
A Clean Flashing/Install Environment:
We first need to establish a clean environment.
Opinions may vary, but I will be clean flashing a stock MIUI ROM via fastboot.
For this, I will be using two software programs and one file;
Mi Flash Tool v20220507, or later, from here https://xiaomitools.com/mi-flash-tool-ru/
7-zip file archiver, from here, 7-zip
You will also need the stock MIUI Rom from here; https://xiaomifirmwareupdater.com/miui/lmi/stable
- make sure the details are as below ;
Device: POCO F2 Pro Global
Codename: lmi
Version: V14.0.1.0.SJKMIXM
Branch: Stable
Type: Fastboot
Size: 5.1 GB
Release Date: 2023-03-17
Package Name: lmi_global_images_V14.0.1.0.SJKMIXM_20230317.0000.00_12.0_global_15e376c371.tgz
This is a ".tgz" file and will need to be extracted to obtain the ".tar" file.
Which will then have to be extracted to obtain the images' folder.
The images' folder should be placed on the Desktop, as that is the default working folder now for the Mi Flash Tool.
Note: It is entirely up to you to use the RECOVERY version instead of the FASTBOOT version, but please remember if you did, in the event that you encounter issues, it may help you to troubleshoot accordingly.
Now we can proceed.
The Flashing Process:
An excellent guide on using the tool made by @NOSS8 can be found here; https://forum.xda-developers.com/t/miflash-guide-use-xiaomi-flash-tool.4262425/01. Extract the Mi Flash Tool archive.
02. Open the Mi Flash Tool folder and create a folder called 'log'.
03. This is to avoid an error when we have to authenticate our Mi account.
04. Open the Mi Flash Tool app and select 'Authentication'.
05. Log in with the same credentials you used for your Xiaomi/Mi account and/or to unlock your Bootloader.
06. Select English.
07. Enter your details and wait for the "Login successful[CN]" message, like below, then MINIMISE that window.
Spoiler: Login successful [CN]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
08. Select "Driver" to install drivers to communicate with your device.
09. Select "Configuration", in the "Configuration" window, nothing should be selected/written/filled/checked.
10. In the 'Check Point' section, if you see, "\$fastboot -s .* lock" be sure to delete it and don't leave any blank spaces.
Spoiler: Check Point
11. Click "OK".
12. Select "select" and select your images' folder.
Spoiler: images' folder
13. On your device, Developer Settings/Options must be enabled.
14. Place your device into fastboot mode.
15. Now connect your device to your computer with your data cable.
16. Verify the device is connected by using "fastboot devices" in a terminal window.
Upon confirmation, we can proceed.
17. Verify that at the bottom of the Mi Flash Tool Window that you have selected the "clean all" radio button and that to its right you can see "flash_all.bat" in the drop-down box.
Spoiler: clean all radio button
18. Now you can click, "flash" and the process will begin.
Spoiler: flash result; success
19. Eventually you will see 'success' highlighted in green under "result", shortly after which your device should reboot to system for the first time, in this order; POCO boot logo > MIUI boot animation > Activation screen..
20. It should ask you to connect to a Wi-Fi network, so you can activate the device.
21. Tap "Open Wi-Fi Settings", select the network of your choosing, enter the password, under Advanced Options when entering the password, I usually select Device/Stable MAC because I have had issues with Randomised MAC in the past.
22. Confirm your connection then back out to the main screen to "Activate this device", enter your login details.
23. The MIUI setup process will begin, agree/yes to everything EXCEPT restoring your Google account.
Skip/Ignore the account restoration process as it is a waste of time, we're here for Custom ROMs mate.
DO NOT PUT A PIN/SCHEMA/PASSWORD.
24. Eventually you'll get to the Home Screen, where you'll see the Settings icon in the middle, open it.
25. Now go, Settings > About Phone > All specs > Tap MIUI version until it says Developer Settings unlock, normally 7 taps I think.
26. Now go, Settings > Additional Settings > (scroll to bottom) Developer options > enable USB Debugging, I'm aware etc., 10 sec countdown, tap OK.
Done, now we can get to flashing a Custom Recovery and then our Custom ROM.
27. Reboot your device to fastboot, "adb reboot bootloader" or any other method.
28. Locate your recovery image (TWRP-3.7.0_12-v7.8_A13_FBEv2-lmi-skkk.img) and, using a terminal window, 'cd' to the directory. Then use "fastboot flash recovery twrp.img" to flash your recovery. After which, use "fastboot reboot recovery" to boot your recovery.
29. Assuming TWRP, under the "Wipe" category, perform a Factory Reset" then Wipe Data, after which, REBOOT TO RECOVERY.
30. Copy the ROM and NikGApps to the device, flash the ROM, reboot to recovery, flash NikGApps, reboot to recovery, factory rest and format data, reboot to system.
(Some will say this is excessive but from my perspective, it has eliminated many issues I was having when flashing ROMS)
31. Complete your device first boot setup.
So at this point, I will assume you have done as I have and waited to have restored your Google backup, WhatsApp etc.
EDIT; DUE TO A NEWLY RELEASED TWRP, THE MAGISK DELTA APK CAN BE RENAMED TO .ZIP AND FLASHED FROM RECOVERY WITH THE TWRP LINKED AT THE TOP OF THIS THREAD
Spoiler: Deprecated steps
32. Reboot to recovery. Here you will notice that you cannot mount the Data partition. As of the 9th January, 2023 there is no recovery for our device that can decrypt A13 ROMs, so when rooting the device we will be using "adb sideload" to send and flash Magisk.
33. In your recovery (assuming TWRP), go to Advanced > ADB Sideload, don't wipe Dalvik/Cache > Swipe to start ADB Sideload.
34. In a Command Prompt or Terminal window, opened as Administrator, use ADB sideload by entering the command similarly as seen here;
35. Reboot to System > install the Magisk Delta 25.2 delta 6 apk > open the app > ensure that the installed version is "a0b2003b-delta (25206)"
36. Install Magisk Delta by flashing the apk you have renamed to .zip as mentioned above.
36a. Go to Magisk Delta App > Settings and change the following :
Enable DNS over HTTPS
HIDE the Magisk App
Tap on Systemless Hosts once if you want to use an adblocker like AdAway later on.
Enable Zygisk
Enable Bootloop Protection
Enable MagiskHide
REBOOT
37. Now go to > Configure MagiskHide > search for these apps and use these settings;
For Google Play Store, enable it for com.android.vending
For Google Play Services, enable it for com.google.android.gms AND com.google.android.gms.unstable
You can go ahead and add detection apps like AppList Detector, MOMO, TB Checker etc.
38. In Magisk, flash Universal SafetyNet Fix 2.4.0 and Zygisk LSPosed 1.8.5-6649
REBOOT
39. Allow the shortcut of LSPosed to be added to your Home Screen, open LSPosed, tap the Respository button on the bottom-left side and search for and then install Hide My AppsList 3.1.1, tap on the notifcation and enable the app/module in LSPosed, then REBOOT.
40. Open Hide My Applist > Template Manage > Create a blacklist template with whatever name you want, I just use 'Blacklist' > Edit list > Add the Magisk app and Hide My Applist > back out and the changes will be saved.
41. Open Hide My Applist > App Manage > Search and select your detection apps, and Google Play Store and Services. Ensure that you can see the word "Enabled" next to the selected apps' names, open each and Enabled hide, then under Template config, tap "Using 0 templates" and select the Blacklist you just made.
42. Reboot and check your detection apps, they should look like this;
Spoiler: Detection Apps
Great guide, thanks for your hard work.
Can you share a link to delta 6 zip?
Old_grinch said:
Can you share a link to delta 6 zip?
Click to expand...
Click to collapse
Just rename the .apk to .zip and you can flash it.
I don't even own this phone but this guide it's very good.
typo edit:
30. Copy the ROM and GApps to the device, flash the ROM, reboot to recovery, flash GApps, reboot to recovery, factory rest and format data, reboot to system.
(Some will say this is excessive but from my perspective, it has eliminated many issues I was having when flashing ROMS)
Click to expand...
Click to collapse
"factory rest and format data" - "factory *reset and format data"
"Enable MagiskHide
REBOOT
37. Now go to > Configure MagiskHide > search for these apps and use these settings; "
Is this prefered ? I use SuList mode . Am I wrong and shold use "configure MagiskHide" instead ?
"Pass Basic SafetyNet Attestation - Universal SafetyNet Fix 2.4.0 by kdrag0n"
It works correct on Poco F3 but not on Poco F2 Pro (Crdroid). I suggest to use working :
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Tomek0000 said:
"Enable MagiskHide
REBOOT
37. Now go to > Configure MagiskHide > search for these apps and use these settings; "
Is this prefered ? I use SuList mode . Am I wrong and shold use "configure MagiskHide" instead ?
"Pass Basic SafetyNet Attestation - Universal SafetyNet Fix 2.4.0 by kdrag0n"
It works correct on Poco F3 but not on Poco F2 Pro (Crdroid). I suggest to use working :
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Click to expand...
Click to collapse
KernelSU and/or SUList will not be implemented in the guide until I start using it.
This SafetyNet fix is no longer needed on CrDroid 9.5 20.05 build, but thank you for this, though, I hope it helps someone if they encounter issues.
OP Updated.
Deleted member 10679719 said:
I don't even own this phone but this guide it's very good.
typo edit:
"factory rest and format data" - "factory *reset and format data"
Click to expand...
Click to collapse
Good looking out, I think I got all the typos, if not most this time around when I updated the guide a little.
Old_grinch said:
Can you share a link to delta 6 zip?
Click to expand...
Click to collapse
Spoiler: Check here
Glad to see the guide updated
Lughsen said:
Glad to see the guide updated
Click to expand...
Click to collapse
You're welcome!
The process outlined can work for many ROMs, but I focus on CrDroid because I use it as my daily driver.
I'll try my best to update it as often as I can (once/twice every two weeks) but for the moment I have exams.
Gonna made a rom installation round.
I'll tell you if the guide works on other roms
With lastest TWRP FBEv2, all roms installed with no issues.
I´m having problems (i hope i will solve it) with the fastboot full rom installation. I think new version on twrp has an option to prevent from installing new recovery checked by default, so brand new miui installation always fails.
On your next update of the guide, maybe you need to point about this
Lughsen said:
With lastest TWRP FBEv2, all roms installed with no issues.
I´m having problems (i hope i will solve it) with the fastboot full rom installation. I think new version on twrp has an option to prevent from installing new recovery checked by default, so brand new miui installation always fails.
On your next update of the guide, maybe you need to point about this
Click to expand...
Click to collapse
Thanks for reminding me about FBEv2, needed to add that in for some time.
I just updated the guide after following the steps, changing/adding only the recent builds of TWRP FBEv2, CrDroid 9.5, NikGapps.
I had no issue at the fastboot clean flash section, using the TWRP linked in the guide.
I require more specificity on the issues related to the fastboot clean flash, so I can reproduce them on my side and write a detailed solution/circumvention into the guide.
Thanks for looking out @Lughsen
lots of unneeded step, i succesfully do it 5x faster than this.
coming from miui13:
ubl, flash latest twrp, reboot reovery
format data, reboot recovery
flash latest fw>rom>nik core>magisk official>reboot system
after boot, open magisk>direct install>reboot
open magisk, install unisafetynetfix>magiskhidepropconf, enable zygisk, reboot
open magisk, deny playstore stuff
all works fine, safetynet passed.
i wonder why you need to torture yourself by going full miui flash and lsposed.