Database Users

[Root any Moto G] with screenshots [Simple Method|Well Explained]

Hi...
This is the tutorial to root any Moto G
To root any Moto G, three basic steps need to be followed... you can either do them manually or use a tool do them for you. It is advised to follow them manually so that if there's some bug in the tool you don't get into any trouble.
CAUTION - You will lose all data and files so better back them up.
For Google Play edition devices, the process is same and only the recovery.img file is different. For GPe CWM Advanced Edition recovery go here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ and select falcon_gpe and download the latest one.
For AT&T and Verizon models don't do anything written above. Just download the Towelroot app. Its a one click root app and doesn't require a PC. Itis trustworthy but is not guaranteed to work but you must give it a try since it won't do any harm and claims of never bricking a phone. Please reply with the result and your android and kernel version.It will probably not work on phones build after June 3 but you can give it a try. You can download it from the website https://towelroot.com
The three steps are :-
1) UNLOCKING THE BOOTLOADER
2) FLASHING CUSTOM RECOVERY
3) INSTALLING SuperSu.zip FILE THROUGH RECOVERY. (SuperSu is acknowledge as the best app to give superuser and root rights)
UNLOCKING THE BOOT LOADER - The instructions to unlock the boot loader are given in the official Motorola website here https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a . Don't be scared by their warnings.
UPDATE - There currently seems to be an issue with unlocking the bootloader on devices running 4.4.4 though it works for 4.4.2. The issue is with Motorola and is that, the unlock code given by the company is showing an error. They are fixing it and it may take some time though you can give it a try as it won't do any harm. Or you can downgrade the boot loader to 4.4.2 and then unlock it.
As confirmed by the Motorola agent, the problem of unlocking bootloader on 4.4.4 has been fixed
FLASHING CUSTOM RECOVERY :-
To flash a custom recovery, you need these things
1) PC and a USB data cable
2) Android SDK ( developer.android.com/sdk/index.html ) For flashing recovery only SDK is needed but it's your wish if you want to download the ADT bundle. After downloading and unzipping the sdk , open the SDK manager and download only the platform tools for this.. rest is your wish..... and separately download ADB tools and fastboot and extract them minimal-adb-and-fastboot.software.informer.com/1.1/
3) Recovery.img file - You can either use CWM foum.xda-developers.com/showthread.php?t=2563599 or CWM advanced editionforum.xda-developers.com/showthread.php?t=2639583 or TWRP forum.xda-developers.com/showthread.php?t=2561757. EDIT - If your phone had come pre installed with 4.4.4 then use only CWM Advanced Edition. CWM Advanced Edition doesn't make backup on XT1033
4) Motorola drivers https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
5) Enable USB Debugging mode in your phone by going to Settings-About Phone and then tap the build number until you get the toast 'You are a developer'. Now go to Settings again and you will see a new Developer Options there. Go there and enable USB debugging.
6) Have at least 25% of charge on your phone.
After getting all these things:-
1) Download the recovery.img file to your PC and copy paste it to android SDK/platform tools folder.
2) Boot your phone to fastboot mode by first switching it off and holding the volume down and power button for 3 seconds.
3) When in fastboot mode, connect your phone to pc, go to the platform tools folder, there pres shifft and right mouse click simultaneously and select 'open command prompt window here'.
4) In the command window enter
Code:
fastboot devices
If it shows a number and fastboot then we are good..
5) Then enter
Code:
fastboot flash recovery recovery.img
( where in recovery.img the recovery is the name of your recovery file. Example if the name of recovery file is ABC then enter fastboot flash recovery ABC.img)
5) Press enter and if the command prompt window displays the message okay then the recovery is successfully flashed.
6) Now just boot your phone to recovery mode through fastboot mode by following the on screen instructions and in recovery mode select Reboot System Now to reboot your phone normally.
(see attached images below for screenshots)
INSTALLING SuperSu
To install SuperSu :-
1) Download SuperSu zip file download.chainfire.eu/452/SuperSU/ and transfer it to your phone
2) Reboot to recovery via fastboot.
3) Select install zip and select choose from SD card.
4) Locate the file and install it.
5) Now reboot your phone.
YUP.. YOU ROOTED YOUR PHONE!
Download any root checker app from the Play Store to check whether your phone is rooted or not.
If you get into any trouble, please contact and don't forget to hit thanks if it helped
Consider rating the thread by going to the option 'rate thread' which is located above the thread on the right side. You can also participate in the poll

I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app

sisqoboy said:
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Yup dude...this works for sure..!
I also added screenshots.. check them out.

Meuuks13 said:
Yup dude...this works for sure..!
Click to expand...
Click to collapse
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks

motocruiser said:
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
Click to expand...
Click to collapse
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.

And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app

xrilex said:
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have Verizon I see. The only you will probably face is unlocking the bootloader.. Oh, wait first let me laugh... lol...OK....At one point of time you couldn't unlock the bootloaders for AT&T and Verizon and then we were blessed by the 'one click root' app by the famous hacker geohot called TowelRoot. This app claims to root all the AT&T and Verizon devices with just a click. You don't even need a PC. Just download the app and in the app chick 'make it rain'. Though this is not guaranteed to work but must give a try as it won't do any harm but there's a chance of bricking the phone but you can easily recover from a soft brick by flashing the stock firmware.
Towelroot - https://towelroot.com/
P.S. - Please reply if you tried this and if it didn't work reply with your android version and kernel version. Well reply with your android version and kernel version anyway.
Edit- I added it to the OP

Meuuks13 said:
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
Click to expand...
Click to collapse
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self

motocruiser said:
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
Click to expand...
Click to collapse
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?

Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!

t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell which android version your phone came preinstalled with and what recovery you used.
Also when you reboot to recovery, after the blank screen do you see the android logo lying down with a red triangle?

t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell your phone's android version and the recovery you used and what did you enter at the command prompt?

Meuuks13 said:
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Click to expand...
Click to collapse
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks

motocruiser said:
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
Click to expand...
Click to collapse
Testdrive image?

Meuuks13 said:
Testdrive image?
Click to expand...
Click to collapse
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image

motocruiser said:
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
Click to expand...
Click to collapse
So basically you want to downgrade the bootloader and then unlock it?
Well if you are on KitKat you can downgrade the bootloader by flashing 4.3 , then unlocking the bootloader and then updating to KitKat

Thanks for the guide. I've already recommended it to someone who was having problems.

jselene said:
Thanks for the guide. I've already recommended it to someone who was having problems.
Click to expand...
Click to collapse
Cool.

Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566

JDCGW said:
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I got something wayyyy better than that!
I let you remove that sign and use the pics given here forum.xda-developers.com/moto-g/themes-apps/shareboot-logos-t2875147 or you can give me the pic you want and I will make it in such a way that you can use it.

Need TWRP Backup of UK version, a2017g

Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance

Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !

shia786 said:
Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Click to expand...
Click to collapse
djona12 said:
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
Click to expand...
Click to collapse
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619

i cannot seem to find tenfar tool anywhere
DrakenFX said:
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
Click to expand...
Click to collapse

i have found the tool but i think i flashed the US version of the boot image now my phone does not boot up at all,
it goes to stock recovery
if i turn the phone on then it goes to ZTE LOGO for about half a second then the screen goes blank
i can access fastboot but only through stock recovery which when i go to bootloader i cannot run any fastboot commands, even if i run fastboot reboot it does not reboot the phone at all
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse

Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.

shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Cricius said:
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
Click to expand...
Click to collapse
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.

DrakenFX said:
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
Click to expand...
Click to collapse
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file

shia786 said:
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
Click to expand...
Click to collapse
Try enable " OEM Unlocking " under developers option and try again

DrakenFX said:
Try enable " OEM Unlocking " under developers option and try again
Click to expand...
Click to collapse
I cannot access the software at all, all I got is stock recovery

shia786 said:
I cannot access the software at all, all I got is stock recovery
Click to expand...
Click to collapse
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.

DrakenFX said:
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
Click to expand...
Click to collapse
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery

shia786 said:
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
Click to expand...
Click to collapse
You can just boot into TWRP using tenfar tools and Flash the zip.

DrakenFX said:
You can just boot into TWRP using tenfar tools and Flash the zip.
Click to expand...
Click to collapse
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB

shia786 said:
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
Click to expand...
Click to collapse
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop

DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working

shia786 said:
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
Click to expand...
Click to collapse
Hi,
I have the exact same issue
Did you find a way to get your phone booting again ?

DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
That doesn't work on the A2017G, you have to use "adb reboot edl", so you see the problem. Also, the A2017G doesn't actually have an EDL mode but something very similar that's ZTE call Handset diagnostic Interface - quite why, who knows, this is ZTE after all...

TWRP for the TB3-850F

Hello all
Im trying to Root my Lenovo TB3-850F and I need a TWRP for this model
please help and IM willing to pay 40 CAN$ for the link (PAYpal) or I will take it for free also
regards

Hi @Teligen,
There is already an ongoing thread, about this very topic over here... that shows it's current status.
At the moment, we're just about getting there... but it's by no means an easy feat yet....
Cheers, Lister
Teligen said:
Hello all
Im trying to Root my Lenovo TB3-850F and I need a TWRP for this model
please help and IM willing to pay 40 CAN$ for the link (PAYpal) or I will take it for free also
regards
Click to expand...
Click to collapse

I flashed this one which works fine on my X50F.
TWRP-2.8.7.7_YT3-X50M
http://lenovo-forums.ru/topic/14846...x50lm-расширенное-рекавери-twrp-by-sevenmaxs/

Twrp install
Would you by chAnce have the instructions on how to install The twrp
Thanks

I would tell you but I am a bit hesitent because I am just an advanced user not a dev and I don't want to be held responsible if something goes wrong…

5T33Z0 said:
I flashed this one which works fine on my X50F.
TWRP-2.8.7.7_YT3-X50M
http://lenovo-forums.ru/topic/14846...x50lm-расширенное-рекавери-twrp-by-sevenmaxs/
Click to expand...
Click to collapse
That twrp is for a different device. I wouldn't flash it unless you have a backup of your boot/recovery or stock firmware for your device

Hemphiz said:
That twrp is for a different device. I wouldn't flash it unless you have a backup of your boot/recovery or stock firmware for your device
Click to expand...
Click to collapse
The only difference is that F has no Modem and SIM Slot for mobile Data but it works fine.
I only use it to root the device without actually flashing it.
Just put the twrp image in your ADB Folder on your PC, then run fastboot with the command:
Fastboot boot twrp.img
This uploads twrp on your device and boots it to twrp. You can leave the system recovery untouched and flash supersu for rooting.
The bootloader has to be unlocked of course.

5T33Z0 said:
The only difference is that F has no Modem and SIM Slot for mobile Data but it works fine.
I only use it to root the device without actually flashing it.
Just put the twrp image in your ADB Folder on your PC, then run fastboot with the command:
Fastboot boot twrp.img
This uploads twrp on your device and boots it to twrp. You can leave the system recovery untouched and flash supersu for rooting.
The bootloader has to be unlocked of course.
Click to expand...
Click to collapse
Ok cheers. Appreciate the info. So I'm wrong in assuming the Tb3-850f came with an already unlocked bootloader? Like many lenovo tabs
Edit. Also the yoga yt3-850f is a different device to lenovo tab3 tb3-850f

Hemphiz said:
Ok cheers. Appreciate the info. So I'm wrong in assuming the Tb3-850f came with an already unlocked bootloader? Like many lenovo tabs
Click to expand...
Click to collapse
No, no. You have to unluck it via fatboot as well.
1. Enable Developer Options
2. Enable "OEM unlocking" Option in there
3. Reboot to Bootloader (Restart and hold down Volume down)
4. Run fastboot oem unlock-go
Next, the Android Bot and a process Bar appears on the tablet and does it's thing. Once that's finished the Tablet restarts and enters the initial Android Setup Screen. So it unlocks the bootloader but ALSO performs a factory reset.

5T33Z0 said:
No, no. You have to unluck it via fatboot as well.
1. Enable Developer Options
2. Enable "OEM unlocking" Option in there
3. Reboot to Bootloader (Restart and hold down Volume down)
4. Run fastboot oem unlock-go
Next, the Android Bot and a process Bar appears on the tablet and does it's thing. Once that's finished the Tablet restarts and enters the initial Android Setup Screen. So it unlocks the bootloader but ALSO performs a factory reset.
Click to expand...
Click to collapse
Yea I think your referring to the yoga tab 3, not the lenovo tab 3
Lenovo_TB3_850F and Lenovo_YT3_850F
I can see why one would get confused lol

Hemphiz said:
Yea I think your referring to the yoga tab 3, not the lenovo tab 3
Click to expand...
Click to collapse
Yes, I have the YogaTab 3 (X50F). But there probably won't be any harm done unlocking the device and booting (not flashing) from the afore mentioned twrp.img.

5T33Z0 said:
Yes, I have the YogaTab 3 (X50F). But there probably won't be any harm done unlocking the device and booting (not flashing) from the afore mentioned twrp.img.
Click to expand...
Click to collapse
That's a good point, fastboot boot is a safe method

Teligen said:
Hello all
Im trying to Root my Lenovo TB3-850F and I need a TWRP for this model
please help and IM willing to pay 40 CAN$ for the link (PAYpal) or I will take it for free also
regards
Click to expand...
Click to collapse
Do you still need TWRP for the Lenovo Tab 3 8/TB3-850f?

MotoJunkie01 said:
Do you still need TWRP for the Lenovo Tab 3 8/TB3-850f?
Click to expand...
Click to collapse
Yes, do you have it ?

Teligen said:
Yes, do you have it ?
Click to expand...
Click to collapse
I have a build that I compiled for my device from TWRP. No bugs. Works great

Teligen said:
Yes, do you have it ?
Click to expand...
Click to collapse
What is your Software Build #?

MotoJunkie01 said:
What is your Software Build #?
Click to expand...
Click to collapse
I'd also appreciate a TWRP image for this device. My software Build is TB3-850F_S100030_161209_ROW
Thanks

julian67 said:
I'd also appreciate a TWRP image for this device. My software Build is TB3-850F_S100030_161209_ROW
Thanks
Click to expand...
Click to collapse
Here is TWRP recovery and a SuperSU 2.78-SR3 flashable zip for the Lenovo Tab 3 8/TB3-850F.
https://drive.google.com/file/d/0B7-zQU1VihD3ZVF5cEJHUVpNZjg/view?usp=drivesdk
Credit goes to @Hemphiz for his tutorial and files on TWRP + Root for the Lenovo Tab3 8". https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786

Brilliant! Thank you very much. Just got this Tab 3 yesterday and love it. Will love it even more with root+adaway.

It works great. I used adb & fast boot to unlock the bootloader & then boot from twrp image on PC and install SuperSu. Have been using Samsung for a long time but fast boot is much nicer, especially being able to boot a recovery without modifying partitions or filesystems on the device.

unlocking/rooting on nougat A2017G

Hi All, i'm numb searching for a solution. I have a brand new axon7 and i want root. There are a lot howto's but they are confusing me a lot. I'm on 1.2.0B05.
I understand i have to downgrade my device to marshmellow. Will the link on http://www.ztedevice.com/support/detail?id=1170789A90BA42E18B3364B80C7F5A26 , the middle one, be sufficient to go back to marshmallow so i can get into the bootloader, so i can use fastboot?

Zobat said:
Hi All, i'm numb searching for a solution. I have a brand new axon7 and i want root. There are a lot howto's but they are confusing me a lot. I'm on 1.2.0B05.
I understand i have to downgrade my device to marshmellow. Will the link on http://www.ztedevice.com/support/detail?id=1170789A90BA42E18B3364B80C7F5A26 , the middle one, be sufficient to go back to marshmallow so i can get into the bootloader, so i can use fastboot?
Click to expand...
Click to collapse
No. First of all, check the model on the back of the phone. If it is an A2017 (you bought it in Aliexpress) then you need to use other guides. If it is an A2017G, then MAYBE you can simply use axon7toolkit, which is basically a 'one-click' tool. But before that, activate 'Enable OEM unlocking' and 'USB debugging' and 'ADB over network' on the Developer options. If you don't you just won't get anywhere.
Otherwise, if your phone IS an A2017G, you can use Controllerboy's guide ('unlock BL, root, TWRP, custom ROMS' or something on the lines). It doesn' use fastboot, which is the only limitation of Nougat stock for the G afaik. Just be aware that axon7tool is not the same as axon7toolkit

Choose an username... said:
No. First of all, check the model on the back of the phone. If it is an A2017 (you bought it in Aliexpress) then you need to use other guides. If it is an A2017G, then MAYBE you can simply use axon7toolkit, which is basically a 'one-click' tool. But before that, activate 'Enable OEM unlocking' and 'USB debugging' and 'ADB over network' on the Developer options. If you don't you just won' get anywhere
Click to expand...
Click to collapse
Its a ZTE A2017G. USB debugging and OEM unlocking is done. I'm on linux so i hope there is a way to access the bootloader for "fastboot oem unlock" and flashing twrp.
edit i will try find controlerboys guide.
2nd edit: found the guide at https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 . But it states: "Users on stock Nougat, do not proceed, this guide won't work for you. You need to downgrade to Marshmallow first."

Zobat said:
Its a ZTE A2017G. USB debugging and OEM unlocking is done. I'm on linux so i hope there is a way to access the bootloader for "fastboot oem unlock" and flashing twrp.
edit i will try find controlerboys guide.
2nd edit: found the guide at https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 . But it states: "Users on stock Nougat, do not proceed, this guide won't work for you. You need to downgrade to Marshmallow first."
Click to expand...
Click to collapse
Okay, but:
-Downgrading to Marshmallow probably won't restore fastboot
-To get Fastboot (at least in February) you needed to flash a package called 'A2017U_FASTBOOT_UNLOCK_EDL' through MiFlash. I think you could flash it even with the bootloader locked, and it didn't matter that it was for the U. Now, I don't know if there's a MiFlash for Linux. I guess you should find a Win10 x64 pc for this, since most tools (axon7tool, axon7toolkit, axon7root, maybe miflash) are windows only. Someone tried to root the phone from linux though, you can search if he could at the end or not.
The bootloader mode is not there. For some reason it can't be enabled by downgrading unless you flash the aboot.img which seems to be done with miflash

Choose an username... said:
Okay, but:
-Downgrading to Marshmallow probably won't restore fastboot
-To get Fastboot (at least in February) you needed to flash a package called 'A2017U_FASTBOOT_UNLOCK_EDL' through MiFlash. I think you could flash it even with the bootloader locked, and it didn't matter that it was for the U. Now, I don't know if there's a MiFlash for Linux. I guess you should find a Win10 x64 pc for this, since most tools (axon7tool, axon7toolkit, axon7root, maybe miflash) are windows only. Someone tried to root the phone from linux though, you can search if he could at the end or not.
The bootloader mode is not there. For some reason it can't be enabled by downgrading unless you flash the aboot.img which seems to be done with miflash
Click to expand...
Click to collapse
it looks like i have to find myself a win64, with administrator rights for installing drivers, somewehere

Choose an username... said:
Okay, but:
-Downgrading to Marshmallow probably won't restore fastboot
Click to expand...
Click to collapse
FYI. I can confirm that fastboot will be restored using the B11 MM downgrade build from ZTE. Downgraded an hour ago and tested it with success.

I used this tool to unlock and root my A2017G, though it was LP...
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108

christoophat said:
I used this tool to unlock and root my A2017G, though it was LP...
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
tell me please should i downgrading my phone to marshmallow before using those tools , or no matter what the version is oreo or marshmallow i can use those tools to unloack bootloader and rooting my phone "zte axon 7 a 2017 g"

Zobat said:
it looks like i have to find myself a win64, with administrator rights for installing drivers, somewehere
Click to expand...
Click to collapse
-------------------------------
please tell me my phone is "zte axon 7 a2017 g version oreo " and i don"t found proper images to unloack bootloader for my version a 2017 g oreo ; i just found images for marshmallow and naugat , who can please tell me if before flash an ota marshmallow should i unloack the bootloader or not need for that !

FifthAxiom said:
FYI. I can confirm that fastboot will be restored using the B11 MM downgrade build from ZTE. Downgraded an hour ago and tested it with success.
Click to expand...
Click to collapse
did u downgrade without unloack the bootloader !!

so i have been looking for a guide on how to install twrp on my axon 7, with 7.1.1, but everything is out of date which send you to other links to down load which dont work or the link itself doesnt open. '
so here i am asking
point me to a link THAT WORKS AND IS A GUIDE. thanks.
yes i have flashed a 6p to pixel experience so i figured it should be to hard but finding what i need is kind of....hard

Bricked Verizon VS995 in Fastboot loop

Hi,
I’ve got an older Verizon LG V20 that’s been bricked. I hid it in a drawer for the past year or so, and stumbled across it again. If I can get this fixed, I’d love to update it and give it as a gift to an older friend who has a 6 yr old crap android phone. But first, some history…
-bought used in great shape and rooted with Dirty Santa to run on TMobile. I don't recall which ROM I used, but it was very stock minus the carrier apps. My wife had a chance to go to Italy, so we bought a 3rd party european SIM with 30 days of data and voice from Three UK. Short story is that the phone never recognized the SIM, but she used it to take some great pics during her stay.
-once back in the US, I decided to try a different ROM and I think I flashed the wrong files or something… it’s my fault but I honestly can’t recall if I loaded a Samsung image instead, or what exactly happened.
Currently, the phone boots ONLY into fastboot mode. ADB does not recognize the device, and I’m thinking that I’ve lost TWRP Recovery since I can’t enter Recovery Mode at all.
If I do hold Vol Down + Power, I get a Hard Reset menu, but nothing in there helps.
I tried using LGUP, but the device is "not recognized."
I’m at a loss as to what to do at this point. If there IS a way to un-brick this, I think it would make a great phone for a good friend.
If anyone has any suggestions, I’d love any ideas that you may have. I tried looking to see if any other threads cover this, but I’m not seeing anything with specifics or pointers to How-Tos. If I missed the relevant links, I’d appreciate being pointed to them.
Also…
-if I can return to Stock condition, I can then unlock the bootloader and flash a more current ROM again. Would I need to pick a new radio so it better matches TMobile vs the Verizon setup it originally came with?
thanks for reading!
motionmonk

Since you can get to fastboot why not flash a twrp to see if you will get recovery

0x0null said:
Since you can get to fastboot why not flash a twrp to see if you will get recovery
Click to expand...
Click to collapse
When I run fastboot in Terminal, I get a blank response-- that is, a simple carraige return with no info listed.
This is on a fresh Win10 install with the latest Platform Tools package (Justt adb & fastboot) from the Android Studio website.
Are there other drivers that I need? When I installed LGUP, I did install the LGMobileDriver_WHQL_Ver_4.1.1.exe installer as well.
-motionmonk

motionmonk said:
When I run fastboot in Terminal, I get a blank response-- that is, a simple carraige return with no info listed.
This is on a fresh Win10 install with the latest Platform Tools package (Justt adb & fastboot) from the Android Studio website.
Are there other drivers that I need? When I installed LGUP, I did install the LGMobileDriver_WHQL_Ver_4.1.1.exe installer as well.
-motionmonk
Click to expand...
Click to collapse
That is bad, can you try it ona windows 7 PC?

0x0null said:
That is bad, can you try it ona windows 7 PC?
Click to expand...
Click to collapse
I could... I need to find my Win7 install disks for an old laptop.
I'll report back by tomorrow.
I don't do this often... what makes WIndows 7 a better method than Win 10?
-motionmonk

motionmonk said:
I could... I need to find my Win7 install disks for an old laptop.
I'll report back by tomorrow.
I don't do this often... what makes WIndows 7 a better method than Win 10?
-motionmonk
Click to expand...
Click to collapse
issues with drivers

It took longer than I thought to find my Win7 installers... I'm in the middle of the reinstall now.
I plan to load the Android Platform Tools, LG Mobile Drivers, LGUP framework... is there anything else I should install?
thanks for any suggestions; I don't root often at all and am rusty at this
-motionmonk

Win 7 update
Ok, I've installed WIN7, Android Platform Tools (just ADB & Fastboot), LG drivers and LGUP.
Now when I do the fastboot command, I get a true response:
fastboot devices
VS995aa11a111 fastboot (where a=letters, 1=numbers)
YAY!
So at this point, if I load a TWRP.zip, would I be able to boot into Recovery, instead of fastboot mode?
I checked the official TWRP website, and the latest is TWRP 3.2.3-0.
EDIT: I looked in the LG Section, and it appears that there is not an official TWRP for the LG V20. Is that right?
Having gotten to the point where the laptop recognizes the phone, I really don't want to make a dumb mistake :silly:
thanks for getting me this far!
-motionmonk

motionmonk said:
Win 7 update
Ok, I've installed WIN7, Android Platform Tools (just ADB & Fastboot), LG drivers and LGUP.
Now when I do the fastboot command, I get a true response:
fastboot devices
VS995aa11a111 fastboot (where a=letters, 1=numbers)
YAY!
So at this point, if I load a TWRP.zip, would I be able to boot into Recovery, instead of fastboot mode?
I checked the official TWRP website, and the latest is TWRP 3.2.3-0.
EDIT: I looked in the LG Section, and it appears that there is not an official TWRP for the LG V20. Is that right?
Having gotten to the point where the laptop recognizes the phone, I really don't want to make a dumb mistake :silly:
thanks for getting me this far!
-motionmonk
Click to expand...
Click to collapse
There is no official twrp build for the V20, search for Phoenix's unofficial twrp thread
Sent from my LG-H910 using XDA Labs

cnjax said:
There is no official twrp build for the V20, search for Phoenix's unofficial twrp thread
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thank you cnjax... I think I got it now:
recovery-twrp-vs995-2018-10-18

Now that I have the TWRP Installer, I connect the phone (in perma-fastboot mode), and verify that it is connected by using fastboot devices. I get a recognition string in reply. So now I move on...
-rename recovery-twrp-vs995-2018-10-18.img as TWRP.img
-move TWRP.img to my platform-tools folder
-issue flashing command fastboot flash recovery TWRP.img
Here's what I get:
Sending 'recovery' (25984 KB)
OKAY [ 0.889s]
Writing 'recovery'
FAILED (REMOTE: 'unknown command'}
Finished. Total time: 1.092s
I'm pretty sure I have the syntax correct, and the TWRP.img file is being recognized, but -something- isn't working.
Have I missed something here?
thanks for any suggestions,
motionmonk

fastboot help pages
motionmonk said:
Now that I have the TWRP Installer, I connect the phone (in perma-fastboot mode), and verify that it is connected by using fastboot devices. I get a recognition string in reply. So now I move on...
-rename recovery-twrp-vs995-2018-10-18.img as TWRP.img
-move TWRP.img to my platform-tools folder
-issue flashing command fastboot flash recovery TWRP.img
Here's what I get:
Sending 'recovery' (25984 KB)
OKAY [ 0.889s]
Writing 'recovery'
FAILED (REMOTE: 'unknown command'}
Finished. Total time: 1.092s
I'm pretty sure I have the syntax correct, and the TWRP.img file is being recognized, but -something- isn't working.
Have I missed something here?
thanks for any suggestions,
motionmonk
Click to expand...
Click to collapse
Hi
I'm just a noob but I am interested in the problem you are having and am following it to see what comes up with it.
There is a good fastboot thread here:
https://forum.xda-developers.com/showthread.php?t=2277112
On the first page you have options to wipe before flashing - i.e. system, boot, data, RECOVERY etc,
Maybe give those pages a read while waiting for someone more knowledgeable to fix your phone...
Since you are not sure what happened maybe the modem was affected which I think is bad...
I think doing a "fastboot getvar all" might give you a status of what you are dealing with .... since it gives you versions
of things...
Anyhow, good luck reviving the phone - "rooting" for you haha!
---------- Post added at 10:33 PM ---------- Previous post was at 10:05 PM ----------
This link might also be a good read
https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732

secondhand2 said:
There is a good fastboot thread here:
https://forum.xda-developers.com/showthread.php?t=2277112
. . .
I think doing a "fastboot getvar all" might give you a status of what you are dealing with .... since it gives you versions
of things...[/url]
Click to expand...
Click to collapse
secondhand2,
THX for the links! Those were very helpful!
No need to call yourself a noob... I think I outrank you in that department at this point!
I did try your suggestion of fastboot getvar all, and found something interesting...
when I did the command it returned (bootloader) unlocked:no
which I thought was WEIRD, since the phone -was- unlocked with a custom ROM before I messed things up.
I have attached a screenshot to this msg with the full info report.
So now I'm wondering if that's why my previous attempt at flashing TWRP failed?
Does this mean I have a soft-brick or a hard-bricked phone at this point?
I"m learning more through everyone's help and input, but I'm still lost as to where to go from here.

Hi,
I have a US996 and I unlocked it using the lg web site - they send a bin file that you can use to unlock the phone.
There are different exploits on different versions of V20 phones. THere are also versions of Nougat that have an anti rollback that stop you from going from a recent OTA update back to an older one that can be exploited to get root. For example, on the US996 I have., if I had bought it and it had been patched with 10p (not 100% sure which version was the cutoff point) even if the phone was unlocked, I might not be able to get root. So the versions of the ROMs/firmware are imnportant. As it happened I had the 10f version so rooting was possible - but I followed the threads on this site for my specific phone and stuck to STOCK rom's.
So I'm not sure about what ROM you have - i..e which version of the vs995 is rootable after you unlock the phone. And the unlocking method to use - I'm not familiar with dirty santa or lafsploit (might not have spelled that correctly). There is a tool called LGUP and a good thread on that below that I was reading but it is long read which is good for learning.
I can only point you to some threads - but unlocking is the next hurdle.
You might also want to use the latest TWRP and Magisk if you do get to root the phone. I used PHOENIX591's TWRP
- there is a good thread on that. https://forum.xda-developers.com/v2...-t3720239/post78529520?nocache=1#post78529520
Sorry I can't help you more with this - you do need to get the phone unlocked first. Some of these things are very device specific
I'm still keeping an interested eye on this...
Here is the other thread
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Good Luck!

secondhand2 said:
Hi,
I have a US996 and I unlocked it using the lg web site - they send a bin file that you can use to unlock the phone.
There are different exploits on different versions of V20 phones. THere are also versions of Nougat that have an anti rollback that stop you from going from a recent OTA update back to an older one that can be exploited to get root. For example, on the US996 I have., if I had bought it and it had been patched with 10p (not 100% sure which version was the cutoff point) even if the phone was unlocked, I might not be able to get root. So the versions of the ROMs/firmware are imnportant. As it happened I had the 10f version so rooting was possible - but I followed the threads on this site for my specific phone and stuck to STOCK rom's.
So I'm not sure about what ROM you have - i..e which version of the vs995 is rootable after you unlock the phone. And the unlocking method to use - I'm not familiar with dirty santa or lafsploit (might not have spelled that correctly). There is a tool called LGUP and a good thread on that below that I was reading but it is long read which is good for learning.
I can only point you to some threads - but unlocking is the next hurdle.
You might also want to use the latest TWRP and Magisk if you do get to root the phone. I used PHOENIX591's TWRP
- there is a good thread on that. https://forum.xda-developers.com/v2...-t3720239/post78529520?nocache=1#post78529520
Sorry I can't help you more with this - you do need to get the phone unlocked first. Some of these things are very device specific
I'm still keeping an interested eye on this...
Here is the other thread
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Good Luck!
Click to expand...
Click to collapse
You're incorrect arb hasn't been incremented on the 996
Sent from my LG-H910 using XDA Labs

Hi cnjax
The thread I used discussed arb but from what I remember it was never clear how to know which arb ( 0 or 1 ) a particular update was at. Are you saying there is never an increment for the us996?
Thank you for clarifying

secondhand2 said:
Hi cnjax
The thread I used discussed arb but from what I remember it was never clear how to know which arb ( 0 or 1 ) a particular update was at. Are you saying there is never an increment for the us996?
Thank you for clarifying
Click to expand...
Click to collapse
Was just pointing out that through the 996 oreo release lg hasn't incremented arb on the 996
Sent from my LG-H910 using XDA Labs

Hi cnjax
It is a bit difficult to read everything n get a clear picture sometimes. I'm hoping you would clarify something
If TWRP is not installed and the phone is unlocked but not rooted which method could be used to install oreo 20f?
Would you be forced to install 10f (nougat) to root and install twrp first before moving on to oreo?
In this scenario I assumed nougat was on the phone originally and it seems the phone is locked from the fastboot info given...but let's say it gets unlocked
Is there a method to install oreo first instead of starting with nougat and version 10f? If there is that would be awesome
Thank you!

secondhand2 said:
Hi cnjax
It is a bit difficult to read everything n get a clear picture sometimes. I'm hoping you would clarify something
If TWRP is not installed and the phone is unlocked but not rooted which method could be used to install oreo 20f?
Would you be forced to install 10f (nougat) to root and install twrp first before moving on to oreo?
In this scenario I assumed nougat was on the phone originally and it seems the phone is locked from the fastboot info given...but let's say it gets unlocked
Is there a method to install oreo first instead of starting with nougat and version 10f? If there is that would be awesome
Thank you!
Click to expand...
Click to collapse
If his bootloader is locked he'll need to downgrade, root and unlock the bootloader with dirty santa, flash updated twrp, flash a rom and magisk
Sent from my LG-H910 using XDA Labs

Post #71 about dumping contents/partitions with lgup seems a good idea -
Then I would try fastboot oem unlock to see what happens but not sure if that can break the bootloader or not. I think you would be in a deeper hole if it went south on you. I'm not sure if doing fastboot oem unlock can be risky at this point