Hi experts,
I'm chiming in here to see how to resolve issue with updating TWRP to latest version.
Currently have a bootloader unlocked (rooted) stock Verizon ROM VS996_20i with TWRP recovery. When using adb to try to flash updated recovery, the commands 'adb devices' does show phone ID. But then... 'adb reboot bootloader' immediately reboots/restarts the phone. So I'm unable to get to Fastboot commands and therefore can't run 'fastboot flash recovery'.
Upon further investigation, I found out that I am also unable to get into 'Download Mode'. With phone powered off while pressing Volume Up button, when I plug phone into PC it powers on and briefly shows 'Download Mode' icon. But then the phone immediately reboots the system and restarts. Phone still enters recovery mode as expected with full functioning TWRP.
Did I somehow lose (or corrupt) both Download and Bootloader mode(s)? I'd appreciate any advice. thanks
steevo23 said:
Hi experts,
I'm chiming in here to see how to resolve issue with updating TWRP to latest version.
Currently have a bootloader unlocked (rooted) stock Verizon ROM VS996_20i with TWRP recovery. When using adb to try to flash updated recovery, the commands 'adb devices' does show phone ID. But then... 'adb reboot bootloader' immediately reboots/restarts the phone. So I'm unable to get to Fastboot commands and therefore can't run 'fastboot flash recovery'.
Upon further investigation, I found out that I am also unable to get into 'Download Mode'. With phone powered off while pressing Volume Up button, when I plug phone into PC it powers on and briefly shows 'Download Mode' icon. But then the phone immediately reboots the system and restarts. Phone still enters recovery mode as expected with full functioning TWRP.
Did I somehow lose (or corrupt) both Download and Bootloader mode(s)? I'd appreciate any advice. thanks
Click to expand...
Click to collapse
Try flashing back to stable TWRP. See if you have those issues.
The beta TWRP is clearly labelled experimental.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Try flashing back to stable TWRP. See if you have those issues.
The beta TWRP is clearly labelled experimental.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Thanks for responding.
I'm running (i think) a stable TWRP (3.2.3.7). This is the latest stable version, right? But my wife is on an older version. (3.1.?.?)... so I'm trying to update hers to the latest. Problem with both of our phones is that I can't seem to get to the flash commands using ADB. As above, when I run 'adb reboot bootloader', the phone simply restarts. In other words, how do we perform "flashing back"?
steevo23 said:
Thanks for responding.
I'm running (i think) a stable TWRP (3.2.3.7). This is the latest stable version, right? But my wife is on an older version. (3.1.?.?)... so I'm trying to update hers to the latest. Problem with both of our phones is that I can't seem to get to the flash commands using ADB. As above, when I run 'adb reboot bootloader', the phone simply restarts. In other words, how do we perform "flashing back"?
Click to expand...
Click to collapse
Oh, I thought you were trying the new 3.3.0 beta. 3 2.3.7 is the stable one.
Wow. How did she get on that old one?
You can update TWRP within TWRP. Go to TWRP Install, and change to "IMG" (lower right) and then it'll show you img files instead of zip files. You want to flash to Recovery, not any other partition.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Oh, I thought you were trying the new 3.3.0 beta. 3 2.3.7 is the stable one.
Wow. How did she get on that old one?
You can update TWRP within TWRP. Go to TWRP Install, and change to "IMG" (lower right) and then it'll show you img files instead of zip files. You want to flash to Recovery, not any other partition.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Thanks for reminding me of how to update TWRP from within TWRP. I'll have to go that route.
But i'm still concerned about the inability to get into 'Download mode'. At some point I'll probable need to use LGUP again or need Fastboot commands. I'm wondering if the issue could be PC related or using an older platform tools for ADB. Or possible a bad cable? I'll troubleshoot.
steevo23 said:
Thanks for reminding me of how to update TWRP from within TWRP. I'll have to go that route.
But i'm still concerned about the inability to get into 'Download mode'. At some point I'll probable need to use LGUP again or need Fastboot commands. I'm wondering if the issue could be PC related or using an older platform tools for ADB. Or possible a bad cable? I'll troubleshoot.
Click to expand...
Click to collapse
Not sure what's going on with your Download mode, but you won't have fastboot flash commands while on VS996 firmware. Of the North America variants, only US998 has fastboot flash commands. That's why you had to temporarily Frankenstein to US998 for WTF Bootloader Unlock and TWRP installation....
However the only reason you needed fastboot flash commands was to unlock bootloader and install TWRP. After that, you use TWRP to install firmware, Magisk modules, ROMs.
If you ever need fastboot flash commands again, you'll have to flash to US998 firmware. You can do that with TWRP-flashable zip. You do NOT need to do the LGUP Frankenstein again.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Not sure what's going on with your Download mode, but you won't have fastboot flash commands while on VS996 firmware. Of the North America variants, only US998 has fastboot flash commands. That's why you had to temporarily Frankenstein to US998 for WTF Bootloader Unlock and TWRP installation....
However the only reason you needed fastboot flash commands was to unlock bootloader and install TWRP. After that, you use TWRP to install firmware, Magisk modules, ROMs.
If you ever need fastboot flash commands again, you'll have to flash to US998 firmware. You can do that with TWRP-flashable zip. You do NOT need to do the LGUP Frankenstein again.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Ah-ha! Didn't know that about Verizon and Fastboot commands. Thanks for your continued help, support and education.
Related
HI! I recently upgraded to an lg g3 and I immediately unlocked bootloader, installed twrp, and put a custom ROM on, now I want to switch back to the stock firmware. I don't have a backup of the LAF file and I can't enter fastboot or download mode in order to fix download mode so that I can revert to stock firmware! When I try to enter download mode (holding down top volume key and plugging into PC [I've tried both usb 3.0 and 2.0 with original cable]), lg logo briefly flashes on screen and blue led flickers then the screen is black and the phone shows up on my computer in device manager as Qualcomm HS-USB QDLoader 9008. I wiped my phone through twrp and restored my early backup from when I had just rooted it but that didn't change anything. Now the thing is, I have twrp installed and I can enter twrp just and the phone boots into any custom rom just fine.. The phone is rooted and bootloader is unlocked. I need to relock the bootloader and unroot but I can't without download mode. Any help would be really appreciated! I'm on an lg vs985.
7064N said:
HI! I recently upgraded to an lg g3 and I immediately unlocked bootloader, installed twrp, and put a custom ROM on, now I want to switch back to the stock firmware. I don't have a backup of the LAF file and I can't enter fastboot or download mode in order to fix download mode so that I can revert to stock firmware! When I try to enter download mode (holding down top volume key and plugging into PC [I've tried both usb 3.0 and 2.0 with original cable]), lg logo briefly flashes on screen and blue led flickers then the screen is black and the phone shows up on my computer in device manager as Qualcomm HS-USB QDLoader 9008. I wiped my phone through twrp and restored my early backup from when I had just rooted it but that didn't change anything. Now the thing is, I have twrp installed and I can enter twrp just and the phone boots into any custom rom just fine.. The phone is rooted and bootloader is unlocked. I need to relock the bootloader and unroot but I can't without download mode. Any help would be really appreciated! I'm on an lg vs985.
Click to expand...
Click to collapse
1. there is no fastboot
2. the bootloader is not unlocked (not possible)
3. here is the laf img you requested.
bweN diorD said:
1. there is no fastboot
2. the bootloader is not unlocked (not possible)
3. here is the laf img you requested.
Click to expand...
Click to collapse
Thanks! Sorry I guess I meant that I have twrp recovery installed and I can get into that and I can boot into the OS.
How do I flash the laf to my phone? And will that fix download mode?
7064N said:
Thanks! Sorry I guess I meant that I have twrp recovery installed and I can get into that and I can boot into the OS.
How do I flash the laf to my phone? And will that fix download mode?
Click to expand...
Click to collapse
i could speculate and say, use the recovery install command line code, changing recovery to laf, but i have no idea if thats ok to do with laf.
try at your own risk.
bweN diorD said:
i could speculate and say, use the recovery install command line code, changing recovery to laf, but i have no idea if thats ok to do with laf.
try at your own risk.
Click to expand...
Click to collapse
Ok I'll try that.
bweN diorD said:
i could speculate and say, use the recovery install command line code, changing recovery to laf, but i have no idea if thats ok to do with laf.
try at your own risk.
Click to expand...
Click to collapse
Ok so the problem is still the same and twrp dissapeared when I tried to use the same process to flash the laf. When I try to enter twrp the blue/green leg starts blinking. I put twrp back on. :crying:
I'm sorry to bump the thread but i'm kind of desperate here. I need to flash the laf file to restore download mode but fastboot isn't working at all.:crying:
7064N said:
I'm sorry to bump the thread but i'm kind of desperate here. I need to flash the laf file to restore download mode but fastboot isn't working at all.:crying:
Click to expand...
Click to collapse
There is no fastboot, sorry.
bweN diorD said:
There is no fastboot, sorry.
Click to expand...
Click to collapse
How do people use fastboot commands, whenever I try it just says "waiting for device" and i've tried downloading drivers many times. ADB is working though. How can I restore download mode?
7064N said:
How do people use fastboot commands, whenever I try it just says "waiting for device" and i've tried downloading drivers many times. ADB is working though. How can I restore download mode?
Click to expand...
Click to collapse
Sorry I don't know, but people are not using fastboot commands because it's not there, Verizon removed or blocked it.
suljo94 said:
try to get an vs985 laf.img from someone(I can't help because I have an d855) then put it onto the internal memory of your phone and typ this adb command
Code:
adb shell
su
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Click to expand...
Click to collapse
Solution if anyone needs it down the road. LAF file I pulled from vs985: http://goo.gl/EdtEFu
edit: on vs985, broken download mode fixed
7064N said:
Solution if anyone needs it down the road. LAF file I backed up myself: http://goo.gl/EdtEFu
Click to expand...
Click to collapse
edit it and add the version of the g3 you have, to prevent problems down the road
7064N said:
Solution if anyone needs it down the road. LAF file I backed up myself: http://goo.gl/EdtEFu
Click to expand...
Click to collapse
im confused as to what the solution was exactly. if your laf was broken as you said, how did you fix it to pull your own laf?
the laf file i gave you is official, and is exactly the same as the one you posted. verified by md5 comparison.
bweN diorD said:
im confused as to what the solution was exactly. if your laf was broken as you said, how did you fix it to pull your own laf?
the laf file i gave you is official, and is exactly the same as the one you posted. verified by md5 comparison.
Click to expand...
Click to collapse
The solution was just fixing broken download mode without fastboot. Your LAF probably would have worked as well, oops. I had two laf files, one was 32mb, and one was the one from you, I thought I just downloaded it twice and threw away the one you posted thinking it was a duplicate. I went hunting through my phone's files for the laf I backed up when flashing twrp later on after the other laf didn't work. Sorry about that.
I screwed up my phone lol, when I was updating it to oreo, I didn't know that the update.zip file was corrupted.
Now I'm stuck on
Error!
Func NO : 9 (hifi image)
Error NO : 1 (security image failed)
My version was...
STF-L09C185B170
What i tried to install that failed is...
STF-L09C185B361 (8.0.0.361)
I can still go to fastboot with everything unlocked, I can also flash a twrp recovery, but only by typing flash recovery_ramdisk(instead "recovery"), and when I try to do the update method by pressing vol up, vol down, and power, it doesnt take me to the update section, it just show me a crashed screen, then goes back to error message.
I also tried volup and power, I can't seem to go to twrp(I think booting to twrp and flashing zip files can be one of the only ways to fix this). Is there a way to go to twrp recovery using fastboot?
I've also tried flashing extracted files from update.app manually, it doesn't work. Some files can be flashed, while some can't.
Please I'm begging u guys, pls halp :crying:
also I guess the lesson here is: double check if your file is corrupted before installing/flashing
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
oslo83 said:
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
Click to expand...
Click to collapse
I downloaded the oreo file using a browser and installed it with HWOTA, everything got inserted into my device, but the update failed and it gave me the error when I reboot. Also I can't get to erecovery or upgrade mode(that's the crashed screen), and "fastboot reboot recovery" doesn't work, it just show me a list of commands(which I assume happens if the command is invalid).
Ok I'll try HWOTA8, but I need to configure it so it recognizes my device, only my adb recognizes it.
Do 'fastboot devices work'?
Try english hwota8.
oslo83 said:
Do 'fastboot devices work'?
Try english hwota8.
Click to expand...
Click to collapse
Nah, I figured it out, I backed up my adb folder and just merged hwota8 with it. Yes, it does work.
Btw how do I fully turn off the device? it just keeps bootlooping if i hold down the volup and power key, maybe this is the reason why I can't get into twrp recovery.
My only hope is that I can flash something on fastboot that will let me go to update mode(or erecovery) or twrp.
Like.. anything, even boot.img fails when I try to flash it. It must be stuck on oreo partition.
Also I did considered dc phoenix, but I don't have the money to pay for an account. Man, why is unbricking not free on huawei devices? That guy prolly made a fortune by now(for holding everyone with unbrick leverage lel), and it's a huge mistake for me to fiddle with a huawei device, it has so many problems with twrp and root.
If anyone can find a way to do unbrick it, like anything, that would be great.
So you didn't manage to use honor9's hwota8 ?
oslo83 said:
So you didn't manage to use honor9's hwota8 ?
Click to expand...
Click to collapse
I used it but it didn't worked, I need to be either booted in the phone's os or inside twrp recovery bec. all of the commands executed by hwota8 are adb shell, not fastboot. Like I said, I only have access to fastboot, but I'll try again tomorrow. This is taking a lot of my time and I'm having panic attacks that I may not be able to fix this lol. Oh yeah, thanks for helping out.
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
oslo83 said:
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
Click to expand...
Click to collapse
I already did that, read the OP. Like I said, I can't boot into any recovery, not twrp not stock, not even upgrade mode, nothing.
As for hwota8, nope, it doesnt start from the bootloader, it's already trying to use the adb shell commands.
Anyway I'm taking all chances, I'm trying to research oreo's partitions names, and I'm also trying to find out how to bypass this message "FAILED (remote: Command not allowed)" bec. it might be the only way I can salvage this phone.
edit: ok im trying hwota8 again, maybe i missed something, and yes it has fastboot, sorry i was rushing but im trying again now, i'll post my progress later
Hello,
After unlocking the boot loader, I wanted to downgrade from firmware V11m to V10F to flash TWRP recovery. The download mode is not working. I tried to flash the LAF partition without success.
"fastboot flash laf laf.img"
The following error was displayed.
"FAILED (remote: Cannot flash this partition in unlocked state)"
How can I restore the download mode?
Can I close the bootloader again?
Everything else works fine. I'm very grateful for help.
Best regards
patber307 said:
Hello,
After unlocking the boot loader, I wanted to downgrade from firmware V11m to V10F to flash TWRP recovery. The download mode is not working. I tried to flash the LAF partition without success.
"fastboot flash laf laf.img"
The following error was displayed.
"FAILED (remote: Cannot flash this partition in unlocked state)"
How can I restore the download mode?
Can I close the bootloader again?
Everything else works fine. I'm very grateful for help.
Best regards
Click to expand...
Click to collapse
See the TWRP H930 thread. Lots of people have downgraded and talked about it there.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
See the TWRP H930 thread. Lots of people have downgraded and talked about it there.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
That's right, but the download mode is Bricked.
The laf partition is responsible for the download mode. This can not be flashed with Fastboot.
My english is not good but google helps me with that.
patber307 said:
That's right, but the download mode is Bricked.
The laf partition is responsible for the download mode. This can not be flashed with Fastboot.
My english is not good but google helps me with that.
Click to expand...
Click to collapse
Then they're downgrading through some other method. I'm pretty sure they discuss it in the thread how they're doing it.
Like this:
https://forum.xda-developers.com/showthread.php?t=3738917
Sent via open market LG US998 V30/V30+
I have already read this thread.
There the Software LGUP is used for the Upgrade. With LGUP, the Phone restarts automatically in Download mode and updates the Firmware.
On Post #9 states, that the Download mode is a Part of the LAF Partition. But the LAF Partition seems to be broken on my Phone. My Phone starts on Fastboot mode instead.
I have extracted the laf_6.bin from the official Firmware and renamed it in laf.img. Then I tried using "fastboot flash laf laf.img" to repair the LAF Partition, without success. Even the previous delete by means of "fastboot erase laf" (took unusually long) brought no success.
How can I just fix the download mode?
I obviously have a very similar problem. My H930 depends on "fastboot format userdata" in the bootlogo. I can not turn it off. I'm not in the download mode. And I can not boot into the system either. Can anyone help me?
Sky67 said:
I obviously have a very similar problem. My H930 depends on "fastboot format userdata" in the bootlogo. I can not turn it off. I'm not in the download mode. And I can not boot into the system either. Can anyone help me?
Click to expand...
Click to collapse
Hello Sky67,
I also had this problem.
Connect the phone to your PC. To turn off press the Power- Button and the Vol. down- Button at the same Time until the Phone restarts, now release the Power-Button. You should be in Fastboot now.
Or you start in Recovery mode.
Do not connect the Phone to the PC. Press the Power- Button and the Vol. down- Button at the same time and hold. As soon as the Phone restarts, wait until the first Logo and just release the Power- Button and press it again. The Phone should boot into Recovery.
Hallo patber307, thanks but that does not work. Neither do I get the H930 off, nor do I manage to come in any known way in the download mode or recovery mode.
Sky67 said:
Hallo patber307, thanks but that does not work. Neither do I get the H930 off, nor do I manage to come in any known way in the download mode or recovery mode.
Click to expand...
Click to collapse
Did you find a way to repair your phone?
I´ve got the same Problem...
I recently bought an unlocked Moto G Play 2021 with the intent of learning how to flash custom rom's etc. The steps I've done so far are below.
Went to Motorola's site and got the code to unlock the bootloader
Waited for the "OEM Unlock" button to be available in the Developer Options menu.
Followed the directions Here to try to get an unofficial version of TWRP installed.
when I type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Using the vbmeta.img from the link above, I get some kind of anti-rollback error and can't boot to recovery.img
So far, what I've found says I need to be on Android 10 for this to work but I can't find a stock rom of Android 10 for this device. Electimon posts AOSP builds for this phone Here so I assume there's a way to get this to work, I just don't know what it is and I've gone through these threads a few times now and can't piece it together. Any assistance would be greatly appreciated.
Additionally, thanks Electimon for doing those AOSP builds.
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Luiz Vinicius said:
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Click to expand...
Click to collapse
I'm not sure entirely what happened, but after I used the TWRP app my phone bricked and I had to use the Lenovo rescue app on my pc to factory reset it.
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
svoc said:
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
Click to expand...
Click to collapse
Thank you for the response!
I made sure my phone was on wi-fi and checked for updates. I then rebooted to fastboot and flashed recovery to the MotoGuamnaFixed2.img. I still got a blank screen when I tried to reboot to recovery. I then rebooted to fastboot manually and did
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
It said ok both times, and when I try to reboot to recovery, I get a blank screen that I can't interact with. Pressing the power and volume buttons does nothing. Rebooting and letting the phone go through the boot process, to include waiting for the warning about the unlocked bootloader to go away results in a blank screen.
I also tried booting to fastboot and selecting "Recovery Mode" from the fastboot menu. Same result. That being said, I followed the instructions in the second link anyway, which are
fastboot -w
fastboot update (filename).zip
Now my phone has a blank screen I cannot interact with, but when I type "adb devices" I see the phone. Typing "adb shell ls -l" shows there is definitely a file structure there.
Just download the rom for the version that your device is unzip it and manual flash each one to the correct spot except recovery flash the twrp and then reboot and let me know look at flash file.xml to see where to flash each IMG and bin to make shur you download your rom and not another one for the same device but different carrier what it sounds like to me is happening is you downloaded the wrong ROM when you tried to do a force update
Send me a screenshot of your about device screen please I might need to make a change to a few things to get it working
I'm stuck in a boot loop right now. WIll the output from fastboot getvar work?
What carrier do you have
Download your rom first then follow my last post to get it back out of a bootloop
svoc said:
What carrier do you have
Click to expand...
Click to collapse
It's an unlocked phone, no carrier, no SIM. I did the factory reset with the Lenovo rescue tool and sent you the screen shot of the device info page.
Update - svoc has spent a crap ton of his personal time trying to help me with this. I've learned a bunch and wanted to publicly acknowledge his willingness to go way above and beyond trying to get this working.
I don't understand why I can't get twrp to boot I'm not for shut what the problem is if any one has any idea please let me and I will try
Big thanks to svoc for all the phone calls and troubleshooting my device, that is apparently possessed by at least 3 demons and a donkey. There are two links below. The first is the link to the intstructions that worked.
The second is to the compressed file that gave me a degoogled android. It's really, really basic and you'll have to side load the app store of your choice onto the device but it works.
*NOTE* I have not used a sim card or tested the cellular capability. If you do the things below and it doesn't work, reboot to bootloader and flash the radio.img with the one from your stock rom, which can be obtained from lolinet.
Any custom ROMs out there for Moto g play 2021 (guamna)?
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
forum.xda-developers.com
https://github.com/phhusson/treble_experimentations/releases/download/v412/system-squeak-arm64-ab-vanilla.img.xz
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
BigZ1 said:
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
Click to expand...
Click to collapse
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
BigZ1 said:
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
Click to expand...
Click to collapse
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.