Related
Hello, guys this is my first post but i am quite sure that my methods work.If there any problems then u can surely ask in the section below. This thread will be a GUIDE TO ROOT AND INSTALL CUSTOM RECOVERY FOR MOTO G 1st Gen users.
Some prerequisites are:
1. Motorola drives (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481)
2.Fastboot and recovery files (https://www.dropbox.com/sh/9jf2va51ffg0pzq/AAAxDT-ETf7AESIcHGnfEgv7a?dl=0)
[ Let these files be downloaded and kept in Cdrive of ur pc and and place them on the desktop.. Please name this folder MOTO FILES]
3. SuperSu files https://download.chainfire.eu/696/supersu/ and[/url] paste it in ur phones internal memory and please do this after unlocking the bootloader cause bootloader unlocking will delete everything so its better to do it after unlocking bootloader
Download these files and ur done... Now lets continue to the fun part
This process involves three very simple steps :
1. Unlocking the Bootloader:-
This process is infact very easy to do. There are several guides on the internet regarding this process but the one that i suggest is by High On Android/ Max Lee . Follow his method and u can very easily unlock ur bootlader. Copy this url and see it for urself fellow guys...http://highonandroid.com/android-smartphones/how-to-unlock-bootloader-on-motorola-android-smartphone
2. Erasing ur previous recovery and installing a new one and rooting ur phone all in one process
Some users have been reporting that even after installing custom recovery , whenever they go into recovery they enter into stock recovery. The actual problem is that the stock rom of the Moto G rewrites over the new custom recovery installed.
So we have to install the recovery actually twice but it only takes a few minutes
i) Firstly be sure to have lots of juice in your phone
ii) Boot ur phone into the bootloader by power offing ur device and then pressing the volume down and power button together for 10 seconds and then leaving both of them together.
iii) Now connect ur device to ur pc/laptop
iv) Now open a cmd and enter the following commands(press enter after every command)
- cd Desktop
-cd MOTO FILES
-fastboot flash recovery Recovery2.img
-fastboot reboot-bootloader
[MAKE SURE NOT TO REBOOT UR DEVICE ]
v) Now ur phone has custom recovery installed in it and u shud now enter into recovery mode by choosing the option from the bootloader, by pressing volume down and then volume up while in bootloader mode.
vi) This will open the Philz recovery that i have provided with. I prefer the philz recovery over the cwm one. Now go on and install the SuperSu update zip file. And BOOM ur Device is now rooted !!!!.
vii) Now reboot ur phone and u must install
-ROOT CHECKER (to check root)
- and most importantly ROOT EXPLORER
viii) After following step (vii), now if u try to go into recovery, u will be booted to stock recovery. So to prevent that use the ROOT EXPLORER app and go to the root \system\etc and delete the file named install-recovery.sh .
ix) After deleting the file u will once again have to follow step (iv) and install custom recovery this will ensure u having custom recovery even after rebooting ur device and u will have ROOT access as well
On which android version , were you on before rooting . 5.01 or 5.1 .
This method works for both 5.1 and 5.01
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Is the first post too heavy for you?!
Follow the steps and be happy.
Gesendet von meinem Moto G mit Tapatalk
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Andus1988 said:
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Click to expand...
Click to collapse
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Ajay P said:
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Click to expand...
Click to collapse
whats the problem u facing ?
sanilch99 said:
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Click to expand...
Click to collapse
It could cumber the inbuilt root!
sanilch99 said:
whats the problem u facing ?
Click to expand...
Click to collapse
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Ajay P said:
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Click to expand...
Click to collapse
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
sanilch99 said:
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
Click to expand...
Click to collapse
Thank you
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
notuger said:
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
Click to expand...
Click to collapse
I will recheck that super su. file and make sure its perfect... Thanks for the response:good:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Works but could be simplified
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
issam029 said:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
i have edited the previous link and given the new one. You can use this SU file. It will solve ur prob.
pcgardner said:
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
Click to expand...
Click to collapse
Reinstallation of custom recovery is not must its just for safety precautions and I have finally updated the SuperSu link. As far as Busybox u will have to install it customly only.
issam029 said:
once i finished steps all, when i open supersu, popup window says, "there is no su binary installed, and supersu cannot install in it. This is the problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
If i check with root checker,
sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
use the new su files i updated the link
facing problem after unlock bootloader mood for moto g 1st gen
Thanks a lot for your information...:good:
Bro!! I have already unlock bootloader mood.. Before rooting is it necessary to clear all data & app...??
Hello Guys,
At first a little background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately, I applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
I am not responsible if anything goes wrong.
Ok, so let's get started:
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Windows: https://forum.xda-developers.com/showthread.php?t=2588979
Linux/Mac: http://rootmygalaxy.net/install-adb-and-fastboot-on-mac-or-linux/
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of your choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip not working anymore, official link:
http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201801.zip
-As many of you are experiencing problems with my previously mentioned TWRP 2.8.7.3 version I am replacing the link with the official TWRP Shield Tablet Download Site. Just take the newest stable version: https://dl.twrp.me/shieldtablet/ (Put the file into the ADB+Fastboot Folder)
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder): Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "sudo" in front of it...)
Mac:
You also don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "./" in front of it...)
Flash Recovery
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installed, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
EDIT: 4.1 To enable the fastboot protocol, you must select "Fastboot mode" on the Tablet. After that type
Code:
fastboot devices
in order to check if fastboot is enabled.
5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. Now you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-x.x.x-x-shieldtablet.img
6.2 Wait until it is finished then navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a custom rom
Custom Rom
If you want to be on the safe side you should consider wiping the /data partition (Troubleshoot section at the end of the Post)
1. You can access your tablet from your PC
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice.
2.1.1 Cyanogenmod 12.1 (Android 5.1.1) and BlissPop v4.0.3 https://www.androidfilehost.com/?w=files&flid=150249
2.1.2 Cyanogenmod 13.0 (Android 6.0) https://androidfilehost.com/?w=files&flid=27600&sort_by=date&sort_dir=DESC
2.1.3 Nvidia Shield Tablet Resurrection ROM (Android 6.x) https://androidfilehost.com/?w=files&flid=60681&sort_by=date&sort_dir=DESC
2.1.4 BlissPop
2.2 Download Google Apps (Gapps) (ARM Device)
2.2.1 Android 5.1 http://opengapps.org/?api=5.1&variant=stock
2.2.2 Android 6.0 http://opengapps.org/?api=6.0&variant=nano
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
3.1 Now go to Wipe. For a dirty flash you will only need to wipe the Dalvik and Cache for a full wipe select Dalvik, System, Data, Cache
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips and select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
For Android 7.0 (Nougat) the SuperSU r4 2.78 version is confirmed working.
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installed
Xposed Framework
Download the Xposed Framework Zip file, take the newest version:
(The Shield Quad Core has a 32 bit arm architecture, so you need the framework for arm)
SDK21 for Android 5.0: http://dl-xda.xposed.info/framework/sdk21/arm/
SDK22 for Android 5.1: http://dl-xda.xposed.info/framework/sdk22/arm/
SDK23 for Android 6.0: http://dl-xda.xposed.info/framework/sdk23/arm/
and the apk: https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
and move them to you Tablet.
Developer Thread (for the uninstaller): https://forum.xda-developers.com/showthread.php?t=3034811
Go to Recovery with Root
1. Now that you have root you don't need you PC anymore. Go to the Play store and download Quick Boot
2. Open Quick Boot and klick on Recovery
3. Allow Root rights and the Tablet should boot into recovery
Go to Recovery without Root
1. Shut down your Tablet
2. Press and hold the Vol down button and the Power button until the Bootloader screen appears
3. Navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
Install Xposed Framework
1. In the TWRP Recovery (Optionally you can make a Backup) select Install and choose the xposed-v80-sdk22-arm.zip file
2. When you get an Error let me know
3. Now Restart you Tablet and install the .apk file normally
4. In the App Press Framework and now there should be a green writing saying: Xposed Framework version 80 is active
5. Here is a list of very useful programs for the Xposed Framework: http://forum.xda-developers.com/android/general/best-xposed-modules-android-t3103027
Please Leave a post if you are getting errors or something isn't clearly explained! And if I could help you, consider giving me a Thanks
Troubleshoot
If you are stuck in a Bootloop:
Without data loss(e.g. when you installed Xposed framework zip and its stuck in a bootloop)
1. flash the stock rom boot image BUT ONLY IF YOU DONT USE A CUSTOM ROM (it will probably loose root). go to https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet K1&tx=$additional,shield and download the latest NVIDIA SHIELD Tablet K1 Recovery OS Image
2. Unpack the zip file and flash it to your Tablet
Code:
fastboot flash boot boot.img
If something went wrong while flashing a custom rom (after that you will need to flash the custom/stock rom again)
wipe the /data partition. It could be encrypted from the previous rom. Be aware that you need to reinstall the rom, therefore loose all your data. Troubleshot guide by agentbob123
-Toby
Credits:
@xsquid mac support
@agentbob123 suggestion to mention to wipe the /data partition as a solution for being stuck in a bootloop
@champs777 suggested the newest TWRP
@grävling mentioned importance of waiting until the recovery flash is finished
Toby9 said:
Hello Guys,
At first a litte background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately i applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
Ok, so let's get started:
I am not responsible if anything goes wrong.
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of you choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder):
Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a sudo in front of it...)
Mac:
2016/02/16 Please leave a post if you how to do this
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installen, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
5. Before you can do anyting you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. No you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-2.8.7.3-shieldtablet.img
6.2 Wait until it is finished then move with the volume buttons through the Menu on your Tablet an choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a cutom rom
Custom Rom
1. You can access your tablet on your pc
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice. I decided to use Cyanogenmod 12.1 (Android 5.1.1) http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
2.2 Download Google Apps (Gapps) (ARM Device) http://opengapps.org/?api=5.1&variant=stock
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips an select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installen
Please Leave a post if you are getting errors or someting isn't clearly explaned!
-Toby
Click to expand...
Click to collapse
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
xsquid said:
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
Click to expand...
Click to collapse
Thank you I added this in guide
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
Try other TWRP versions like 2.8.7.0 or 2.8.7.1 i think the 3.0.0.0 is for Andoid 6.0 devices so if you are currently in the newest version of the Android OS try this one out
The 3.0 versionof TWRP was unstabel on my device so you should flash it wipe the storage and flash one of the older ones
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
fards said:
Try deleting recoveryonboot.p in /system
Click to expand...
Click to collapse
Credit to fards.
xsquid said:
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
Credit to fards.
Click to expand...
Click to collapse
How can I remove this file without root ?
SonicDBZFan07 said:
How can I remove this file without root ?
Click to expand...
Click to collapse
Try your normal command line for flashing recovery except change flash to boot. It doesn't flash it, just boots to it.
In other words, if you are using:
1. Fastboot Flash recovery recoveryname.img
Do instead:
2. Fastboot boot recovery recoveryname.img
While in recovery (make sure the supersu zip is on the sd card or wherever you normally flash files from first) flash supersu. You should now be rooted but without a recovery.
Go then to delete the file and then reboot, flash the recovery as normal (#1), reboot and then it should be good to go. It was for me.
rooted device no need to unlock bootloader it will unlock for ittself
just go to playstore and dowload twrp manager
choose the name of your device
and choose one of the two versions available
for shield tablet the version 3.0.0.0 doesnt work well it spilts the screen but wthe other version Works great
the link is twrpmanager on play.google
this way you dont need to connect your tablet to your pc
Great work!
Thank you for the awesome guide. Besides deleting the TegraOTA apk, is there any other app/service that I should disable to prevent OTA updates?
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
diji1 said:
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
Click to expand...
Click to collapse
I'm sorry that you had that problem but this guide is a general guide and not an screw nvidia (besides they are awesom giving us a really good tablet for 200 Buck, but jea?) guide. TWRP v3.0.0 has his bugs so generally when you have finished deleting the stock rom you should flash TWRP 2.8.7.3 works the most stabel.
Trafalgar Square said:
Great work!
Click to expand...
Click to collapse
Thanks, i appreciate that
Add TWRP to M image (Shield 1.1)
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
psychic99 said:
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
Click to expand...
Click to collapse
After you flash twrp reboot to recovery. I may be wrong, but I think the stock ROM overwrites the custom recovery at reboot. If you reboot to twrp first after flash, twrp will disable this.
Sent from my SHIELD Tablet K1 using Tapatalk
Rooting
Hi everyone,
Yesterday got my new Nvidia Shield Tegra K1 and upon using it I noticed it's a great tablet for it's price range and will do my job easier while flying my Phantom 4. To be honest it's seems very stable and solid but was thinking about rooting it. I have some questions regarding the process wince I haven't rooted anything since my HTC Fire, log time ago that was. What are the benefits of rooting this device ? Will I still be able to update the Shield with its official updates ? Will I be able to roll back to an unrooted tablet should I need too ? I wasn't planning on flashing a custom rom but if I'll do what are the pros and cons of doing so ? I know that maybe searching this forum I would find all the answers needed but since there is so much information and threads I'm lost as from were to start from.
Would be nice to guide me about how to properly root my device with all the necessary links. My tab is running on Android 6.0.
I thank you so much guys for the hard work you all do in providing such information. I know it takes a lot of time and patience.
I just got a Shield K1. I like it a lot but I wanted to root it. Then I saw how confusing it is to distinguish between it and the previous model. My guess is whatever is out there that says Shield Tablet means the old one not the K1. I also updated mine to MM cause I'm using and 128GB micro sd card for internal storage. I guess I'll just have to wait until more support comes out for this tablet such as a stable TWRP 3.0 Recovery and the ability to gain root access and custom ROMs like CM 13.
do you recommed to install all OTAs before install custom recovery and custom roms or is it better to install twrp-2.8.7.1 out of the box and then go for the custom stuff ?
I would install all updates to get the latest bootloader. Do not install twrp 2.8.7.1. Install the official 3.0.x from the official site.
Hi to everybody
I'm doing this thread because I've seen that there's a lot of confussion about how to install all this things properly, and I think that concentrating the wide-spread information could help you to get rid of this. First of all I have to thanks @aaawqw and @Moyster for their great efforts.
This is going to be a recopilatory of several sources and personal tips to help you to do this the easiest way. I'm not responsible of bricked phones nor your personal problems.
Please, read the full tutorial before doing anything, to avoid bricks and those things.
PREPARE THE RECIPE
Download these files:
- Unlocking bootloader tool: HERE
- TWRP image from Moyster (creator of LOS14 for our device): here
- If you want to install a modified version of FlymeOS, use this one from Romul35 from 4PDA: here. Original post
- Last LineageOS 14 build: from this thread. PLEASE DON'T FORGET TO THANK THE DEVELOPERS
- GApps: here I recommend the nano option. Choose ARM64 and Android version 6.0.
Put those three last files into your internal memory. If you've got an microSD card, I recommend you to put them into it (it's safer and easier).
UNLOCKING THE BOOTLOADER
To unlock the bootloader go to:
- Kevin.MX @aaawqw) post: here
Finally we have a guide to unlock the bootloader of Meizu m2 note. We need Mediatek SP Flash Tool, MTK phone drivers and the images/bin files for unlocking. No modaco superboot, no fake tutorials any more
Now here's the guide:
1. Download the files I provide
Then unzip it. You'll get a folder with FlashTool, Phone drivers and unlock images.
2.Install drivers for Mediatek platform.
3.Flash the temp-unlock-secro.img via Flashtool. (secro row)
4.Flash secro.img, lk.bin, preloader_meizu6753_65c_l1.bin via Flashtool. (secro, lk and preloader rows respectively)
5.Disconnect USB data cable and power on the phone. If you see the "=>Normal boot" sign(it's quite small.......) in the left bottom cornor of the screen, then the unlock is done. You can now flash things in whatever way you like. The guide is over~~~
The full tutorial is here
The unlock tool is here
Thank you for testing&trying!
If you've seen this spoiler and didn't thank Kevin, please go to here and thank him. This motivates him and gives him the recognisement he deserves.
- Robot Hijau 97 Youtube video: here It isn't in English, but may help if you find any problem or get lost during the unlocking. Leave him a like if it helped you.
This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights )
THIS METHOD DOES WORK FOR M571H MODEL. DON'T WORRY, THE ONLY ONE THAT GIVES SOME ISSUES IS THE M571C.
The great user @aaawqw states "And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions"
Tips to unlock the bootloader easily:
- If you're going to do it from a Windows 10 or 8 pc, have in mind that to install unsigned drivers you'll have to unlock the feature in your pc. A guide to do this: here
- Select the images to flash and hit the Download button before connecting your Meizu (pressing Vol Down button). This will help you if it turns on and off and makes the flashing impossible.
- Download the guide or see the video to correctly follow all the steps. You don't want to lose your phone, don't you? Don't try to mix guides, because you may skip a step and brick your phone. The video and Kevin.MX guide are the same procedure, they both are safe.
INSTALLING TWRP
Once done this part, we'll proceed with the installation of TWRP recovery image. There are two ways, choose the easier to you:
- Flash TWRP from SP Flashtool (original idea from @widagdag. The post: here)
+Turn off your device
+ By using your pc or laptop, extract the TWRP zip for meizu m2 note, there's a file "recovery.img"
+ You can flash it via SP flash tool (clicking the recovery, then select the file)... then click Download, wait until finished!! (Check symbol)
+ You can reboot ur device now, unlocked bootloader and installed twrp!
*The profit is u didn't need to root first and install any flash tool such as Rash, FlashFire, Flashify, etc. saving you some time
Click to expand...
Click to collapse
- Flash the recovery image from Flyme:
+ Get root access (if you do, skip this step). You can get it downloading Kingroot: here. Just install this apk and follow the steps
+ Unzip TWRP zip into a known folder
+ Download Flashify from the Playstore
+ Grant superuser access
+ (Optional) make a backup of your current recovery going to backup tab
+ Tap Recovery Image
+ Choose a file
+ Find TWRP img that you unzipped before and flash it
Click to expand...
Click to collapse
INSTALLING CM AND GAPPS
We're close to the end of this post. The final step: installing your desired ROM and GApps. I will flash CM from the thread whose link is at the download section.
I hope you've put it into your memory (internal/external) as we said
Ok so:
- Turn off your phone
- Go into the TWRP recovery (Vol up+power)
- (Optional but recommended) Make a backup of Flyme, just in case you don't like the new ROM and would like to go back to Flyme. If it takes up too much memory, move it to your pc after making the backup.
- Go to Wipe menu
- Go to advanced wipe
- Select these:
+ System
+ Cache
+ Dalvik Cache
+ Data
- Swipe to do the wipe
- Go to install.
- Select your zip image (in my case the cm13 I downloaded).
- Install also the GApps zip file you downloaded
- Restart to System, and check what you've done.
Some final tips:
- Make the backup, seriously, it takes 10 min and you'll have a Flyme backup if you don't like CM.
- If you want to transfer all your apps and their data from Flyme to your new ROM, use Titanium Backup.
- If you want to install Xposed Framework, it's the same procedure: enter into TWRP, tap install, select the zip and swipe.
- This won't delete your images or videos, but I would recommend to transfer them to a microSD card or your PC.
- Yes, you need to do all this to install a custom ROM. Yes, even unlocking the bootloader. Don't try to skip a step if you aren't sure about what you're doing.
I think that's all, I'll update this post if I lost anything.
I hope this helped you to move into CM world. If you have any doubt don't hesitate to ask.
I know this seems exhausting, but trust me, it worths it. Welcome to the custom ROMs world in your Meizu M2 Note. Let the magic begin.
ADDITIONAL GUIDES
RELOCKING THE BOOTLOADER
If you want to relock the bootloader just follow this simple steps:
Flash the original recovery image from Flashtool of from Flashify (the steps are the same as installing TWRP). You can find this image here
From there, install an update.zip (download them from the official flyme web: here and put it into the storage )
Now you have flyme again with a locked bootloader.
INSTALLING FLYME WITH TWRP
It's very important that you don't install an update.zip from the original Flyme page, because you will cause a bootloop. To get the flyme updates, you can follow one of these two methods:
METHOD 1: 4PDA
-Download the modified zips from 4PDA: here]. Translate it to English. It's on custom firmware>Flyme
-Flash them from TWRP
METHOD 2: DO IT YOURSELF
-Download the update.zip file from the Flyme page
-Open it and remove the preloader- files
-Flash it from TWRP. It will give you an error: IGNORE IT.
Reboot and done, you've got Flyme and TWRP.
UNBRICK A PAPERWEIGHT
BIG THANKS TO @numpea FOR THIS:
This just a firmware that has all the partitions and can be used to unbrick to device using SPFlashtool
Here is the link:
FIRMWARE
- Flash temp_unlock_secro.img with sp flashtool like you do when unlocking the bootloader.
- When done, disconnect the device and add the firmware to sp flashtool. You need to select "format all+download", click on "Download" and connect the device. The flashing process will start. After it finishes, the device will start again.
You wil notice that you lost your imei number you can add it back by:
Using MTK Engineering Mode (does not requires root)
Open engineering mode » Click on Engineer Mode (MTK) » Swipe left to Connectivity » click on CDS Information » Radio Information
Click on phone 1 if you want to change your sim 1 or choose Phone 2 to change sim 2 IMEI, follow this guide:
For Phone 1: “AT+ EGMR=1,7,â€YOUR NEW IMEI NO†(make sure you add a space in between AT+ & EGMR)
For Phone 2: “AT+ EGMR=1,10,â€YOUR NEW IMEI NO†(make sure you add a space in between AT+ & EGMR)
Using Chamelephon (requires root, but much more easier)
Just copy the IMEIS from the phone's box and put them into the app.
hope this is helpful
Click to expand...
Click to collapse
I'll keep updating the info!
Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks !
Moyster said:
Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks !
Click to expand...
Click to collapse
Moyster xDD :laugh::laugh: Thanks to you, without you this wouldn't have been possible
Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.
Xtian Rey said:
Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.
Click to expand...
Click to collapse
Very true, thanks a lot. I introduced the platform and the Android version of GApps
Thanks nice guide... Very useful for everyone who want play and modified the M2 note.
"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*)"
I Am Using M571C, But Everything Fine.
Sent from my M2 Note using XDA Forums Pro.
Mr0oHo0 said:
"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*)"
I Am Using M571C, But Everything Fine.
Sent from my M2 Note using XDA Forums Pro.
Click to expand...
Click to collapse
I include this on the guide. I read it bricked the phone in several cases, but I'm glad yours didn't.
Thanks for your guideline , it helps a lot !
Great work lol
Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing partAny problem just send me a private message. I'll check when i have time.
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…
Another thing is, Kingroot is not suggested. It cannot be detected by Flashfire and some other tools. And cannot be replaced by SuperSU. So Kingo Root+SuperSU might be better.
aaawqw said:
Great work lol
Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing partAny problem just send me a private message. I'll check when i have time.
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
And Meizu M571C shoukd use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…
Click to expand...
Click to collapse
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10
Line 10 to 15 you have the partitions size
Code:
$ cat /proc/partinfo
example :
Name------------Start-------------Size
recovery 0x0000000004840000 0x0000000001400000
Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size
PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers
This unlocking guide only works for M571 model.
Click to expand...
Click to collapse
Mine is M571H, can I proceed?
Qeemi said:
This unlocking guide only works for M571 model.
Mine is M571H, can I proceed?
Click to expand...
Click to collapse
Mine too and it worked. I can't assure you anything, but I think that the problem are m571C which are different. Good luck if you're going to give it a try!
Moyster said:
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10
Line 10 to 15 you have the partitions size
Code:
$ cat /proc/partinfo
example :
Name------------Start-------------Size
recovery 0x0000000004840000 0x0000000001400000
Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size
PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers
Click to expand...
Click to collapse
See it. I'll give a try on m2 note(M571C, China Telecom). At least try to build twrp But seems my pc's hdd is not enough No space for source code
little problems.
bootloader unlocking and twrp and roms works very well..
1. OTG is working for me.. :good:
2. unfortunately my phone is not detected by PC..
(show USB is not connected, USB debugging is not accessible..)
3. little bit lag here and there..
4. wifi works well :good:
Need more optimization.. Expecting lot more from you
thankyou very much for this :good:
DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?
dinkan01 said:
bootloader unlocking and twrp and roms works very well..
1. OTG is working for me.. :good:
2. unfortunately my phone is not detected by PC..
(show USB is not connected, USB debugging is not accessible..)
3. little bit lag here and there..
4. wifi works well :good:
Need more optimization.. Expecting lot more from you
thankyou very much for this :good:
DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?
Click to expand...
Click to collapse
hi,which build of cm 12 you put in phone?
M571U
I have the Meizu M571U Model. Can I do this or will it be bricked?
Thank you very much
venturaj said:
I have the Meizu M571U Model. Can I do this or will it be bricked?
Thank you very much
Click to expand...
Click to collapse
It won't, the only problematic model is the M571C, have fun
LBA97 said:
It won't, the only problematic model is the M571C, have fun
Click to expand...
Click to collapse
How can I check which model my m2 note is..?
[email protected] said:
How can I check which model my m2 note is..?
Click to expand...
Click to collapse
Check the store page you bought it from. If you bought it from China, then probably it's a M571C. Good luck
***WARNING***
This is NOT an official guide and I'm not affiliated with Offensive Security [ :crying: ].
This is just my personal guide.
I've been playing with this today and lot of my tries ended up with bricking my device.
Currently this method is working, but I am NOT responsible for any bricked devices.
If you never encountered/heard of bootloop/brick, please consider ignoring this tutorial.
DON'T FORGET TO MAKE A NANDROID BACKUP!!!
Hi guys! This is my quick-guide on how to install a Kali NetHunter on Huawei Honor 8.
It's quite simple, just read every step carefully.
This is just a guide. All credits goes to: CyanogenMod , TWRP, Offensive Security
So let's start!
*REQUIREMENTS*
- Rooted device
- Custom recovery TWRP/CWM
- A bit of patience
- Brain
You will need to flash a new recovery image through your old one .
So it's exactly very easy. I've already tested a lot of things and everything is working just fine.
So follow this steps:
1. Download CM 13 for Honor 8 and put it on your SD card. Link here.
2. Download this TWRP image for CM 13 / Honor 8 and put it on your SD card. Link here.
3. Download OpenGApps (Select arm64, 6.0, mini) and put in on your SD card. Link here.
4. Download Kali NetHunter (generic-arm64) and put in on your SD card. Full version: HERE. Minimal version: HERE. Just select the version you prefer. I'm using FULL, but I also tried minimal and it's working fine.
So after you downloaded all the files and you have it on your SD card:
1. Power off your Honor 8
2. When it's already off, press&hold Power and Volume Up button, until your device vibrates and the display starts up.
3. You should now be in your recovery. Press Install and select the TWRP recovery image, which you have downloaded on you SD card. Slide the panel to flash.
4. After you successfully flashed the image, head into main TWRP menu and select Reboot -> Recovery.
5. After you reboot into your recovery, choose cancel, if device ask for password key. If TWRP asks you if you want to allow write access to the system partition. IT IS VERY IMPORTANT THAT YOU ALLOW THIS. Check the box that says to never ask this question again.
6. Do a basic WIPE
7 . Flash the CM 13 then flash GApps
8. !IMPORTANT! Now reboot to your system and complete the basic "First-start" settings. Do NOT flash Kali NetHunter, if you haven't completed the first-time boot settings.
9. When you set up your phone and you are already on your Home Screen, power off your phone and boot to recovery again.
10. Now flash the Kali NetHunter, which you have downloaded on your SD card.
11. After the installation is complete, you can reboot to your system.
12. Press the power button on the Huawei Unlocked Bootloader warning screen. It will take a bit longer to boot than normal. It's completely fine. Just let it be for like 30 secs.
13. Now the Kali Bootanimation will start. Your phone will probably turn off during the bootanimation on your first boot. DON'T PANIC. It's fine. It will automatically restart and boot to your new system.
14. Now open up the NetHunter app. It will ask you for some permissions. It's important to ALLOW all the permissions.
15. After you allowed it all permissions, you can now close the NetHunter app and enjoy your Kali NetHunter
Sorry for my bad English
If you brick your phone, wipe your data and flash everything except the TWRP image again.
It's not my fault if you damage your phone by doing this. Remember that you are doing this on your own risk.
Have fun with your NetHunter on Honor 8
Screenshots:
http://imgur.com/a/8Wdyf
http://imgur.com/a/95dx0
http://imgur.com/a/YBxRS
http://imgur.com/a/E4gZ0
http://imgur.com/a/mkwet
will it works on stock rom??
Do I need to be on a specific build for this or does it not matter?
VenuGopalu said:
will it works on stock rom??
Click to expand...
Click to collapse
Unfortunately no. It requires some components from CyanogenMod.
FreeLineTM said:
Do I need to be on a specific build for this or does it not matter?
Click to expand...
Click to collapse
You mean specific NetHunter build or CyanogenMod build?
I tried one older build of NetHunter and it worked fine as well, but I'm not sure about the CyanogenMod. I think there are only 4 builds of CM13 for Honor 8 and this one is the newest. But I think the older builds would work too.
Flexy' said:
Unfortunately no. It requires some components from CyanogenMod.
You mean specific NetHunter build or CyanogenMod build?
I tried one older build of NetHunter and it worked fine as well, but I'm not sure about the CyanogenMod. I think there are only 4 builds of CM13 for Honor 8 and this one is the newest. But I think the older builds would work too.
Click to expand...
Click to collapse
I mean the EMUI stock build. I'm currently on FRD-L09C432B381
FreeLineTM said:
I mean the EMUI stock build. I'm currently on FRD-L09C432B381
Click to expand...
Click to collapse
Unfortunately no I tried it on stock build but without any success. It definitely requires CyanogenMod
it is working on my phone with stock mm rom ,, the boot animation was awesome ,, it was booted my device well and several apps were installed .i will attach a pic in below
Flexy' said:
Unfortunately no I tried it on stock build but without any success. It definitely requires CyanogenMod
Click to expand...
Click to collapse
I mean what build I need to be on to flash Cyanogen?
---------- Post added at 07:13 PM ---------- Previous post was at 06:55 PM ----------
Stuck on your device is booting now after flashing new TWRP and rebooting to recovery, but can still boot to system and flash old TWRP.
VenuGopalu said:
it is working on my phone with stock mm rom ,, the boot animation was awesome ,, it was booted my device well and several apps were installed .i will attach a pic in below
Click to expand...
Click to collapse
Wow, I couldn't get it working My phone always booted to the EMUI, but none of NetHunter components were installed. Strange.
FreeLineTM said:
I mean what build I need to be on to flash Cyanogen?
---------- Post added at 07:13 PM ---------- Previous post was at 06:55 PM ----------
Stuck on your device is booting now after flashing new TWRP and rebooting to recovery, but can still boot to system and flash old TWRP.
Click to expand...
Click to collapse
Oh, I don't know if there is a build number limitation, but you definitely need MM ROM firmware.
Link to the original CM 13 Honor 8 thread.
Hmm.. Strange. What version of TWRP were you using to flash the Honor 8 one?
Flexy' said:
Wow, I couldn't get it working My phone always booted to the EMUI, but none of NetHunter components were installed. Strange.
Oh, I don't know if there is a build number limitation, but you definitely need MM ROM firmware.
Link to the original CM 13 Honor 8 thread.
Hmm.. Strange. What version of TWRP were you using to flash the Honor 8 one?
Click to expand...
Click to collapse
It's not strange because I was on nougat with latest nougat TWRP when I tried the first time. But I rolled back to mm and completed the steps. However, the data partition was encrypted after rebooting to recovery with the new TWRP. I had to format data then reboot to recovery again. You should add this to the guide.
Flexy' said:
Wow, I couldn't get it working My phone always booted to the EMUI, but none of NetHunter components were installed. Strange.
Oh, I don't know if there is a build number limitation, but you definitely need MM ROM firmware.
Link to the original CM 13 Honor 8 thread.
Hmm.. Strange. What version of TWRP were you using to flash the Honor 8 one?
Click to expand...
Click to collapse
I have tested on twrp-3.0.2-0-frd.img&twrp-3.1.1-0-frd.img both are working without any issue
link for twrp:::: https://dl.twrp.me/frd/
I successfully flashed nethunter on stock Nougat (FRD-L09C432B360).. DriveDroid which is the only thing I want didn't work with stock because it couldn't find USB mass storage. I tried to install it via nethunter instead but it didn't work there either. Might be because I forgot to open nethunter once for setup though..
FreeLineTM said:
I successfully flashed nethunter on stock Nougat (FRD-L09C432B360).. DriveDroid which is the only thing I want didn't work with stock because it couldn't find USB mass storage. I tried to install it via nethunter instead but it didn't work there either. Might be because I forgot to open nethunter once for setup though..
Click to expand...
Click to collapse
Can you tell me how you installed Nethunter on FRD-L09? I am pretty new to this android scene , also you know if the fingerprint sensor works normally?
darkrsing said:
Can you tell me how you installed Nethunter on FRD-L09? I am pretty new to this android scene , also you know if the fingerprint sensor works normally?
Click to expand...
Click to collapse
I don't think fingerprint worked if I recall correctly. I installed NetHunter as any custom ROM if I remember correctly.
I have installed it on Stock rom by using Magisk (and root of course). Very simple, very powerful.
Obsolete, move to the new thread here below.
(EASY ROOT) Z982 via QFIL or TWRP B20_Modified SYSRW 4/8/19
xxMoon said:
!!!!!WARNING!!!!!!
This will wipe your phone.
Prep
Enable USB Debugging and OEM Unlocking on your phone
Install ADB Driver
Install EDL Drivers
Restart Computer
Files
ZTE_BLADE_Z_MAX_edl.7z
Guide
1. Extract the folder inside ZTE_BLADE_Z_MAX_edl.7z to your desktop.
2. Connect your phone to your computer.
3. Open the folder "ZTE_BLADE_Z_MAX_edl" that you just extracted.
4. Right click on ZTE_BLADE_Z_MAX_edl.bat
5. click run as administrator
6. Press Y
7. Press 1
8. Press 2
9. Press Y
10. Press N
11. Press 1
12. Press 3
13. Press Y
14. Press N
15. Press Q
16. Disconnect your phone from the computer.
17. Press and hold "Power and Vol+" untill the ZTE Logo Appears then release the power button while continuing to hold vol+
18. Once booted into TWRP Recovery, swipe to allow modifications.
19. Tap Wipe
20. Tap Format Data
21. Type yes
22. Tap Blue checkmark
23. Back out to the main screen.
24. Tap Reboot
25. Tap System
"Initial Boot will take some time, and may even reboot"
"If more than 5 mins elapses, press and hold power button to restart device"
26. Setup Android
27. Locate Magisk and open it.
28. Install magisk manager "May have to anable unknown sources first"
!!!!DO NOT UPDATE MAGISK!!!! Only update the magisk manager.
Profit!!!!
Click to expand...
Click to collapse
nvm fixed my issue
So upto magisk v18.0 works fine. However, 18.01 causes the phone to go into dfu mode.
It is important that you only update magisk manager, not magisk itself.
xxMoon said:
So upto magisk v18.0 works fine. However, 18.01 causes the phone to go into dfu mode.
It is important that you only update magisk manager, not magisk itself.
Click to expand...
Click to collapse
Even though it says I have 18.0 installed, whenever I download a module it says that I need version 17.0+ which sucks because I really want to change the fonts. Whenever I try booting into twrp to manually flash, it never shows my files, no matter where I put them, I tried using Es file explorer to move them to/system/bin but it says operation failed every time so I do not know what to do at this point. I cant flash files via twrp or magisk and I really would like some help on this.
---------- Post added at 06:40 PM ---------- Previous post was at 06:32 PM ----------
If so can you give me a detailed explanation on how to flash modules through ADB, seems that it is my only option until Magisk lets me download what I want. All I want to do right now is change my fonts so I can get rid of these blob emojis. If it helps, the file I'm trying to obtain offf magisk is called IOS 12.1 Emoji but like I said, it says I need v17.0 to install and gives me installation failed everytime
Good ****!!!!
Since a lot of people are having problem with magisk all just rebuild my boot.img so you won't have to add the su file. Then hopefully people would use it because it currently up to date without any issues I can find
Jasonls221 said:
Since a lot of people are having problem with magisk all just rebuild my boot.img so you won't have to add the su file. Then hopefully people would use it because it currently up to date without any issues I can find
Click to expand...
Click to collapse
I did a whole reflash using yours and magisk wasnt there so I had to go back to the original one posted from moon. Can you explain what you did to flash yours and get it to work? Can you also re-upload the file on here? Thank you
evtoofly said:
I did a whole reflash using yours and magisk wasnt there so I had to go back to the original one posted from moon. Can you explain what you did to flash yours and get it to work? Can you also re-upload the file on here? Thank you
Click to expand...
Click to collapse
The only problem with mine was you had to transfer the su file I supplied to /system/bin
Jasonls221 said:
The only problem with mine was you had to transfer the su file I supplied to /system/bin
Click to expand...
Click to collapse
so without fully reflashing , all i have to do is use a file explorer to transfer su, and then use twrp to flash the boot image only? I really dont wanna have to wipe my device again and set up my phone again
---------- Post added at 05:35 AM ---------- Previous post was at 05:33 AM ----------
Thats another problem I face as well, no file explorer has let me move a file to the bin folder so how did u do it?
evtoofly said:
so without fully reflashing , all i have to do is use a file explorer to transfer su, and then use twrp to flash the boot image only? I really dont wanna have to wipe my device again and set up my phone again
---------- Post added at 05:35 AM ---------- Previous post was at 05:33 AM ----------
Thats another problem I face as well, no file explorer has let me move a file to the bin folder so how did u do it?
Click to expand...
Click to collapse
I used twrp and adb. adb push su /system/bin
Jasonls221 said:
I used twrp and adb. adb push su /system/bin
Click to expand...
Click to collapse
where did u place the boot file on your device for twrp because twrp never sees files for me
also with the su file, can I put that anyweher on my device and run that adb command for it to transfer? sorry im confused
edit: I managed to get everything working and now I can install modules and also have the latest version of Magisk, thank you!
evtoofly said:
where did u place the boot file on your device for twrp because twrp never sees files for me
also with the su file, can I put that anyweher on my device and run that adb command for it to transfer? sorry im confused
edit: I managed to get everything working and now I can install modules and also have the latest version of Magisk, thank you!
Click to expand...
Click to collapse
Cool, I'll try to make this automated but I'm not good with windows
I cant wait for roms to come out for this device! Also gotta learn how to turn s secure on for this device , now that its rooted.
evtoofly said:
I cant wait for roms to come out for this device! Also gotta learn how to turn s secure on for this device , now that its rooted.
Click to expand...
Click to collapse
I could make a custom ROM once there's a TWRP recovery able to flash zips successfully
good job...
Legit works like a charm.. Very impressive!! All hail the ZTE PIMP!!
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
Question i have a zte z970 that has had the firmware deleted. Anyone know of a fix for this?
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
I can boot into normal recovery but i cant flash any of the stock firmware i can find....
For z970 , that is a easy fix, get your twrp firmware backup and restore it ...Don't tell me you don't have the backup...I have backup but it interludes my person things together
Would I be able to install systemless xposed via magisk or no?
evtoofly said:
Would I be able to install systemless xposed via magisk or no?
Click to expand...
Click to collapse
I've tried, but I dont think it worked.
xxMoon said:
I've tried, but I dont think it worked.
Click to expand...
Click to collapse
It actually does work. With the latest magisk, all you do is download the xposed sdk 25(Android 7.1) module on magisk and then download xposed 3.15 apk installer and xposed will work. I have been using it all day and already have some xposed modules installed:good: