Database Develop

[STOCK][C6603&C6602] Update to 10.1.1.A.1.307 [Rooted & XZDualRecovery][LB/UB]

[STOCK][C6603&C6602] Update to 10.1.1.A.1.307 [Rooted & XZDualRecovery][LB/UB]
Built from the FTF uploaded by @Psicao: Xperia Z_10.1.1.A.1.307_Unbranded BE.
Requirements:
Flashtool by @Androxyde
A recovery (can be both CWM and TWRP)
NOTE: As some people have problems flashing the update, please update your existing recovery to the latest recovery with XZDualRecovery
Current FW version: 10.1.A.1.350, 10.1.A.1.434 10.1.1.A.1.253: maybe others too, try and let me know!
From the users in the thread I noticed people CWM running into trouble because their cache partition is gone. See the 'Known Issues' in the OP of the XZDualRecovery link above for more info and links to a fix. Fix that first before you attempt this update using CWM!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.4 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guides I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.1.1.A.1.307:
For C6602: Download C6602.flashable.307.zip (Bittorrent: 716MB) and Xperia_Z_10.1.1.A.1.307_C6602_TW-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6602.flashable.307.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.307_C6602_TW-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.307_C6602_TW-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6602.flashable.307.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.1.1.A.1.307:
For C6603: Download C6603.flashable.307.zip (Bittorrent: 736MB) and Xperia_Z_C6603_10.1.1.A.1.307_BE-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6603.flashable.307.zip' on (the external) SDcard1;
Put 'Xperia_Z_C6603_10.1.1.A.1.307_BE-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_C6603_10.1.1.A.1.307_BE-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6603.flashable.307.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone and after that, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
All known issues in TWRP and CWM on locked boot loaders apply, see their respective threads for more information.
Be especially careful with the cache partition when using CWM. Hopefully version 2.0 solved the cache issues but in case of problems with /cache use the FTF in my files to restore the cache partition if yours ever stops mounting due to the CWM issues, read this and this for more info on that.
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery answering the question 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/xbin/busybox pkill -f /sbin/ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a .434 /system ONLY using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.13
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperUser (default in this ROM) to SuperSU you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
{
"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"
}

Success with UK unbranded.
I was still waiting for .253 and just had enough waiting.

c6602 version please.thank you =)

nicestupid89 said:
c6602 version please.thank you =)
Click to expand...
Click to collapse
thanks for the guide! works like a charm here on C6603:laugh::good:

Thanks a lot. Update running perfectly fine.

Reserved
Sent from my LG-LS970 using xda app-developers app

I followed the instructions without any problem. Thanks a lot . Can i flash other mods on customizations on this rom yet?

I`ve got reboots after mounting r/w in root explorer

long2905 said:
I followed the instructions without any problem. Thanks a lot . Can i flash other mods on customizations on this rom yet?
Click to expand...
Click to collapse
As long as they are ODEX, Yes.
DennisDD78 said:
I`ve got reboots after mounting r/w in root explorer
Click to expand...
Click to collapse
Use the guide in the known XZDualRecovery issues...
nicestupid89 said:
c6602 version please.thank you =)
Click to expand...
Click to collapse
As soon as an unbranded/General FTF will be available.
Sent from my C6603 using xda app-developers app

Tried to flash mutator, it hangs both recoveries, at the start of installation. Earlier i flashed .253 f/w using your instruction, there was no problems with reboots.
---------- Post added at 06:10 AM ---------- Previous post was at 06:05 AM ----------
[NUT] said:
Use the guide in the known XZDualRecovery issues...
Click to expand...
Click to collapse
I`m sorry, i can`t get what do i have to exactly to do to fix the reboot problem ?

DennisDD78 said:
Tried to flash mutator, it hangs both recoveries, at the start of installation. Earlier i flashed .253 f/w using your instruction, there was no problems with reboots.
---------- Post added at 06:10 AM ---------- Previous post was at 06:05 AM ----------
I`m sorry, i can`t get what do i have to exactly to do to fix the reboot problem ?
Click to expand...
Click to collapse
Then try the guide at the CWM Usage warning. Doing that will most probably be the solution.
Just remember to answer the question just before rebooting from CWM with NO in the future...
Sent from my C6603 using xda app-developers app

:good:
Thx nut!!!
I came from 434 with root and lb. I have done every step in your op and everything works great!!!
I follow you since the first day of xz and you make a great work and very good support. For this a small beer should be now on your paypal account Thx man

eagle1977 said:
:good:
Thx nut!!!
I came from 434 with root and lb. I have done every step in your op and everything works great!!!
I follow you since the first day of xz and you make a great work and very good support. For this a small beer should be now on your paypal account Thx man
Click to expand...
Click to collapse
I'll drink to that

I am coming from RomAur 4.3 and when i flash the ftf, i have the following error message: Any suggestion?
07/040/2013 16:40:31 - INFO - <- This level is successfully initialized
07/040/2013 16:40:31 - INFO - Flashtool Version 0.9.10.2beta6 built on 2013-04-21 22:23:00
07/040/2013 16:40:36 - INFO - Selected Xperia Z / C6603_10.1.1.A.1.307_BE / No
07/040/2013 16:40:37 - INFO - Preparing files for flashing
07/040/2013 16:40:37 - INFO - Device disconnected
07/040/2013 16:40:37 - INFO - Please connect your device into flashmode.
07/040/2013 16:40:50 - INFO - Device connected in flash mode
07/040/2013 16:40:50 - INFO - Opening device for R/W
07/040/2013 16:40:50 - INFO - Device connected in flash mode
07/040/2013 16:40:51 - INFO - Start Flashing
07/040/2013 16:40:51 - INFO - Processing loader
07/040/2013 16:40:51 - INFO - Checking header
07/040/2013 16:40:51 - INFO - Ending flash session
07/040/2013 16:40:51 - ERROR -
07/040/2013 16:40:51 - ERROR - Error flashing. Aborted
07/040/2013 16:40:51 - INFO - Device connected in flash mode
EDIT: I need to download to 434 from the video guide (http://www.youtube.com/watch?feature=player_embedded&v=zX9ho2OmHmk#!) and wipe all data. Will try and report.
Strange! I tried to downgrade to 434 fw but got the same error message. I choose wipe all but still get the same error message.
Silly me. I connected by USB to a USB hub! Connect directly to computer and no problem.

So I have hit an NFC issue, it can't be turned on, the check will briefly appear and then the box will be unchecked again.
Not much in the log
Code:
I/NfcService( 2056): Enabling NFC
E/NFCJNI ( 2056): phLibNfc_Mgt_ConfigureDriver() returned 0x0106[NFCSTATUS_INVALID_DEVICE]
W/NfcService( 2056): Error enabling NFC
D/NFCHandover(31946): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
D/NFCHandover(31946): ! !
D/NFCHandover(31946): ! NFC OFF
D/NFCHandover(31946): ! !
D/NFCHandover(31946): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
D/SmartKey Service(32277): isPlaying false
D/dalvikvm( 4852): GC_CONCURRENT freed 2025K, 33% free 19719K/29123K, paused 13ms+15ms, total 49ms
D/dalvikvm(15181): GC_CONCURRENT freed 6313K, 25% free 28143K/37319K, paused 13ms+23ms, total 95ms
D/SmartKey Service(32277): isPlaying false
UPDATE
Ok issue resolved, it was the /data/usf directory problem that can happen with the rooting method.
I renamed that directory and restarted.
I got a message about upgrading NFC firmware when it had rebooted, it worked fine after that.

timchew said:
I am coming from RomAur 4.3 and when i flash the ftf, i have the following error message: Any suggestion?
07/040/2013 16:40:31 - INFO - <- This level is successfully initialized
07/040/2013 16:40:31 - INFO - Flashtool Version 0.9.10.2beta6 built on 2013-04-21 22:23:00
07/040/2013 16:40:36 - INFO - Selected Xperia Z / C6603_10.1.1.A.1.307_BE / No
07/040/2013 16:40:37 - INFO - Preparing files for flashing
07/040/2013 16:40:37 - INFO - Device disconnected
07/040/2013 16:40:37 - INFO - Please connect your device into flashmode.
07/040/2013 16:40:50 - INFO - Device connected in flash mode
07/040/2013 16:40:50 - INFO - Opening device for R/W
07/040/2013 16:40:50 - INFO - Device connected in flash mode
07/040/2013 16:40:51 - INFO - Start Flashing
07/040/2013 16:40:51 - INFO - Processing loader
07/040/2013 16:40:51 - INFO - Checking header
07/040/2013 16:40:51 - INFO - Ending flash session
07/040/2013 16:40:51 - ERROR -
07/040/2013 16:40:51 - ERROR - Error flashing. Aborted
07/040/2013 16:40:51 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
Can you look in the FlashTool folder and see if there is a file called stderr.log ?
It might tell you what went wrong... sounds a little like a FlashTool bug... but the above log does not say much...
DiscipleOfKane said:
So I have hit an NFC issue, it can't be turned on, the check will briefly appear and then the box will be unchecked again.
Not much in the log
Code:
I/NfcService( 2056): Enabling NFC
E/NFCJNI ( 2056): phLibNfc_Mgt_ConfigureDriver() returned 0x0106[NFCSTATUS_INVALID_DEVICE]
W/NfcService( 2056): Error enabling NFC
D/NFCHandover(31946): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
D/NFCHandover(31946): ! !
D/NFCHandover(31946): ! NFC OFF
D/NFCHandover(31946): ! !
D/NFCHandover(31946): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
D/SmartKey Service(32277): isPlaying false
D/dalvikvm( 4852): GC_CONCURRENT freed 2025K, 33% free 19719K/29123K, paused 13ms+15ms, total 49ms
D/dalvikvm(15181): GC_CONCURRENT freed 6313K, 25% free 28143K/37319K, paused 13ms+23ms, total 95ms
D/SmartKey Service(32277): isPlaying false
[snip]
Click to expand...
Click to collapse
Just to prove it does work before we try to troubleshoot your problem:
So... from what FW version did you come up to this one?
DiscipleOfKane said:
UPDATE
Ok issue resolved, it was the /data/usf directory problem that can happen with the rooting method.
I renamed that directory and restarted.
I got a message about upgrading NFC firmware when it had rebooted, it worked fine after that.
Click to expand...
Click to collapse
I actually LOL'ed ... as it was my hunch and i was planning on guiding you through to that
timchew said:
EDIT: I need to download to 434 from the video guide (http://www.youtube.com/watch?feature=player_embedded&v=zX9ho2OmHmk#!) and wipe all data. Will try and report.
Click to expand...
Click to collapse
No, actually you do not HAVE to, you can try that to solve problems. Your problem with FlashTool aborting the flashing operation might actually be a simple case of a fubar by FlashTool or your phone losing connection due to a bad cable/connector/contact...
Try:
- Closing all applications but FlashTool;
- Disconnecting all USB devices except mouse and keyboard;
- Rebooting your pc;
- Connecting your phone to a different cable;
- Connecting your phone on a different port;
And see what FlashTool says in the stderr.log inside the C:\FlashTool directory.

[NUT] said:
Just to prove it does work before we try to troubleshoot your problem:
So... from what FW version did you come up to this one?
Click to expand...
Click to collapse
I just got it fixed, it was the /data/usf directory problem.
I came from the .434 firmware.

Im on existenz v3 rom now,BL Unlocked with doom kernel v7 installed. What will i flash,is it the zip file on the first post or the one with aroma installer? And is this rom deodexed? And do i need to flash the tft file using flashtool or i go straight to the flashable zip?sorry im a bit confused

dyepnoodle said:
Im on existenz v3 rom now,BL Unlocked with doom kernel v7 installed. What will i flash,is it the zip file on the first post or the one with aroma installer? And is this rom deodexed? And do i need to flash the tft file using flashtool or i go straight to the flashable zip?sorry im a bit confused
Click to expand...
Click to collapse
1. You CAN flash the FTF, but as most things are equal between .253 and .307 regarding the FTF contents, you don't need to. When you do, don't forget to untick the kernel, as you have a custom kernel, you want to keep that.
2. This ROM is ODEX (it is Stock Sony)
3. The link to the ROM is in the step-by-step guide. It is a non-aroma flashable zip.
4. You only need the ROM Mutator if you run into problems (root explorer remount rw reboot issue) or want to switch from SuperUser to SuperSu.
Is it clear now? :angel:

[NUT] said:
1. You CAN flash the FTF, but as most things are equal between .253 and .307 regarding the FTF contents, you don't need to. When you do, don't forget to untick the kernel, as you have a custom kernel, you want to keep that.
2. This ROM is ODEX (it is Stock Sony)
3. The link to the ROM is in the step-by-step guide. It is a non-aroma flashable zip.
4. You only need the ROM Mutator if you run into problems (root explorer remount rw reboot issue) or want to switch from SuperUser to SuperSu.
Is it clear now? :angel:
Click to expand...
Click to collapse
Any issues flashing BE Generic on a UK Three handset?

Rooting and Unroot Huawei P8 [6.0] [FOR All EMUI4.0.1] all [GRA-Types]

{
"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"
}
Rooting and Unroot Huawei P8 GRA-xxx Marshmallow (Android 6) [All Stock-Firmwares with EMUI4.0.1]​
For newer Firmwares use following Guide: https://forum.xda-developers.com/showpost.php?p=75460388&postcount=323
Note: DONT FLASH SUPERSU OVER EXISTING ROOT - SINCE SUPERSU 2.82 IT IS REQUIRED TO UNROOT YOUR PHONE BEFORE USING NEWER VERSION!
SuperSU-v2.82-SR5-permissive.zip by Tecalote: https://www.androidfilehost.com/?fid=962187416754458671 MD5: b168a88bc815d3fac521ace97402a949
It enables init.d and SELinux Permissive (required for installing several mods like Viper4Android etc...)
NEW TWRP released by @AD2076 : https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img.html
This new method should work on all types of GRA (GRA-L09-TL00-CL00-UL00-UL10-TL10-CL10) for newer Firmwares from 2017 on!
For Unroot you can do it directly from SuperSU App - with restoring the boot.img (SuperSU App ask you, answer with YES) - or alternative you can flash UnSU Script with TWRP:
http://forum.xda-developers.com/showpost.php?p=63615067
If you flash unsu script - you must restore your original unmodified boot.img from TWRP Backup! This make sure you can boot straight to system after Unroot.
If you flash instead boot.img extracted from update.app you cannot boot to system before installing EMUI Recovery and doing Factoryreset.
But it is possible to Root your Phone directly after flashing boot.img to BOOT
Restoring boot.img is required after Unroot in every case! A) If you like to stay unrooted and B) if you want to Root with new Version of SuperSU. If you want Root with new SuperSU, you must restore original boot.img. After you have restored it from TWRP Backup or flashed it with adb in Fastboot Mode, you can Root directly after restoring without boot to system before.
If you cannot restore boot.img, because you have no TWRP Backup from Boot, you can download the Firmware for your build Number (Settings/About Phone) from here:
http://pro-teammt.ru/firmware-database/?firmware_model=GRA&firmware_page=0
With following Tool you can extract boot.img from UPDATE.APP - Huawei Update Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Unlocked Bootloader required
Unlocked Bootloader:
If your Bootloader is locked install the App Huawei-ID on your Phone. On newer Firmwares, the Huawei-ID App is already preinstalled.
But anyway update it to this version: https://www.androidfilehost.com/?fid=385035244224383206
After you must visit website for login and requesting the unlock-code. Visit: http://emui.huawei.com/en/plugin/hwdownload/download and click: Unlock Bootloader.
Make an Account or Login with your Huawei-ID, click again: Unlock Bootloader. Fill out form - you can find all information in Settings "About the Phone" and "Status" - for the Product-ID use dialer ( *#*#1357946#*#* ). Submit information and you receive the Unlock Code.
- On your phone activate the developer options (Settings "About the phone" press several times consecutively the "Build-Number")
- In developer options activate "USB-Debugging"
- In Settings "Security" activate "Unknown Sources" and HiSuite HDB accept
- install the latest HiSuite (from Huawei) on your PC - Download: http://consumer.huawei.com/minisite/HiSuite_en/index.html
- start HiSuite and connect your Phone with the USB-Cable with your PC. You will receive a fingerprint question on your Phone, acitvate "Always" and "Yes"
- accept also the installing of HiSuite on your Phone. As soon the drivers are installed and your phone is succesful connected, close HiSuite (even in the background).
- unzipp "Minimal ADB + Fastboot", install it on your PC - Download: https://www.androidfilehost.com/?fid=385035244224386526
- (the path will be C:\Program Files (x86)\Minimal ADB and Fastboot) - after open the Program as Administrator
- tap: adb devices (your device must listed with ID)
- tap: adb reboot bootloader (Phone restart in Fastboot-Mode) You will see, your bootloader is locked
- wait until PC installs additional drivers, after:
- tap: fastboot devices (your device must listed with ID)
- tap: fastboot oem unlock YOUR16DIGITCODE (which you have received from Huawei) - after unlock tap: fastboot reboot
If you have problems to execute fastboot-commands and you see just: "Waiting for any devices" - or if you have trouble with hardware-buttons read following information: http://forum.xda-developers.com/showpost.php?p=69440645&postcount=129
Old methods (2016) - not reccomended for newer Firmwares (2017..)
It is no more possible to Root Huawei Firmware up to EMUI 4.01 with newer Versions of SuperSU (current stable 2.78) neither with the Force Systemless Command! Dont try it, because SuperSU will destroy the original boot.img of the Firmware - See Screenshot 1. You can flash the zip but your phone would not boot and staying on the Rescue-Screen of the Bootloader.... That´s why I maked this Thread!
All methods updated 13.10.2016 - everything works now! .
For systemless rooting (like my method A) you can also use the SRKToolHuawei 2.0 by @somboons
- Download: https://www.androidfilehost.com/?fid=529152257862664925 - Thread: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Before you going to root your phone make a full Nandroid Backup (all shown Partitions) with TWRP - if something goes wrong you can restore your backup.
Thread for German Speakers GRA-L09: http://www.android-hilfe.de/thema/huawei-p8-b380-root-anleitung.797464/
Requirements:
1) Unlocked Bootloader:
If your Bootloader is locked install the App Huawei-ID on your Phone. On newer Firmwares, the Huawei-ID App is already preinstalled.
But anyway update it to this version: https://www.androidfilehost.com/?fid=385035244224383206
After you must visit website for login and requesting the unlock-code. Visit: http://emui.huawei.com/en/plugin/hwdownload/download and click: Unlock Bootloader.
Make an Account or Login with your Huawei-ID, click again: Unlock Bootloader. Fill out form - you can find all information in Settings "About the Phone" and "Status" - for the Product-ID use dialer ( *#*#1357946#*#* ). Submit information and you receive the Unlock Code.
- On your phone activate the developer options (Settings "About the phone" press several times consecutively the "Build-Number")
- In developer options activate "USB-Debugging"
- In Settings "Security" activate "Unknown Sources" and HiSuite HDB accept
- install the latest HiSuite (from Huawei) on your PC - Download: http://consumer.huawei.com/minisite/HiSuite_en/index.html
- start HiSuite and connect your Phone with the USB-Cable with your PC. You will receive a fingerprint question on your Phone, acitvate "Always" and "Yes"
- accept also the installing of HiSuite on your Phone. As soon the drivers are installed and your phone is succesful connected, close HiSuite (even in the background).
- unzipp "Minimal ADB + Fastboot", install it on your PC - Download: https://www.androidfilehost.com/?fid=385035244224386526
- (the path will be C:\Program Files (x86)\Minimal ADB and Fastboot) - after open the Program as Administrator
- tap: adb devices (your device must listed with ID)
- tap: adb reboot bootloader (Phone restart in Fastboot-Mode) You will see, your bootloader is locked
- wait until PC installs additional drivers, after:
- tap: fastboot devices (your device must listed with ID)
- tap: fastboot oem unlock YOUR16DIGITCODE (which you have received from Huawei) - after unlock tap: fastboot reboot
If you have problems to execute fastboot-commands and you see just: "Waiting for any devices" - or if you have trouble with hardware-buttons read following information: http://forum.xda-developers.com/showpost.php?p=69440645&postcount=129
2) There is a new TWRP released by KangV from the Huawei Rom Team (HRT) v. 3.0.2 - multilingual. ​ Download: https://www.androidfilehost.com/?fid=529152257862681510
- rename the .img to "TWRP" (TWRP.img) and flash it with ADB.
- first store the TWRlP.img in C:\Program Files (x86)\Minimal ADB and Fastboot, after open the Program (Phone must be connected with USB to PC)
- tap: adb devices (your device must listed with ID)
- tap: adb reboot bootloader (Phone restart in Fastboot-Mode - you will see, your bootloader is unlocked now)
- tap: fastboot flash recovery TWRP.img
If the flashing of the Recovery is succesfully done - disconnect your Phone from USB!
- press the Vol+ button first (staying on Vol+) and simultaneously press the Power Button
- wait until the phone reboot - in the moment you see the Huawei Logo skip pressing the Power Button but stay on Vol+ until you are succesfully bootet to TWRP
- TWRP ask you by the first start for root access "Allow to modify system partion" - swype to confirm "yes"
- go to button "Backup", select your external Storage and make a complete Nandroid Backup of all shown partititions
- after you can Root your Phone now - see description
Note: If you make something wrong booting first time to TWRP and the Phone reboot to system instead of TWRP, Stock-Recovery will be reflashed and you must flash TWRP again with ADB
A) Rooting in systemless Mode (by maintaining the original Stock-Kernel)
Note: This kind of rooting your phone is for for normal use (Root-Explorer, Root-Apps) but not for Hardliner-Mods
Your TWRP should always have write permissions, if it ask you swype to confirm this! If it don`t have, you can enable this in the Mount button (disable system partition read only)
1.) Download SuperSU with your Browser (not with Downloadmanager) 2.67: https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip?retrieve_file=1
- or download the file from the attached file below in OP and place SuperSU 2.67 on the external SD
2.) Boot to TWRP and make a complete Nandroid Backup first (if you dont have it already)
3.) In TWRP go to the Advanced button and use the Terminal.
On the first screen tap on the ok button and after write following Force Systemless Command:
echo SYSTEMLESS=true>>/data/.supersu
and quit this with the ok tab
4.) Navigate back to the main menu and use the Install button
5.) Navigate to the location of the placed SuperSU 2.67
6.) Swype to confirm flash - after use: Reboot
7.) If TWRP ask you for Root - "Your device does not appear to be rooted - Install SuperSU now?" - NO - use: DO NOT INSTALL Button!
Older Versions of TWRP ask you this - the newest TWRP 3.0.2 dont.
8.) P8 reboots now 2 times and rebooted finaly to system.
9.) Open the SuperSU App (it will be on an empty site of your home) - you have now systemless Root
10.) Open Playstore an Update the SuperSU and after say yes to Update the Binary.
11.) The Phone must be restarted and you are up-do-date with the Root.
Uninstall this kind of Root:
If you want to unroot your Phone and you have used method A, do following:
1) If you have Xposed Framework installed - uninstall it with the uninstaller.zip (matching your phone) in TWRP - directly after you must Wipe Cache and Dalvik - next step: reboot your phone.
2) If you have BusyBox installed - uninstall it with BusyBox-Cleaner.zip in TWRP - Download: https://www.androidfilehost.com/?fid=24591000424941581
3) Reboot Phone open SuperSU and tap "complete Unroot"
4) If SuperSU ask you to restore your original Boot Image - say yes!
5) If the phone reboot automatically Unroot is ready - check it with Root Checker
6) If the phone dont reboot automatically, boot into TWRP and:
7) flash unsu.zip - Download: http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893 - reboot your Phone and Unroot is ready.
8) If the Download-Link of unsu.zip has changed, because it gets updates - you find it on this site: http://forum.xda-developers.com/showpost.php?p=63615067
B) Rooting in SYSTEM-Mode (by using modified Stock-Kernel made for Rooting with SuperSU)
1.) Download SuperSU - current version 2.79 Stable (with Browser, not with Downloadmanager): https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip?retrieve_file=1- it is the original one from Chainfire, not CCMT
2.) Download the Kernel, which allow you to Root: https://www.androidfilehost.com/?fid=385035244224383592
3.) Place both zips on the external SD
4.) Reboot to TWRP Recovery
5.) Make a comlete Nandroid Backup
6.) Navigate back to the main menu
7.) Use: Install - and navigate to the place of the Kernel-for-Root-Stock-MM.zip
8.) Swype to confirm flashing the Kernel-for-Root-Stock-MM.zip
9.) Directly after this flash navigate back to the main menu
10.) Use: Install - navigate to SuperSU.zip
11.) Swype to confirm flashing SuperSU - after use: Reboot
12.) If TWRP ask you for Root - "Your device does not appear to be rooted - Install SuperSU now?" - NO - use: DO NOT INSTALL Button!
Older Versions of TWRP ask you this - the newest TWRP 3.0.2 dont.
13.) P8 reboots one times directly to the system
14 Open the SuperSU App (it will be on an empty site of your home) - you have now Root in the System with the latest stable SuperSU
Unroot this Installation of Root in System-Mode:
1) If you have Xposed Framework installed - uninstall it with the uninstaller.zip (matching your phone) in TWRP - directly after you must Wipe Cache and Dalvik - next step: reboot your phone.
2) If you have BusyBox installed - uninstall it with BusyBox-Cleaner.zip in TWRP - Download: https://www.androidfilehost.com/?fid=24591000424941581
3) Reboot Phone open SuperSU and tap "complete Unroot" - Needs some seconds, after:
4) flash unsu.zip - Download: http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893 - reboot your Phone and Unroot is ready.
5) If the Download-Link of unsu.zip has changed, because it gets updates - you find it on this site: http://forum.xda-developers.com/showpost.php?p=63615067
6) Reboot your Phone, and if
7) If TWRP ask you for Root - "Your device does not appear to be rooted - Install SuperSU now?" - NO - use: DO NOT INSTALL Button!
Older Versions of TWRP ask you this - the newest TWRP 3.0.2 dont.
8) After Reboot check it with a Root Checker - Your devices is not Rooted!
C) Systemless Rooting (by using modified Stock-Kernel made for Rooting with SuperSU)
Note: This is the only kind of Root to install the Systemless Xposed Framework!
This Thread does not officially Support the issue "how do hide Root" . Please use other Threads made for this. But you're invited to post ideas and solutions for this issue - if you have any! Because many people searching for a good solution
1.) Download SuperSU - current version 2.79 Stable (with Browser, not with Downloadmanager): https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip?retrieve_file=1 - it is the original one from Chainfire, not CCMT
2.) Download the Kernel - which allows you to Root: https://www.androidfilehost.com/?fid=385035244224383592
3.) Place both zips on the external SD
4.) Reboot to TWRP Recovery
5.) Make a comlete Nandroid Backup
6.) Navigate back to the main menu
7.) Use: Install - and navigate to the place of the Kernel-for-Root-Stock-MM.zip
8.) Swype to confirm flashing the Kernel-for-Root-Stock-MM.zip
9.) Directly after this flash navigate back to the main menu
10.) After go to the Advanced button and use the Terminal.
On the first screen tap on the ok button and after write following Force Systemless Command:
echo SYSTEMLESS=true>>/data/.supersu
and quit this with the ok tab
11.) Use the install button and navigate to SuperSU.zip
12.) Swype to confirm flashing SuperSU
13) Reboot your Phone
14.) If TWRP ask you for Root - "Your device does not appear to be rooted - Install SuperSU now?" - NO - use: DO NOT INSTALL Button!
Older Versions of TWRP ask you this - the newest TWRP 3.0.2 dont.
15.) P8 reboots now 2 times and rebooted finaly to system.
16 Open the SuperSU App (it will be on an empty site of your home) - you have now systemless Root with the latest stable SuperSU
Uninstall this kind of systemless Root:
If you like to Unroot your Phone from this systemless Root, do following steps:
1) If you have Xposed Framework installed - uninstall it with the uninstaller.zip (matching your phone) in TWRP - directly after you must Wipe Cache and Dalvik - next step: reboot your phone.
2) If you have BusyBox installed - uninstall it with BusyBox-Cleaner.zip in TWRP - Download: https://www.androidfilehost.com/?fid=24591000424941581
3) Reboot Phone open SuperSU and tap "complete Unroot"
4) If SuperSU ask you two times to restore the original Stock-Boot Image say: YES
5) Phone reboots automatically
6) Check it with Root Checker: succesfully unrooted
7) If the phone dont reboot automatically - reboot by yourself to TWRP
8) flash unsu.zip - Download: http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893 - reboot your Phone and Unroot is ready.
9) If the Download-Link of unsu.zip has changed, because it gets updates - you find it on this site: http://forum.xda-developers.com/showpost.php?p=63615067
10) Reboot your Phone - Root is uninstalled
After you have rooted your phone - it is recommended to flash Busybox in TWRP:
I always prefere BusyBox YDS by YashdSaraf for Huawei P8. This busybox recognizes which kind of Root and architecture you have and it will install to in the right directory. It uses also arm64 Binarys - just flash it after Rooting and first boot to system with TWRP.
You can find the Thread here: http://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
Use in Download Section the Universal zip or the ARM zip (it conains arm64).
Credits:
Many thanks to @Chainfire for his grandiose SuperSU
Many thanks to @AD2076 for the new TWRP-Recovery twrp-3.1.1-0-grace.img for Huawei p8 marshmallow.
And thanks a lot to @YashdSaraf for very good BusyBox
Last Update: 06.02.2018

Will this work on GRA-UL10?
Thanks a lot.

lordcookies said:
Will this work on GRA-UL10?
Thanks a lot.
Click to expand...
Click to collapse
Sorry for my late answer. I saw your message just right now. GRA-UL10 is Chinese Unicom Dual 4G model, with Kirin 935 chipset and 64GB ROM. Which firmware version do you have? The Root Method A should work without problem. Be sure you make before rooting a complete Nandroid Backup. If something goes wrong you can reboot to TWRP with hardware keys and restore system, data and boot. So nothing bad could happened.
The Methods B and C needs to flash the Custom Kernel, I don't know if it works with GRA-UL10. But with a Full TWRP Nandroid Backup you can try... Please let me know if it works for you
Info:The TWRP should work with GRA-UL10 without problems - or do you have another one working for marshmallow? If yes, please post. Thanks

Result without success
Hi, thanks for your post. I tried with the first option with SYSTEMLESS and STOCK Kernel. Everything worked as you described but after I tried to reboot the phone was dead. I had to reinstall the B370 update I had in /dload folder. I followed very carefully your instructions step by step.
First successful rooted boot, I updated SuperSu with the binary option and rebooted without problems. But one hour after I tried to reboot the phone manually and then the problem appeared.
My phone is working now but I don't know how to make this permanent. Do you have any idea?
Ps: attached screenshot of my current build
Thanks again!

juanzete said:
Hi, thanks for your post. I tried with the first option with SYSTEMLESS and STOCK Kernel. Everything worked as you described but after I tried to reboot the phone was dead. I had to reinstall the B370 update I had in /dload folder. I followed very carefully your instructions step by step.
First successful rooted boot, I updated SuperSu with the binary option and rebooted without problems. But one hour after I tried to reboot the phone manually and then the problem appeared.
My phone is working now but I don't know how to make this permanent. Do you have any idea?
Ps: attached screenshot of my current build
Thanks again!
Click to expand...
Click to collapse
Did you have a custom Rom before? I am wondering - normally the Model number shows Huawei GRA-L09 or GRA-UL00 and not GRACE. Grace is both http://consumer.huawei.com/tz/support/products/technicalspecs/grace-tz.htm?utm_source=Viber&utm_medium=Chat&utm_campaign=Private
So, which Model do you have? Please tell me.
You said you did it step by step with my instruction. I wrote several times to make a Backup of system, data and boot with TWRP. You had TWRP, otherwise you could not flash SuperSU. If the phone got a problem you could boot it to TWRP by holding vol+ and power key and restore the backup. No need to flash again the firmware. Didn't you make a TWRP Nandroid Backup?
The other thing I cannot understand is - normally it is absolutely necessary to flash back the Original Stock Recovery before doing any stock firmware update with dload. And it is also important to unroot. I am wondering if this was successful...
Which Rom (version) did you have before? Was your phone rooted before b370? Did you unroot before upgrade to this version? Did you make a full Wipe before upgrading or a factory reset? If you use b370 your model must be GRA-L09. Because the other models have not this version yet. (if my information is right)
I don't think the problem is the Root Method A.
If your Model is really a GRA-L09 I would recommend Root Method B or C with the custom Kernel. But if you use at the moment a Custom Rom instead of the stock firmware there would no need to root because having already root.
Something in the story is not conform but I need more information to get an idea what is the specific problem. Because I tested all three Versions without any problem...

No, I did not have a custom ROM. The GRACE model appeared as soon as I updated with an official B370 Europe. In fact I have my bootloader unlocked and I had to use this Model Name to get the unlock code from Huawei. Before doing the update I had GRA-L09.
Yes, I have a TWRP backup, I made it before rooting but I didn't use it because the only way to power on the device was either bootloader or recovery (Vol- & Power / Vol+ & Power)
When I tried recovery, Huawei's recovery appeared taking my update.app on /dload (didn't have any other option at that moment, the process started automatically). I didn't lose any data, the phone after the update started normally with all my settings exactly as it was before rooting, but this time SuperSU says the phone needs to be rooted.
For some reason TWRP is not installed anymore. If I try now, the Huawei Recovery starts. I currently have B370 same as before rooting. No full wipe before upgrading neither a factory reset.
I read that Huawei Stock recovery can rewrite your custom recovery, is that possible?
J.

Of course. After flashing the Recovery you must disconnect the USB cable from Phone and PC and boot manually with vol+ and power until you see the Huawei Logo. In that moment you must leave the power button but holding vol+ until the TWRP starts. This need a while. If you don't do this, Stock Recovery will be reflashed. Only the first boot to Twrp is important. After that TWRP will not be overwritten anymore. I am wondering about Model "Grace" I had b321a before and make the update with full firmware - after it shows me also GRA-L09 and not GRACE... Anyway. Sometimes things are strange. Okay. You must flash TWRP again and immediately after successful flashing manually boot to Twrp - but disconnect from PC!
Before all doing this be sure you have the Custom Kernel and SuperSU 2.76 on your SD. Flash first the Kernel and after SuperSU 2.76 - if you want systemless then with Force systemless Command before, if you want Root in System then without this command. And you will be happy and no more having problems with Root

The problem was, that you did not manually reboot to Twrp after flashing

@juanzete - Did you solve your problems now and Root is succesful? @lordcookies Did you try one of the root method for your GRA-UL00?

Tanks
Tanks a lot.It worked for me.(GRA-UL10):good:
---------- Post added at 09:33 AM ---------- Previous post was at 09:08 AM ----------
lordcookies said:
Will this work on GRA-UL10?
Thanks a lot.
Click to expand...
Click to collapse
Yes It Works.

SMhd3000 said:
Tanks a lot.It worked for me.(GRA-UL10):good:
---------- Post added at 09:33 AM ---------- Previous post was at 09:08 AM ----------
Yes It Works.
Click to expand...
Click to collapse
Which one of the three Root method did you use? I would like to know, thanks

GRA-L09, method 3 works but root isn't systemless. I am trying to install systemless xposed but it fails because of system mode root... Any ideas?
Before you ask:
I flashed the custom kernel properly
/data/.supersu is present and contains SYSTEMLESS=true
I said NO to TWRP root offer

AD2076 said:
GRA-L09, method 3 works but root isn't systemless. I am trying to install systemless xposed but it fails because of system mode root... Any ideas?
Before you ask:
I flashed the custom kernel properly
/data/.supersu is present and contains SYSTEMLESS=true
I said NO to TWRP root offer
Click to expand...
Click to collapse
Hi, I made a new Kernel specifically for SuperSU 2.78 - you can download it: https://www.androidfilehost.com/?w=files&flid=109256
Before you try method 3 with the new Kernel and the Original SuperSU 2.78: https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip - you must Unroot your Phone and after install again. It should work.
I tested method 3 several times without any problems.

Tecalote said:
Hi, I made a new Kernel specifically for SuperSU 2.78 - you can download it: https://www.androidfilehost.com/?w=files&flid=109256
Before you try method 3 with the new Kernel and the Original SuperSU 2.78: https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip - you must Unroot your Phone and after install again. It should work.
I tested method 3 several times without any problems.
Click to expand...
Click to collapse
I am gonna try it. Of course I unrooted before trying.
The big problem is I have to completely unroot at every reboot if I wanna play that throw a ball to the monster game
On another device I have systemless root + systemless xposed + suhide and I can play with no problems.
Does this kernel have adb enabled?

AD2076 said:
I am gonna try it. Of course I unrooted before trying.
The big problem is I have to completely unroot at every reboot if I wanna play that throw a ball to the monster game
On another device I have systemless root + systemless xposed + suhide and I can play with no problems.
Does this kernel have adb enabled?
Click to expand...
Click to collapse
If you have then succesful rooted and Xposed Framework installed you can try Module RootCloak

Tecalote said:
If you have then succesful rooted and Xposed Framework installed you can try Module RootCloak
Click to expand...
Click to collapse
RootCloack doesn't bypass SafetyNet check, suhide does.
I can root successfully but there are problems because the root isn't really systemless and SafetyNet detects it even with suhide.
Furthermore systemless xposed fails to install and complains about the supersu version < 2.76.
Of course I used 2.78
Btw your kernel works but required some reboots to work properly. At first boot SIM was not detected and the system was very very laggy.
I am available for more testing

Which Firmware to you use? I have tested it on b370, but with SuperSU 2.76- I will try it again in the evening with 2.78
I cannot understand yet, why it dont root systemless with method 3.
And RootCloack is available also with Support MM (new version) - do you mean, this dont hide root for your game? I write again, as soon I have time solving your issue.

Tecalote said:
Which Firmware to you use? I have tested it on b370, but with SuperSU 2.76- I will try it again in the evening with 2.78
I cannot understand yet, why it dont root systemless with method 3.
And RootCloack is available also with Support MM (new version) - do you mean, this dont hide root for your game? I write again, as soon I have time solving your issue.
Click to expand...
Click to collapse
I use B370 FF Edition from Blackball.
I just noticed I have an old twrp version: 2.8.7.0 by Jemmini. I am gonna upgrade and see if suhide works, it requires twrp > 3

B370 FF Edition is prerooted in Systemmode. I think, thats why the SuperSU Installer ignore perhaps the systemless command.
Dont know if there is a way to do it. May you ask Fromfuture in his Thread.
Or you install the Original Stock Version b370.

I used the completely unroot option in supersu before rooting systemless

[GUIDE] OTA updates with Magisk

If you have managed to root your phone with Magisk, getting updates after that for the stock ROM isn't always a smooth thing. Here are some steps to be successful with updates.
1. Open Magisk Manager and disable all installed modules by unchecking the circle for each.
{
"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"
}
Please note that steps 2-4 can be done with the stock 1+ updater so long as it senses that you are rooted and offers to download a full rom. So a note about magisk hide which is used to hide root. Make sure you haven't managed to hide root for any process related to the 1+updater or it won't know you are rooted and will offer incremental updates.
2. Install Oxygen Updater (This app may become abandoned in 2019 requiring the use of the stock updater which is slower or manually downloading roms.) https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
3. Open the app, verify that your device is identified correctly. Open it's settings and set Update Method to "Full Update"
4. Check for an update and download it. Make sure you end up with a full 2GB ROM image not an incremental small one. It will be in the root of internal storage.
DO NOT use Oxygen Updater to update the phone (unless you have TWRP and that is for a different GUIDE)
5. Open the built in OnePlus updater: Settings - System - System Updates - Gear - Local Upgrade and select the newly downloaded update. TAKE NOTE while it is installing which slot it is installing too. It will say something like "inactive slot a". Remember this as it is the "new" slot.
6. After it has installed DO NOT reboot the phone or you will lose root. Open Magisk Manager and install Magisk, even though it says "installed". Select the option when it prompts for "after OTA". This will install magisk in the boot partition of the new slot.
7. Reboot and If all went well you shouldn't boot loop and you'll be running the new slot. If you want TWRP (optional), install the zip now from Magisk->Modules->+ (sign) then select the TWRP zip file and install it. Do NOT reboot. Then do a "Direct Install" of Magisk again, then reboot.
8. Open Magisk Manager and go to the downloads section and reinstall the modules you want to use. Do this from the Downloads screen or using the + button on the Modules screen. This will install them in the current slot.
DO NOT simply reenable the modules with the check mark or you will boot loop. Some modules aren't listed in Magisk and can't be automatically moved from slot to slot. If you installed one of those previously, you must reinstall it with the plus button manually from the modules tab.
You should be done now.
Oh no I'm boot looping: Don't panic.
1. Make sure you have adb/fastboot 1.4.3 or newer on a PC https://forum.xda-developers.com/showthread.php?t=2317790
2. Boot the phone into Bootloader/fastboot either through the recovery menu or VolDn + Pwr
3. If in step 5 above the inactive slot was "a", issue the command from a PC command prompt:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
If you are not sure which to use try one or fastboot getvar current-slot
4. Then: fastboot reboot
This will allow the phone to boot into the last good ROM version. Now you figure out what went wrong.
Another option If your phone didn't retain root, you can stay in the unrooted slot. download a rooted boot image of your firmware version, place it in the your fastboot pc directory, reboot the phone to fastboot and issue the command: fastboot boot boot.img (or whatever the downloaded image is called.) this is a temporary root that is non destructive. Then do a direct install from Magisk manager even though it already says installed. That will permanently root your boot copy. Then install your modules.
Here is the 9.5.11 1917AA rooted boot image https://www.dropbox.com/s/6csxd9zaa4mihwk/boot_a_backup_2019-08-04_19-05-29.img?dl=0
If your phone looped right after flashing, you may not have disabled Magisk modules properly. You can still disable them from the good slot, swap active slots again using fastboot and see if it boots into the new ROM. If not, swap back to the good old slot again and start over flashing again from the beginning.
If you looped after reenabling your modules, it is possible you only enabled one but didn't install it into the new slot. Again swap back to the good slot and disable the modules. Swap back to the new slot and install the modules again even if Magisk thinks they are there.
If all else fails, you can stay in the good old slot until you sort things. If you are looping in both slots then something really went bad and you have to flash back a full ROM from fastboot. See this thread
https://buzzfire.de/xda/t3931424
Then root again using the rooted boot image above.
You may be able to boot into the old rooted slot and root the new slot with the ota option also.
If you have issues where stuff like Wifi doesn't work, then somewhere along the line or previously you flashed a (boot) image that didn't match the /system image in the slot you were working on. This error will persist in that slot every time you use that slot until it gets a fixed set of images.
Hope this helps!

I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.

If you are on bootloop, just simply flash magisk_uninstaller.zip on twrp
boot into system > then flash magisk on twrp again.

Perfect manual and working great

gtelnet said:
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
Click to expand...
Click to collapse
You Sir are the good damn man i have spent 3hrs trying to update to 9.5.9 cheers boss!!

Will this method work if I was a TMobile OnePlus 7pro which converted to international running 9.5.8 currently?

Yes if you are offered the aa rom in the updater

@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339

I just start the update under settings, system, syst update
It found new update and tell me he need to download full ROM (I have rmagisk installed).
While it was downloading full ROM I uninstall magisk from magisk app.
After update finish before restart I installed magisk again (option after ota update) and restart.
Now I'm updated and with magisk installed
Inviato dal mio GM1913 utilizzando Tapatalk

SlyUK said:
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
Click to expand...
Click to collapse
Yes I'm thinking, In the worst case it may be possible to use the stock updater as it senses root and downloads the full update now. Simply substitute the step where oxygen updater is used to download with the stock updater.
There may be a slightly longer delay before the stock updater offers an update as 1+ does it in waves. I have to hand it to 1+for even offering updates as most phones won't.

hi experts,
what and where to set or unset to make sure there is NO auto OTA update?
How do I control the update time on my op7p?
I'd like to avoid surprise of getting update in background that would / can remove root, magisk and etc that were manually added?
as example I use xXx over magisk and I's like to be prepared ahead of time to apply the OTA update
thanks for the education.

The 1+ updater has a setting to auto download updates or not. You can change it.

If we have TWRP installed could we get a guide for using the updater app?

kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
This is the method i use. Screenshot it from a thread here on XDA and unfortunately cannot remember the posters name to give credit. But it is the job!

kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Disable all Magisk modules and substratum themes
3.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App (OTA Option) **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx

i.Design said:
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
3.) Disable all Magisk modules and substratum themes
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
Click to expand...
Click to collapse
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10

Pvt WhoOkid said:
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Click to expand...
Click to collapse
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
I had issues of bootloop where I would get past the unlocked message and boot up animation but then would freeze with my background showing only (no launcher, no status bar, etc).

i.Design said:
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
Click to expand...
Click to collapse
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.

Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
I was running Riru Core, edXposed and ended up dropping both, it wasn't worth the hassle for me since I run Renovate Ice and it does most of the tweaks I want from GravityBox (reason I was running Xposed).

Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
Try disabling all the modules and see if you can boot into 9.5.10 slot. If it does, reinstall them (then reenable them)

[GUIDE] Pixel 4 "flame": Unlock Bootloader, Update, Root, Pass SafetyNet

If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 3aXL
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"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"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!

@V0latyle The Pixel phone I'm rooting belongs to a friend who wants it rooted. Prior to doing anything (thankfully!), I established that the phone is actually a Pixel 4, not a 4a.
I downloaded the correct stock image for that model and then followed all your instructions. This included updating the bootloader and radio from the factory stock zip before flashing the Magisk-patched boot image.
Everything went well and the phone is now rooted with your recommended Magisk modules to pass SafetyNet. However, the wifi no longer works on the phone. I don't have his sim to test if mobile signal/data works. Thinking the problem might be the new radio, I found and reflashed the oId radio image but no joy.
What steps do I need to take to resolve the situation and get wifi working again?
Thanks for your help.
UPDATE: I've managed to restore the phone back to stock firmware (Mar 22 flame for Pixel 4 - the version it was given to me in) ang got the wifi working again. The bootloader is still unlocked. I cannot figure out what I did in the rooting process that affected the functioning of the wifi

largeruk said:
@V0latyle The Pixel phone I'm rooting belongs to a friend who wants it rooted. Prior to doing anything (thankfully!), I established that the phone is actually a Pixel 4, not a 4a.
I downloaded the correct stock image for that model and then followed all your instructions. This included updating the bootloader and radio from the factory stock zip before flashing the Magisk-patched boot image.
Everything went well and the phone is now rooted with your recommended Magisk modules to pass SafetyNet. However, the wifi no longer works on the phone. I don't have his sim to test if mobile signal/data works. Thinking the problem might be the new radio, I found and reflashed the oId radio image but no joy.
What steps do I need to take to resolve the situation and get wifi working again?
Thanks for your help.
UPDATE: I've managed to restore the phone back to stock firmware (Mar 22 flame for Pixel 4 - the version it was given to me in) ang got the wifi working again. The bootloader is still unlocked. I cannot figure out what I did in the rooting process that affected the functioning of the wifi
Click to expand...
Click to collapse
I had your post moved to this thread to keep the other one on topic.
I don't think there's anything you could have possibly done during the flashing or patching process to cause WiFi to stop working. Try again using the latest update; make absolutely sure it's for "flame", no other version.

Dear
V0latyle​Will the magisk posted here and process work on latest Android 13 build ?
Many Thanks

zerodi said:
Dear
V0latyle​Will the magisk posted here and process work on latest Android 13 build ?
Many Thanks
Click to expand...
Click to collapse
Rooting Android 13 works exactly the same way as Android 12 and 11. Just make sure you're using the latest Magisk release, which should be 25.3.

V0latyle said:
Rooting Android 13 works exactly the same way as Android 12 and 11. Just make sure you're using the latest Magisk release, which should be 25.3.
Click to expand...
Click to collapse
excellent many thanks

[ROM][UNOFFICIAL][2022 MODEL] LineageOS 20.0 for Galaxy Tab S6 Lite 2022 (Qualcomm)

{
"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"
}
Disclaimer:
I'm not responsible of any damage made to your device by installing this ROM
Following the installation process will trip Knox, thus your device warranty may be void.​
Click to expand...
Click to collapse
What's working?
- Audio
- Bluetooth
- LTE
- Display
- WiFi
- Charging
- Location
- Encryption
- Camera
- S-pen
- Enforcing SELinux
What's not working?
- You tell me
Installation instructions​
Spoiler: Installation instructions
Installation requirements
- A computer
- ADB installed on the computer, you can find a guide here
- Odin (v3.14.1 is verified to work fine), you can find it here
- A decent battery level on the device
Step 1 - Unlocking the bootloader
You may skip this section if you have already unlocked your device
- Enable developer options
- In developer options, toggle the "Allow OEM unlocking" setting
- Reboot into download mode following the instructions below
- Once into download, long press the volume up button and follow the instructions on the screen
- After the bootloader is unlocked, your data will be erased, so make sure to back it up first.
- Now, once the system has finished booting, you MUST connect to a WiFi network, enable developer options again, and make sure that the OEM unlocking toggle is on and grayed out. If you do not see the toggle on the developer settings, close the settings and try again a few times.
- Once you see the toggle greyed out, all is set.
Step 2 - Installing the LineageOS recovery
In order to flash the ROM, you need a custom recovery, which you can find on the downloads section.
For installing the recovery:
- Boot into download mode as described below
- Press the volume up button a single time to fully enter download mode
- Connect your device to your computer
- Once you are in download mode, open Odin and make sure that it detects your device
- Go to options on Odin, and disable auto-reboot (DO NOT ENABLE ANY OPTIONS OTHER THAN F. Reset Time and Auto-Reboot)
- Download the vbmeta.tar file from the downloads section
- Select on the "Ap" button the vbmeta.tar file and then click "Start"
- Download the recovery.tar file from the downloads section
- Select on the "Ap" button the recovery.tar file and then click "Start"
If Odin gets stuck (specially when flashing recovery.tar), you might try the following:
- After you flash vbmeta, reboot into download again, and directly flash the recovery (once you have flashed the vbmeta once you shouldn't need to flash it again)
- Try a different PC or USB cable
- Try a different version of Odin
Click to expand...
Click to collapse
- Once the flashing completes, power off your device by pressing power + volume down, and after the screen turns off, quickly press the key combination for booting into recovery
- If everything went fine, you should be now on the LineageOS recovery
Warning: if you boot into the OneUI again, it will overwrite the custom recovery and you'll need to install it again!
Step 3 - Installing the ROM
- Download the ROM from the downloads section (make sure you download the .zip file and not the .sha256sum file)
- Once in recovery, go to the "Apply update" section, and click "ADB sideload"
- Connect your device to the computer, and sideload the update with adb sideload path/to/file
An example of the command on Windows can be adb sideload C:\Users\myuser\Downloads\lineage-20.0-20230223-unofficial-gta4xlveu.zip
Click to expand...
Click to collapse
- Your device should start verifying and installing the update
- After the installation has finished, you need to format the data partition (Factory reset -> Format data/factory reset)
- Now, click "Reboot to system"
- If everything went correctly, you should be booting LineageOS
​How to boot into recovery/download modes:​
Spoiler: Booting into recovery/download
Download
- For booting into download, you will have to press at the same time the power and the two volume buttons until the "Download" screen shows up.
- If you want to boot into download with the device powered on, you have to press the reboot option and right after that, press the key combination as mentioned above.
Recovery
- First, make sure to connect the device to a computer, otherwise the tablet won't allow you to boot into recovery (it's a Samsung restriction).
- For booting into recovery, just press the power and volume up buttons. Once the Samsung logo / bootloader unlocked warning has appeared, you can release the buttons and press the power button to skip the warning screen.
- Just like with the download mode, if you want to boot into recovery with the device powered on you just have to press the keys right after pressing the reboot button.
Downloads​All files (ROM, recovery and vbmeta) are available at https://files.danielml.dev/android/gta4xlveu/.
Both models (WiFi and LTE) are compatible with the same ROM zip (gta4xlveu).
Help and support​Join the Telegram group for getting support
Other details:
Kernel source: https://github.com/gta4xlve-dev/android_kernel_samsung_gta4xlve
Device source: https://github.com/gta4xlve-dev/android_device_samsung_gta4xlveu

Reserved

Thank you very much, i will test it next week.

Testing out the new ROM, glad to see one for the Qualcomm 2022 version.
Battery stats works
Camera works
Using lawnchair 2 and it works! Pixel keeps crashing (?)
Thanks!

K9droid56 said:
Testing out the new ROM, glad to see one for the Qualcomm 2022 version.
Battery stats works
Camera works
Using lawnchair 2 and it works! Pixel keeps crashing (?)
Thanks!
Click to expand...
Click to collapse
Glad to see that you liked the ROM.
Here Pixel launcher works, not sure why it doesn't there.
Anyways, I'll remove GApps by default on future builds so the Pixel launcher won't be present. (Of course, you'll be able to install a custom GApps package).

Thank you! Also started to test now. I disabled most of google app from the start and went fdroid/aurora way (waiting with anticipation for no google version). Nothing crashed yet.

btw, how to root this image? is patching boot.img and replacing it in zip and then flashing as above enough, or is there any changes required for vbmeta?

bugit said:
btw, how to root this image? is patching boot.img and replacing it in zip and then flashing as above enough, or is there any changes required for vbmeta?
Click to expand...
Click to collapse
Well, I didn't try, but just flashing Magisk *should* be enough.

daniml3 said:
Well, I didn't try, but just flashing Magisk *should* be enough
Click to expand...
Click to collapse
unfortunately this method does not work: during sideload it fails with `Unable to repack boot image` and recovery logs are somehow empty, but still managed to boots after this error
i will try with patching boot.img when i will have more time

ok, i managed to flash image with patched boot.img (extract zip, uload boot.img to device, patch with magisk, download patched boot.img, remake zip image),
but just flashing patched image from recovery made my existing system unbootable
and i had to reflash stock firmware and then repeat flashing steps from scratch
(flash vbmeta/recovery, and then flash patched image),
with this the device is booting and root is working
notes:
- the unbootable state from above was device going into black screen just after samsung logo, with no hints of activity (10 min was max i waited)
- only pressing all tree keys (power, volume up and down) made it reboot with about one second of turn off state (so one can't actually power off the device, it just boots up again into black screen after logo)
- after reboot i was not able to enter recovery or download mode by just pressing known combinations of buttons, and the only way to enter download mode was: during this 1 second power off state to press volume up and down keys and connect usb cable (spend some time finding this solution)
- during flashings after uploading vbmeta i could not flash recovery right after vbmeta (it gets stuck during upload) and i had to reboot again into download mode and then flash recovery (this happened both during my first try to install this image, and with the patched image)
- for some reason in this image i have two sets of navigation buttons at the bottom of the screen (the triangle, circle and square buttons), one is standard android set and one compressed to the right side of nav.bar; stopping pixel launcher removes the compressed one, but the square button (task switching) stops working
- after installing patched image i also noticed (in hindsight) that actually during first install the scroll was very choppy (and the system was kind of slow), but in second install this problem went away

Thanks a lot for the ROM. The following steps for rooting lead to success for me:
1. flashing according to the instructions as described by daniml3.
2. copy Magisk 25.2 to the external SDCARD and rename to .zip
3. reboot in recovery
4. factory reset -> format data/factory reset
4. do not boot, but install Magisk from tablet via ADB from SDCARD
5. reboot
6. rename magisk to .apk again and install the app
7. set up Magisk
8. after reboot be sure to complete ANDROID setup
It rocks!
The navigation buttons are also duplicated for me.
I hope I could help.
I wish a LineageOS without Google.

Thanks everyone for the feedback! There are a few notes:
- I'll release a version without Google Apps as soon as possible (most likely this weekend).
- The lag when booting is caused due to some overlay issue, I still have to look into it, but as it doesn't affect much to the functionality after a few seconds its not a "priority".
- The duplicated navigation buttons are actually an issue from the Google Apps (maybe the Pixel Launcher?). This will be fixed with the Google app-less version of the ROM. If you switch to gesture navigation this issue dissapears.

Is there a possibility for SM-P619 LTE version?

Razor64 said:
Is there a possibility for SM-P619 LTE version?
Click to expand...
Click to collapse
As I said on the post, if you have the LTE model, and want to try a build, just let me know (preferably by Telegram).

Uninstalling the pixel launcher via adb removes the extra icons.
Small lag at start-up but other wise a smooth-running rom.
Thanks!

Today (if everything goes as planned) I'll publish a new update for the WiFi-only model, including:
- Enforcing SELinux
- Removed GMS by default (you can install them as a separate package, personally BitGapps worked perfectly)
- Fixed some background services crashing
This will probably be the last update in a (few) week(s), as I'm working on an source-built-vendor device tree, which may take some time.
I'm also working on a build for the LTE variant, which will be published as soon as I verify that it works correctly.

At the moment I am not at home. After my short vacation I am looking forward to try it at the end of the week.
Many thanks for your work.

A new update for the SM-P613 (gta4xlvewifi) was published just now with the following changes:
- Enforcing SELinux
- Removed GMS by default (you can install them as a separate package, personally BitGapps worked perfectly)
- Fixed some background services crashing
Download it at https://sourceforge.net/projects/gta4xlve-dev/files/gta4xlvewifi/lineage-20.0/
Warning: If you used GMS, you'll need to manually install them (I use BitGapps and they work correctly).

Latest update runs really smooth with bitgapps. Lawnchair works with no problems. Thanks again for this ROM!

Bit of a stretch to ask, but would it be possible for the build to identify itself as a tablet, rather than a phone? And the possibility of defaulting the orientation to landscape? (90 degree rotation as default rather than 0)