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.

[ROOT][Surnia]Moto E 2015 root all the things!

disclaimer:
Code:
I take no responsibility for any devices that may be bricked,
or any bad things that will happen to you.
flash/boot twrp from here
either flash SuperSU by chainfire, or reboot system and accept installing supersu via TWRP.
we've experienced a bug on the first boot after flashing supersu, where there is no boot animation. instead the warning sign will stay up saying "you're unlocked".
Do not worry. It will still load, and supersu will prompt you to finish installing SU. do so, and everything will be back to normal.
A known issue happens, where root breaks the camera.
If this happens to you, then change SeLinux to permissive. I may look in to fixing it properly at a later point.
thank you to @fix-this for testing
previous post:
Please note this is a development thread. If something is said that is NOT constructive, I will have it deleted.
OK so this thread doesn't tell you how to root your device... yet.
in the process of rooting my device, I have essentially soft bricked it until I can get hold of either a boot/recovery image, or I find out the kernel base, ramdisk offset and tags offset.
long story short, I shouldn't have been messing about with the system while I was tired, so I forgot about dm-verity, and now it won't boot since the boot image contains a dm-verity key. hurrah for perma root prevention systems finally working.. sort of..
Motorola has implemented a nifty method in to their bootloaders. It essentially allows you to dump a partition. This is when I stumbled on yet another security measure. to allow you to do anything with the bootloader, you must flick a switch in the android dev settings to give full access... oh wait, I can't load the system I don't know if this switch is done by writing a value to memory, or is passed on with the reboot reason. I don't know Java that well, and I sure as hell don't know smali.
So far I have attempted:
Dump a modified system image (Failed because dm-verity).
Pull the boot image (Failed because SELinux)
Dump the boot image via moto fastboot (failed because either outdated mfastboot, or security from [read above])
Boot directly in to DLOAD mode. (Failed. seems with the msm8916, they've changed the method of accessing it, and having dload mode is now optional [which they disabled.. probably..]. I'm not going to risk wiping the bootloader to see if DLOAD mode will load as a fail safe).
so how can you help?
method failed. trying something else..
I need someone who doesn't mind unlocking their bootloader (or already has done), and doesn't need their hand holding. (request for hand holding isn't development, it will be deleted).
unlock bootloader.
get mfastboot
go to settings, dev settings, and allow oem unlock
boot to fastboot/bootloader
run this command
Code:
mfastboot oem partition dump recovery
If this fails, then try this (with this fastboot) (Thank you @m1cha for this version of fastboot, sources here)
Code:
fastboot_dump dump recovery.img oem partition moto-dump recovery
send the results back to me
Hopefully, this will all go well. If not, I'll spend a few hours figuring out the values they've used for the kernel base and offsets.
If anyone else has any ideas (even if it's to get a temp root), then feel free to share them
Big thankyou to @PotatoJ who has donated a very generous $20

And it finally begins

Gave em both the commands, nothing. Both are restricted. Ugh...
C:\windows\system32>fastboot dump recovery.img oem partition moto-dump recovery
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.002s

more updates. just been told that those commands are for internal use only.
had an idea though.. will get back to you

cybojenix said:
more updates. just been told that those commands are for internal use only.
had an idea though.. will get back to you
Click to expand...
Click to collapse
Whatever you need, let me know. I've got the phone waiting for commands.

if im correct i think the system images are now available. ill help with what i can to obtain root. id hope rooting this wont be too hard considering we can unlock the bootloader via moto.
i also messaged jcase to see if he might be able to help us.

fix-this! said:
if im correct i think the system images are now available. ill help with what i can to obtain root. id hope rooting this wont be too hard considering we can unlock the bootloader via moto.
i also messaged jcase to see if he might be able to help us.
Click to expand...
Click to collapse
No need for jcase now. the boot image is out. I can patch it, and talk with chainfire about how to best handle dm-verity

cybojenix said:
No need for jcase now. the boot image is out. I can patch it, and talk with chainfire about how to best handle dm-verity
Click to expand...
Click to collapse
Yeah jcase responded and said since we can unlock the bootloader all we needed was a custom recovery to flash superuser. Was just trying to help.

fix-this! said:
Yeah jcase responded and said since we can unlock the bootloader all we needed was a custom recovery to flash superuser. Was just trying to help.
Click to expand...
Click to collapse
it's kind of a pain to make a custom recovery without having a recovery/boot image

Do you plan on making the recovery work with the boost mobile Variant

903tex said:
Do you plan on making the recovery work with the boost mobile Variant
Click to expand...
Click to collapse
no. I don't have the device.
btw, got twrp on it, however the return of the "No touch till screen goes off" bug is back.

Xda seems to be glitching, and won't show there's a thread in original dev from the main forum, so here's a direct link.
http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726

if you need me to test, pm me. otherwise ill wait until you say its ok to root.

Code:
$ adb shell
[email protected]_umts:/ $ su
[email protected]_umts:/ #

cybojenix said:
Code:
$ adb shell
[email protected]_umts:/ $ su
[email protected]_umts:/ #
Click to expand...
Click to collapse
congratulation to you to gaining root access. :good::good::good:
we want rooting all together:laugh::laugh:

cybojenix said:
Code:
$ adb shell
[email protected]_umts:/ $ su
[email protected]_umts:/ #
Click to expand...
Click to collapse
you hard work is much appreciated.

so some bad news. the GB and EU variants have different camera blobs it seems.
unless I get decent testers, I will not be supporting the different variants.

cybojenix said:
so some bad news. the GB and EU variants have different camera blobs it seems.
unless I get decent testers, I will not be supporting the different variants.
Click to expand...
Click to collapse
how would i know if i have a gb or eu variant? and yes that's sad indeed for users. ill test whatever you need. i have an unlocked lte gsm model from moto.

root is done, thanks @fix-this for doing the final testing

cybojenix said:
root is done, thanks @fix-this for doing the final testing
Click to expand...
Click to collapse
Whatever you need for the CDMA variant I'll be happy to provide!

Unlocking Bootloader Problem

Im a veteran in the rooting of phones, but with the 6P when I OEM Unlock it says "failed remote: unknown command" ironically it lets me reboot and the other commands, I tried the new "flashing unlock" command with no avail, anyone help?

AquaticXi said:
Im a veteran in the rooting of phones, but with the 6P when I OEM Unlock it says "failed remote: unknown command" ironically it lets me reboot and the other commands, I tried the new "flashing unlock" command with no avail, anyone help?
Click to expand...
Click to collapse
Make sure your android SDK is up to date.
Sent from the Nodes of Ranvier

dumb question, but did you enable bootloader unlocking in Dev options?

You will need to update your SDK. Just do the platform tools and tools sections.

Roscopcoletrain said:
dumb question, but did you enable bootloader unlocking in Dev options?
Click to expand...
Click to collapse
Yes it's unlocked, and @ the first guy I've been rooting since 2009 so I thought the SDK was static. Maybe that's the issue.

AquaticXi said:
Yes it's unlocked, and @ the first guy I've been rooting since 2009 so I thought the SDK was static. Maybe that's the issue.
Click to expand...
Click to collapse
The command is now fastboot flashing unlock

Update: So I unlocked the bootloader, but when I go to root it with the Skipsoft program it says device is 'null' can't flash or sideload the SuperSU.zip file either. Any work arounds?

AquaticXi said:
Yes it's unlocked, and @ the first guy I've been rooting since 2009 so I thought the SDK was static. Maybe that's the issue.
Click to expand...
Click to collapse
The SDK gets updated every few months, sometimes more. Definitely update to the latest 6.0 platform-tools. If you're using tools from Eclair....yeah, it's gonna break.

AquaticXi said:
Update: So I unlocked the bootloader, but when I go to root it with the Skipsoft program it says device is 'null' can't flash or sideload the SuperSU.zip file either. Any work arounds?
Click to expand...
Click to collapse
Flash TWRP recovery first and throw SuperSU.zip on the phone storage and flash it with recovery. That's the easiest way to root IMO.

Please help me build twrp on oppo a37f

Oppo a37 does not have a fastboot option first i need help about enabling it. .... someone on forum said they removed it so is there any way to flash fastboot in oppo.. ?
I also need someone to help me build twrp for oppo a37 .......I'll provide all the necessary files.. ....
if someone already unlocked bootloader or has twrp for oppo a37(neo 9) then please reply here.. .
i have rooted it with latest kingroot app

Hey i rooted with kingroot and i ported twrp3.0.2 .But twrp touch not working. You can replace super su with twrp by twrp manager.

KoSett said:
Hey i rooted with kingroot and i ported twrp3.0.2 .But twrp touch not working. You can replace super su with twrp by twrp manager.
Click to expand...
Click to collapse
if touchscreen is not working, unpack recovery and see if it has the modules inside, put them on Twrp if its not there, use stock boot.img and copy all the modules to twrp and it should have touchscreen working, its just a little help since i did this to my device and it started working.

Ruben Craveiro said:
if touchscreen is not working, unpack recovery and see if it has the modules inside, put them on Twrp if its not there, use stock boot.img and copy all the modules to twrp and it should have touchscreen working, its just a little help since i did this to my device and it started working.
Click to expand...
Click to collapse
The twrp @KoSett ported when i flash it then it does not work .... phone reboot to normal .... recovery doesn't work at all.... can you tell me what is the problem here

hamzachaudhry36 said:
The twrp @KoSett ported when i flash it then it does not work .... phone reboot to normal .... recovery doesn't work at all.... can you tell me what is the problem here
Click to expand...
Click to collapse
is bootloader unlocked?

Ruben Craveiro said:
is bootloader unlocked?
Click to expand...
Click to collapse
no sir ... the thing is oppo a37f does not have fastboot binarys and also bootloader is locked .....

hamzachaudhry36 said:
no sir ... the thing is oppo a37f does not have fastboot binarys and also bootloader is locked .....
Click to expand...
Click to collapse
all devices have fastboot.. reboot to bootloader and try to unlock bootloader after you on debug settings enable oem unlocking, on bootloader it acts like fastboot..

Ruben Craveiro said:
all devices have fastboot.. reboot to bootloader and try to unlock bootloader after you on debug settings enable oem unlocking, on bootloader it acts like fastboot..
Click to expand...
Click to collapse
I tried oem unlocking.
when reboot to bootloader through flashify it reboots normally.
when using PC and adb the command to reboot to bootloader/fastboot boots device normally.
Please check this thread : http://forum.xda-developers.com/r7-plus/help/decision-oppo-bootloader-fastboot-t3348114

Ruben Craveiro said:
all devices have fastboot.. reboot to bootloader and try to unlock bootloader after you on debug settings enable oem unlocking, on bootloader it acts like fastboot..
Click to expand...
Click to collapse
Also can you help me port Xiaomi Redmi 2 twrp for my Oppo a37f ? I will provide all the required files PLEASE!

hamzachaudhry36 said:
Also can you help me port Xiaomi Redmi 2 twrp for my Oppo a37f ? I will provide all the required files PLEASE!
Click to expand...
Click to collapse
if bootloader is locked, the bootloader wont allow twrp to boot since its an unofficial unsigned image (not signed by the OEM)

Ruben Craveiro said:
if bootloader is locked, the bootloader wont allow twrp to boot since its an unofficial unsigned image (not signed by the OEM)
Click to expand...
Click to collapse
Two Questions :
1)Is there a way out of this? (Can bootloader be unlocked somehow)
2)How did @KoSett succeeded in installing twrp in his oppo a37f with locked bootloader

hamzachaudhry36 said:
Two Questions :
1)Is there a way out of this? (Can bootloader be unlocked somehow)
2)How did @KoSett succeeded in installing twrp in his oppo a37f with locked bootloader
Click to expand...
Click to collapse
1- i read something about a project from the thread link you showed me that it restores bootloader functions
2- he problably used that method or still uses old software versions where the patch to remove bootloader hasnt been made yet..

Ruben Craveiro said:
1- i read something about a project from the thread link you showed me that it restores bootloader functions
2- he problably used that method or still uses old software versions where the patch to remove bootloader hasnt been made yet..
Click to expand...
Click to collapse
Its project spectrum rom instead of colorOS rom, but it is not compatible for oppo a37f
and i think he is using the same software but still i'll ask him for his version of OS.....
It's all my fault i didn't go through details of phone before buying....
So the final thing is i am stuck with a phone without fastboot and locked bootloader and can't install TWRP... It sucks!

hamzachaudhry36 said:
Its project spectrum rom instead of colorOS rom, but it is not compatible for oppo a37f
and i think he is using the same software but still i'll ask him for his version of OS.....
It's all my fault i didn't go through details of phone before buying....
So the final thing is i am stuck with a phone without fastboot and locked bootloader and can't install TWRP... It sucks!
Click to expand...
Click to collapse
And is there a way that i can get his Binarys for my phone or his whole rom 'cuz on the internet there is only latest rom (afterall our phones are the same)

hamzachaudhry36 said:
And is there a way that i can get his Binarys for my phone or his whole rom 'cuz on the internet there is only latest rom (afterall our phones are the same)
Click to expand...
Click to collapse
i dont think so.

Hey bro, We will get twrp officially at tomorrow.And Unlocked bootloader with miui8 rom.
Thank .I will made new thread wait 8hrs.Thz.

Whats the progress now?

KoSett said:
Hey bro, We will get twrp officially at tomorrow.And Unlocked bootloader with miui8 rom.
Thank .I will made new thread wait 8hrs.Thz.
Click to expand...
Click to collapse
It's tomorrow now, how's progress going?

I have submitted my source code to twrp official.. They will send direct link to test build soon be ready.

Hey, Use oppo tool with unlock bootloader then flash recovery image.

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