Database Users

[Guide] Unlock, Root & Update Huawei Mate 8 L-29 (all files and Howto Video)

[Howto Video]
https://www.youtube.com/watch?v=LDdV2OMaXPI&feature=youtu.be
WORKS WITH HUAWEI MATE 8-L29.
Step One things you need:
DC-Unlucker Client
Device Driver (Install Huawei HiSuite or use Driver in the Package)
TWRP (recovery.img)
BETA-SuperSU-v2.67
ADB AND FASTBOOT
NXT-L29C900B162
Download the complete Package:
https://drive.google.com/open?id=0B0tMO0kNwZpvZ0phU3F2clZLVWc
Step two:
Copy the NXT_C900B162.zip and the BETA-SuperSU-v2.67.zip on your SD CARD!
Install your Drivers ( or Hisuite)
Install ADB & FASTBOOT!
After installing ADB move the file 'recovery.img' in the minimal adb fastboot folder.
Open the DC Unlucker.exe
Select "HUAWEI PHONES"
Take your phone and dial "*#*#2846579#*#*"
Select these:
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Connect your Phone
Let em search ur phone (magnifier)
BUY 4 Credits on this Site: (https://www.dc-unlocker.com/buy)
Back to the Unlocker client after you buyd the credits
Connect to server with the Username you choosed and the password from Mail.
If you are connectect click Unlocker
= choose the "Read Bootloader Code" to get the code you need to unlock the bootloader. NOTE THE CODE.
Boot the Mate 8 in bootloader mode
Turn off phone
Press Volume down
and insert USB CABLE.
Start Minimal ADB & FASTBOOT.
Check your Phone with "fastboot devices" if its there go on. IF NOT = CHECK DRIVERS!!
next command you need:
"fastboot oem unlock XXXXXXXXXXXX"
XXXX is your Bootloader Code.
/done. Start your Phone.
*Step Three Enable USB debugging on your device:
Open Settings on your device.
Go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and you’ll see “Developer options” there, open it.
Connect your Phone
Tick the USB Debugging checkbox.
Open minimsl adb fastboot again
Connect your device to the in Fastbootmode again and the command u need is:
fastboot devices is your phone there, go on!
fastboot flash recovery recovery.img
next command should be
fastboot reboot
YOU HAVE NOW TWRP
LAST AND IMPORTANT STEPS:
Start TWRP (Turn Phone off, press volume Up and Power button till your phone starts - release power button but still hold volume up)
now you click "Format Data" (ALL YOUR DATA WILL BE DELETE!!!)
Confirm with typing YES
Swipe to format data
go back click "INSTALL" select the SD CARD and then "NXT_C900B162.zip"
Swipe to install again.
DONT REBOOT! Go back!
Click "Install" again
SELECT "BETA-SuperSU-v2.67.zip"
Swipe again.
after installing SuperSu your phone is rooted and ready for a reboot.
If you want TWRP Recovery you have to flash Recovery again via Fastboot. (marked with a *)

question and answers faq

good job there, im sure this will be helpful for new users

After unlocking bootloader how to remove the new boot screen thas sayes your phone is not trusted?

rowihel2012 said:
After unlocking bootloader how to remove the new boot screen thas sayes your phone is not trusted?
Click to expand...
Click to collapse
Atm there is no Option for this. You can only press the PowerButton one time then he loads faster.
But i dont know a Option to remove this. Sorry

maybe future custom roms will include the removal of that screen, it is indeed somewhat annoying

jbmc83 said:
maybe future custom roms will include the removal of that screen, it is indeed somewhat annoying
Click to expand...
Click to collapse
That screen cant be removed its in the bootloader. The nexus 5x and 6p also have it.

I'll make that decrypted boot.img into a flashable TWRP zip file tonight so you can just flash it in TWRP instead of having to use Fastboot.

ajsmsg78 said:
I'll make that decrypted boot.img into a flashable TWRP zip file tonight so you can just flash it in TWRP instead of having to use Fastboot.
Click to expand...
Click to collapse
go back click "INSTALL" select the C00B129SP02 decrypted boot imgzip"
its already in a zip for TWRP. if you read the instruction i said try it with TWRP . But for me it dosnt worked - my way was the fastboot way

EGOiST1991 said:
go back click "INSTALL" select the C00B129SP02 decrypted boot imgzip"
its already in a zip for TWRP. if you read the instruction i said try it with TWRP . But for me it dosnt worked - my way was the fastboot way
Click to expand...
Click to collapse
I'll check it out tonight and try and get it working Thanks.

Thanx guys. Will try when I get my mate8...
BTW boot.img does not download for some reason...

try with a mobile browser
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk

icy20 said:
Thanx guys. Will try when I get my mate8...
BTW boot.img does not download for some reason...
Click to expand...
Click to collapse
Yeah, thats right you have to download with mobilephone (chrome works for me).
If someone can upload it anywhere?! That would be nice. I can send the boot.img for upload - googledrive for example - i dont have this ****

i dont understand why it only works via a mobile browser, hm.... especially since im using the share links provided on my laptop

ajsmsg78 said:
I'll make that decrypted boot.img into a flashable TWRP zip file tonight so you can just flash it in TWRP instead of having to use Fastboot.
Click to expand...
Click to collapse
I did not flash this boot why i should flash it ???

well if u didnt need it then dont worry about it

I unlocked the mate 8 bootloader with the old way like mate 7 and p8max
With facebook account

I know this guide was made for the L29 version so does anyone know if its OK to flash decrypted boot image on the AL10 model

jjerickson19 said:
I know this guide was made for the L29 version so does anyone know if its OK to flash decrypted boot image on the AL10 model
Click to expand...
Click to collapse
Yes jbmc83 flashed it on AL10.
Wait for his confirmation but im sure he have the same boot image likr me.
Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk

What's that method plz
Sent from my HUAWEI NXT-AL10 using Tapatalk

[Guide] (2017.12.07update) How to root ur Mate9 oreo (emui 8.0)

First of all, sorry for my awesome English.i am praticing my writing
if u understand Chinese,congratulations!these is the Chinese version:
Notice:
A. Warning! Flash phone might get it bricked. I am not responsible for it.
B. Phone is already Oreo firmware.
C. i cant guarantee these is no needless steps , but at least , i execute the steps from a to m, and i succeed to root my mate9 oreo {MHA-AL00 8.0.0.334(C00)}
-----------------------2017.12.07 update---------------------------
sorry for so many needless steps of the old method.
root mate9 emui8 now only need 2 steps (so please neglect the old method).
new method:
1. reboot to fastboot mode . and fastboot flash recovery_ramdisk this
2. reboot to recovery mode. flash supersu 2.82 sr5 mod. (download link)
done!
ps: i have compared the "supersu 2.82 sr5 mod" to official supersu 2.82 sr5
the only different is:
the 683th line of file: "/META-INF/com/google/android/update-binary"
official package is : TRY="boot_a BOOT_A $TRY"
and the mod package is: TRY="ramdisk_a RAMDISK_A $TRY"
so the the mod package can be trusted i think.
that's all !
as the Chinese popular saying goes： 无图无真相！( no pictures! no truths ! )
but i dont know how to upload my picture, imgur?tumblr? anybody teach me?
HOPE THE ABOVE IS CLEAR.
GOOD LUCK
----------------------------------------------------------------
old method ( too many needless steps, please read the new method!):
Prepare:
1. FunkyHuawei Mate 10 Root/Rebranding tool (find lastest release here)
2. TWRP 3.1.1-0 for Mate 9/EMUI 8 (click me)
3. HWOTA8 Package ( get it from this post)
4、update_data_public.zip & update_all_hw.zip for the corresponding version you need (mine is MHA-AL00 8.0.0.334(C00), you can find wat u need at here)
5、supersu 2.82 SR5 (donwload link ,we only need the superuser.apk in /common.)
steps:
a. Unlock bootloader (backup all the data you need before this step)
b. Decompress the HWOTA8 Package on ur PC.
c. Copy the TWRP 3.1.1-0 to this folder (created by Decompression ),and rename this recovery img file (TWRP 3.1.1-0) to "TWRP8_3.0.3.img"
d. Connect ur mate9 to PC by USB cable and Use Vol-Dn +Power to boot into fastboot mode.
e. Use "Replace_Recovery.bat" in the folder (created by Decompression ) to flash TWRP recovery
f. Disconnect USB cable, use Vol-Up + Power to boot into TWRP
g. Format Data in TWRP, and connect USB cable again.
h. Reboot into fastboot mode .
i. Decompress FunkyHuawei Mate 10 Root/Rebranding tool Package on ur PC.
j. Run the "FHMate10Tool.exe" and choose Option 1 to root. and it will reboot later
k. Phone reboot ---> appare the warming interface ( it said:your device has been unlocked and cant trusted blablalba..... ) ---> appare the huawei welcoming interface -----> suddenly, phone reboot. notice!: please keep USB cable disconnecting from ur Phone. and after phone reboot suddenly , keep holding the Power + Vol up as fast as u can to reboot to recovery mode. (ps: why do we hold the keys as fast as u can? because it will prevent ur rebooting phone enter the huawei welcoming interface again. if the huawei welcoming interface appearing we cant execute the step l following)
l. flash the update_data_public.zip & update_all_hw.zip in TWRP. and reboot to system .
m. if supersu is not installed, please install supersu 2.82 SR5 manually.
the step k & l is not necessary,but recommended. because if you neglect them, u cant use the Theme( i am sure) and other.... important things (maybe) .

thanks very much!!!!!!

OP, How did u upgrade to oreo? I also have an AL00

Astra1 said:
OP, How did u upgrade to oreo? I also have an AL00
Click to expand...
Click to collapse
there are two posts told me how to update mate9 from nougat to oreo
1. https://romprovider.com/2017/11/update-emui-8-0-huawei-mate-9/
2. https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
notice:
a. the part of post 1 --"2.1 Method 1 using HWOTA Tool–" works on my mate9 Android N (emui 5.0) .
b. the part of post 2 --"Downgrade Nougat" works on my mate9, i succeed to downgrade to Nougat emui5.0 MHA-AL00C00B233.
c. the attachment of the post 1 seem to be designed to work on mate9 pro(because of the "LON") , so i modified the package to fit mate9. i don't know if it's neccessary.
i have wrote a guide，but it's in Chinese . 2rd floor (2#) of this post
Good Luck！

abbyvictor said:
First of all, sorry for my awesome English.i am praticing my writing
if u understand Chinese,congratulations!these is the Chinese version:
Notice:
A. Warning! Flash phone might get it bricked. I am not responsible for it.
B. Phone is already Oreo firmware.
C. i cant guarantee these is no needless steps , but at least , i execute the steps from a to m, and i succeed to root my mate9 oreo {MHA-AL00 8.0.0.334(C00)}
Prepare:
1. FunkyHuawei Mate 10 Root/Rebranding tool (find lastest release here)
2. TWRP 3.1.1-0 for Mate 9/EMUI 8 (click me)
3. HWOTA8 Package ( get it from this post)
4、update_data_public.zip & update_all_hw.zip for the corresponding version you need (mine is MHA-AL00 8.0.0.334(C00), you can find wat u need at here)
5、supersu 2.82 SR5 (donwload link ,we only need the superuser.apk in /common.)
steps:
a. Unlock bootloader (backup all the data you need before this step)
b. Decompress the HWOTA8 Package on ur PC.
c. Copy the TWRP 3.1.1-0 to this folder (created by Decompression ),and rename this recovery img file (TWRP 3.1.1-0) to "TWRP8_3.0.3.img"
d. Connect ur mate9 to PC by USB cable and Use Vol-Dn +Power to boot into fastboot mode.
e. Use "Replace_Recovery.bat" in the folder (created by Decompression ) to flash TWRP recovery
f. Disconnect USB cable, use Vol-Up + Power to boot into TWRP
g. Format Data in TWRP, and connect USB cable again.
h. Reboot into fastboot mode .
i. Decompress FunkyHuawei Mate 10 Root/Rebranding tool Package on ur PC.
j. Run the "FHMate10Tool.exe" and choose Option 1 to root. and it will reboot later
k. Phone reboot ---> appare the warming interface ( it said:your device has been unlocked and cant trusted blablalba..... ) ---> appare the huawei welcoming interface -----> suddenly, phone reboot. notice!: please keep USB cable disconnecting from ur Phone. and after phone reboot suddenly , keep holding the Power + Vol up as fast as u can to reboot to recovery mode. (ps: why do we hold the keys as fast as u can? because it will prevent ur rebooting phone enter the huawei welcoming interface again. if the huawei welcoming interface appearing we cant execute the step l following)
l. flash the update_data_public.zip & update_all_hw.zip in TWRP. and reboot to system .
m. if supersu is not installed, please install supersu 2.82 SR5 manually.
the step k & l is not necessary,but recommended. because if you neglect them, u cant use the Theme( i am sure) and other.... important things (maybe) .
as the Chinese popular saying goes： 无图无真相！( no pictures! no truths ! )
but i dont know how to upload my picture, imgur?tumblr? anybody teach me?
HOPE THE ABOVE IS CLEAR.
GOOD LUCK
Click to expand...
Click to collapse
how can me update my phone and i on oreo (C185log) i would like move it to (C636)
Sent from my [device_name] using XDA-Developers Legacy app

Maheriraqi said:
how can me update my phone and i on oreo (C185log) i would like move it to (C636)
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
if nougat to oreo ,you should read this: https://romprovider.com/2017/11/upda...huawei-mate-9/
if oreo to higher version oreo OR oreo to nougat , you should read this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
these articles are very helpful!

abbyvictor said:
if nougat to oreo ,you should read this: https://romprovider.com/2017/11/upda...huawei-mate-9/
if oreo to higher version oreo OR oreo to nougat , you should read this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
these articles are very helpful!
Click to expand...
Click to collapse
Thank you, but I need to files twrp and how to install on the oreo 8
Sent from my [device_name] using XDA-Developers Legacy app

Its quite confusing at first. And I manage to make it works after 4 - 7 times repeating the process. To get that themes work. Thanks a lot.
I spend few days figure this out. Thanks!

AlemSalleh said:
Its quite confusing at first. And I manage to make it works after 4 - 7 times repeating the process. To get that themes work. Thanks a lot.
I spend few days figure this out. Thanks!
Click to expand...
Click to collapse
It's my pleasure.
but i found this guide contains many redundant steps
i will simplify it later.....

viper4android for emui 8.0 ?

[No message]

hijibiji said:
viper4android for emui 8.0 ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2191223
no version for Oreo until now as i know

I want to restore my Mate 9 to stock recovery and have used Huawei Update Extractor to extract the Oreo 1.9GB Update.app.
Which of the following files should I use to fastboot flash the stock recovery?
RECOVERY_RAMDIS.img 32MB
RECOVERY_VBMETA.img 6,93kB
RECOVERY_VENDOR.img 16MB

Flavio said:
I want to restore my Mate 9 to stock recovery and have used Huawei Update Extractor to extract the Oreo 1.9GB Update.app.
Which of the following files should I use to fastboot flash the stock recovery?
RECOVERY_RAMDIS.img 32MB
RECOVERY_VBMETA.img 6,93kB
RECOVERY_VENDOR.img 16MB
Click to expand...
Click to collapse
/recovery has a new name "recovery_ramdisk" in mate9 oreo
if you want to flash stock recovery , you should execute " fastboot flash recovery_ramdisk xxxxxxxxxxxxx.img" in fastboot mode.
"RECOVERY_RAMDIS" may be refer to "recovery_ramdisk", so try to execute " fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img" in fastboot mode.
i'm not sure.
gook luck!

NEW!! [ROM-KERNEL-MODS] Last official 9.6.1.0 global stable - antutu 101000

(last update post and files 10-07-2018)
I AM NOT RESPONSIBLE FOR NOTHING
download all requerted files ( without rom and MiFlash_unlocker.exe )
https://drive.google.com/file/d/1Hy6p_6wgEJqQyMlXPFUMcZ63zcBz8ifm/view google drive
hi,
STEP 1
first of all unlock your phone :laugh:
Code:
go options -> about phone -> click 7 times MIUI version and enable developer option
after that join developer option (optons->extra options->developer options)
and enable unlock device Xiaomi
and also usb debugging
********************************************************
HOW TO UNLOCK XIAOMI DEVICE
download Xiaomi unlocker from [COLOR="red"]here[/COLOR]
[url]https://en.miui.com/unlock/[/url]
[url]https://drive.google.com/open?id=1EwjgSU0KVqNjWalRTxyXf-zxmJWwT2G6[/url]
reboot your phone to download mode(push volume down+power button)
unzip download file
and run unlocker.exe
log in with your xiaomi account
connect your phone
request unlock your phone from Xiaomi server
wait 3-5 work days (show you,how hours need to wait)
and run unlocker again
in download mode(push volume down+power button) and unlock your device
**************************************************************************
after all that
STEP 2
install recovery TWRP
Code:
install ADB drivers,download [COLOR="red"]here[/COLOR]
[url]https://drive.google.com/open?id=1yeCfi-VHRj17hUJziWSO-77ssgW8y87m[/url]
(use ONLY win 7 or XP - dont use win 10,8,8.1)
connect your phone with pc and reboot phone to download mode(push volume down+power button)
and run "flash_TWRP.bat" file.download [COLOR="red"]here[/COLOR]
[url]https://drive.google.com/open?id=1rlV_yz0xqb_YgbtJSEhD39ajJFnmZ8w8[/url]
download all files and run flash_TWRP.bat
STEP 3
download rom
Code:
download any last official rom from [COLOR="red"]here[/COLOR] :
[url]https://xiaomifirmware.com/downloads/download-latest-miui-roms-redmi-note-4-mtk//[/url]
"Recovery ROM" ONLY********* NOT "for SP Flash Tool / MiFlash installation"
i use this rom
xiaomi.eu_multi_HMNote4_V9.5.3.0.MBFCNFA_v9-6.0.zip
[url]https://drive.google.com/open?id=1U2bjdh8yfzoH5Fag-zCDbtzMEgg2Cx3J[/url]
new version rom has been released :)
[COLOR="Red"](kernel dont work in 9.6.1.0)[/COLOR]
9.6.1.0 Global Stable Recovery ROM | V9.6.1.0.MBFMIFD [URL="https://xiaomifirmware.com/download/9322/"]download here[/URL]
STEP 4
after download
boot to recoveryTWRP(push volume up+power button)
and install rom
Code:
after install rom
install fix_boot with
FIX_FIRST_BOOT.img download from [COLOR="red"]here[/COLOR]:
[url]https://drive.google.com/file/d/1SGyf3CYJewj0ew7hkexBX2XlDrei1sZi/view?usp=sharing[/url]
first boot need half hour and more
after 40 minutes booting...
give you bootloop..
reboot to recovery (push volume up+power button)
and fix again boot with FIX_FIRST_BOOT.img
join :)
**********************************************************
OK now you have official rom.
*********************************************************
STEP 5
if you like install tools
install tools from recoveryTWRP (push volume up+power button):
root.zip https://drive.google.com/open?id=1zvJMMXAGVUSGs0OBEBojdelZjFIL53Lw only install from TWRP
dolbyatmos.zip https://drive.google.com/open?id=1SSpoH3JDniWb2T9oUesT7aiPwDupg1k3 only install from TWRP
disable boot animation https://drive.google.com/open?id=15QWPNSslmjXsVDxyb3McOMMT9nI7oyWE read .txt file
install tools from XDA Forum - read first original post
GPUmod https://drive.google.com/open?id=1FSlYnURWT1ZJ9SjhkQ4Nxv6NdMAmJ9t0 read original post here
CPUmod https://drive.google.com/open?id=1cv6Z4MMFiRMBGpiafB5CK_LWLhA-HSz9 read original post here
CosmicTweack https://drive.google.com/open?id=1U1iD9YDpl7HhJKZjQJQOY80AGmLBO0vC read original post here
Dualboot https://drive.google.com/open?id=1yQ6b7J6Xc6hpnZHcM1rlW685uPWV1TkB read original post here
Kernel Xtreme97 V2.0 read original post here
install kernel...(dont work in 9.6.10)
Code:
go to developer options and enable USB Debugging and connect your phone with pc
accept to your phone usb debugging request
download the "find device remover" [COLOR="red"]here[/COLOR]
[url]https://drive.google.com/open?id=1gIekgMhjRWPZlX_YYrNBZVrEtzQ7ymdY[/url]
download all files and run remove_mi_find_device_ONLY.bat
[COLOR="Red"]-> AFTER THAT YOU CANT USE FIND DEVICE SERVICE <-[/COLOR]
must delete find_device application (1 app-mi service)
********************************************************
if you dont delete this app
before install kernel,ok but..
give you error after boot
all time-again and again
you cant use the phone
**********************************************************
my opinion-remove all xiaomi apps-run 4 bat files-clean mobile
**********************************************************
reboot to recovery TWRP(push volume up+power button)
and install kernel
download kernel from [COLOR="red"]here[/COLOR]:
[url]https://forum.xda-developers.com/red...ernel-t3625082[/url]
[url]https://drive.google.com/open?id=1MmFKzsIQEWOBnVrtNMxNc2jSrT-vmhHB[/url]
wipe-clear dalvin + cache
reboot to system
SPECTRUM APK FILE [COLOR="Red"]here[/COLOR]
[url]https://drive.google.com/open?id=12RG90ynEsi83jo2HTERYvCvIwDucuft4[/url]
THIS IS IT :good::good:
NOW YOU HAVE EXCELLECT HARDWARE AND SOFTWARE
CREDITS:
ALL TOOLS AND MODS INCLUDED IN XDA FORUM - also thanks Xiaomi
thanks all developers
kisses from Greece
have fun :laugh::laugh:

Redmi Note 4 MTK Nikel-ROM-KERNEL SPECTRUM-TWRP-ROOT SU-ANTUTU 101000-DOLBY ATMOS
(moderetor delete me)

Would it work on a MiuiPro rom? Does it needs a clean installation?

SalPhobos said:
Would it work on a MiuiPro rom? Does it needs a clean installation?
Click to expand...
Click to collapse
to install kernel
dont need clean install
but before install kernel need delete all xiaomi service
all this work 100% with all official roms https://xiaomifirmware.com/downloads/download-latest-miui-roms-redmi-note-4-mtk//
in MiuiPro?i dont know.i havent rom.make backup from twrp and try it. :silly:
https://miuipro.by/

if you like to install kernel...
join options and enable USB Debugging and connect your phone with pc
accept to your phone usb debugging request and after that run "remove_mi_find_device.bat" files (2 files).download here
https://drive.google.com/open?id=1gIekgMhjRWPZlX_YYrNBZVrEtzQ7ymdY
download all files and run .bat (2 files)
-> AFTER THAT YOU CANT USE ANY XIAOMI SERVICE <-
Just one more question, if I run te bat files you provide I eliminate xiaomi services, then I install the kernel and then, should I have to install, again, xiaomi services? If so, where can I find them?
Every time I change my rom, this kernel has to be installed again?
Thanks in advance.

SalPhobos said:
if you like to install kernel...
join options and enable USB Debugging and connect your phone with pc
accept to your phone usb debugging request and after that run "remove_mi_find_device.bat" files (2 files).download here
https://drive.google.com/open?id=1gIekgMhjRWPZlX_YYrNBZVrEtzQ7ymdY
download all files and run .bat (2 files)
-> AFTER THAT YOU CANT USE ANY XIAOMI SERVICE <-
Just one more question, if I run te bat files you provide I eliminate xiaomi services, then I install the kernel and then, should I have to install, again, xiaomi services? If so, where can I find them?
Every time I change my rom, this kernel has to be installed again?
Thanks in advance.
Click to expand...
Click to collapse
if you install rom and kernel
phone give you error.
need delete find_divice application
**************************************
if you like to delete all bloatware run all .bat (3files)
(now have 3 bat files)
if you delete all bloatware you cant install it again.(use play store to download again-maybe)
kernel installed one time.if you change rom need install kernel again

akaluptos21 said:
hi,
first of all unlock your phone :laugh:
join options -> about phone -> click 7 times MIUI version and enable developer option
after that join developer option (optons->extra oprions->developer options)
and enable unlock device Xiaomi
and also usb debugging
********************************************************
HOW TO UNLOCK XIAOMI DEVICE
download Xiaomi unlocker from here
https://en.miui.com/unlock/
https://drive.google.com/open?id=1EwjgSU0KVqNjWalRTxyXf-zxmJWwT2G6
reboot your phone to download mode(push volume down+power button)
unzip download file
and run unlocker.exe
log in with your xiaomi account
connect your phone
request unlock your phone from Xiaomi server
wait 3-5 work days and run unlocker again
in download mode(push volume down+power button) and unlock your device
**************************************************************************
after all that
connect your phone with pc and reboot phone to download mode(push volume down+power button)
and run "flash_TWRP.bat" file.download here
https://drive.google.com/open?id=1rlV_yz0xqb_YgbtJSEhD39ajJFnmZ8w8
download all files and run .bat
download any last official rom from here "Recovery ROM only" not "for SP Flash Tool / MiFlash installation":
https://xiaomifirmware.com/downloads/download-latest-miui-roms-redmi-note-4-mtk//
after download
boot to recovery(push volume up+power button)
and install rom
after install rom
install
FIX_FIRST_BOOT_boot.img download from here:
https://drive.google.com/file/d/1SGyf3CYJewj0ew7hkexBX2XlDrei1sZi/view?usp=sharing
first boot need half hour and more
if give you bootloop reboot to recovery and fix boot.img again.
**********************************************************
OK now you have official rom.
*********************************************************
also install from recovery(push volume up+power button):
root.zip https://drive.google.com/open?id=1zvJMMXAGVUSGs0OBEBojdelZjFIL53Lw
dolbyatmos.zip https://drive.google.com/open?id=1SSpoH3JDniWb2T9oUesT7aiPwDupg1k3
GPUmod https://drive.google.com/open?id=1FSlYnURWT1ZJ9SjhkQ4Nxv6NdMAmJ9t0
CPUmod https://drive.google.com/open?id=1cv6Z4MMFiRMBGpiafB5CK_LWLhA-HSz9
CosmicTweack https://drive.google.com/open?id=1U1iD9YDpl7HhJKZjQJQOY80AGmLBO0vC
Dualboot https://drive.google.com/open?id=1yQ6b7J6Xc6hpnZHcM1rlW685uPWV1TkB
disable boot animation https://drive.google.com/open?id=15QWPNSslmjXsVDxyb3McOMMT9nI7oyWE
*******************************************************
if you like to install kernel...
join developer options and enable USB Debugging and connect your phone with pc
accept to your phone usb debugging request and after that run "remove_mi_find_device_ONLY.bat" files .download here
https://drive.google.com/open?id=1gIekgMhjRWPZlX_YYrNBZVrEtzQ7ymdY
download all files and run .bat
need delete find_divice application (1file)
**************************************
if you like to delete all bloatware run all .bat (3files)
-> AFTER THAT YOU CANT USE FIND DEVICE SERVICE <-
reboot to recovery menu(push volume up+power button) and install kernel
download kernel from here:
https://forum.xda-developers.com/red...ernel-t3625082
https://drive.google.com/open?id=1MmFKzsIQEWOBnVrtNMxNc2jSrT-vmhHB
SPECTRUM APK
https://drive.google.com/open?id=12RG90ynEsi83jo2HTERYvCvIwDucuft4
THIS IS IT :good::good:
CREDITS:
ALL TOOLS AND MODS INCLUDED IN XDA FORUM
thanks all developers
Kisses from Greece
have fun :laugh::laugh:
Click to expand...
Click to collapse
Make a video with tutorial and post the link please!

this kernel can use for miui 9 MM?

Alvian_P said:
this kernel can use for miui 9 MM?
Click to expand...
Click to collapse
i use it in 9.5.3.work fine
https://forum.xda-developers.com/redmi-note-4/development/spectrum-support-xtreme97-kernel-t3625082
--------------------------------------------------------------------------------------------
magnodjs said:
Make a video with tutorial and post the link please!
Click to expand...
Click to collapse
defecult man but i try it

akaluptos21 said:
if you install rom and kernel
phone give you error.
need delete find_divice application
**************************************
if you like to delete all bloatware run all .bat (3files)
(now have 3 bat files)
if you delete all bloatware you cant install it again.(use play store to download again-maybe)
kernel installed one time.if you change rom need install kernel again
Click to expand...
Click to collapse
Well. I tried to install the kernell but the drive folder isn't downloading everything 'cause google detects adb.exe and some other files as a virus, even thoug I replaced that file, I tried to run the .bat files, i just got a cmd32 window with "Enter adb.exe folder path:" so, maybe i'm lost. Should I have to enter my device in fastboot mode? can you give more details to install the kernell? i was able to do the mods but I think this is as important as that...

akaluptos21 said:
i use it in 9.5.3.work fine
https://forum.xda-developers.com/redmi-note-4/development/spectrum-support-xtreme97-kernel-t3625082
--------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Thx, i'll try on MTk rn4

SalPhobos said:
Well. I tried to install the kernell but the drive folder isn't downloading everything 'cause google detects adb.exe and some other files as a virus, even thoug I replaced that file, I tried to run the .bat files, i just got a cmd32 window with "Enter adb.exe folder path:" so, maybe i'm lost. Should I have to enter my device in fastboot mode? can you give more details to install the kernell? i was able to do the mods but I think this is as important as that...
Click to expand...
Click to collapse
Code:
[COLOR="Red"]DONT INSCUTED VIRUSES. BAT FILES ALERTED
i re-upload files in third-party page[/COLOR]
man if you like install kernel.
read how to install kernel from original post
kernel (bootv2.img) installed from recovery twrp.
not from pc with ADB :good:
Code:
https://forum.xda-developers.com/redmi-note-4/development/spectrum-support-xtreme97-kernel-t3625082
"WE AREN'T RESPONSIBLE FOR NOTHING
INSTALLATION:
-We reboot in the TWRP, press install, install image and select the bootv2.img that we downloaded from the post, select flash in the "boot" partition and install it
-Flash Supersu
-Restart
- Go to the Play Store and look for the Spectrum app (Go to the Screenshot tab and the icon app for zero confussions) and download it
-We open it, grant root access and select the behavior we want"

have installed kernel. remove find device. but my phone bootloop, white loading bar under Mi logo continuesly

Alvian_P said:
have installed kernel. remove find device. but my phone bootloop, white loading bar under Mi logo continuesly
Click to expand...
Click to collapse
so was i, i really confused with the step.
where can i find the batch for remove find device? or is it have to do manually?
i do manually remove find device app using adb shell, but after all that still getting stuck at bootloop and loading bar again and again, i tried almost 10 times and still cannot through that.
when i try to remove all bloatware, batch file saying " failure - internal device error or not installed for 0 "
but some app success to remove..
what do i missed?

feelsgood said:
so was i, i really confused with the step.
where can i find the batch for remove find device? or is it have to do manually?
i do manually remove find device app using adb shell, but after all that still getting stuck at bootloop and loading bar again and again, i tried almost 10 times and still cannot through that.
when i try to remove all bloatware, batch file saying " failure - internal device error or not installed for 0 "
but some app success to remove..
what do i missed?
Click to expand...
Click to collapse
bat files is here
https://drive.google.com/drive/folders/1gIekgMhjRWPZlX_YYrNBZVrEtzQ7ymdY
also need to work and win32 files.incluted.
wait for re-upload files in third-party page incluted zip
wipe-clean dalvin + cache from recovery TWRP
boot for 10 minutes...with MIUI bar

akaluptos21 said:
Code:
[COLOR="Red"]DONT INSCUTED VIRUSES. BAT FILES ALERTED
i re-upload files in third-party page[/COLOR]
man if you like install kernel.
read how to install kernelfrom original post
kernel (bootv2.img) installed from recovery twrp.
not from pc with ADB :good:
Code:
https://forum.xda-developers.com/redmi-note-4/development/spectrum-support-xtreme97-kernel-t3625082
"WE AREN'T RESPONSIBLE FOR NOTHING
INSTALLATION:
-We reboot in the TWRP, press install, install image and select the bootv2.img that we downloaded from the post, select flash in the "boot" partition and install it
-Flash Supersu
-Restart
- Go to the Play Store and look for the Spectrum app (Go to the Screenshot tab and the icon app for zero confussions) and download it
-We open it, grant root access and select the behavior we want"
Click to expand...
Click to collapse
yeah, I didn't ask correctly, the problem I'm having is uninstalling xiaomi services. I'll try again. Thank you!

SalPhobos said:
yeah, I didn't ask correctly, the problem I'm having is uninstalling xiaomi services. I'll try again. Thank you!
Click to expand...
Click to collapse
download all requerted files in one zip file ( without rom and MiFlash_unlocker )
https://drive.google.com/open?id=1Hy6p_6wgEJqQyMlXPFUMcZ63zcBz8ifm

new version rom has been released
9.6.1.0 Global Stable Recovery ROM | V9.6.1.0.MBFMIFD download here
(kernel dont work in 9.6.10)

ask question
sir why my handhpone cant go to recovery, i lost my twrp and i cant connect to my pc. please give a solution sir thanks :good:

anantaeka96 said:
sir why my handhpone cant go to recovery, i lost my twrp and i cant connect to my pc. please give a solution sir thanks :good:
Click to expand...
Click to collapse
volume down+power button
connect with usb
run "fastboot boot recovery"
give more details

Root or ROMs for 2019 Tab A 8.0" (SM-P200/5)

I realize this may be quite hard to answer but hopefully someone has some idea
I'm really tempted by the new galaxy tab a 8 with s pen (sm-p200/sm-p205). It's the perfect size for quick note taking
Thing is, I really want root and custom roms for it, does anyone have any thoughts as to how likely these are to eventuate? It shares the same chipset (exynos 7885) as the 2018 Galaxy A8 phone which has been rooted
Is this device likely to get root or custom rom support?

It seems we have magisk root here :
https://blog.gsm-social.com/2019/07/p205-u1-9-and-magisk/
But I don't understand Arabic. Can anyone check this site?

Could someone update on any feedback if they managed to get the P200/205 rooted?
Thanks a lot for the info

I've actually try this method on my P205 (China/ Hong Kong version) but could not make it work. It's possible that maybe works on an international version of the P205 or on the P200. Has anyone else tried this method with any success?
http://androidbiits.com/root-samsung-galaxy-tab-a-sm-p205-wisdom-easily/

VeEuzUKY said:
I've actually try this method on my P205 (China/ Hong Kong version) but could not make it work. It's possible that maybe works on an international version of the P205 or on the P200. Has anyone else tried this method with any success?
http://androidbiits.com/root-samsung-galaxy-tab-a-sm-p205-wisdom-easily/
Click to expand...
Click to collapse
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb

flushback666 said:
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb
Click to expand...
Click to collapse
Thanks a lot for the info! I'm on a Hong Kong/Chinese Global ROM (stock of course). What version of Android are you running in your rooted device now and do you have the WiFi or LTE version?
Thanks again

VeEuzUKY said:
Thanks a lot for the info! I'm on a Hong Kong/Chinese Global ROM (stock of course). What version of Android are you running in your rooted device now and do you have the WiFi or LTE version?
Thanks again
Click to expand...
Click to collapse
Hi,
i have the LTE Version SM-P205. As it arrived it had an old firmware so I first updated to the current stock Firmware P205DXU2ASH2 with the normal Samsung Update.
I downloaded the correspondending firmware files again for magisk patching with samfirm tool or if you or prefer from the usual samsung firmware download pages.
As i have a CSC from malaysia i took the XME CSC Firmware. From there on you can just fellow the magisk tutorial. Hopefully someone compiles a twrp recovery as firmware sources are available. So now i am on stock rooted firmware P205DXU2ASH2 .
I am using the LTE Version here in germany without any problems.
flushb
Download Mode Key Combo is VOL - + Vol +

flushback666 said:
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb
Click to expand...
Click to collapse
flushback666 said:
Hi,
i have the LTE Version SM-P205. As it arrived it had an old firmware so I first updated to the current stock Firmware P205DXU2ASH2 with the normal Samsung Update.
I downloaded the correspondending firmware files again for magisk patching with samfirm tool or if you or prefer from the usual samsung firmware download pages.
As i have a CSC from malaysia i took the XME CSC Firmware. From there on you can just fellow the magisk tutorial. Hopefully someone compiles a twrp recovery as firmware sources are available. So now i am on stock rooted firmware P205DXU2ASH2 .
I am using the LTE Version here in germany without any problems.
flushb
Download Mode Key Combo is VOL - + Vol +
Click to expand...
Click to collapse
Thanks again for the info. I will try follow the same steps and attempt to root again. I've had endless Samsung devices and this is the first time I am having problems trying to get one rooted.. Then again this is a much different process than the usual and we don't have Recovery yet. Given the limited sales and interest in this Tab (which is really a shame), probably there won't be too much development around it. This is actually the best price/features Tab Samsung makes now and the perfect form factor/size. If only the hardware was a bit faster and the camera a bit bigger.. but hey, can't have everything, haha
Thanks again for sharing the info, much appreciated

VeEuzUKY said:
Thanks again for the info. I will try follow the same steps and attempt to root again. I've had endless Samsung devices and this is the first time I am having problems trying to get one rooted.. Then again this is a much different process than the usual and we don't have Recovery yet. Given the limited sales and interest in this Tab (which is really a shame), probably there won't be too much development around it. This is actually the best price/features Tab Samsung makes now and the perfect form factor/size. If only the hardware was a bit faster and the camera a bit bigger.. but hey, can't have everything, haha
Thanks again for sharing the info, much appreciated
Click to expand...
Click to collapse
Hi,
no problem if you have questions just ask.
Attached screenshoot from root check
flushb

flushback666 said:
Hi,
no problem if you have questions just ask.
Attached screenshoot from root check
flushb
Click to expand...
Click to collapse
You know, I have received lots of PM regarding root as no one seems to be successful at it. You should start a new thread, call it something like "SM-P205 ROOT ACHIEVED" and post a step-by-step guide on how you did it. Not many people are following this thread here and news of root for this Tab will make thousands of people very happy worldwide.
If you have the time, you should do it. The whole community here appreciation is guaranteed
Thanks again

VeEuzUKY said:
You know, I have received lots of PM regarding root as no one seems to be successful at it. You should start a new thread, call it something like "SM-P205 ROOT ACHIEVED" and post a step-by-step guide on how you did it. Not many people are following this thread here and news of root for this Tab will make thousands of people very happy worldwide.
If you have the time, you should do it. The whole community here appreciation is guaranteed
Thanks again
Click to expand...
Click to collapse
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb

flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
Very cool, and I'll contribute to the thread with my feedback as much as I can myself too. Thanks again

flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
yes, please when you have time, do a tutorial. thanks a lot!!!

VeEuzUKY said:
Very cool, and I'll contribute to the thread with my feedback as much as I can myself too. Thanks again
Click to expand...
Click to collapse
Done!
Samsung Galaxy Tab A 8.0 (2019) with S Pen (SM-P205) ROOT ACHIEVED / Howto
flushb

flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
flushback666 said:
Done!
Samsung Galaxy Tab A 8.0 (2019) with S Pen (SM-P205) ROOT ACHIEVED / Howto
flushb
Click to expand...
Click to collapse
Awesome, I'll check it out now

Just bought the wifi variant of this tablet here in Germany too.....Seems to be a good 8" alternative. Looking forward to installing twrp and a Lineage ROM. Any news for that?

samsung unlockBL downgraderoot AutoBootCharge autoSd3HrIdle Charge to 65%
It is sharing of experience only without any liability or warranty.
Why: I use the tab very rarely but in critical requirement, I am getting it in discharged condition when i needed. Good news is that , in off condition it consumes around 1% per 10 days. I did not want to root it, but this tab at least shoud have have scheduled shutdown like other makes. The battery protect mode does not function properly. However thanks to Samsung for leaving the facility to unlock the Bootloader, rooting etc for advanced users (I feel definitely it has the capability to lock fully like apple )
Pre requirements
1. Samsung Tab A 2019 P200 (I have no experience on other models) charged more than 50%
2. Usb cable
3. Samsung USB Drivers
4. Windows 10 PC with UPS
5. Firmware suitable to your phone / region
6. Odin3-v3.14.4
7. 7Z ZS
8. Magisk Manager
9. Root explorer
I. Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
The following worked for me
• Installed Samsung USB driver on PC
• Allow bootloader unlocking in Developer options → OEM unlocking
• Disconnect the USB cable
• Power off the device
• Press and hold Volume Up & Down keys
• Insert USB cable
• Long press Volume up key
• Press Volume up ( yes) to unlock BootLoader
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
• Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
• Enable developer options, and confirm that the OEM unlocking option exists and grayed out! (yes it happened in my case) The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
• Your bootloader now accepts unofficial images in download mode.
II. Downgrade Flash instructions
1. Extract (unzip) the Samsung firmware file. Recommended using 7-Zip ZS
2) Install Samsung USB driver on PC if already not installed
3. , Extract Odin ZIP file Odin Tool 3.14.4 Downloaded, Open Odin execute file
4.) Remove Samsung . Google etc accounts from Tab
5. Reboot Samsung phone in Download Mode (hold Power + Volume Up buttons, it will booted to Recovery, select reboot to bootloader, Downloading screen will come then plug-in cable)
6. Connect you Samsung phone and wait until you get a blue symbol with com port no in Odin
7. Add the 1 file Samsung firmware to AP/PDA or 4 files Samsung firmware (AP/BL/CP/CSC) to it's slots (for P205 it will be 5 files)
8. Make sure re-partition is NOT ticked at Options at Odin
9. Click the START button, sit back and wait few minutes
Downgrading BootLoader-Theory
Downgrading BootLoader is Not possible unless you modify the BL….. .tar.md5 by removing the .bin files in it, then tar it up and flash in odin (- NOT TRIED).
The secure bootloader (sboot.bin) won't allow the downgrade of itself. you can't downgrade because the bootloader is protected by Rollback Prevention, So apparently I can only install firmware files which come with the same Bootloader.
We need to know what your current "Build Number" is on the phone. You also can't downgrade to other bootloaders that are lower then your current one, so if you're on bootloader 5 you need to use the Oreo bootloader 5 version firmware or it will not work. (Bootloader # is the 5th spot from the right.
Rollback Prevention (RP)
Rollback Prevention blocks the device from loading or flashing an approved but old version of boot components. Old versions of software may contain known vulnerabilities that attackers can exploit. Rollback prevention checks the version of the bootloader and kernel during both boot and updates, and blocks these processes from continuing if versions are unacceptably old. The lowest acceptable version of the bootloader is stored in secure hardware fuses when the device is flashed, and the lowest acceptable version of the kernel is stored in the bootloader itself. Whenever a vendor-applied update occurs, the lowest acceptable version can be incremented in the fuses. Because this value is kept in fuses, it cannot be decremented even through physical tampering. Rollback Prevention fuses are set at manufacturing time in the Samsung factory to prevent old firmware versions from overwriting newer ones.
Present version on device: P200ZHU2ASK2 (Settings>About Tabet>Software information>Build No XXXX XXXXXXX P200ZHU2ASK2, Service Provider SW ver ………….TGY// i.e Hongkong) , tried and failed is : P200ZHU1ASG1 , but now downgraded (bootloader is same version) P200ZHU2ASH2.
III. Rooting
Notes Installing Magisk
• Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
• Installing Magisk WILL trip KNOX (void Warranty)
• Installing Magisk for the first time REQUIRES a full data wipe, backup before continue
• You have to have your bootloader unlocked before following the instructions
Instructions on Rooting
1. Unzip the firmware P200ZHU2ASH2 on PC and copy the AP tar file to your Phone. It is normally named as AP_P200ZHU2ASH2_CL16717766_QB25581052_REV01_user_low_ship_meta_OS9.tar.md5
2. Install the latest Magisk Manager
3. In Magisk Manager: Install → Install > select and patch file> browse to location of file > tap and hold to select >open e.g AP tar file> working version / build is MagiskManager-v7.5.1.apk) (internet connection will make install button visible )
4. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
5. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
It will be copied to PC at C:\Users\......\AppData\Local\VirtualStore\Program Files (x86)\Minimal ADB and Fastboot
6. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options !
7. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
8. We now want to boot into the stock recovery to factory reset our device.
9. Disconnect the phone.
10. Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key (Power + Volume Up) to boot to recovery continue pressing the volume up button until you see the stock recovery screen (Not patched recovery , as it has Factory data reset, try again, view recovery logs only) as we need it.
11. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
12. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key (Power + Volume Up) to recovery. After seeing the bootloader warning screen (first screen), release all buttons so it can boot to the system.
13. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
14. After the device is booted up, done the usual initial setup. The following steps will need an internet connection.
15. I have manually installed the APK , downloaded in step 2 and continued to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
16. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
17. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the key combination for booting from the recovery partition. ( Vol Up + Power) but in my case it is always booting to Magisk.
Theory: Since some devices no longer use ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
After installing Magisk in recovery:
• (Powering up normally) → (System with NO Magisk) or if required reboot phone once OS is loaded
• (OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
• (OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
In my case (for my version of firmware) once magisk system is booted as above , every time it is loading magiskpatched system if shutdown is used (while charger is not connected ), but if we use reboot it is rebooting to Stock system- further, if we shutdown while charger is connected it is will shutting down and start charging with charging animation (means if we press power button it will boot to stock system) great advantage as stock (partially rooted?) also can be booted when required.
Additional Info
• Magisk actually patches 3 partitions on your device:
o vbmeta: replace with empty vbmeta image to disable partition verification
o boot: remove the signature of the image to prevent soft bricks
o recovery: this is where Magisk is actually installed
• Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
• If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
• If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Release Keys ( P&V+) for System with Magisk
Keep pressing volume up for Actual recovery
IV. Splash screen and warning screen change
1. Download the correct firmware of your Samsung
2. Unzip the firmware files with an extractor (winrar, etc)
3. Open the BL file WITH 7-ZIP EXTRACTOR (example) BL
4. BL_P200ZHU2ASH2_CL16717766_QB25581052_REV01_user_low_ship.tar.md5
5. Extract the param.bin.lz4 file WITH 7-ZIP EXTRACTOR
6. Open the param.bin.lz4 file WITH 7-ZIP EXTRACTOR and extract the param.bin file
7. Extract param.bin WITH 7-ZIP EXTRACTOR. All images are extracted in a folder.
8. edit logo.jpg and svb_orange.jpg or any other file suitably
9. select all files(not folder) and right click and select 7-Zip ZS Add archive > select archive format tar>ok to get param.bin.tar
10. Close 7-zip ZS, now change the name of above file from param.bin.tar to param.bin.
11. Right click on above param.bin select 7zip ZS > add archive…> select select archive format tar>ok to get param.bin.tar again
12. Change its name to BL_param.bin_only_to_change_logo (just to remind it is BL) Now we have the param.tar file ready for ODIN.
13. Open ODIN 3.13.3, start your phone in download mode, load the param.bin.tar file in the BL section and click on start.
Note: At the end of the flashing with ODIN the phone restarts showing the modified image, but it starts in recovery mode, you just have to accept restarting the phone, and it will start normally without losing data or the configuration of your Samsung Tab A P200
V. Auto Boot Charger connected once charged to more than 5 %
1. This is a bonus, if magisk is in effective condition, it will auto boot when charger is connected.
i.e. If it boots on auto when charger is connected that means that the sytem is magisk patched
(no need to edit lpm, however if we modify lpm, phone will hang at power symbol screen in non-magisk mode –to reset it, remove charger connection , press power+VolUp+VolDown simultaneously still phone restarts )
VI. Auto shutdown on 3 hours idle
1. Install Automate app
2. Import file
“Boot to on and Auto Shutdown by 3hr idle (reset by Foreground GMusicFMusicPAmp or Charge or 11 min on) V8.flo”
3. At automate settings select Run on System start up
3. Start flow
VII. Auto stop charging at preset max and restart charging preset min shutdown phone at preset battery low
1. Install latest AccA 1.0.23 app from github and connect to internet
(older beta app was changing battery % with every booting , showing fast draining without any actual drain etc, if charger is connected instead of rising battery level , it is showing as decreasing , i.e. battery sync , ghost effect issues)
Or
If above does not work uninstall AccA and connect to internet , open magisk manager >options>downloads>search for acc >install Advanced Charging Controller 2019.7.21-r1 (201907211) > install > rebotot)
Or if above is also not working properly please use battery charge limit v1.1.1 from play store (it will not have all options of AccA.
2. Configure as required like max charge 65 , re charging start level at 35 % shutdown at 5 % etc by editing config.txt file at root>data>adb>acc-data> capacity= 5, 101, 35-65 (101 not to stop intermittently between 35-65 % charging) and save
Now one can connect phone always to power source without wearing out Battery.
It my experince only and thanks and regards to all who contributed on respective sections / fields.

hi,
thx for the comprehensive instruction.
I have successfully rooting my sm-p205
I have 2 questions if u pls help me :
1. I want root my sm-p205 because I want to use tincore keymapper. but although now I have successfully rooted it, it seems that I have to set the selinux to permissive.
I have tried all I've found, from using selinuxmodechanger, selinuxswitch, or even using terminal with su 0 setenforce 0, and all not working. that selinux still enforcing.
can u pls help me how to change the selinux ?
2. if I couldnt change the selinux, than it's no use for me to still on root. Is there anyway to go back to original stock firmware and unroot ? because I read on the last instruction of magisk that I may not flash it again with usual ap file that it may make it brick ?
thx

Any custom ROM available for this tablet? I can't find one anywhere. Thanks

[HOW-TO][EXYNOS/SNAPDRAGON] Root S20 series and upgrade firmware

Applicable Models:
All Exynos models including but not limited to:
SM-G980F or SM-G980F/DS (S20)
SM-G981B or SM-G981B/DS (S20)
SM-G985F or SM-G985F/DS (S20+)
SM-G986B or SM-G986B/DS (S20+)
SM-G988B or SM-G988B/DS (S20 Ultra)
All BL-unlockable Snapdragon models including but not limited to:
SM-G9810 (S20, Hong Kong, Taiwan, China mainland)
SM-G9860 (S20+, Hong Kong, Taiwan, China mainland)
SM-G9880 (S20 Ultra, Hong Kong, Taiwan, China mainland)
SM-G981N (S20, Korea)
SM-G986N (S20+, Korea)
SM-G988N (S20 Ultra, Korea)
Japanese model (SC-*) also use Snapdragon but I can't not confirm that its bootloader is unlockable.
It is known that bootloader can NOT be unlocked on U.S. models (U/U1) .
Frequently used key combinations of S20 series:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S20 series uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S20 series uses A-only partition which means there is only one set of system partition.
3. S20 series uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G9810", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OZL_CHC". The second 3-letter code "CHC" is your CSC.
6. Remember your model and CSC.
{
"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"
}
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
View attachment 4990053
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
If a recovery is available and you don't want to go through the process of downloading official firmware, go to #2.
You can also download a KERNEL TAR archive of your version here:
Exynos: https://github.com/jesec/proprietary_vendor_samsung_xyzs/releases
Snapdragon: https://github.com/jesec/proprietary_vendor_samsung_xyzq/releases
and then skip to Step 6.
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
View attachment 4990061
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G9810ZCU1ATD1). The last 4 letters (ATD1) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
View attachment 4990063
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
View attachment 4990065View attachment 4990067View attachment 4990069View attachment 4990071
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
XDA:DevDB Information
Root S20 series and upgrade firmware, Tool/Utility for the Samsung Galaxy S20
Contributors
jesec
Version Information
Status: Stable
Created 2020-04-08
Last Updated 2020-04-08

Other Methods:
You still need to unlock bootloader and disable AVB. (check Stage 2-3)
Recovery Magisk installation:
1. Open Odin on your computer.
2. Reboot your device to DOWNLOAD mode.
3. Put the recovery TAR flashable into AP slot.
4. Click start.
5. Use Volume Up + Power to reboot into recovery mode.
6. Install Magisk via recovery.
My recovery usually includes Magisk in "Select from root" -> ".builtin" folder. Or you can sideload the ZIP flashable of your choice via adb or https://flash.jesec.io/.
Flash pre-patched boot (Kernel) image:
Basically others have done stage 4-6 for you. Be aware that it is always safer to DIY.
You are welcomed to share your patched image to the community by replying to this thread.
Naming convention: model + firmware version (last four letters of build number) + magisk version .tar
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
SM-G9810_ATD1_ef9d077c.tar:
https://drive.google.com/open?id=1SxKXWHqR0aM_g457Yp7pk524_6aqp1k5

Some Interesting Things:
Change your CSC (carrier code):
You have to root your device. There might be some secret codes to trigger the menu without root, though.
Note that you can only change it to carrier configurations already included in your firmware.
WARNING: Your device will be reset to factory settings.
In a local terminal, type:
su
am start -n com.samsung.android.cidmanager/.preconfig.PreconfigActivity

Cheers jesse seems like years since we were on s9 forums nice friendly guide you made here

What is the purpose of disabling android verify boot?

ngoralph said:
What is the purpose of disabling android verify boot?
Click to expand...
Click to collapse
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
ngoralph said:
Am rooted without doing this step will it cause any problems?
Click to expand...
Click to collapse
You must have done it somewhere in the process. Magisk will patch vbmeta.img for you if you give it a tar archive.

jesec said:
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
Click to expand...
Click to collapse
Am rooted without doing this step will it cause any problems?

Stage 6: Patch the boot (Kernel) image via Magisk
can't Patch the boot (Kernel) image via Magisk
! Unable to repack boot image!
! Installation failed
---update
use 7-zip to creat tar

bigback said:
Stage 6: Patch the boot (Kernel) image via Magisk
can't Patch the boot (Kernel) image via Magisk
! Unable to repack boot image!
! Installation failed
---update
use 7-zip to creat tar
Click to expand...
Click to collapse
you can extrsct boot and re tar it all in mixplorer then just upload to pc and flash in odin

jesec said:
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
Click to expand...
Click to collapse
I'm rooted for weeks now without this... can you explain more in detail what this is for? Why is it advised from you to do this step? maybe in form of examples? like I said rooted without doing this and had no issues so far.

chieco said:
I'm rooted for weeks now without this... can you explain more in detail what this is for? Why is it advised from you to do this step? maybe in form of examples? like I said rooted without doing this and had no issues so far.
Click to expand...
Click to collapse
Backread he already answered it on my inquiry

ngoralph said:
Backread he already answered it on my inquiry
Click to expand...
Click to collapse
I qouted his answer to your question asking for more details.

Magisk Root on Snapdragon based SM-G9860 S20+?
First of all, thanks for putting this guide together - very useful. I did want to share my experience following these instructions.
Everything went well until Stage 6 where I installed the Magisk patched AP file. The AP file was successfully patched with the latest canary Magisk and it also installed properly in Odin (did the full AP file and not the boot image since that encountered errors while trying to repack for some reason).
The problem is that when I reboot, No Magisk installed and No root...
I tried a factory reset just to confirm but same outcome. I did use the same AP file that was used to flash the phone as well.
Anyone successfully root and install Magisk on the Snapdragon based SM-G9860 S20+ (with latest Hong Kong firmware)? I suspect it has something to do with the Magisk not being able to handle the unlocked snapdragon based phones yet (it was like that for the Galaxy 10+ last year - took an extra month to come up with a Magisk branch that was able to handle the phone). I'm also following this thread for Snapdragons based S20 but it doesn't seem to have too many details yet
Cheers
A.A.

chieco said:
I qouted his answer to your question asking for more details.
Click to expand...
Click to collapse
jesec said:
You must have done it somewhere in the process. Magisk will patch vbmeta.img for you if you give it a tar archive.
Click to expand...
Click to collapse
AloxeCorton said:
First of all, thanks for putting this guide together - very useful. I did want to share my experience following these instructions.
Everything went well until Stage 6 where I installed the Magisk patched AP file. The AP file was successfully patched with the latest canary Magisk and it also installed properly in Odin (did the full AP file and not the boot image since that encountered errors while trying to repack for some reason).
The problem is that when I reboot, No Magisk installed and No root...
I tried a factory reset just to confirm but same outcome. I did use the same AP file that was used to flash the phone as well.
Anyone successfully root and install Magisk on the Snapdragon based SM-G9860 S20+ (with latest Hong Kong firmware)? I suspect it has something to do with the Magisk not being able to handle the unlocked snapdragon based phones yet (it was like that for the Galaxy 10+ last year - took an extra month to come up with a Magisk branch that was able to handle the phone). I'm also following this thread for Snapdragons based S20 but it doesn't seem to have too many details yet
Cheers
A.A.
Click to expand...
Click to collapse
My Snapdragon S20 has been rooted with Magisk. I think probably it has problem patching the full AP file. In that case, I recommend you to research how to pack a tar file. I don't recommend you to patch the full AP as it is huge.
Also be aware that all patched file is located in /sdcard/Download and named magisk_patched.*. It is NOT in-place patch. You might accidentally use the unpatched file.

So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...

Orphee said:
So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...
Click to expand...
Click to collapse
As it finishes flashing firmware hold volume buttons as it reboots. Then flash patched boot.img and reboot. Worked for me going from ATCH to ATCT today.

jesec said:
My Snapdragon S20 has been rooted with Magisk. I think probably it has problem patching the full AP file. In that case, I recommend you to research how to pack a tar file. I don't recommend you to patch the full AP as it is huge.
Also be aware that all patched file is located in /sdcard/Download and named magisk_patched.*. It is NOT in-place patch. You might accidentally use the unpatched file.
Click to expand...
Click to collapse
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.

AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
I had the same issue... I used a tool (lz4_win64_v1_9_2) to uncompress lz4 format... I kept it just as boot.img and packed in boot.tar file and it worked.
Just for info, 7-zip built wrong tar file (don't ask me why...)... I had to use cygwin for it (or a linux if you have)

Orphee said:
So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...
Click to expand...
Click to collapse
That's expected.
From Android 10, encryption keys are tied to AVB key (stored in vbmeta). By disabling AVB, you changed the AVB key from Samsung's to none. Though, if I remember correctly, some old versions have security loophole that allows you to boot a patched kernel even if AVB key is intact (recovery is still protected however). That's actually a serious breach of this additional integrity assurance. (your sensitive data is still safe nonetheless as there is a customer key tied to your password/pattern/etc)
Read more: https://source.android.com/security/keystore/version-binding
AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
That should not happen. Here is a screenshot if things are done right:
Make sure you pack the TAR right (see OP for a screenshot of boot.img.lz4.tar) and the file you transfer to your device is the TAR file (boot.img.lz4.tar if you don't change the file name).
Plus, maybe check if Magisk version is right. Make sure you use the Canary builds.

AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
do it on fone thats what i did mixplorer will tar it for you then move to pc and flash