Related
How to root please?
Also, anyone know how to reflash this models firmware?
I think I stuffed 1 of them up trying to root.
Attached is a picture of the model.
Thank you. Have a nice day.
Hi there !
I have started a new thread on how to root spreadtrum devices here: http://forum.xda-developers.com/showthread.php?t=2165554
May be you could find a way to root yours.
I also need you to test an idea to root them, but I'm not sure if it will work.
Because you already have a bricked one, you can try this idea without risking your device (and maybe unbrick it by doing a backup of the others one and flashing this backup on it.)
How have you bricked it precisely ?
Spreadtrum SC6820
ElectronikHeart said:
Hi there !
I have started a new thread on how to root spreadtrum devices here: http://forum.xda-developers.com/showthread.php?t=2165554
May be you could find a way to root yours.
I also need you to test an idea to root them, but I'm not sure if it will work.
Because you already have a bricked one, you can try this idea without risking your device (and maybe unbrick it by doing a backup of the others one and flashing this backup on it.)
How have you bricked it precisely ?
Click to expand...
Click to collapse
Hi there, I recently got my hands on a Mobicel Titan, and after much unclear research, the best I can come up with is that it is a Spreadtrum SC6820a phone, hope I am on the right track. Anyway, my goal is to change the ROM on this phone as the software that Mobicel has bundled on their version of Android is way too much for the phone to handle. I have already rooted the phone using Z4Root successfully. Funny enough, the link you have is the very link I tried for the past week, I've tried ADB and Fastboot on both Windows 8 64bit and Ubuntu 12.10 64bit, and even ResearchDownload, all drivers were installed successfully, but when i try all methods to flash new ROM to the device, nothing seems to happen, even if I use ResearchDownload and follow instructions to the T, flash process doesn't start. After using fastboot to update CWM from Ubuntu 12.10, if I try to restart into recovery mode, it is then stuck on the Mobicel Logo. Is there a guide for the Mobicel Titan?
The Problem:
Phone stuck on LG logo screen with "Security Error" written underneath.
How I Got Here:
Rooted and installed recovery using apks found in these forums. I successfully restored a CWM backup zip found on these forums. Next, I decided to try flashing a ROM. SuperLuminal gave me a "Status 7" error, but when I checked over the thread, I realized that the P769 was not specifically mentioned as a compatible device. So, I decided to give PACman ROM a try, but got the same error.
I googled "status 7 error" and found a guide for fixing this (removing "assert" line in updater-script line). I was aware of the danger in doing this, but since PACman ROM stated "P769" right there in the title, I gave it a shot. Now I'm stuck with the "security error" screen.
What I tried:
I could no longer get into recovery, so I thought restoring it might be a good idea. I tried to use fastboot using the method described in this thread (http://forum.xda-developers.com/showthread.php?t=2310569). However, I quickly realized that I didn't know how to put the phone into a "download mode" like most other phones I've worked with.
I then tried B2CAPP, but phone couldn't be detected. Went and learned how to get into s/w upgrade mode, ran recovery and got an error message saying "updating is not possible any longer due to a fatal error..."
Next, I tried uninstalling all LG software and rebooting PC. Installed LG PC Suite found here (http://en.kioskea.net/download/download-19186-lg-pc-suite), allowed the program to update to latest version. Then tried to run Emergency Firmware Recovery, which opened a window asking if I want to run LG Mobile Support Tool. I clicked OK and was taken to an app that looked exactly like B2CAPP and gave me the same error as above.
So in conclusion, I can only access two screens: the LG logo security error screen and the s/w upgrade screen. Neither appears to give me access to fastboot/adb nor to LG's recovery tools. Am I permanently bricked or is there a way out of this mess? I've been searching these forums extensively and have tried every method I could find. I'm out of options, so I'm kinda freakin out here. Can anyone please help me figure out what else to try?
You did some studying for sure, but you needed to do some more before jumping in.
1. http://forum.xda-developers.com/showthread.php?p=41768774
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sent from my LGMS769 using xda app-developers app
Kuma82, I can't thank you enough for your helpful response.
Here's a shortened version of what I did, in case someone out there finds themselves in a tough spot like I was in:
1. Installed OMAP drivers using method described in link above (right-click on device in Device Manager, manually install driver, etc.). Fastboot worked after this
2. Using Lelus' Fastboot, flashed option 6 (load JB xloader and uboot). This gave me an inverted purple LG logo that still said "security error"
3. I think tried to use fastboot to flash the p4_769.img recovery file. No change. Loading up s/w upgrade mode and the LG Mobile support tool (B2CAPP) was no use (stuck at 15%, no connection to phone).
4. Once again, using one of the links above, I downloaded 3 .img files and proceeded to erase uboot, boot and recovery and flashed those .img files instead. When I rebooted the phone, I got the regular LG logo for a second, then a white flash and then a smaller LG logo with "security error"
5. Now, I installed the LG United mobile driver, went into s/w upgrade mode again and ran the Mobile tool. Got the "updating is not possible..." error again
6. Searched for the offline flash fix method and followed it step-by-step, word-for-word. Phone works again!
I'm pretty sure I could have just done steps 1, 4 and 6 and achieved the same result.
Hope this helps someone, and thanks again Kuma82!
I've had this happen to me twice and was able to get out of it really easily. Basically, I just have my desktop set up for offline flashing and my laptop for online. Just popped into S/W update mode and plugged it into the laptop, started the b2c app, clicked on the "recovery phone" option, and went for a snack. Fixed when I came back.
No problem, glad I could help.
Now that you know how to use fastboot, you are pretty much ready for everything.
It took me a couple of tries to get it running.
Use the new root method, http://forum.xda-developers.com/showthread.php?t=2338816
If you plan on staying on stock, get the cwm for locked bootloader, but first get this busy box http://forum.xda-developers.com/showpost.php?p=43395803&postcount=260
Then this cwm
http://forum.xda-developers.com/showpost.php?p=41613095&postcount=220
Sent from my LG-P769 using xda app-developers app
kuma82 said:
You did some studying for sure, but you needed to do some more before jumping in.
1. http://forum.xda-developers.com/showthread.php?p=41768774
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
Dear, Kuma82!
Thank you very much fot your instruction! It really saves my LGP768 from "security error"! I follow 3 steps and it works, GREAT!
Thank you again and this forum too!
Please help! Bricked LGMS769 (P769)
Solved. The LGMobile Support Tool needed to run on a different computer. It worked when I put the phone into SW Update Mode (press up volume key and plug in USB) and then ran the LGMobile Support Tool.
By the way, this is how I got the phone recovered after it was booting to the small LG logo with the "security error" message as mentioned in Step 4 above.
My lg logo g2 fails, you fall caught. The case is that I haven ´t download mode, I have the official lg recovery but when I do it gets caught when factoring reset. Previously I followed the tutorial for linux, but in the last step of recovery I installed the official TWRP instead of lg. The case now my phone will not start, as I said earlier stays at lg logo and neither recognizes windows. Before the error came out and particiciones qusb_load driver or something. In linux not recognized and therefore can not repeat the steps to install the TWRP recovery
Please have to see a solution, I can not believe that it is irreversible, you need to see a way to start the mobile.
I'm not the only one to whom this has happened, there are more people like me, I'd be really grateful if someone could help because this is frustrating and I had never been anything like
thanks in advance.
Hi dude,
Seems you are stuck in boot loop mode.
Get a KDZ file for your phone and follow instructions in here
http://forum.xda-developers.com/showthread.php?t=2432476
I have posted in that link and follow my tips if running win xp.
Good luck and don't give up. It's easily recoverable.
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Kéno40 said:
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Click to expand...
Click to collapse
Yes he used..read full op.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Power off your phone, connect to PC with power off holding volume up button. It should detect phone as Qualcomm.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
You have noting to do but to flash stock oos 2.1.4 using Qualcomm flasher and driver.I faced the same issue.but I managed to flash using Qualcomm in windows 10.and got my onyx back.
My suggesting is remove the adv or oneplus drivers.just install the Qualcomm driver and connect the device.follow the device manager if the deivce detected or not.it will detect and flash using Qualcomm flasher.
I have a LG K7 that will boot to system, but no matter how many times I try, it wont boot into either download mode or recovery mode. I've tried the combos of vol down + power and vol up + power and every other combination I can think of. Pulled the battery and it didn't improve.
Anybody ever see something like this? Any suggestions on how to get it to work?
BigZ1 said:
I have a LG K7 that will boot to system, but no matter how many times I try, it wont boot into either download mode or recovery mode. I've tried the combos of vol down + power and vol up + power and every other combination I can think of. Pulled the battery and it didn't improve.
Anybody ever see something like this? Any suggestions on how to get it to work?
Click to expand...
Click to collapse
Tried ADB commands?
adb reboot recovery
adb reboot bootloader
bmwdroid said:
Tried ADB commands?
adb reboot recovery
adb reboot bootloader
Click to expand...
Click to collapse
Yes, and adb devices shows nothing. I'm wondering if the bootloader is locked and maybe that's why I'm having problems.
Also, I'm having problems getting TWRP to load. Do you know what version of TWRP will work with K7?
Do you have to root first before installing TWRP from the playstore?
BigZ1 said:
Yes, and adb devices shows nothing. I'm wondering if the bootloader is locked and maybe that's why I'm having problems.
Click to expand...
Click to collapse
If "adb devices" shows nothing imo it's not recognised so not possible to flash.
Tried other cable/port?
BigZ1 said:
Also, I'm having problems getting TWRP to load. Do you know what version of TWRP will work with K7?
Click to expand...
Click to collapse
No idea as I own a G5.
BigZ1 said:
Do you have to root first before installing TWRP from the playstore?
Click to expand...
Click to collapse
Never did that.
Always flashed directly but I guess so.
bmwdroid said:
If "adb devices" shows nothing imo it's not recognised so not possible to flash.
Tried other cable/port?
No idea as I own a G5.
Never did that.
Always flashed directly but I guess so.
Click to expand...
Click to collapse
tried another cable and different port. Status Quo!
Any other ideas/thoughts?
@BigZ1 sorry, none.
OK, finally can get into firmware mode and also recovery mode. Reason I needed this is to be able to try loading custom roms on this old phone. Now I'm on to the next pothole in the road.
I would like to install twrp. twrp from the playstore wont install unless you are rooted. I am using stock rom android 5 unrooted. I've looked at all the options and from what I see, I have the classic chicken and the egg dilema. Can't flash until my OS is rooted, and cant root without flashing.
The only way out is to use adb to flash the twrp file. Unfortunately I can't get adb devices command to acknowledge any devices. I have usb debugging on, and by connecting to a windows computer, I can view internal storage. So the device is communicating, but not via adb commands.
I tried to use the LGUP tool from LG, but it wont let me select my device, It sees the correct model of phone on Com3, but wont let me select the model. I think it's because LG has turned off their servers and cast us adrift.
If anybody has any ideas, it would be much appreciated.
I think my best bet is to get adb devices to work, or find a way to root my OS. I just cant figure out how to make that work. Help, please!!!!
BTW, in the stock recovry mode, LG has removed everything useful (e.g. install zip, reboot options, wipe cache, etc.) so the only option there is factory data reset. Thanks a lot LG!!!!!
BigZ1 said:
....The only way out is to use adb to flash the twrp file........
Click to expand...
Click to collapse
Sorry to tell you but afaik this won't work.
fastboot flash recovery <filename.img> would be the command but this will only work if it's unlocked.
BigZ1 said:
....Unfortunately I can't get adb devices command to acknowledge any devices. ......
Click to expand...
Click to collapse
I doubt that fastboot will work if adb isn't but it's worth a try.
You are right, a fastboot command would do it. Only reason I mentioned adb devices, is that if adb can't see the devices, fastboot wont either. I'll try it again, but so far no luck.
What I don't understand is why usb debugging lets me look at the internal files, but adb devices doesn't work. Perhaps you are right, the bootloader may be locked. Only thing I could find about that is in developer options I turned on OEM unlock.
Is there any other way to unlock the bootloader?
Sure wish I could get some of the LG tools working. They might enable flashing of twrp recovery or one of the various zip files that would root my OS.
Any more ideas? I'm desperate enough to try most anything....
One more question. When you try to execute adb or fastboot commands, should you be in what LG calls "firmware download" mode? Seems to me that when I did adb or fastboot commands on other vendors phones, I was able to do so while the OS was running.
Grasping for straws....
Well, it looks like you are right. There is a fastboot command
fastboot oem unlock
that would unlock the bootloader. Unfortunately while it's locked, I can't get fastboot to recognize any devices, so I can't unlock it.
Is there any way around this?
BigZ1 said:
Well, it looks like you are right. There is a fastboot command
fastboot oem unlock
that would unlock the bootloader. Unfortunately while it's locked, I can't get fastboot to recognize any devices, so I can't unlock it.
Is there any way around this?
Click to expand...
Click to collapse
Fastboot is afaik only working in download/bootloader mode.
ADB working on any other.
So <adb reboot bootloader > usually gets you there (but adb doesn't work) or switch to it manually.
Idk if you need to flash an unlock.bin by LG.
Got it before 31.12.21 for my G5.
bmwdroid said:
Fastboot is afaik only working in download/bootloader mode.
ADB working on any other.
So <adb reboot bootloader > usually gets you there (but adb doesn't work) or switch to it manually.
Idk if you need to flash an unlock.bin by LG.
Got it before 31.12.21 for my G5.
Click to expand...
Click to collapse
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
BigZ1 said:
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
Click to expand...
Click to collapse
Oh yeah, one more thing. The phone is still of some use to me, if I can find a way to root it. So far all the stuff I tried (kingoroot, supersu, magisk) have failed.
Anybody got any suggestions???
BigZ1 said:
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
Click to expand...
Click to collapse
The file got generated by LG after I entered a long code on their developers site which is afaik different for each device.
So someone elses unlock.bin might even harm your device.
You may be right, but at this point I don't have much to lose.
One thing I would like to do with the K7, is get it rooted. I can move files to the internal storage with usb debugging. I can't install any zip files and that makes it really difficult to find anything that can root it. Thanks again to LG for reducing the recovery menu to "factory reset data" so the phone has almost nothing useful.
If you can figure out a way that I can install zip files, please let me know.
I can't find anything that will let me flash the device without root, and I can;t get to root without some tools in the recovery menu.
Thanks
OK, I have not found a way to root. So I thought I'd take one last look at flashing/upating the firmware. I found a .kdz and a .tot file that I'd like to try. At this point I'm not risking much because the phone isn't worth much to me as is.
So, if you had a .kdz and .tot file to try out, what app would you use to flash it to the K7?
I tried to get LGUP to work and LG flash tool, but cant seem to make them work. If I knew what one to use, it would narrow my search. I'm trying to flash the K7 firmware by running exe files (LG UP, LG flash tool) on Windows 10.
What do you guys use?
BigZ1 said:
OK, I have not found a way to root. So I thought I'd take one last look at flashing/upating the firmware. I found a .kdz and a .tot file that I'd like to try. At this point I'm not risking much because the phone isn't worth much to me as is.
So, if you had a .kdz and .tot file to try out, what app would you use to flash it to the K7?
I tried to get LGUP to work and LG flash tool, but cant seem to make them work. If I knew what one to use, it would narrow my search. I'm trying to flash the K7 firmware by running exe files (LG UP, LG flash tool) on Windows 10.
What do you guys use?
Click to expand...
Click to collapse
So, I managed to find a patched version of LG flash tool (2.0.1.6) on this website (thanks to member ieatacid), that doesn't give me errors immediately after I open it. The first thing I notice is that it doesn't appear to recognize the K7. If I try checking the box for manual mode and adding the file I want to flash, the click start, it tells me to "select model dll file". This is probably a result of flash tool not recognizing the phone. Anyway, where am I supposed to find this .dll file? I've searched everywhere and came up empty handed.
Can anybody give me some enlightenment on what I am doing wrong? Any help at all will be much appreciated.
Is there a tutorial on use of the flash tool? I looked but haven't found it yet. Just some youtube videos that are terse and lacking in detail.
Thanks!
BigZ1 said:
So, I managed to find a patched version of LG flash tool (2.0.1.6) on this website (thanks to member ieatacid), that doesn't give me errors immediately after I open it. The first thing I notice is that it doesn't appear to recognize the K7. If I try checking the box for manual mode and adding the file I want to flash, the click start, it tells me to "select model dll file". This is probably a result of flash tool not recognizing the phone. Anyway, where am I supposed to find this .dll file? I've searched everywhere and came up empty handed.
Can anybody give me some enlightenment on what I am doing wrong? Any help at all will be much appreciated.
Is there a tutorial on use of the flash tool? I looked but haven't found it yet. Just some youtube videos that are terse and lacking in detail.
Thanks!
Click to expand...
Click to collapse
I don't know why I didn't think of this earlier. I own 3 LG phones (LGMS300m1, LM-X210ULMG10r. VS500PP9). I tried all 3 with LGUP tool. The tool recognized 2 of the 3, and failed to ID the LGMS300 (K7). Anybody got any ideas why the tool would recognize some but not others?
I am the only owner of the two phones that LGUP would ID. I guarantee that the bootloader on them was never touched (unlocked or locked, in any way). So that's not the answer.
It would be a big improvement for me, if I could at least get the LGUP tool to work for the K7.
BTW, I tried all 3 phones on the 2016 version of LG Flash Tool. All 3 failed to be identified.
Please, if anybody has a hypothesis for the odd behavior of the LGUP tool, I would love to hear it. Any suggestions are welcome.
BigZ1 said:
I don't know why I didn't think of this earlier. I own 3 LG phones (LGMS300m1, LM-X210ULMG10r. VS500PP9). I tried all 3 with LGUP tool. The tool recognized 2 of the 3, and failed to ID the LGMS300 (K7). Anybody got any ideas why the tool would recognize some but not others?
I am the only owner of the two phones that LGUP would ID. I guarantee that the bootloader on them was never touched (unlocked or locked, in any way). So that's not the answer.
It would be a big improvement for me, if I could at least get the LGUP tool to work for the K7.
BTW, I tried all 3 phones on the 2016 version of LG Flash Tool. All 3 failed to be identified.
Please, if anybody has a hypothesis for the odd behavior of the LGUP tool, I would love to hear it. Any suggestions are welcome.
Click to expand...
Click to collapse
Update on the never ending saga!
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). I 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.
Words of wisdom, anyone?