How to root your Huawei device on Nougat
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TUTO
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Hi mates
For all those who, like me, have a lot of trouble to root their Mate 8.
I've successful to root my phone from the B560.
Last tuto (FINAL):
* Have the B560 firmware (or above - ask me for that) without no changes for Huawei Mate 8 with Nougat firmware - for the others devices, ASK ME!!!
* This Boot_Insecure_BXXX_Fix-adb_dm-verity-v2.img or v3- 5 versions for the moment: B560 - B580 - B581 - B582 - B585 - B588- B590- B592- B594- B595- B596. For another kernel, ASK ME!
* Have this TWRP 3.1.0-x - or this one (following the update)
* Have this SuperSU-v2.xx-EMUI5.0.zip on your external sdcard for supersu Chainfire - method 1
* Have the PHH superuser.zip on your external sdcard for PHH superuser - method 2
1 - Easy way to root with supersu Chainfire:
Install the TWRP via adb, or SRKtools or still TWRP if you already have it
Install the new_Insecure_BXXX_dm-verity-v2.img or v3 via adb
Reboot to the recovery
Install SuperSU-v2.xx-EMUI5.0.zip from TWRP
Reboot system
2 - Easy way to root with PHH superuser:
Install the TWRP via adb, or SRKtools or still TWRP if you already have it
Install the new_Insecure_BXXX_dm-verity-v2.img or v3 via adb
Reboot to the recovery
Install PHH superuser.zip from TWRP
Reboot system
Install PHH superuser app via PlayStore (if necessary, you had to make it with previous version)
Devices with which it works:
HUAWEI Mate 8
HUAWEI Honor Note 8
HUAWEI P9
HUAWEI Honor 8
HUAWEI MediaPad M3
HUAWEI P9 Plus
Misc:
It's certainly possible to root others Huawei models . For them, send me the stock boot.img of your current firmware in order that I make an insecure boot Fix-adb dm-verity for your device.
All apps requiring root works well with this method.
Following a problem with access to developer options, a update was made that now makes us to v3.
Credits:
ajsmsg78 - who explained me how to create the insecure boot
jac10000 - who helped me to create the insecure boot Fix-adb dm-verity
Chainfire for supersu
phhusson for PHH superuser
Donators:
Thanks to them
letschky
Frittenfresser
Tecalote
Version Information:
Status: Functionnal
Created: 2017-02-12
Last Updated: 2018-02-07
If you like that, hit the THANKS button below !
Report me if it works fine for you! I'll add you in the OP post.
Report me on which firmware you used my method.
Changes:
Code:
[B][I]Boot_Insecure_BXXX_Fix-adb_dm-verity-v2.img[/I][/B]
* fixes issue adb doesn't work
[B][I]Boot_Insecure_BXXX_Fix-adb_dm-verity.img[/I][/B]
* based on the [URL="https://forum.xda-developers.com/mate-8/orig-development/boot-decrypted-insecure-boot-img-adb-t3555257"]insecure boot[/URL]
* remove the boot checking of dm-verity for a better rooting
* authorize read/ write on the partitions
Thanks!
Install TWRP (SRKtools method)
TWRP TUTO:
Download this twrp.img
Rename it as twrpmate8mm.img
Goes to the SRKtools folder
Goes to the recovery folder
Goes to the mate8 folder
Goes to the emui41 folder
Open mate8.zip file with winrar or other extractor
Inside, you've 2 files,stockrecoverymate8mm.img and twrpmate8mm.img, delete twrpmate8mm.img file in the zip and confirm
Drag and drop your renamed file (twrpmate8mm.img) in the opened zip, confirm
Plug your phone
Authorize Debug mode in Settings\Developper options
Check if "Enable OEM unlock" is ticked
Authorize Debug mode in popup windows
Now, you launch SRKtools app
In the menu, choose 3 (Install recovery 6.0) and enter
Choose 2 (Huawei Mate 8) and enter
Choose 3 (Install Mate 8 TWRP for Marshmallow (EMUI 4.1) and enter
Type y and enter
Type f and enter
Wait the end of installation
The phone will reboot to this recovery and you will see that is good recovery
Install TWRP (ADB method)
TWRP TUTO:
Download this twrp.img
Rename it as twrp.img
Plug the phone with the debug mod activated
Check if "Enable OEM unlock" is ticked
Launch a command prompt from you ADB folder - like on the Flash_boot_img_tuto_02.jpg screenshot
Type: adb devices
Type: adb reboot bootloader
Put the twrp.img file in C: (you can put anywhere but you should know the path. So the better is to follow my instructions)
Type: fastboot flash recovery C:\twrp.img (Wait the end of installation, it's quick)
Brilliant work buddy! Keep it coming
Thank you!
Thank you for your hard work. I will try it immediately, downloading everything I need now.
Will report back when I have done it
---------- Post added at 07:08 PM ---------- Previous post was at 07:02 PM ----------
Question:
If I am already on official OTA B560, can I skip these steps?
16. Install update_data_full_hw_eu.zip - Don't reboot
17. Install update.zip - Don't reboot
Click to expand...
Click to collapse
@dexz 's method arranged by meto avoid to format data again
Only use if you are in the situation below... otherwise follow this method
Good news for those who are in my situation with my method. The @dexz 's method works fine but force again to format data... personnally I had more than tired to format data. So I made this....
You are with the semi rooted B560 or other perhaps
You have Chainfire supersu
You have decrypted your data
You have a Decrypted data boot and you wanted to keep it
Put my Decrypted data boot on the external SD
Phone is on... then unroot it fully with Chainfire supersu in its settings - it asks you to restore the boot.img, I pushed "NO" because I had a doubt if I still had it, in addition it will install again in this tuto
Reboot in TWRP (frd-twrp like @dexz 's tuto)
Install Decrypted data boot
Wipe Dalvik & cache - Strongly advised after to have flashed the boot, it doesn't eat some bread
Install superuser_noverify_nocrypt.zip
Reboot to system - It will take about 3-5mins or less, it's due to the wipe Dalvik & Cache
Go to playstore and Install phh's SuperUser app
And like me, you are fully rooted... Again thanks to @dexz for his method! The one above isn't more complicate and avoid to format again the data if you are in my situation.
franzyroy said:
Thanks!
You can try but I don't know the result. Try at least with update_data_full_hw_eu
Click to expand...
Click to collapse
Okay thanks for quick reply, will try with update_data only
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
franzyroy said:
Thanks!
You can try but I don't know the result. Try at least with update_data_full_hw_eu
Click to expand...
Click to collapse
Another question, last one I promise.
You did not mention this in the thread, not that I saw at least.
Do I need to unlock my bootloader?
lovemajj said:
Okay thanks for quick reply, will try with update_data only
Click to expand...
Click to collapse
Perhaps it will work only with update data... I know someone has already rooted his phone like that (here).
lovemajj said:
Another question, last one I promise.
You did not mention this in the thread, not that I saw at least.
Do I need to unlock my bootloader?
Click to expand...
Click to collapse
Yes! I add it in the OP post!
franzyroy said:
Yes! I add it in the OP post!
Click to expand...
Click to collapse
Okay thank you!
lovemajj said:
Okay thank you!
Click to expand...
Click to collapse
Done
Short question is it possible that someone makes a twrp backup and i just reroll this on my phone?^^
How do I unlock the FRP lock?
EDIT: Nevermind, I figured out how to do it.
If anyone else needs an answer to this question here it is:
Before you unlock the bootloader, you MUST enable "OEM Unlocking".
If you do not do it before you unlock the bootloader, it will be greyed out and you will have to relock the bootloader and do it all over again.
---------- Post added at 09:26 PM ---------- Previous post was at 08:41 PM ----------
I have tried it now and it works!
Although I skipped one thing, which was step 3. I did not install the insecure boot because I know from the past that it screwed up my phone.
In short I did like this:
Enabled OEM Unlocking
Unlocked bootloader
Flashed TWRP (found in OP)
Factory reset
Format Data (here I rebooted to recovery)
Flashed the SuperSU zip (found in OP)
Flashed update_data_full_hw_eu.zip (also found in OP)
Then I flashed SuperSU again.
Reboot to system and done
Thank you for this post
lovemajj said:
How do I unlock the FRP lock?
EDIT: Nevermind, I figured out how to do it.
If anyone else needs an answer to this question here it is:
Before you unlock the bootloader, you MUST enable "OEM Unlocking".
If you do not do it before you unlock the bootloader, it will be greyed out and you will have to relock the bootloader and do it all over again.
---------- Post added at 09:26 PM ---------- Previous post was at 08:41 PM ----------
I have tried it now and it works!
Although I skipped one thing, which was step 3. I did not install the insecure boot because I know from the past that it screwed up my phone.
In short I did like this:
Enabled OEM Unlocking
Unlocked bootloader
Flashed TWRP (found in OP)
Factory reset
Format Data (here I rebooted to recovery)
Flashed the SuperSU zip (found in OP)
Flashed update_data_full_hw_eu.zip (also found in OP)
Then I flashed SuperSU again.
Reboot to system and done
Thank you for this post
Click to expand...
Click to collapse
So it works for you like that.
Thanks for your report, I will add you in the OP post.
Edit: Finally no, I will not add you, you don't match those who have a problem to root.
TWRP.img
franzyroy said:
Install TWRP (ADB method)
TWRP TUTO:
Download this frd-twrp.img
Rename it as twrp.img
Plug the phone with the debug mod activated
Launch a command prompt from you ADB folder - like on the Flash_boot_img_tuto_02.jpg screenshot
Type: adb devices
Type: adb reboot bootloader
Put the twrp.img file in C: (you can put anywhere but you should know the path. So the better is to follow my instructions)
Type: fastboot flash recovery C:\boot.img (Wait the end of installation, it's quick)
Click to expand...
Click to collapse
@franzyroy I do not understand the point 8. Why boot.img fastboot flash recovery? I for flashing the recovery I always used FASTBOOT command FLASH RECOVERY TWRP.img Thanks
apollo_81 said:
@franzyroy I do not understand the point 8. Why boot.img fastboot flash recovery? I for flashing the recovery I always used FASTBOOT command FLASH RECOVERY TWRP.img Thanks
Click to expand...
Click to collapse
It's a typo. Sorry!
@apollo_81
It was a typo, I corrected it.
This is:
Code:
fastboot flash recovery C:\twrp.img
@apollo_81
Can you remove your quote here #16 that others persons don't make the error.
lovemajj said:
Although I skipped one thing, which was step 3. I did not install the insecure boot because I know from the past that it screwed up my phone.
Click to expand...
Click to collapse
I did it and I haven't had any issue.
Related
This is what I have done this afternoon.
Use at your own risk, I'm not responsible for any data losing.
Environment: Oneplus One with stock CM11s XNPH30O
Steps:
1. Apply cm-11.0-XNPH25R-bacon-signed.zip from stock recovery.
2. DO NOT BOOT TO OS when update is finished. After updated, press power button until screen off.
3. Boot to fastboot mode by holding 'Power' button & 'Vol UP(+)'.
4. In fastboot mode, boot to custom recovery by
Code:
fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://techerrata.com/browse/twrp2/bacon
5. Make a nandroid backup for data partition. (Optional)
6. Sideload OnePlusOne-BootUnlocker.zip http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
7. Reboot to bootloader(fastboot mode)
8. Extract cm-11.0-XNPH30O-bacon-signed-fastboot.zip and execute 'flash-radio.sh' to update radio and other binaries.
9. Flash 30O system partition only by
Code:
fastboot flash system system.img
(Don't flash userdata.img or userdata_64G.img or you'll lose all your data.)
10. Reboot. The Bootloader is unlocked.
Sorry for my bad english.
Sick man, gonna try this when i get home
I am running on 33R will this work ???
Or connect to PC.. Adb backup, root, then adb restore
Cool write-up! I re-wrote the guide for use over on the OnePlus forums: https://forums.oneplus.net/threads/...ck-the-bootloader-without-losing-data.103642/
ifg said:
This is what I have done this afternoon.
Use at your own risk, I'm not responsible for any data losing.
Environment: Oneplus One with stock CM11s XNPH30O
Steps:
1. Apply cm-11.0-XNPH25R-bacon-signed.zip from stock recovery.
2. DO NOT BOOT TO OS when update is finished. After updated, press power button until screen off.
3. Boot to fastboot mode by holding 'Power' button & 'Vol UP(+)'.
4. In fastboot mode, boot to custom recovery by
Code:
fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://techerrata.com/browse/twrp2/bacon
5. Make a nandroid backup for data partition. (Optional)
6. Sideload OnePlusOne-BootUnlocker.zip http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
7. Reboot to bootloader(fastboot mode)
8. Extract cm-11.0-XNPH30O-bacon-signed-fastboot.zip and execute 'flash-radio.sh' to update radio and other binaries.
9. Flash 30O system partition only by
Code:
fastboot flash system system.img
(Don't flash userdata.img or userdata_64G.img or you'll lose all your data.)
10. Reboot. The Bootloader is unlocked.
Sorry for my bad english.
Click to expand...
Click to collapse
Big thanks for this guide. You saved my life. And thanks also to developers for this MOD :good:
---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------
Dibbyo123 said:
I am running on 33R will this work ???
Click to expand...
Click to collapse
Be sure to read the steps.
philicibine said:
Or connect to PC.. Adb backup, root, then adb restore
Click to expand...
Click to collapse
How would this be done by steps? I'm somewhat familiar with adb {I have the SDK installed and use it for fastboot) but coming from rooting and modding mostly Samsung devices I don't have experience with this method. Could you elaborate in another thread plz? Just the back up and restore part. I can manage the unlock and root.
erad1 said:
How would this be done by steps? I'm somewhat familiar with adb {I have the SDK installed and use it for fastboot) but coming from rooting and modding mostly Samsung devices I don't have experience with this method. Could you elaborate in another thread plz? Just the back up and restore part. I can manage the unlock and root.
Click to expand...
Click to collapse
i used the steps posted here. although they needed adapting for the one.
the bones of it is there though, so if you understand it, its easy to do.
Kind of went a different route but used this as a base and got it done. It was tricky but I'm unlocked, rooted, stock recovery and got most of my data back! Thanks for heads up philicibine and OP.
someone running on 33R succeeded with this MOD ???
Medosofts said:
someone running on 33R succeeded with this MOD ???
Click to expand...
Click to collapse
Yes. I was on 33R. Went to stock recovery and flashed 25R. Booted to fastboot and remotely ran twrp recovery and did a backup (in case) then flashed Bootloader unlock zip. While still in recovery, flashed 33R zip and SuperSU. I didn't extract any fastboot files, just used the flashable stock signed zip. All said and done, I had unlocked bootloader and root and back on 33R.
Now I was able to use Flashify app if I wanted a permanent custom recovery.
ralphwiggum1 said:
Yes. I was on 33R. Went to stock recovery and flashed 25R. Booted to fastboot and remotely ran twrp recovery and did a backup (in case) then flashed Bootloader unlock zip. While still in recovery, flashed 33R zip and SuperSU. I didn't extract any fastboot files, just used the flashable stock signed zip. All said and done, I had unlocked bootloader and root and back on 33R.
Now I was able to use Flashify app if I wanted a permanent custom recovery.
Click to expand...
Click to collapse
Hello did this wipe the device???
also were did you download the 33R from can you please provide me the link.
Thanks
Hilmesh said:
Hello did this wipe the device???
also were did you download the 33R from can you please provide me the link.
Thanks
Click to expand...
Click to collapse
This did NOT wipe my device. Look for the flashable (NOT fastboot) images in this thread.
http://forum.xda-developers.com/showthread.php?t=2857110
ralphwiggum1 said:
This did NOT wipe my device. Look for the flashable (NOT fastboot) images in this thread.
http://forum.xda-developers.com/showthread.php?t=2857110
Click to expand...
Click to collapse
Hello ,
I am on 33 R and downloading the flash-able zip from the thread you gave. The rest of items i have already downloaded (Please see attachment). Request you to please confirm that once my 33R download is complete am i ready to proceed??? (I also have the Complete SDK Package with me)
Also can you please list me the procedure step by step. This is my very first time doing it this way as i am used to rooting my S2 and that is a totally different method using ODIN.
Hope to receive your positive reply.
Ok. Done. It worked flawlessly on 33R. Followed all the steps as mentioned by @ralphwiggum1 (Thanks a lot mate . Also Thanks to @ifg for making the basic post to be followed. See attached Rootchecker image for proof.
Please note that this procedure worked for me on a totally unrooted & never before tried rooting device with 33R. Also my device info showed Tampered bit as True & unlock bit as False. You can check it by following this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Thanks to @Mnt-XDA.
Hilmesh said:
Ok. Done. It worked flawlessly on 33R. Followed all the steps as mentioned by @ralphwiggum1 (Thanks a lot mate . Also Thanks to @ifg for making the basic post to be followed. See attached Rootchecker image for proof.
Please note that this procedure worked for me on a totally unrooted & never before tried rooting device with 33R. Also my device info showed Tampered bit as True & unlock bit as False. You can check it by following this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Thanks to @Mnt-XDA.
Click to expand...
Click to collapse
Good job!
"As every guide is written with a Foreword so is this. Please try at your own risk. I am not responsible."
Next this is neither my guide nor my work. I went through all the threads as mentioned in the various links given below. All I did was follow procedure from whichever thread / post was related with my condition. Once I even got confused with too much information but then again as they if we don’t try we never know whether we would have failed or succeeded.
So I was able to do this only due the works of other people. All the credit & Thanks goes to them. I have tried and remembered and mentioned all the names. In case I have missed anyone please forgive me and point me the name and I will thank them too.
My Step by step procedure to root the device without wipe for devices who have never tried rooting their Oneplus One and are currently on 33R using the method mentioned in this thread,
Download the Recovery flashable zips of the complete ROMz - XNPH25R, XNPH33R
Follow the ADB & Fastboot Installation Procedure listed HERE(Also if you can then do read the complete post as it is very informative for Noobs like me )
Download the Oneplusone-bootunlocker.zip from HERE (Again if possible please read this complete thread too as it is also very informative)
Download the Supersu file from HERE
Download the custom recovery file from HERE
Copy both the Flashable zips, Bootunlocker, supersu files to your device
Switch off your device. And Then boot into STOCK RECOVERY by pressing the VOL DOWN & POWER key
Apply update – XNPH25R and then keep the power key pressed until the screen turns off. DO NOT REBOOT
Now boot to fastboot mode by holding the POWER button & VOL UP Key. Connect it to the PC and let it install all the drivers
Go to the SDK Installation in your PC, and within that go to the folder PLATFORM-TOOLS. Copy the “openrecovery-twrp-2.8.0.1-bacon.img” or latest file which you must have downloaded from the TWRP site
Within the directory Press the Shift Key and right click and you will get an option “Open command Prompt here” – Do it. Type in the command
Code:
Fastboot boot openrecovery-twrp-2.8.0.1-bacon.img
. Wait for 30 Seconds your device will enter into TWRP Custom recovery
Make a Nandroid backup (Optional)
Go to the install option within the recovery and select the Bootunlocker.zip. make sure the signature verification check box in unchecked. Apply the zip.
Now once again go into install option and select the XNPH33R zip and apply
I rebooted the device after Step 14 as I forgot to apply the supersu
Once again followed the same procedure to enter fastboot mode (Step 9) and loaded the custom recovery as mentioned in Step 11 and then applied the supersu zip as mentioned in Step 13. Again rebooted and device was successfully rooted with SuperSU
Next I wanted to flash Franco’s latest Kernel (franco.Kernel-nightly-r20.zip). Downloaded from HERE
Again put device in Fastboot mode (Step 9) and loaded Custom recovery (Step 11) and installed zip file using same procedure as Step 13
Wiped Cache & Dalvik Cache & Rebooted the device. No Issues. Franco Kernel was installed
Credits - I would like to thank everyone for helping me out. Full Thanks & Credits to @ifg (Guide for XNPH300), @Mnt-XDA (Bootunlocker.zip & a great thread about Reset Unlocker & Tamper Bit), @MICa.fighter (CM11S official & untouched image collection), @franciscofranco (Kernel for Oneplus One), Chromium (From Oneplus One Forum for a great guide on Everything Rooting for Oneplus One), @Chainfire (SuperSU), @ralphwiggum1 (for already trying it and clearing my doubts and giving me confidence to proceed)
Worked like a charm. Thanks!
Yeah, I really wish I found this post before I wiped my OPO, and lost another day reinstalling and configuring apps.
Hilmesh said:
"As every guide is written with a Foreword so is this. Please try at your own risk. I am not responsible."
Next this is neither my guide nor my work. I went through all the threads as mentioned in the various links given below. All I did was follow procedure from whichever thread / post was related with my condition. Once I even got confused with too much information but then again as they if we don’t try we never know whether we would have failed or succeeded.
So I was able to do this only due the works of other people. All the credit & Thanks goes to them. I have tried and remembered and mentioned all the names. In case I have missed anyone please forgive me and point me the name and I will thank them too.
My Step by step procedure to root the device without wipe for devices who have never tried rooting their Oneplus One and are currently on 33R using the method mentioned in this thread,
Download the Recovery flashable zips of the complete ROMz - XNPH25R, XNPH33R
Follow the ADB & Fastboot Installation Procedure listed HERE(Also if you can then do read the complete post as it is very informative for Noobs like me )
Download the Oneplusone-bootunlocker.zip from HERE (Again if possible please read this complete thread too as it is also very informative)
Download the Supersu file from HERE
Download the custom recovery file from HERE
Copy both the Flashable zips, Bootunlocker, supersu files to your device
Switch off your device. And Then boot into STOCK RECOVERY by pressing the VOL DOWN & POWER key
Apply update – XNPH25R and then keep the power key pressed until the screen turns off. DO NOT REBOOT
Now boot to fastboot mode by holding the POWER button & VOL UP Key. Connect it to the PC and let it install all the drivers
Go to the SDK Installation in your PC, and within that go to the folder PLATFORM-TOOLS. Copy the “openrecovery-twrp-2.8.0.1-bacon.img” or latest file which you must have downloaded from the TWRP site
Within the directory Press the Shift Key and right click and you will get an option “Open command Prompt here” – Do it. Type in the command
Code:
Fastboot boot openrecovery-twrp-2.8.0.1-bacon.img
. Wait for 30 Seconds your device will enter into TWRP Custom recovery
Make a Nandroid backup (Optional)
Go to the install option within the recovery and select the Bootunlocker.zip. make sure the signature verification check box in unchecked. Apply the zip.
Now once again go into install option and select the XNPH33R zip and apply
I rebooted the device after Step 14 as I forgot to apply the supersu
Once again followed the same procedure to enter fastboot mode (Step 9) and loaded the custom recovery as mentioned in Step 11 and then applied the supersu zip as mentioned in Step 13. Again rebooted and device was successfully rooted with SuperSU
Next I wanted to flash Franco’s latest Kernel (franco.Kernel-nightly-r20.zip). Downloaded from HERE
Again put device in Fastboot mode (Step 9) and loaded Custom recovery (Step 11) and installed zip file using same procedure as Step 13
Wiped Cache & Dalvik Cache & Rebooted the device. No Issues. Franco Kernel was installed
Credits - I would like to thank everyone for helping me out. Full Thanks & Credits to @ifg (Guide for XNPH300), @Mnt-XDA (Bootunlocker.zip & a great thread about Reset Unlocker & Tamper Bit), @MICa.fighter (CM11S official & untouched image collection), @franciscofranco (Kernel for Oneplus One), Chromium (From Oneplus One Forum for a great guide on Everything Rooting for Oneplus One), @Chainfire (SuperSU), @ralphwiggum1 (for already trying it and clearing my doubts and giving me confidence to proceed)
Click to expand...
Click to collapse
Excellent...well done and will help many!
I don't have anything against toolkits, I just prefer to use adb and fastboot so I have more control over of what's going on. I also think it's a good idea for folks to have a little idea about what they're doing, even if they aren't experts. Below are the steps I used to install TWRP (recovery) and SuperSU (root) for my X522 (aka S3, the US variant which uses the Snapdragon 652). I don't see any reason this wouldn't work for all other Snapdragon variants: X520 (Chinese), X526 (Indian), and X527 (International). That said, you do what you do at your own risk. If you have one of the other Snapdragon variants and this works for you, though, please respond to the thread and let me know!
This thread is intended to be noob-friendly! That means that there are no dumb questions...unless you ask a question that is directly answered in the first post or in the FAQs found in the second post. To that extent, please read and re-read and if you still can't find your answer, please feel free to post your question.
Many thanks to @Rishabh Rao and his team for getting us an official TWRP image.
WARNING: this will reset your phone entirely! Make sure you save anything you want from internal storage before proceeding any further!
WARNING: as of right now, unlocking / rooting your phone will break your ability to take official OTAs. We're not sure why. That said, you should be able to flash modified OTA zip files manually, after a certain block of the update script is removed (see second post for more information).
Unlocking and Rooting your Le 2
Download and install Minimal ADB and Fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download latest official TWRP, place file in ADB installation folder, and rename to "twrp.img": https://twrp.me/devices/leecole2.html
Download SuperSU 2.78 (stable): https://download.chainfire.eu/1001/
Boot up phone and plug into computer
Settings > scroll to bottom to "About phone" > touch "Build" 7 times to enable developer options
Developer options > toggle "OEM unlocking" and "USB debugging" so that they're both enabled
When "Allow USB debugging?" window pops up on phone, check "Always allow..." box and hit OK
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot bootloader
Once in fastboot:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
If password screen comes up, tap "Cancel" button
If it asks, tap "Keep Read Only" button (probably doesn't matter, but whatever)
Wipe > Format Data
Make backups (I suggest boot, recovery, and system since this will allow you to return everything to stock later on)
Mount > Enable MTP
Copy entire TWRP folder from internal storage to your computer
Copy SuperSU zip from your computer to root of internal storage
Reboot > Bootloader
Code:
fastboot oem unlock-go
fastboot flash recovery twrp.img
Hold Vol+ and Pwr until boots into TWRP
Swipe to Allow Modifications
Install > select SuperSU zip > swipe to flash
Wipe Cache/Dalvik
Reboot (first boot will take a little while, so be patient)
Enjoy your rooted phone!
Restoring to Stock(ish)
Follow steps 4-7 above
If your boot and recovery backups from TWRP aren't already on your phone, move them to the appropriate folder (internal storage/TWRP/BACKUPS/[yourphoneserialnumber])
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot recovery
Wipe > check Dalvik, Cache, Data
Restore > select your package, ensure boot and recovery are checked, then Swipe to Restore
Reboot > Recovery
In stock recovery: uncheck "Update system", check "Clear data", and tap "Start"
Reboot to bootloader (hold Vol- and Pwr until it comes up) and then:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
Wipe > Format Data
Reboot > System
Your phone is now back to stock!
If you didn't back up your stock recovery, boot, or system, you can find the ones I pulled from my phone at the link below. They're from 19S. I don't know if that makes a difference (vs 18S) with boot and recovery or not, but obviously that's what you're getting with the system.
https://mega.nz/#F!bV0XUbhJ!k2ZfY5t9bxb8gRa3rKQbyA
FAQs
Fastboot and/or ADB doesn't see my phone!
If you've enabled OEM unlocking and USB debugging and fastboot devices returns <waiting for device> or adb devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (probably something from 2014)
I haven't seen the "Allow USB debugging?" prompt. Where is it?
In some cases, you will need to run an ADB command first to make the prompt show up. If you toggled the appropriate developer options and didn't get the popup immediately, make sure your phone is plugged into your computer and type adb devices in the command prompt. You should get the popup box then.
Stock recovery is in Chinese and I can't read Chinese!
As I was testing the above procedures, this happened to me once or twice and I don't know why. Upon a full restore and boot back into recovery, it was in English again. It might have something to do with the data wipe in TWRP. Anyway, the options in stock recovery are the same in Chinese and English so do this:
Uncheck the first item and check the second
It will direct you to a screen with some red text and a blue button: tap the button
It will return you to the first page: ensure the second item is checked and tap the blue button
Uh, how do I re-lock the bootloader? Am I missing something?
As far as I can tell - and someone please correct me if I'm wrong - using this guide, your bootloader is only ever temporarily unlocked and will re-lock with a reboot. That's why you have to use fastboot oem unlock-go more than once. You can verify this by restarting the phone, rebooting into the bootloader, and using the code below to check the status:
Code:
fastboot oem device-info
If for some reason your phone shows that you still have an unlocked bootloader, you can re-lock it using:
Code:
fastboot oem lock-go
I'm stuck in a stock recovery bootloop. How do I get out of it?
This probably happened because you're just holding down the power button to reboot instead of using the "restart" button in stock recovery. If you use the "restart" button to in stock recovery, it should kick you out of the loop.
Thanks for this guide , can we expect some roms from your side.
Just curious to know if any developer is working for rom on le2
Great guide for beginners but can you tell that how can one lock the bootloader again and when we make a backup does it make the back up of TWRP recovery of stock recovery?
Great!! Informative thread for beginners!
Miketoulson said:
Just curious to know if any developer is working for rom on le2
Click to expand...
Click to collapse
Yes. @Rishabh Rao and his team (the same ones who did TWRP and the AIO toolkit) are working on CM. As a reminder, please do not ask for ETAs. They will post the ROM when it's available.
Swastik Raj Chauhan said:
Great guide for beginners but can you tell that how can one lock the bootloader again and when we make a backup does it make the back up of TWRP recovery of stock recovery?
Click to expand...
Click to collapse
1.) Regarding the bootloader: good question. I've updated the FAQ.
2.) Regarding recovery backup: that's why we only boot into TWRP the first time, rather than replacing recovery from the beginning. That way, stock boot and recovery are backed up. Later on, when we flash TWRP, stock recovery is replaced.
I'm having trouble with this guide. I have TWRP recover flashed, but it isn't working correctly. It says there is nothing in my sdcard directory and my computer won't connect to the phone in recovery. I've also tried "adb push ... /sdcard/" method. The SuperSU files gets put in the sdcard directory and I can flash it, but it says "unable to mount storage" and the file is gone after a reboot. Is this because it's encrypted and I'm just hitting cancel when it asks for a password?
abel408 said:
I'm having trouble with this guide. I have TWRP recover flashed, but it isn't working correctly. It says there is nothing in my sdcard directory and my computer won't connect to the phone in recovery. Is this because it's encrypted and I'm just hitting cancel when it asks for a password?
Click to expand...
Click to collapse
Sounds like you missed steps 12 and 14.
rczrider said:
Sounds like you missed steps 12 and 14.
Click to expand...
Click to collapse
Nope... I formatted data and enabled MTD. When I enable MTD, my computer tells my the phone is locked...
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
My bootloader keeps locking itself...
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I can unlock it, but it locks itself after a reboot.
abel408 said:
Nope... I formatted data and enabled MTD. When I enable MTD, my computer tells my the phone is locked...
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
My bootloader keeps locking itself...
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I can unlock it, but it locks itself after a reboot.
Click to expand...
Click to collapse
That's expected and is addressed in the FAQ
You're only ever temporarily unlocking it. You will need to unlock it every time you reboot the phone.
rczrider said:
That's expected and is addressed in the FAQ
You're only ever temporarily unlocking it. You will need to unlock it every time you reboot the phone.
Click to expand...
Click to collapse
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
---------- Post added at 07:45 PM ---------- Previous post was at 07:27 PM ----------
And now I'm stuck... I cannot go back to stock because TWRP doesn't mount the storage.
---------- Post added at 08:01 PM ---------- Previous post was at 07:45 PM ----------
abel408 said:
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
---------- Post added at 07:45 PM ---------- Previous post was at 07:27 PM ----------
And now I'm stuck... I cannot go back to stock because TWRP doesn't mount the storage.
Click to expand...
Click to collapse
I was able to fix this by wiping Internal Storage... You may need to add that to your guide. Thanks for the guide!
abel408 said:
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
Click to expand...
Click to collapse
I can't get permanent root using the AIO Toolkit, but maybe it's just the 2 phones I've tried. I'd love to hear from other users (X522 or other variants) on whether or not their unlock actually sticks after a reboot.
abel408 said:
I was able to fix this by wiping Internal Storage... You may need to add that to your guide. Thanks for the guide!
Click to expand...
Click to collapse
If other folks run into the same issue, I'll add it. I followed my own steps on a second phone (one that had never been unlocked/rooted before and was currently set up and in use) after your post and I didn't have any need to do anything different. I'm wondering if that need arose because you didn't unlock the bootloader a second time before booting into TWRP. If that's the case, the guide works as written, so I'll add it to the FAQ.
I seem to have done something wrong. I'm having a really difficult time accessing the Data partition in TWRP. Every time I reboot into recovery I cannot access the files on the sdcard (it is simply empty). I reboot and the files are still in storage (along with the TWRP backups I made) - I just can't seem to get to them in TWRP. I cannot mount Data because it doesn't appear. There is a box to decrypt data but that then requires a password (which I obviously don't know). Don't want to go any further if I can't seem to have a dependable way to access backups. Any suggestions?
Edit: Enable MTP also doesn't work for me in TWRP so there is no way to bring any files over from my PC while in TWRP - also adb push/pull doesn't seem to be working
skyman88882002 said:
I seem to have done something wrong. I'm having a really difficult time accessing the Data partition in TWRP. Every time I reboot into recovery I cannot access the files on the sdcard (it is simply empty). I reboot and the files are still in storage (along with the TWRP backups I made) - I just can't seem to get to them in TWRP. I cannot mount Data because it doesn't appear. There is a box to decrypt data but that then requires a password (which I obviously don't know). Don't want to go any further if I can't seem to have a dependable way to access backups. Any suggestions?
Edit: Enable MTP also doesn't work for me in TWRP so there is no way to bring any files over from my PC while in TWRP - also adb push/pull doesn't seem to be working
Click to expand...
Click to collapse
If TWRP is asking for a password, that means you missed step 12.
I'm trying to upgrade from 18s to 19s and I'm getting upgrade failed every time. I've tried restoring to factory defaults and restoring my TWRP backup. Seems to be fully on stock now and it still fails. My question is, do you think it would be alright if I restored your 19s TWRP backup so that I am on 19s?
abel408 said:
I'm trying to upgrade from 18s to 19s and I'm getting upgrade failed every time. I've tried restoring to factory defaults and restoring my TWRP backup. Seems to be fully on stock now and it still fails. My question is, do you think it would be alright if I restored your 19s TWRP backup so that I am on 19s?
Click to expand...
Click to collapse
Tell you what: give me an hour or two. I'm currently on non-stock (ie. rooted) 18S and since the Xposed module EUI Moder (http://forum.xda-developers.com/xposed/modules/mod-leeco-eui-moder-t3416932) doesn't work (lockscreen flicker / system UI crash), I don't mind wiping the phone and testing the ability to go back to stock and do an OTA update to 19S. If it doesn't work for me, I'll restore 19S (from my other S3) via TWRP and see if that does it.
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
rczrider said:
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
Click to expand...
Click to collapse
Thanks buddy!
Thank you sir, this worked (almost) perfectly. For some reason on my laptop, I wasn't able to get the phone to connect with debugging (never got the prompt for permission, etc.). No clue why not, I've got drivers and everything, and that laptop works with many other phones. Oh well. Went to a different PC and it worked perfectly.
rczrider said:
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
Click to expand...
Click to collapse
I think I'm doing something wrong @rczrider, but I can't get TWRP to even recognize the backup you uploaded. Do I just drag the extracted files to the TWRP folder?
This guide is supposed to help you root your lg k8 (2016) or k10 (2016) device (i guess any models with and unlockable bootloader and working TWRP).
Not for the 2017 models!
Why "friendly" root? Go see my old guide how unfriendly the method used to be:
https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Guys with latest (2017 febr. 1) security patch read this before you proceed:
https://forum.xda-developers.com/showpost.php?p=71469157&postcount=183
https://forum.xda-developers.com/showpost.php?p=72414225&postcount=250
Short version:
1. unlock bootloader (read step 2.1 if there is no device corrupt message during every boot up after unlocking bootloader!!!)
2. boot into TWRP (i tested with 3.0.0 twrp and above, never tested below)
3.1 install rce_univ.zip (download from this thread: https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327, but follow instructions here!)
3.2 install supersu
3.3 install rce_univ.zip again
reboot
Long version:
The links written with italic fonts are video guides (please excuse me for the quality they were made by my mobile phone)
1. unlock bootloader
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
video guide for above steps: Link Removed by Moderator
- make sure you installed all the drivers for your mobile from lg's site (LGMobileDriver_WHQL_Ver_4.1.1.exe and also lg bridge) - Link Removed by Moderator
- set up adb/fasboot using 15 seconds adb installer: https://forum.xda-developers.com/showthread.php?t=2588979 - Link Removed by Moderator
- go to the folder it's installed (in my case it's C:/adb - adb.exe and fastboot.exe supposed to be there) hold shift and right click "open cmd here" - Link Removed by Moderator
- in the command window type "adb devices"
it will start adb services and will print a line like "...lgk350... or ...lgk420... lgk430, etc"
if you can't find your device there check device manager or google how to work things out
normally in device manager you should find "LGE Mobile USB Serial Port" under Ports - Link Removed by Moderator
- now reboot to fastboot mode typing the command: "adb reboot bootloader"
your phone should go blank and only print fastboot mode on the bottom of the screen
- check your fastboot connection: type: "fastboot devices"
same as before (in my case it was writing some unrecognizable letters - probably wrong coding) if you see nothing then check device manager -Link Removed by Moderator
you may try to install android SDK (command line tool is enough - https://developer.android.com/studio/index.html - bottom of the page Link Removed by Moderator) if the connection is not working - however there must be a way to make it work (i had a hard time in device manager - i changed each driver a million times until it worked)
in device manager you should find "android bootloader interface" in my case its under "samsung android phone" i don't know why but it works
- In case you have a working adb and fastboot connection type (if you lost connection you have to get to fastboot again: "adb reboot bootloader"):
"fastboot oem unlock" - the phone will ask you if you really mean it, using the volume and the on/off buttons (twice) you can accept
you will lose all your data!!! and most likely lose warranty as well!!! Link Removed by Moderator
however your phone shell restart just fine (you have to manually restart it by taking out the battery or boot into twrp and reboot from there. There should be some message during boot up that your system is vulnerable from now on.
- after reboot you may want to check if your bootloader is really unlocked: get back to fastboot and type "fastboot getvar all" and find the line which sais if your bootloader is unlocked (if it's not you may repeat the process)Link Removed by Moderator
set up developer settings again:
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
Link Removed by Moderator
- !!!if there is no device corrupt message during every boot up then you need an additional step i'll describe at step 2.1!!! - Link Removed by Moderator
2. find a working TWRP for your device (i collect them in the first comment below - https://forum.xda-developers.com/showpost.php?p=70375626&postcount=2):
- put the recovery image (e.g "k8twrp.img") into your ADB folder (like c:\adb - where you opened command promt earlier)
- Get back to fastboot again and boot to TWRP - type in cmd: "fastboot boot k8twrp.img" (or whatever your TWRP image's filename is)
- if its not booting into TWRP normally try another TWRP (comment #2)
- on the first screen of the TWRP it's asking for password to decrypt data - just hit cancel
- if you have the device corrupt message during every boot up you can skip the next step (go straight to step 3.)
2.1. in case you have no device corrupt message during every boot up follow the next steps
- on the keep system read only? screen of the TWRP let it allow modifications (swipe!)
- reboot to System
- Link Removed by Moderator
you must see the device corrupt message during boot up -> you are ready to go for a root
- try to reboot the device if the device corrupt message is still there during boot up (Link Removed by Moderator). If it's not there you may repeat the process or check my old guide for troubleshooting.
3. the rooting part -Link Removed by Moderator[/I]
(you can read my old guide why we need to tweak the boot image before installing SuperSU - if you are interested)
- download the ramdisk compression exchanger: https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327 (we need this because SuperSU can only work with gzip compressed ramdisks while we have lz4 compressed ones)
- download latest SuperSU TWRP flashable version: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- put this (rce_univ.zip) and latest SuperSU (i used v2.79) on your sd card (you need external sd because the internal sd is encrypted in TWRP)
- reboot your device into TWRP (through adb and fastboot as before)
- cancel decrypt data
- don't swipe on system modifying screen just click on "keep read only"
- go to backup, backup your boot image (tick only boot partition /untick the rest/ and select storage as micro sd card) in case anything goes wrong during the rest of the process you can always restore it
- go to install
- select storage and chose micro sd card
- install rce_univ.zip (it will recompress your ramdisk to gzip - so SuperSU can tweak it)
- when it's finished don't wipe or don't reboot! Go back (hit back button button) and install SuperSUxxx.zip
- go back again (without restart or wipe) and install rce.zip again (this will recompress your ramdisk to lz4)
- now you can reboot to system (without any wipe) - it will bootloop a few times, be patient!
If something goes wrong check my old guide for deeper understanding and troubleshooting!
If you have any problem with installing rce_univ.zip please post comments to it's thread:
https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327
Comments in this thread shell be only TWRP related or deeply device specific.
No promises... and no responsibility i take... !!!
Supported TWRPs:
in case you want to go for sure or you can't find a working TWRP port it yourself easily using my guide: https://forum.xda-developers.com/lg-k10/development/mtk-portable-twrp-porter-t3536123
or use the ones already ported:
Lg k10 k430: https://forum.xda-developers.com/lg-k10/development/teamwinrecoveryproject-3-0-0-0-lg-k10-t3404434
Lg k10 k430dsy (firmware: 10k - 2017 feb security date): Link Removed by Moderator
(Lg k10 k420n/ds: https://forum.xda-developers.com/lg-k10/development/unofficial-twrp-3-1-0-k420-ds-n-t3571943 - different root method required)
Lg K8: https://forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-lg-k8-k350-mtk-t3517894
others take a look around here: https://forum.xda-developers.com/lg-k10/development
or use this guide: http://www.chinaphonearena.com/foru...752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial
Looks cleverly. May take a try
Could it be this SuperSU?
https://download.chainfire.eu/696/supersu/
a_lewicki said:
Could it be this SuperSU?
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
Well... why would you use that old one? This might not even be systemless root so it would not work. Why dont you check the link i posted in the OP so you could find this one i recommend to use: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
after flashing rce.zip i got an error " unpacking boot image failed! aborting..."
what should i do to fix that? i've tried reading throught your old guide but i'm a noob and i couldn't find anything i could understand.
help anybody???
pedrodgr said:
after flashing rce.zip i got an error " unpacking boot image failed! aborting..."
what should i do to fix that? i've tried reading throught your old guide but i'm a noob and i couldn't find anything i could understand.
help anybody???
Click to expand...
Click to collapse
Next time you try, please make a recovery log (In recovery advanced menu) and send it to me or upload it here!
Which model? Which TWRP?
Also upload or send me your boot image that you backed up!
I added one more line to the script to see where its found the boot partition so please download again before you proceed for a better troubleshooting experience!
@gottlasz after everey install reboot system? (rce.zip then reboot supersu and reboot and rce.zip again and reboot?) or without rebooting?
a_lewicki said:
@gottlasz after everey install reboot system? (rce.zip then reboot supersu and reboot and rce.zip again and reboot?) or without rebooting?
Click to expand...
Click to collapse
No way! Do not reboot! Once you install rce.zip it changes the ramdisk compression so the phone can't boot up. Then the supersu tweaks the boot image (roots the phone) then you install rce.zip to change the ramdisk compression back to normal. Then you can reboot.
@gottlasz thank you so much IT WORKS
a_lewicki said:
@gottlasz thank you so much IT WORKS
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
@gottlasz thank you so much IT WORKS
Click to expand...
Click to collapse
I know it works...
Do you mind me asking which phone you have (k8/k10), which model and which TWRP you used?
gottlasz said:
I know it works...
Do you mind me asking which phone you have (k8/k10), which model and which TWRP you used?
Click to expand...
Click to collapse
twrp 3.0.2
lg k10 k430dse
---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------
[mention]gottlasz[/mention] do you know how to make snapchat working on root?
a_lewicki said:
twrp 3.0.2
lg k10 k430dse
---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------
[mention]gottlasz[/mention] do you know how to make snapchat working on root?
Click to expand...
Click to collapse
okay, thanks for the info. I dont know anything about snapchat. If you just download it from playstore?
yes from playstore but i read this app won't work with root
a_lewicki said:
yes from playstore but i read this app won't work with root
Click to expand...
Click to collapse
I just downloaded and tested. Works without any issue...
gottlasz said:
I just downloaded and tested. Works without any issue...
Click to expand...
Click to collapse
Hmmm that's strange...
On my device I can't login to this app and i read this app won't work with root
a_lewicki said:
Hmmm that's strange...
On my device I can't login to this app and i read this app won't work with root
Click to expand...
Click to collapse
I don't know man... i don't think it's a root related issue. The app should promt if it had any problem with root.
However if you use any paid service through the app that can be an issue. Still.. the app has to write something about root if it has a problem with it.
gottlasz said:
Next time you try, please make a recovery log (In recovery advanced menu) and send it to me or upload it here!
Which model? Which TWRP?
Also upload or send me your boot image that you backed up!
I added one more line to the script to see where its found the boot partition so please download again before you proceed for a better troubleshooting experience!
Click to expand...
Click to collapse
Thanks for the fast reply, it's the k10 430dsf
i'll try downloading it again and give it a new try.
I was also using the twrp 3.0.0
i'm downloading the 3.0.2 now and i'll let you know if it works.
Thanks once again.
Happy new year for everyone:good:
i have the LG K8 (K350F) model.
Can i root my phone with this method???. Anyone with this model has probe this tutorial???.
thanks in advanced
raul2903 said:
i have the LG K8 (K350F) model.
Can i root my phone with this method???. Anyone with this model has probe this tutorial???.
thanks in advanced
Click to expand...
Click to collapse
If you have a working TWRP then its gonna work. Did you test any TWRPs already?
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Needed tools : Backup your phone before following any steps
1. Minimal adb and fastboot
2. official TWRP 3.3 for jasmine_sprout Download img file from twrp website
3. latest magisk manager 19.2 zip file from magisk manager website
First step : Boot loader unlock
1) Tap on build number more than 7 times and unlock developer option in about phone.
2) turn on OEM Unlocking and USB debugging
Now open command windows in adb shell folder and connect your device to computer.
type : 1) adb devies (this should show your device after giving permission in your phone : conformation that your device is
connected)
2) adb reboot bootloader
3) fastboot devices ( conformation that your phone is coonected in fastboot mode)
4) fastboot oem unlock
( after that you need to follow according steps in your phone and grant to unlock phone)
keep in mind this will reset your phone. Afteer reboot again turn on developer options and usb debugging
5) fastboot flashing unlock_critical
( the warning and steps you need to follow again in your phone like in step 4)
this will again reset your phone.Afteer reboot again turn on developer options and usb debugging
Congratulations your bootloader is Unlocked now.
STEP 2. Flashing TWRP and Magisk Install
before that keep in mind As Mi A2 follows A/B boot partition system so DONT DIRECT FLASH TWRP FROM
FASTBOOT.
" Dont forget to turn on developer options and usb debugging "
open command window in adb shell folder and boot your phone in bootloader mode as told earlier and connect to computer.
Copy twrp-3.3.0-0-jasmine_sprout.img to minimal adb and fastboot folder. you can rename it to your convenient name
type : 1) fastboot boot twrp-3.3.0-0-jasmine_sprout.img
or if you renamed it
fastboot boot YourRenameName.img
this will temporarily boot twrp in your Device. As twrp is booted you will be able to see your phone connected in computer
(file transfer mode)
Copy and paste both magiskmanager.zip (current latest stable is 19.2 ) into phone
Flash your downloaded version of Magiskmanager.zip
Reboot your Phone.
Congratulations If nothing goes sideways Your phone is Magisk Rooted.
If you want to flash something using TWRP now is the time Otherwise as Mi A2 has A/B slot form and no Recovery Partition You Cannot flash TWRP permanently.
But You can always boot TWRP from adb and use it.
ROM flashing help
Can't flash ROM after using this method
Torque422 said:
Can't flash ROM after using this method
Click to expand...
Click to collapse
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Failed
No such a directory problem, please help
Please elaborate more about the problem ? @shahidrok
shahidrok said:
No such a directory problem, please help
Click to expand...
Click to collapse
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
TYPHOON9055 said:
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thanks ?, i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now?
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Hve done everything but when i try to reboot to twrp it gets stuck on twrp logo,dont know what im doing wrong.
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
I get error 1 during flashing
Amnvlad said:
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
Click to expand...
Click to collapse
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Alucard said:
I get error 1 during flashing
Click to expand...
Click to collapse
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic ?
Torque422 said:
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic
Click to expand...
Click to collapse
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
Available custom roms are for Oreo versions if you have updated ur device to pie , it won't work.
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
I was on stock pie + may update (10.0.9)
Follow this way , unlock the bootloader via fastboot oem unlock, fastboot flashing unlock it will reboot here, goto developer settings Enable usb debugging
Then do this fastboot flashing unlock_critical It will again reboot
Now, install the magisk app And download the patched boot image from internet Whatever your build no is, mine was 10.0.9 so i downloaded version 10.0.9_boot.img
Open the magisk app, click on install , select and patch a file, Then choose this downloaded patched image, it will flash it successfully, if it don't Then you have mistaken something..
After this there will be a patched.img in download folder Which is just created by magisk, copy this img to pc, Through fastboot Flash it "fastboot boot patched.img"
Now, flash TwrpImage3.3.img through fastboot
When you boot in , Copy and paste your rom, gapps
Now flash twrpVersion3.2.img via fastboot
Clear system,data,caches, Flash the rom in slot B
Now flash the twrp3.2.zip through installed twrp, click on recovery And it will boot to twrp
Now Flash the gapps in slot a (i used nano)
Now flash magisk.zip through twrp
Reboot , That's it!
(Twrp 3.2 is stable for flashing rom and gapps , Just for first time When we coming from stock
Twrp 3.3 latest Gives us MTP transfer, The difference is this in using both of these)
Installation of magisk is the last process, it is part of rom, First installed ur desired rom and then magisk
You said, You installed twrp, as i mentioned above You forgot to do some steps as about patched boot + installation of magisk through patched file etc..
Though you can try to search on google for your next step
patched supported magisk Version x.x.x for mi a2
If you got the file, You are lucky.. otherwise flash the stock rom with mi flash tool
And Start from unlocking bootloader
Magisk Module available.
Torque422 said:
Please elaborate more about the problem ? @shahidrok
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
Thanks , i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Click to expand...
Click to collapse
There is a magisk module available for installing kali nethunter in this device. i never tried installing it but it should work fine. Read proper descriptions before installing it though.
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
the adb recognized my phone but fastboot do not, help me out please
Andrew.kathy said:
the adb recognized my phone but fastboot do not, help me out please
Click to expand...
Click to collapse
Probably a problem with drivers, check and reinstall drivers
Can i use this method to flash magisk on Mi 9T pro?
I can't boot into twrp
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Topper8118 said:
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Click to expand...
Click to collapse
Checklist:
- there is file of <compatible TWRP recovery> in ADB/Fastboot directory with the name you are typing in fastboot command
- ADB drivers installed correctly (both "adb devices -l" and "fastboot devices" return valid results in corresponding phone states)
- only one phone (namely MiA2) is connected to PC
- phone fully unlocked (OEM debugging enabled and PC was previously approved for ADB in phone)
- USB port on MB of PC is USB-2.x or USB-3.x-compatible-with-Mi-A2<which is not true in general>
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
HTCDevil said:
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical
Nubia Red Magic 5G and 5S Roms and Root support Thread
Second post for TWRP and Magisk installation. Mirror for all roms and tools at end of post
Latest Official Rom updates
Android 11
US/Asia - V8.70 Nubia Link MD%: will update soon
EU - V7.70 Nubia Link MD5: will update soon
China - V9.50 Nubia Link MD5: 361AC13CA52AB83C239783FBAB088CEA
Android 10
US/Asia - V8.12 Nubia Link MD5: 6e930fc2431b3daeae2d94145926a6c1
EU - V7.15 Nubia Link MD5: bb9e3153716851e87f196ae6b4f44a2e
China - V6.23 Nubia Link MD5: BD447840ACA4D48F9443B94D2EAD890F
Change Log - 8.70 / 7.70 Android 11
- Security Patch October 2022
- Game Space enhancements
- Game space Gyro sensitivity menu
- game space touch sample rate improvement
- Fixed: corner of screen non-touchable in some cases
- Fixed: issue where game would fail to close
- Fixed: location of caller display
-Fixed: screen tearing when using 144hz
-
Bugs -
in Testing
- Always on display notification not showing
- memory leak in nubia launcher (requires forced close often to stop phone from lagging)
- small window mode for telegram and discord have wrong zoom/ aspect levels.
_____________________________________________________________________________________________________________
UNBRICK TOOL for 5S - Courtesy of @johnny886
Use this tool, with directions on the thread to restore your device to USA/Asia 8.07
you can then install TWRP and after flash any region rom after creating a somewhat universal unbrick tool for those in different regions.
Follow directions on the thread. but here is a link to the Thread. A Mirror for the tool is in my Personal Mirror at the bottom of this thread post.
Link to Thread
Confirmed working with 5G devices - but its recommended to update as soon as you unbrick.
_____________________________________________________________________________________________________________
For unlocked bootloader
Fix your fingerprint sensor.
here Link
--------------------------------
Update Instructions.
Note
for Android 11 do not flash through TWRP you will softbrick.
____________________________________________________________________
For Stock devices without root
- disable security. No pin, no face unlock, no finger print, no pattern. remove all security.
-download zip file
-go to system update tap three dots and select local update
-Navigate to update.zip and select.
-your phone will reboot and install new rom
- you phone will reboot once more and you will be greeted with your lock screen
- setup Phone with security options as before flash.
For devices with "LOCKED bootloader" Root / TWRP (not tested on A11)
- take backup of vbmeta and recovery partitions in TWRP
- change the name of both files to vbmeta.img and recovery.img
(VBmeta is often 64kb big and Recovery is often 90+mb big.)
- copy and paste these new img files into the update zip.
- flash through TWRP
- go back to main menu, select advanced, then select option
"disable replace TWRP" to keep TWRP as your recovery.
for devices with "Unlocked bootloader" (not tested on A11)
-make full backup
-download zip
-install zip through TWRP
-reboot
__________________________________________________________________________________
Custom Roms and Kernels
Kernel
Mattofthedead's Redmagic 5S kernel for LOS and Stock roms LINK
Roms
Rom Builder Ra's Custom Roms - Please post any bugs or issues in the related threads.
Pixel Experience Plus
Ressurection Remix
NOTE : to boot any Custom rom on the 5S device. Flash the Rom following the directions. then flash Matts LOS kernel Version 3
__________________________________________________________________________________
------------------------------
Old roms
Android 11
V8.65 Nubia Link MD5: 3d52e18c66366d3d23744184425d3926
V8.64 Nubia Link MD5: a7e61f5e2f7c377a6850cf6ac3a62aa7
V7.65 Nubia Link MD5: 746dad5b6145dfba1108355095a6ad46
V7.64 Nubia Link MD5: 55371ee8e5728aee2bc7df5b3a7d6585
V9.42 Nubia Link MD5: D492B92DD83B366508CDD74DE7D152A3
V9.40 Nubia Link MD5: D28F26289A9B75F771EF4F623F0BB367
V8.57 Nubia Link MD5: 266819d4b09c2c52aadb39e948dc84bc
V8.59 Nubia Link MD5: d7e32b7a3e833adc57fcf734aa47f5a3
V7.57 Nubia Link MD5: 81ee71869f660a28b631d871ffb59524
V7.60 Nubia Link MD5:
V9.26 Nubia Link MD5: 8997375CD97D8F7F261F21121FC8EFAA
Android 10
v6.18 Link MD5: 9AC5EA5F64835C1995E4A81D4973FB71
V6.13 Link MD5: F38ED2D7CB58252D308B29D1D4517DB9
V7.07 Link MD5: ffc3fdaf4afc522aa3a084d9275f2cb6
V7.14 Link MD5: 0f879160fbf8b556de5303207b93d0d1
V8.07 Link MD5: b30dab221be73292c5da7884afc0363f
V8.11 Link MD5: 85d9366a3017112cb68d66041e725ce6
________________________________________________________
Personal Mirror - Located in Eastern Canada
________________________________________________________
TWRP and root guide for 5S and 5G on Android 10 only - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked during and after process is complete.
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put an installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file found at the end of this post
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted. (CD = Change Directory)
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable replace TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Reboot to system for the first time and complete the initial setup. this is to create the user space partitions data/media ( preferably do not make a pin or pattern at this stage)
13. once in the rom, connect to PC and copy over the Magisk zip to the internal memory. then reboot holding Volume up
14. once back into TWRP (if you created a pin during setup TWRP will ask you for your pin to access data) go into install and flash the Magisk.zip you moved in step 13 then reboot. once back into the rom, you will see a Magisk app, tap it and allow to update, the APK will install latest version of the manager.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have an update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini - zip updated with Magisk 21.4 zip
MD5 for ADBfastbootmini.zip: 0ad97a9ae1539b26ef78c849b169e807
I'm working on a process that will update to Android 11, through TWRP and root, without losing data. Much like a stock update.
I will update the thread once my tests are complete.
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
josehdx said:
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
Click to expand...
Click to collapse
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Patrick Morgan said:
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Click to expand...
Click to collapse
Thanks
Working fine after full data partition wipe.
I have an additioal question regarding further updates, and i would not want to open a new topic. so, after flashing the zip, i "lost" TWRP but i already have root access. I wonder if is possible to flash upcoming updates with the default recovery built in on the phone, if not, i would assume i need to install TWRP again.in any case, will side loading update make any problem with the current system? i hope my question and context is clear
As these are official ROMs, they will replace the recovery and remove root from the phone.
If you do not have root, flashing these zips from the system menu local update should work. But if you have root or TWRP it's better to flash through TWRP.
You could just flash TWRP again after flash, but I personally modify the zip and add the recovery to it to save me going into fastboot after each update.
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Darkvenum79 said:
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Click to expand...
Click to collapse
I've spoken with another EU rom user, that has the same issue before. it seems it was an error in the stock rom.
reinstalling 7.07 from the links above should fix your problem.
both 7.07 (the EU rom) and 8.07 (the US rom) are exactly the same. the only difference is the languages from what I can tell.
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
No it wont.
There is a specific step by step that is required to get it functioning again. And it only survives until your next full wipe, which i assume you will do more often flashing non official roms.
I can grab the steps and edit this post for you.
Edit -
Prep.
have a black / very dark brown leather. (belt, wallet, etc)
a soft gel plaster / Bandaid
(something skin textured and in a pink / light beige colour) texture and colour are important.
First step is clear data in the infingerprint app in app info and remove permissionfor data memory - (you need to show system apps to find it)
- digit in call phone code:
*#9959#
(android 11 use Activity launcher (playstore) to enter fingerprint menu)
- uncheck performance checkbox , check only calibration checkbox
Steps -
1. Press start then wait.
2.Press next and with plaster / bandaid press on circle
3.Press next and use wallet / belt ( the display becomes black for black calibration)
4.Press next and use gel plaster / bandaid again but pinch it in so only the part with your finger touches the circle.
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access to data memory then reboot device.
Enjoy your Finger Print once more!
P.S. = do this procedure in a very dark room to improve the chances of it succeeding.
Thanks to qtr1st (Salem) and mikekrunk (Mike) for the steps and information.
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Patrick Morgan said:
TWRP and root guide for 5S - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked after process is complete.
Pretty short step by step to get twrp and Magisk if you want, on your phone. (Red Magic 5S)
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put a installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file attached or mirrored
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted.
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have a update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
where is the link of twrp.img
sansha1211 said:
where is the link of twrp.img
Click to expand...
Click to collapse
Patrick Morgan said:
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
that file called Link ADBmini has all you need
Is it ok to flash Eu rom to my NA/asia rom?
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
reboot to bootloader by... power off device -> press and hold volume down and power button until you see the logo -> connect device to your computer then do the steps 7 to 12
also once you are in TWRP make sure you ... this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
if you have not removed your pin before flashing any of the roms. it asks you for YOUR own pin that you made when you setup the phone. so use your own pin.
the process of rooting your device, clears a security partition. (the VBmeta partiton)
this deletes the encryption you had on your phone. so the devices partitions are unaccessable and need to be wiped before you can boot to system.
you need to clear data. all data. then check in TWRP file browser if your data partition is clear. .. if you see folders with random letters its not been formatted correctly.
so, in the wipe menu on TWRP you should go into advanced and change the partition type to ext4 then back to f2fs to clear the partition of data.
once your phone is clear you should be able to wipe cache and davik then reboot to system for it to start like a factory reset.
sansha1211 said:
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
where is the link of twrp.img
Click to expand...
Click to collapse
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing lock
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
via cmd -- fastboot flashing lock
After i reboot in TWRP and disable replace TWRP, i install magisk from a USB otg, and then i wipe all data, then i reboot system but it keeps opening TWRP in every reboot, i had to install Stock Rom to have my phone back but without root, what im doing wrong?? thanks
Edit: now it worked, tried a few times and worked don't know what failed