Database Info

Root Moto G on Lollipop 5.0.2

Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked

n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
Click to expand...
Click to collapse
can i use with stock recovery?
thanks.

vbnoob said:
can i use with stock recovery?
thanks.
Click to expand...
Click to collapse
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta

n1c00_ said:
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta
Click to expand...
Click to collapse
My phone is unlocked bootloader with stock recovery.
Thanks.

vbnoob said:
My phone is unlocked bootloader with stock recovery.
Thanks.
Click to expand...
Click to collapse
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...

n1c00_ said:
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...
Click to expand...
Click to collapse
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.

I think I screwed phone. Being a noob I didn't realise fastboot and Bootloader screens are different. I went and use chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions link
in fastboot. After error failed now it ADB doesn't detect my phone.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>
Any advise to help me? Tried hard method going to bootload still nothing either or at least I think its nothing since this is first attempt I ever tried root my phone. Everytime I plugin in fastboot or even in normal mode the pc does detect it. But it just won't show up in adb.
Decided to try again using leocuervo1983 method for fastboot it stated as fail as well but somehow I got root even though adb still no longer detect my phone.
Edit:
Just found out fastboot doesn't use adb commands or do they? I feel stupid. I Guess there are no issues then even if failed still got root. Fastboot commands works adb doesn't work.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
TAXXXXXXXX fastboot

The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.

pfufle said:
The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.
Click to expand...
Click to collapse
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?

Xicor Yagami said:
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?
Click to expand...
Click to collapse
Yes since the recovery isn't entirely compatible with the new kernel.

pfufle said:
Yes since the recovery isn't entirely compatible with the new kernel.
Click to expand...
Click to collapse
Tried latest TWRP? same results?

Xicor Yagami said:
Tried latest TWRP? same results?
Click to expand...
Click to collapse
yep.

n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked
Click to expand...
Click to collapse
Thanks a lot! Worked like a charm using mfastboot command.

Works fine
My bootloader was however unlocked...I tried this on CM12....extract the img file from the CF-Auto root File and then flash on the bootloader mode...with mfastboot boot filename.img

The method same as that of kitkat works for lollipop too...you could made some mistake unknowingly somewhere in the middle while following the original procedure
Sent from my Moto G using XDA Free mobile app

is there any method to root moto g?
Any side effects of chainfire method?

leocuervo1983 said:
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.
Click to expand...
Click to collapse
It did'n work for me .... I ran the bat file , and when I pressed a key, it was waiting for the phone and nothing happened.
Edited:
Sorry... I forgot to unlock bootloader first.... worked fine!!! Thanks a lot!!!

Bricked? Please help!

My OPO is 100% stock currently running the second latest OTA update(coz I'd received a notification saying theres new update today but i haven't updated)
It was working perfectly fine until just now when I withdraw it from my pocket it shows the 1+ Powered by android loading screen.
I re-booted and it stuck at the same screen. I then boot into recovery and factory reset, wipe data wipe cache and boot and its still stucking at the same loading screen.
P/S : I was on wifi for a while in the cafe maybe it had downloaded the new OTA and maybe when the screen rubs against my pants in my pocket idk how it unlocks itself and it update itself with the downloaded(maybe) software update and eventually it dies. This might be one of the possibilities because if otherwise, it just dies itself without reason lel.
I've researched abit and someone suggested me to flash a stock rom using fastboot mode and PC adb command prompt which idk wtf is that lel. But in order to use that u need to unlock bootloader right, being 100% stock my bootloader is probably locked right?
omfg please guide me through this i need to solve this asap i dont have a backup phone. :silly::silly::silly::silly::silly::silly:

kingdew11 said:
My OPO is 100% stock currently running the second latest OTA update(coz I'd received a notification saying theres new update today but i haven't updated)
It was working perfectly fine until just now when I withdraw it from my pocket it shows the 1 Powered by android loading screen.
I re-booted and it stuck at the same screen. I then boot into recovery and factory reset, wipe data wipe cache and boot and its still stucking at the same loading screen.
P/S : I was on wifi for a while in the cafe maybe it had downloaded the new OTA and maybe when the screen rubs against my pants in my pocket idk how it unlocks itself and it update itself with the downloaded(maybe) software update and eventually it dies. This might be one of the possibilities because if otherwise, it just dies itself without reason lel.
I've researched abit and someone suggested me to flash a stock rom using fastboot mode and PC adb command prompt which idk wtf is that lel. But in order to use that u need to unlock bootloader right, being 100% stock my bootloader is probably locked right?
omfg please guide me through this i need to solve this asap i dont have a backup phone. :silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Follow this
http://forum.xda-developers.com/oneplus-one/help/solved-how-to-recover-oneplus-soft-t2864800
OR
Agai u can manually download any cm firmware
Then go to recovery
Factory reset
And flash desired firmware
FOLLOW this ( this is cm12 os)
http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/
If u don't like lollipop u can flash cm11s
FOLLOW this
http://www.technobuzz.net/update-oneplus-one-cm-11s-44s-resolve-several-bug-fixes/
note: u can find most guides on Google just search with keywords of your problems
Second mentioned flashing methods are most easiest prrocess
Factory reset and flash u r zip file

Problem solved. Detailed solutions for noobs like me!
OKAY here is what I DID. it may not work for u, but it worked for me. so if ur gonna follow these steps do it at ur own risk. and please dont expect me to helpp u to counter any special circumstances i.e. any condition not stated here coz im a perfect noob too, lel.
FYI this is called flashing roms in fastboot mode. And i had successfully flashed my OPO back into CM12.
STEPS :
Using a windows PC:
1) Download the UNIVERSAL ABD driver for Windows and freaking INSTALL IT.
2) Download the OnePlus One CM12 factory image “cm-12.0-YNG1TAS0YL-bacon-signed-fastboot.zip” (fastboot flashable package).
3) Download the flashing tools. ( it contains 4 things: adb.exe AdbWinApi.dll AdbUsbWinApi.dll and fastboot.exe)
the download links are available from this link:
ok im not allowed to attach links but u can search for it " webtrickz[dot]com how to flash cm12 factory image fastboot mode"
however, the steps given in the above link are crappy as well so follow mine =P just do the downloadings only from there.
4) Extract the 4 things from the flashing tools zip file into a folder, name it whatever****ing folder u want. we call it folder X.
5) and then extract all the things in the CM12 rom zip file into folder X.
6) Boot ur phone into fastboot mode simply by pressing and holding down the power button and the volume up button simultanoesly until u see "fastboot mode" with an Android face appears.
7) Connect ur phone to your PC with a USB cable. Now ur phone should be connected to the pc in fastboot mode.
8) open up folder X. then right click in folder X while holding down the Shift button, and click on "Open command window here"
p/s : this, I think, is like a special way to open up a cmd prompt used specifically for abd/fastboot. U can also actually open up cmd prompt normally but in order to do that you need to install idk some **** so that ur NORMAL cmd prompt will recognise abd or whatever **** it is. however, if u do that, u do not need to extract the CM12 rom files into folder X as the NORMAL cmd prompt will have the ability to, sorta like detect the CM12 ****s. anyways, forget it, just ****ing use the special way i.e. go to folder X , shift + right click to open up the SPECIAL cmd prompt)
9) a command prompt(cmd) should appear, Now check if u are connected by keying in "fastboot devices" in the cmd. Then the serial number of ur phone should turn up, and not " waiting for device" "devices not found" or any messages of that sort.
If the latter appears, idk how to help u sort that out urself lel.
10) Now u have to unlock the OEM in order for this flashing process to work. idk whats unlocking oem but just unlock it FFS. To do this, simply key in "fastbook oem unlock"
11) I think that under normal circumstances, a pop-up will appear in ur phone to let u choose if u really wanna unlock this oem thingy. BUT for me, my phone just rebooted back into the ****ing 1+ Powered by android screen idk why, but its alright i was on the right track as my oem has been unlocked. Then i powered off my phone and booted in back into fastboot mode once again. (FYI whenever I have to boot my phone to fastboot mode I disconnect the usb cable idk if this is necessary but thats what i DID)
12) go back to the CMD just now, and freaking paste the commands listed below into the CMD.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
13) Wait for several minutes, and when everything's done, the commands will stop at the last command which is "fastboot reboot"
Press Enter! and ur phone will reboot normally! =)

walpanmad said:
Follow this
http://forum.xda-developers.com/oneplus-one/help/solved-how-to-recover-oneplus-soft-t2864800
OR
Agai u can manually download any cm firmware
Then go to recovery
Factory reset
And flash desired firmware
FOLLOW this ( this is cm12 os)
http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/
If u don't like lollipop u can flash cm11s
FOLLOW this
http://www.technobuzz.net/update-oneplus-one-cm-11s-44s-resolve-several-bug-fixes/
note: u can find most guides on Google just search with keywords of your problems
Second mentioned flashing methods are most easiest prrocess
Factory reset and flash u r zip file
Click to expand...
Click to collapse
I can't flash it with recovery, as i cant 'insert' any ROM into my internal memory, as i cannot access my Internal memory, coz the phone wont boot?
However thank you so much! problem solved =)

kingdew11 said:
I can't flash it with recovery, as i cant 'insert' any ROM into my internal memory, as i cannot access my Internal memory, coz the phone wont boot?
However thank you so much! problem solved =)
Click to expand...
Click to collapse
Phone wont boot means?
If u are able to get in to recovery then its always possible to flash any official firmware without root with factory reset its easiest process to solve soft bricked device
First method mentioned is the same process u had done
(fastboot recover) but its automated process with OPO tollbox
Again fastboot method is usefull if u already enabled usb debugging in developer option before u went in to bootloop
I think u have previously enabled usb debugging
So it is also a method to recover u r problem
Any way its great news u got it worked

Flashed stock recovery and thought I soft bricked my shield tablet.

First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!

i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester

did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.

Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.

I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.

rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.

Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help

Possible Way to Unlock Bootloader?

I wrote this earlier in the Bounty page for the bootloader unlock, but just so other people can see this as well, here is it in post form! This is the way to unlock bootloader on G3 so if anyone is on lollipop and is rooted, could they try it?
-- STEP 1: Remove LG Download mode (laf)
Important! You’ll need root access to remove (laf), so make sure you’ve rooted before proceeding with the steps below:
Download ADB files:
Prepare your phone:
Enable developer options: Go to your phone’s Settings » select About phone » Scroll to the bottom and tap on “Build number” seven times to enable developer options
Enable USB Debugging: Open phone’s Settings » select Developer options » Tick the “USB debugging” checkbox (under Debugging section)
Connect your phone to PC with a USB cable and if/when a pop-up screen shows up on Phone asking you to ‘Allow USB debugging?‘ for the computer, make sure you tick the checkbox and tap OK
Now type/paste the following ADB commands to backup LG Download Mode (laf), so you can restore it later when necessary
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Now run the following command to remove laf and reboot your phone
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
exit
adb reboot
Your phone will now reboot
Now to go into fastboot
adb reboot bootloader
Unlock bootloader!
fastboot oem unlock
or
fastboot flashing unlock
I took this info from original source listed below and made a few changes..
http://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445

Good..but there is no fastboot in g flex 2.. Even if there was no fastboot commands would work..
So thats that

adds08 said:
Good..but there is no fastboot in g flex 2.. Even if there was no fastboot commands would work..
So thats that
Click to expand...
Click to collapse
My point is that the G3 also can't go into fastboot until you do this. So I just want people to see if it'll work, cause I'm on Linux and marshmallow so I can't test it. I think the G Flex 2 is more similar to the G3 than the G4 so that's why I'm asking for people to try it out

People already managed to enter fastboot, but no fastboot commands works.

I m going to try it but I need the commands to reflash download mode.
And then how do I know I succeeded?
I mean,with bootloader unlock,is there any way to flash a custom recovery to see if it works?

Pungasul said:
I m going to try it but I need the commands to reflash download mode.
And then how do I know I succeeded?
I mean,with bootloader unlock,is there any way to flash a custom recovery to see if it works?
Click to expand...
Click to collapse
Checking Bootloader Unlock : fastboot oem device-info
reflashing download mode : dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf

Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..

adds08 said:
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
Click to expand...
Click to collapse
Just out of curiosity, but what commands did you use?

adds08 said:
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
Click to expand...
Click to collapse
Because the Nexus 6P is known for saying unknown command if you type fastboot oem unlock instead of fastboot flashing unlock

Try it... But dont forget to backup laf in case of failure .. I have done every possible commands new or old

Hi,
I tried this and erased the LAF. Then when you hold "Vol+" and plug-in USB cable you will see "[310] Fastboot mode started".
In Windows device manager I got "Marshall London Bootloader Interface" ... can't remember that I installed any driver but this is the LG G Flex 2.
Unfortunately it seams that there are no fastboot commads are working. I tried this with Android 5.0.1 because this was the only version I got rooted.
So this looks good to me but also it seams an dead end at the moment.
Best regards

CryptMan said:
Hi,
I tried this and erased the LAF. Then when you hold "Vol+" and plug-in USB cable you will see "[310] Fastboot mode started".
In Windows device manager I got "Marshall London Bootloader Interface" ... can't remember that I installed any driver but this is the LG G Flex 2.
Unfortunately it seams that there are no fastboot commads are working. I tried this with Android 5.0.1 because this was the only version I got rooted.
So this looks good to me but also it seams an dead end at the moment.
Best regards
Click to expand...
Click to collapse
i have a 950 that died on me some months ago and now i get Fastboot mode started but no commands work .
maybe if i put the LAF back on it it will boot ?

caesar170988 said:
maybe if i put the LAF back on it it will boot ?
Click to expand...
Click to collapse
I don't think so.
But with LAF back and started you should be able to use "LG UP" to flash a new firmware.
I can't tell you how you will be able to do that if it is not booting.

erased os on mi mux 2s

Hi ppl. I need help bad! I accidentally erased my os. So when I try to flash a rom using the mi flash tool(which is amazing) it won't work because I have no operating system to enable USB debugging.so it says enable USB debugging but I can't. Any help would be appreciated TW RP installed unlock bootloader. Thanks in advance!!

just flash recovery rom using twrp then.

Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.

So twrp is flashed? Then yes try sideload. Also make sure your ADB is up to date as I've had that cause issues with large files and sideload before.
M.

dirtyrott3njb said:
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
Click to expand...
Click to collapse
Miflash doesn't need for usb debugging to flash rom I believe. It's all fastboot. If ur phone is not detected by pc, it means drivers.

It does indicate USB debuging not on. So yes it does . I've used it before to flash TWRP. The flash will also install the drivers before you use it so I can understand why it won't let me transfer anything from PC to phone when fastboot mode. It won't let me get past that stuff in this USB debugging is enabled. Frustrating brand new phone to only a couple weeks old.

Have you booted to twrp and format data (the one where you have to type "yes")?
Mi flash only required adb because it needs to run adb reboot fastboot. I'm in the States as well, PM me and maybe we can get this guy working over remote support. I haven't seen this issue myself, so I can't comment much.
Sent from my Mi MIX 2S using Tapatalk

@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?

dirtyrott3njb said:
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
Click to expand...
Click to collapse
Its all good. I'm about to pick up my kids from school, so let me head home, I'll PM you in a bit. We can use TeamViewer or something. If it comes down to it, I also have my work login to use for remote assist. You just need a semi up to date laptop or desktop computer.
Hopefully we can get this solved quickly. I'm unfortunately not in your immediate area, otherwise much easier hands on. The company I work for is down the street from your location however, I'm just a remote systems guy.
Sent from my Mi MIX 2S using Tapatalk

How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?

dirtyrott3njb said:
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
Click to expand...
Click to collapse
Tried to pm you but msg sent failed.

Only thing is for some reason I can't transfer anything for my PC to TW RP or my internal storage some reason just doesn't accept it and it's not my computer

I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.

sg01fc said:
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
Click to expand...
Click to collapse
The OP's issue was solved by just flashing TWRP, booting to it and sideloading the Stock ROM. I had the OP download the fastboot files as well, but we ended up not needing them.