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.
I recently updated to 5.2 and everything seemed to be fine andworked. A few days later, the device was in a boot loop. I downloaded the Stock Rom from nVidia site (NVIDIA SHIELD ANDROID TV Recovery OS Image 5.2.0 2017/06/15) and flash it using the following commands:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Everything flashed fine, but the device is still in a boot loop. Any suggestions?
Thanks!
vuser74 said:
I recently updated to 5.2 and everything seemed to be fine andworked. A few days later, the device was in a boot loop. I downloaded the Stock Rom from nVidia site (NVIDIA SHIELD ANDROID TV Recovery OS Image 5.2.0 2017/06/15) and flash it using the following commands:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Everything flashed fine, but the device is still in a boot loop. Any suggestions?
Thanks!
Click to expand...
Click to collapse
Flash TWRP, make a Full Wipe, Restart to the bootloader and flash the Stock Rom again.
LM209 said:
Flash TWRP, make a Full Wipe, Restart to the bootloader and flash the Stock Rom again.
Click to expand...
Click to collapse
Thanks for the great suggestion. I'll remember this for next time. I ended up RMA the device.
Hello how to fixed step by step
First you need fastboot rom extract fastboot rom on your pc after extract find 3 file
1-boot
2-recovery
3-system
Flash with fastboot
Turn off your phone and going to fastboot
Type
Fastboot devices
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Done device can't boot but you can install twrp China version link ?
https://www.lanzous.com/i6ahykh
after installation you can go to twrp
Download fastboot miui 10 install from twrp
Sorry for me English
I accidentally flashed a magisk_patched.img thinking that it is going to Install Magisk into my phone.
I entered the following command: fastboot flash boot magisk_patched.img (Not specifying the boot slots)
Once I rebooted, it says system UI is not responding.
I went back to fastboot mode, and entered the following commands knowing it had worked previously before:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
I tried switching boot slots, but both shows the same error once I am rebooted "System UI not responding".
I have no TWRP installed and I just want to start FRESH. I have the OOS 10.3.1 Zip file ready. I just do not know how to install it.
It also seems like my phone does not want to boot into recovery mode. It is currently stuck in fastboot. Both slots have this error.
Pleasee help me out!
Use MSMDownloadTool to reflash stock image. Follow directions of that. Can be found easily here on forums.
Alternatively, since fastboot is working you can try and use a fastboot version of OOS rom and flash without relocking bootloader.
AdlietMeyer said:
I accidentally flashed a magisk_patched.img thinking that it is going to Install Magisk into my phone.
I entered the following command: fastboot flash boot magisk_patched.img (Not specifying the boot slots)
Once I rebooted, it says system UI is not responding.
I went back to fastboot mode, and entered the following commands knowing it had worked previously before:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
I tried switching boot slots, but both shows the same error once I am rebooted "System UI not responding".
I have no TWRP installed and I just want to start FRESH. I have the OOS 10.3.1 Zip file ready. I just do not know how to install it.
It also seems like my phone does not want to boot into recovery mode. It is currently stuck in fastboot. Both slots have this error.
Pleasee help me out!
Click to expand...
Click to collapse
I still don't understand why people are so eagerly desperately searching to use patch img method.... We have a working TWRP you just have to fastboot boot temporarily twrp and flash Magisk zip installer....
Anyway, why did you mess with slots? 90% of time it leads to soft brick. You don't need to specify slot when fastbooting an img, it's flashed automatically on active one.
In your situation, try to fastboot flash the ROM, there is a thread in Guide News section providing OOS in fastboot format.
Or use MSMdownload to put your phone in factory fresh state, there is a thread in same section about that it's called 'collection of unbrick tools'
And my thread in same section explains how to root 10.3.1
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.