Fastboot error - G2 Q&A, Help & Troubleshooting

I have tried to install twrp recovery via fastboot and I get this error
1.C:\fastboot>fastboot flash recovery recovery.img
2.target reported max download size of 1526722560 bytes
3.error: cannot load 'recovery.img': No error
All other commands work to erase, reboot etc, but cannot flash recovery twrp on to my LGG2 D803 , any help will be appreciated.

Got it to work but flashed 3 different twrp and cm mod img and will not boot into recovery

Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014 in the command mode, by holding the volume up mode and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.

Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014, in the command mode, by holding the volume up button and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.

Related

[Q] VS980 Stuck in fastboot

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.

[GUIDE] Recovery from fastboot loop

I attempted flashing a ZVA zip earlier that uses `qcom.install_radio`. Unfortunately, this somehow causes my LS980 to loop in fastboot mode. I've seen a few other people talking about this happening to them as well, so decided I would share this.
Thanks to http://direct.xda-developers.com/showthread.php?t=2451426, I was able to get the original *.img files and drop them in with fastboot.
You'll need to go to http://downloads.codefi.re/autoprime/LG/LG_G2 and download the partitions that you need. After that is done, run the following (replacing with your file names along the way):
Code:
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash tz tz.img
fastboot flash rpm rpm.img
fastboot flash modem modem.img
fastboot flash laf laf.img
fastboot flash sbl1 sbl1.img
You can continue flashing the rest of the files, but these were the files that were effected by the zip I used and sufficed for getting it back online.
After that's done, you need to flash the *.img file for the recovery that you want. For instance, mine would be:
Code:
fastboot flash recovery twrp.img
You'll need to turn the phone completely off, then reboot it while holding power and volume down. This will get you into your recovery and allow you to recover from a backup, or whatever you'd like to do at that point.

No Os No Recovery & Boot failed

Guys, i need some help. i was messing with my nexus 7. then i tried to start fresh again by re-installing the stock 4.4.4. It's been a while since i flash Stock roms. So i find this tutorial, Erase boot, erase userdata etc. then when i tried to flash the bootloader, it always fail (unknown error). So im stuck with a OS-less Nexus 7 and no recovery. I can go to Fastboot. My device is recognizable through Fastboot devices. My old Rom was 4.4.4 stock. Please help me guys
Hello @vyrus027,
flash the files inside the factory image manually with these commands, it'll do the trick:
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
Keelah se'lai,
GethPrime

fastboot commands done by yotaphone flasher

This is the commands run by yotaphone flasher:
fastboot flash aboot firmware/emmc_appsboot.mbn
fastboot flash boot firmware/boot.img
fastboot flash system firmware/system.img
fastboot flash recovery firmware/recovery.img
fastboot flash cache firmware/cache.img
fastboot flash modem firmware/radio/NON-HLOS.bin
fastboot flash sbl1 firmware/radio/sbl1.mbn
fastboot flash rpm firmware/radio/rpm.mbn
fastboot flash tz firmware/radio/tz.mbn
fastboot flash userdata firmware/userdata.img
fastboot reboot
robinmalmberg said:
This is the commands run by yotaphone flasher:
fastboot flash aboot firmware/emmc_appsboot.mbn
fastboot flash boot firmware/boot.img
fastboot flash system firmware/system.img
fastboot flash recovery firmware/recovery.img
fastboot flash cache firmware/cache.img
fastboot flash modem firmware/radio/NON-HLOS.bin
fastboot flash sbl1 firmware/radio/sbl1.mbn
fastboot flash rpm firmware/radio/rpm.mbn
fastboot flash tz firmware/radio/tz.mbn
fastboot flash userdata firmware/userdata.img
fastboot reboot
Click to expand...
Click to collapse
It is a mistery for me. I make all this commands and the flash it is ok for all but my yd201 it is in bootloop always. I have tried alk kind if Roms kit kat, lollipoop. Version RU, EU, Chine, Hong Kong.
It worked! I used these commands to flash my yd206 to yd201 coming from 4.4.3 kitkat to 5.0.0-RU1.1.124 (the archive I downloaded from the Internet contained all required files) and after running them using the fastboot, as I said already, it worked! The first boot took very long, like like 8-10 minutes, I am not sure how long it took, but it was a while, but it worked in the end.

I've tried everything...

I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Reserved.
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Nimiskiv said:
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Click to expand...
Click to collapse
I can't even boot TWRP, it just shows the Oneplus logo and the"fastboot mode" thing forever. It's been 10 minutes now.
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
BillGoss said:
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
Click to expand...
Click to collapse
nope, still cant boot into twrp
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
BillGoss said:
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
Click to expand...
Click to collapse
OOS is 11.1.0.2.KB09CB
I've tried TWRP 3.6.1, 3.6.0, and 3.6.2
OOS does boot cleanly.
Phone is KB2007.
The bootloader is unlocked.
I've truly never had this problem before.
You'll probably have to upgrade to the latest version of OOS 11 (or 12) before TWRP will boot.
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version (kb2005) it can work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin unto payload dumper after extracting them all into a folder then use the commands to flash them all with adb. Then reboot to recovery, factory reset, and MSM tool back to TMO.
do these commands one by one replacing the .img with the location of the .img. actually, just drag and drop the file after. ( ex: fastboot flash logo C:\Users\???\Desktop\???.img )
Just an extra recommendation to wipe the device
( Fastboot -w )BEFORE THE OTHER COMMANDS but you don't need to if it works without wiping.
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
I'm way too inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
honest recommendation, just use TMO to International MSM tool after. unless you want to keep it TMO (kb2007)
Nimiskiv said:
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version so we got to work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin then use the .bat to flash them all onto the phone. Then reboot to recovery, factory reset and MSM tool it back to tmo. do these commands one by one replacing the .img with the location of the .img. actually just drag and drop the file after. ex: fastboot flash app (file)
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Ex: fastboot flash app ( c:/????/desktop/payload_dumper/extracted/app.img ) idk
Just an extra recommended to wipe the device
Fastboot -w but you don't need to if it works without.
I'm way to inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
Click to expand...
Click to collapse
MirageSteezyBoi said:
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Click to expand...
Click to collapse
Sorry I'm very bad at this. I was thinking you didn't even boot properly.... just update to the latest using oxygen updater or the systems bultin update... Im a moron and ill be leaving that up there.

Categories

Resources