I have a rooted Verizon LG G2 and have been trying to install a recovery mod. I somehow got rid of the stock recovery, but couldn't setup a new one. Now my phone is stuck on the fastboot screen. I've been able to get it to the stock recovery screen, but when it starts to wipe the drive, it just takes me back to the fastboot screen. I'm very new to this and haven't been able to figure this out through any other threads. I'm using Ubuntu. Any help would be greatly appreciated!
joshuascan said:
I have a rooted Verizon LG G2 and have been trying to install a recovery mod. I somehow got rid of the stock recovery, but couldn't setup a new one. Now my phone is stuck on the fastboot screen. I've been able to get it to the stock recovery screen, but when it starts to wipe the drive, it just takes me back to the fastboot screen. I'm very new to this and haven't been able to figure this out through any other threads. I'm using Ubuntu. Any help would be greatly appreciated!
Click to expand...
Click to collapse
I'm in the same boat. I tried to install TWRP using the Autorec but accidentally used the one for the LS980, and now I'm stuck at the fastboot screen. Did you ever solve this?
eye_rule said:
I'm in the same boat. I tried to install TWRP using the Autorec but accidentally used the one for the LS980, and now I'm stuck at the fastboot screen. Did you ever solve this?
Click to expand...
Click to collapse
Code:
1. download fastboot
2. download laf.img boot.img aboot.img for your variant
(or download your kdz, download kdz/tot extractor and extract partitions --and rename them from boot_45465757.bin to boot.img)
* boot_45465757.bin is just an example.
3. fastboot flash aboot aboot.img
4. fastboot flash boot boot.img
5. fastboot flash laf laf.img
-> download mode should be back
sorry for jumping back on this thread but im having the same problem...phone boots up to just fastboot....ive been reading for 4 days now trying to find any possible way to fix my phone...it really sucks not having a phone...so now im able to connect the phone to the laptop via fastboot but im looking for this laf.img, boot.img etc files. where can i find them?
Also vs980?
robledjl said:
sorry for jumping back on this thread but im having the same problem...phone boots up to just fastboot....ive been reading for 4 days now trying to find any possible way to fix my phone...it really sucks not having a phone...so now im able to connect the phone to the laptop via fastboot but im looking for this laf.img, boot.img etc files. where can i find them?
Click to expand...
Click to collapse
This can be fixed .
1. You Will need to Download the Stock KDZ/TOT file for your phone , find the right KDZ or TOT file from here .
2. Now you would have to extract the KDZ/TOT file that you downloaded above using WindowsLGFirmwareExtract-1.2.1.0-Release.zip , this is available in the guide here.
3. Extract all the files fro the KDZ/TOT .
4. Now flash the extracted files , based on the fastboot method , which is described here.
Code:
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash dbi dbi.img
fastboot flash laf laf.img
fastboot flash misc misc.img
fastboot flash modem modem.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm.img
fastboot flash sbl1 sbl1.img
fastboot flash tz tz.img
Let me know if you need more help.
Why so many partitions. Be sure to flash same version as your current android is at least.
I was looking for a light 2.1 rom and found this one: http://forum.xda-developers.com/showthread.php?t=1038337 (Lite edition)
Being a beginner, i got a few questions.
Do i need my phone flashed to V20E using .kdz beforehand? My current is V20B + fastboot.
There is kernel img provided, but iam not sure how to use it.
Which clockwork recovery do i need? As i understand 2.1 roms can only be flashed with old recoveries, such as 2.5.x.x . My current version is 3.0.2.4.
Thanks.
Img files can be flashed via fastboot commands:
on your PC type:
fastboot devices (makes sure its recognized)
fastboot -w (wipes data, cache)
fastboot erase boot
fastboot erase system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
You'll need the fastboot drivers to be installed of course
Tnx for fast reply.
But do i need V20E.kdz rom specifically and flash my phone with KDZ updater? I couldnt find working links for V20E.kdz, only A,B&C.
berins said:
Tnx for fast reply.
But do i need V20E.kdz rom specifically and flash my phone with KDZ updater? I couldnt find working links for V20E.kdz, only A,B&C.
Click to expand...
Click to collapse
nope thats not needed
Hello guys, I wanted to share something I've discovered so that others will not repeat my same mistake. And yes I'm a noob
A little backstory
I have an Asian XT1033 Moto G, bootloader unlocked, rooted and using Faux's kernel. So, after reading some feedback about 5.1.1 for XT1033, I've been tempted to flash 5.1.1 over my 4.4.4.
The problem
I've downloaded the stock 5.0.2 Asia XT1033 firmware in img format, and proceeded to flash them via fastboot using Minimal ADB and Fastboot. (I tried to fastboot flash 5.0.2 stock firmware directly from 4.4.4 stock). Everything was fine, after flashing each part, Okay messages were shown. After rebooting, my Moto G booted and showed the usual "Warning Bootloader Unlocked" screen. EXCEPT, the "Warning Bootloader Unlocked" screen stayed for more than 10minutes......., I've spent the whole midnight trying to reflash back using 4.4.4 stock Asia firmwares (same stucked at warning screen), baffled, googling for similar problems encountered in hopes of a solution, but found nothing. The next day something came to my mind and I googled "the difference between fastboot and mfastboot" which led me to Mark_Venture's website, and after some reading, I first facepalmed myself hard and then screamed Eureka with my mind
What's causing this
To rephrase Mark_Venture, "fastboot is compatible with almost all Android devices, but is limited on how big the size of files it can actually flash, while Motorola have their own version called mfastboot which surpassed the file size limits of the usual fastboot", so basically when I tried to flash via fastboot, the command I've typed was "fastboot.exe flash partition gpt.bin" which is wrong and should be "mfastboot.exe flash partition gpt.bin", so basically I've used the usual fastboot.exe instead of Motorola's own mfastboot.exe. This probably explains why all the other files from the stock firmware are successfully flashed, EXCEPT the system.img_sparsechunk.0123 files due to their average sizes easily exceeding 256MB (my own take here, correct me if I'm wrong). This probably explains why rebooting after flashing via fastboot doesn't work because the system imgs are not flashed, and hence the phone get stucked at "Warning Bootloader Unlocked" screen because there is no ROM to boot to.
Alternatively, actually much more easier
You can also flash using fastboot a custom recovery, then boot into the custom recovery and either adb push or using USB OTG to install ROM zips. Personally I've used USB OTG with PhilZ Touch Recovery to install custom ROM and my phone finally boots.
TL;DR
Use mfastboot.exe instead of fastboot.exe when flashing via fastboot
Big credits to Mark_Venture and his website
Source: http://mark.cdmaforums.com/MotoX-mFastboot.htm
Great find. TIL for me too
Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.
where do you get the stock firmware?
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
We're you able to revert to a locked bootloader after this, I am looking forward to do so
We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier
downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions
Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks
astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition
I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan
My V35ULM was soft-bricked after using LGUP to flash the Pie kdz (likely because the LGUP exe was not patched correctly). The download mode is corrupted and the phone always enters into fastboot mode. I'm trying to fastboot an external download-mode image by:
fastboot boot laf.img
However, the laf.img extracted from the Pie kdz cannot pass the boot security check. Can anyone who has this phone (LMV350ULM) with Oreo 10i ROM help dump a stock laf.img with LGUP? Many thanks!
I was able to get a stock laf.img using Elliott Mitchell's kdztools python scripts. However, fastmode boot laf.img still won't boot. Maybe only the image backed up from the original phone can work?
II guess you were using the partition dl mode to update your phone and do not chose them all?
any way
try this
plug in your USB, vol- + power or fastboot reboot to reboot your phone ,then immediately press the VOL+ before the v35 thingQ shows
by the way,even if use 9008\oct-p to unlock the v35.
not like the g7,boot xxx.img is still useless,
flash xxx_a XXXX.img can works
like flash boot_a patched_boot.img(magisk)