Where to begin?
I upgraded from Paranoid Android (Android 4.3.1 variant) to KITKAT 4.4 which I believe has turned my phone into an LG E960? Nexus 4.
After some data issues with 4.4 I decided to go back to PA and things seemed OK for a day or two outside of com.android.phone crashes once in a while. Then a random power cycle (initiated by me) brought me to a softbrick? beyond repair (at least every flash/fix seems to do little)
I have been able to boot into both DLmode and Recovery (TWRP 2.6) since this problem began but nothing allows me past either of those or any of the following : LG Logo (reached after my 8th or 9th teenybin attempt, and first attempt at flashing stock teeny. OR the Google logo with tiny unlock symbol at bottom.
I became frustrated and wiped everything (formatted data) through TWRP and have failed miserably with every attempt to sideload or lgnpst both .zips and .bins respectively. Now any attempt to sideload results in a "failed" attempt as it there is no folder "TWRP/Backups/......."
I have tried LGFLASHTOOL and followed directions to a T. but the issue here seems to be this. LGFLASHTOOL recognizes my phone as the LG E960 and states the LG LS970.dll isn't compatible with my phone.
Is there anybody out there that can make sense of my ranting explanations here?
The two MAIN problems troubling me seem to be this:
1) The phone is being recognized as the E960 via FLASHTOOL thus any LS970 flash or file creates a not compatible error.
2)Though TWRP seems functional, it is maybe only partially so. It wants to access a folder within itself that isn't there TWRP/Backups/....(specific random backup number)
ANY help would be GREATLY APPRECIATED. I have been at this for a day and a half.
p.s. a very odd side note. One sideload rom I flashed was Carbon, which failed to boot initially. I DID manage to have teenybin unlock, flash and reboot the phone directly into Carbon (with no data or gapps) and was able to usb over a couple .zips before getting an error "cannot be copied because device has been disconnected or has stopped responding" I thought I was in the clear and booted back into recovery via the carbon rom to flash gapps only to revert right back to my initial problem(s).......
WTF! I am lost. I've had this phone for almost a year and have used LGNPST more than a couple times with great success. I've flashed, unbricked and restored this phone and many others multiple times over the years (i.e. not a noob) Just effing dumbfounded.
edit: I have searched and read through countless threads in an attempt to find a fix for my problem with no luck. I've searched constantly to find a fix with no luck.
That was a lot of info. So lets see if you've tried these things yet.
Are you sure you don't still have the att TWRP to flash KK?
Flash TWRP 2.5.0.0
And try to flash a Stock ROM.
to get sideload to work: there is an option to make a log. it will make the partition writable after a format. had a similar issue when i first go the phone.
otherwise use an img. not a teeny bin and go back to stock zvb.
engine95 said:
That was a lot of info. So lets see if you've tried these things yet.
Are you sure you don't still have the att TWRP to flash KK?
Flash TWRP 2.5.0.0
And try to flash a Stock ROM.
Click to expand...
Click to collapse
I noticed in bootloader it references the device as mako, with a bootloader version of MAKOZ10f
I'll try TWRP v2.5.00 now. I just downloaded a Stock ZVC build.
I feel dumber and dumber as this process drags on. But appreciate the replies. I now realize my OP wasn't full of a ton of specific information. Sorry.
octhrope said:
to get sideload to work: there is an option to make a log. it will make the partition writable after a format. had a similar issue when i first go the phone.
otherwise use an img. not a teeny bin and go back to stock zvb.
Click to expand...
Click to collapse
in TWRP (still 2.6) I went into Advanced and ran 'Copy Log to SD' a button/feature I have always saw before, and never used.
I'm going to try to install TWRP 2.5 back onto the device first per previous post(er) and then I'll run this again before I try to install a stock rom.
Thanks for the idea.
I've used fastboot to flash twrp 2.5 and proceeded to 'Copy log to SD' before attempting to sideload stock rom.
In CMD this error is now returned when using commnd "adb sideload update.zip" :
failed to write data 'protocol fault <no status>
LGNPST method still giving same results. Gets to 85% error (I know this is normal) but when rebooting, boots to nothingness/black screen after quick glimpse of Google logo....
toastedjelly said:
in TWRP (still 2.6) I went into Advanced and ran 'Copy Log to SD' a button/feature I have always saw before, and never used.
I'm going to try to install TWRP 2.5 back onto the device first per previous post(er) and then I'll run this again before I try to install a stock rom.
Thanks for the idea.
Click to expand...
Click to collapse
Glad to hear ZVC almost worked for you.
If you can get into fastboot, you can install a different TWRP. fastboot erase recovery then fastboot flash recovery recovery.img
Or in TWRP flash a different TWRP, octhrope has them all here. http://forum.xda-developers.com/showpost.php?p=47679587&postcount=123
EDIT. Yeah... I was slow. lol
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
toastedjelly said:
I've used fastboot to flash twrp 2.5 and proceeded to 'Copy log to SD' before attempting to sideload stock rom.
In CMD this error is now returned when using commnd "adb sideload update.zip" :
failed to write data 'protocol fault <no status>
LGNPST method still giving same results. Gets to 85% error (I know this is normal) but when rebooting, boots to nothingness/black screen after quick glimpse of Google logo....
Click to expand...
Click to collapse
2 things:
Are you running as admin in the CMD prompt?
Make sure to use USB 2.0. Not USB 3.0
After LGNPST, press and hold the power button+vol up for 20sec+. Then press power+vol up again and maybe TWRP?
engine95 said:
Glad to hear ZVC almost worked for you.
If you can get into fastboot, you can install a different TWRP. fastboot erase recovery then fastboot flash recovery recovery.img
Or in TWRP flash a different TWRP, octhrope has them all here. http://forum.xda-developers.com/showpost.php?p=47679587&postcount=123
EDIT. Yeah... I was slow. lol
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
2 things:
Are you running as admin in the CMD prompt?
Make sure to use USB 2.0. Not USB 3.0
After LGNPST, press and hold the power button+vol up for 20sec+. Then press power+vol up again and maybe TWRP?
Click to expand...
Click to collapse
A similar thing happened when flashing a stock ZVB rom via lgnpst. This time it hit 85% and rebooted past Googe and hung briefly on the LG logo. It started to boot and ran the "optimizing apps" function. It loaded the OS and a couple seconds later rebooted itself back into the hanging LG logo bit.
In using sideload, I had COMPLETELY forgot to "erase recovery" before flashing a new one. Maybe that was causing the issue? Flashing a recovery over a recovery. Time to try sideload again.....
When it gets back to lg logo and goes no further then turn it off and get back in recovery and do a factory reset
Sent from my LG-LS970 using xda app-developers app
foxsdaddy67 said:
When it gets back to lg logo and goes no further then turn it off and get back in recovery and do a factory reset
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
WOOOOOOO that did it for me! I'm now on stock 4.1.2 LMAO. I used LGNPST to get a stock (rooted) ZVB build onto it. I let it reboot and sit on the LG logo for 10 minutes to err on the side of caution, Then powered down and back into recovery to do a factory reset.
It can make calls and connect to wifi. But no data. Probably just need to flash the zvb radio but again I'm almost scared to turn off/reboot/update anything at this point. Just happy to see the phone back after 2 plus days all jacked up.
Thanks for the help everyone!
toastedjelly said:
WOOOOOOO that did it for me! I'm now on stock 4.1.2 LMAO. I used LGNPST to get a stock (rooted) ZVB build onto it. I let it reboot and sit on the LG logo for 10 minutes to err on the side of caution, Then powered down and back into recovery to do a factory reset.
It can make calls and connect to wifi. But no data. Probably just need to flash the zvb radio but again I'm almost scared to turn off/reboot/update anything at this point. Just happy to see the phone back after 2 plus days all jacked up.
Thanks for the help everyone!
Click to expand...
Click to collapse
Ive had that happen before and it was the only thing that i could find that would work. glad it worked for you
try updating your PRL and Profile now might get data back
foxsdaddy67 said:
Ive had that happen before and it was the only thing that i could find that would work. glad it worked for you
try updating your PRL and Profile now might get data back
Click to expand...
Click to collapse
I managed to do a complete back-up in TWRP of the fully functional 4.1.2 I got up and running. My data (wifi + lte) came back after I eventually flashed the correct radio.
I'm going to maybe stay stock for a couple days. I honestly can't remember the last time I used stock Android on my phone....
Right now I'm attempting to update it to zvc because i'm impatient. Fingers crossed.....
Normally I run stock rooted. Can't beat the battery life on stock. Running asop kit Kat right now
Sent from my LG-LS970 using xda app-developers app
Related
its just sitting on the freaking LG screen... every time i vol dwn + pwr and double press power it goes normal but then cwm doesn't come up and it just restarts and hangs at LG again. i ****ing hate this phone can someone please help me out? why won't cwm load
can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?
aquariuz23 said:
can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?
Click to expand...
Click to collapse
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.
mic.mayorga said:
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.
Click to expand...
Click to collapse
Sorry to hear that. Unfortunately I can't help much at all since I haven't done either yet (CWM or Kernels/rom installations) so rather than making things worse for you, I'll leave it to the Pros here to help you. Im sure one of them will respond back soon enough.
Try this:
Disconnect the phone and pull out the battery.
Put battery back in and plug phone to a wall charger. Let it boot to the battery charging screen. Once there press and hold POWER + VOLDOWN
Depends on type of the problem, it helped me 9 out 10 times...
tried it at least 20 times now. just realized that i didn't format /system nor did i update cwm yesterday. probably the root of all these problems. I'm just gonna start fresh with the kdz. I'm on a mac though so its going to be a long night starting with boot camp.
I'm having the same problems...well kind of...
I followed all the instructions for CWM and everything went great. No real issues but had to reinstall the .img twice and then was perfect thereafter. Saw the beta 2 ROM and figured what the hey...downloaded and installed to SD Card. Used CWM/Nandroid to do a backup then installed the zip for the ROM from the sd card.
It took a matter of 10 seconds and said it was successful/done and restarted phone-got a boot loop on LG screen for about 15 minutes and finally did a battery pull-tried several times to get it into CWM with no luck and finally was able to get in-but had to plug it into the wall and wait for charging screen to show. Was able to restore and all was well until turning the phone off.
Turning off the phone now causes the phone to loop on the ATT screen-I can get into download mode and can get into CWM and restore and all is well until turning phone off.
I figured it just needs a fresh install so I've been trying to flash the kdz but the firmware updater keeps faulting and never makes it through the process...so I'm stuck...have all the files I need (I believe) and have everything in place...just can't get it back to normal.
Any ideas from here?
Thanks in advance!
Yeah, sometimes it could be quicker just start over and restore backups...
While you there, would you mind do this: Needed SystemUI.apk from SU640
[EDIT]
@fishscale28:
did you do kdz unbrick before? If not, then perhaps you are not doing it right...btw, kdz file for LU6200 didn't work for me.
Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...
fishscale28 said:
Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...
Click to expand...
Click to collapse
I installed from the kdz yesterday and didn't have to delete any files. I'm on Win 7 x64. The first time it ran it told me to restart my phone cause it didn't see it, but the second time it ran until my phone reboot and I killed the program. Be sure you have the KDZ_FW_UPD_EN with UpTestEX_mod2_marwin.exe in it. Hope this helps.
Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!
Maybe http://www.microsoft.com/windows/virtual-pc/ can help?
alright so i got to the 4% thing and my phone rebooted but it kept looping to the screen LG Optimus LTE bootscreen with the pink candy cane. thats it. i did vol dwn + pwr and got the android arrow and box with loading bar no text, then it rebooted back to the optimus lte screen. never got to the setup screen. tried the kdz again and my phone died. now when i plug it in i only get download mode... does it charge in download mode and why did it not get to the setup screen?!
fishscale28 said:
Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!
Click to expand...
Click to collapse
Even after running the kdz, my phone still does that after installing CWM. I don't know if it's something with my ROM or something with CWM, but if you can't get into CWM you probably don't need to run the kdz. I couldn't get into CWM anymore when I ran it.
So you're saying you go into the boot loop after turning off your phone even after unbricking?
I don't get it-now I can't get into recovery and it keeps up with the boot loop. I've tried running on the virtual PC/XP deal and it doesn't crash but now it doesn't even see the phone...reinstalled all the drivers, etc. and still no luck. Is there anyway to get the kdz installed without this updater?
fishscale28 said:
So you're saying you go into the boot loop after turning off your phone even after unbricking?
Click to expand...
Click to collapse
Yes. I don't think that was happening until I put CWM on. But I can live with it until the issue is solved. I don't think I'm the only one having it.
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Reynolds1029 said:
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Click to expand...
Click to collapse
Just bricked mine installing 9 also. Can't do anything, but mess around in TWRP. LGPNST won't detect my phone. Stuggling here. I guess I need to reactivate the evo for a while. Really pissed.
Hey guys, I've tried installing stock all over again and that won't even work for this problem. what a conundrum.
Reynolds1029 said:
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Click to expand...
Click to collapse
the easy way to get back on your phone is doing the restore method using lgnpst tool..there are differents methods guides..
1)AutoLGNPST-tSilenzio.zip
2)LGNPST-PhantomPhreak53.zip
3)lgnpst-shelnutt.zip
so with these tools you can go back to v7 fool unroot and then update it to v8 and v9 ,just you want to make sure if your phone can get the download mode,,,for more information you can go to irc freenode guyz its is a private chat,,,and then ask them about the lgnpst tools link,im sure they will give you more information about it,,,they have the link for both software restore(v7 and v9 .tot files)if not i posted in general the v9 .tot file link, dont worry your phone still alive,i hope adb to push files directly to custom recovery it doesnt work so the easy and method way is restore it!!!:laugh:
MikeDroid said:
Just bricked mine installing 9 also. Can't do anything, but mess around in TWRP. LGPNST won't detect my phone. Stuggling here. I guess I need to reactivate the evo for a while. Really pissed.
Click to expand...
Click to collapse
did you put your phone into download mode when you tried lgpnst
I want to tell to everybody if you installed the v9 update dont try to root and unlock or install custom recovery,even going back and restor the v7....if you try the phone it wont restar...
---------- Post added at 08:57 AM ---------- Previous post was at 08:44 AM ----------
THIS IS THE GUIDE HOW TO RESTORE IT OR UNROOT IT.....
1. Install LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1 (LG USB Drivers)
2. Install LGNPSTv1.3_Lab_Verison_RightClickReg (LGNPST)
3. Install LGNPST_GenericModels_Ver_5_0_12_0 (LGNPST Generic Modules)
4. Install LGNPST_Components_Ver_5_0_20_0 (LGNPST Components)
5. Copy the Models folder to C:\LG Electronics\LGNPST\
6. Start a command prompt as admin
7. Type regsvr32 "C:\LG Electronics\LGNPST\Models\LGNPST_LS970.dll"
8. Download the proper .tot file for your phone
9. Rename .tot to .bin
10. Open LGNPST
11. Select the LGNPST_LS970.dll and your .bin file
12. Press Start
If LGNPST errors out at 85%, turn your phone off and hold the power button until the phone powers on, then release.
never mind....
Sent from my LG-LS970 using xda app-developers app
Fix
Reynolds1029 said:
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Click to expand...
Click to collapse
Accessing Recovery Screen (First Step if you have bricked your phone)
This is our initial step for any problems that might arise. If you can access recovery, usually you're in a perfectly fine situation.
1. Power off your phone by holding Volume down & power at the same time.
2. When the screen shuts off, switch to entering fastboot by holding Volume Up & Power. Release immediately once you see a black screen with some text on the bottom.
3. You should see a black screen with some text at the bottom.
4. Press volume down 2x and then the power button.
5. You should see either TWRP or CWM recovery.
6. Wipe Cache, Dalvic Cache, and Factory Wipe
7. Flash new stock zip. Wipe caches again.
8. Restart.
If you need further help view the full post by AdriVelazquez (HERE)
Reynolds1029 said:
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Click to expand...
Click to collapse
Well good new here for all that brick is that you can go to any sprint store and exchange it as a defective device, but please do all you cn to get it back into working order, simply because Sprint does not have an official rooting policy it simply states "if phone appears rooted , make a note and continue as normal"
Now be ready with the correct verbage as everything in the Sprint world is at managers discretion which simply means a manager can say no and you would have to take it to retention, no body wants this. So just be cool and tell them you did the OTA and this is what happened simple as that. If worse comes to worse just tell ask them to DHRP it since the phone is so new you will get a new 1 anyways.
BUT PLEASE FOR THE SAKE OF ALL US INCLUDING YOURSELF GIVE IT YOUR BEST SHOT AT RETURNING IT TO STOCK , IF YOUR HAVING TROUBLE HIT UP SOME OF THE DEVS ON GTALK , Im sure one of them or I if I am home will do our best to walk you through it.
Hey all i forgot i posted this thread awhile ago sorry kinda just me n my bro went hard at work and finally fixed the phone and i found the probelm.. At the IRC at the time there were different versions of LGNPST i used the one directed to in the guide i used and that was the autoLGNPST and it was version 1.3 but it never recognized the device in download mode so my bro said it had to be a driver issue so im like ok we find a few drivers install just to make sure and at that point we knew that the computer was reconizing the phone because on ADB we can push a file through and i can install a ROM which i did but for some reason it never could install.. it was the lifeless ROM and dont worry i cleared everything but it never booted after that just kept booting into CWM. So im like ok i bring it to the sprint store the next day the Technician wasent there that day so i hada wait till the next day but that night i tried one more time 2 fix this thing and turns out that day the IRC puts up new files and it was a new version of autoLGNPST v2.2 or v2.3 i believe new DLLs and a new .bin file for ZV7 and the old ones were corrupt i used the new files a viola IT WORKED!! BUT... i cant for the life of me get a flippin ROM on here dont matter which ROM i try or if i use CWM or TWRP i cant get a ROM on always either the install fails or i install it and it reboots but just comes up with a blank screen after the LG logo and mind u i use the AiO tool on the forums to unlock the bootloader and root it and install TWRP or CWM and im on ZV8 when im installing them n ive tried many many times and i just wind up LGNPSTing it again backups never work either any help with this would be greatly appreciated
lgnpst 85% error cause: download failed
ALBERTOSCLN said:
I want to tell to everybody if you installed the v9 update dont try to root and unlock or install custom recovery,even going back and restor the v7....if you try the phone it wont restar...
---------- Post added at 08:57 AM ---------- Previous post was at 08:44 AM ----------
THIS IS THE GUIDE HOW TO RESTORE IT OR UNROOT IT.....
1. Install LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1 (LG USB Drivers)
2. Install LGNPSTv1.3_Lab_Verison_RightClickReg (LGNPST)
3. Install LGNPST_GenericModels_Ver_5_0_12_0 (LGNPST Generic Modules)
4. Install LGNPST_Components_Ver_5_0_20_0 (LGNPST Components)
5. Copy the Models folder to C:\LG Electronics\LGNPST\
6. Start a command prompt as admin
7. Type regsvr32 "C:\LG Electronics\LGNPST\Models\LGNPST_LS970.dll"
8. Download the proper .tot file for your phone
9. Rename .tot to .bin
10. Open LGNPST
11. Select the LGNPST_LS970.dll and your .bin file
12. Press Start
If LGNPST errors out at 85%, turn your phone off and hold the power button until the phone powers on, then release.
Click to expand...
Click to collapse
This is what my LGNPST does, it shows an error at 85% saying
"Process: Upgrade_Masterbin
"Subproc : Masterbin Donwload
Cause: Download Failed"
I did what you suggested (hold the power button until the phone powers on? rather powers off, right?) I am in donwload mode and tried taking out the battery and restarting into download mode and repeating the flashing process (unitl 85%) various times... always with the same error message as a result... what is the problem?
Cause: Download Failed
zendoo said:
This is what my LGNPST does, it shows an error at 85% saying
"Process: Upgrade_Masterbin
"Subproc : Masterbin Donwload
Cause: Download Failed"
I did what you suggested (hold the power button until the phone powers on? rather powers off, right?) I am in donwload mode and tried taking out the battery and restarting into download mode and repeating the flashing process (unitl 85%) various times... always with the same error message as a result... what is the problem?
Click to expand...
Click to collapse
You managed to solve it
my LG G PAD v500 is stuck at :
Fastboot mode started
udc_start()
the only thing hat i can do is to be turned off....help!!!!!!!!!!!!!!
:crying:
im unable to go to download mode...... can you please instruct me in detailed in what to do?
Hey i have the same problem
I have the same problem after i did a factory software upgrade and i was rooted but no recovery. did yo ever get it fixed
Solematrix said:
I have the same problem after i did a factory software upgrade and i was rooted but no recovery. did yo ever get it fixed
Click to expand...
Click to collapse
If this error shows up because of bad recovery, boot into normal ROM, root and flash stock recovery or twrp
If this error shows up because of bad boot.IMG, then you'll have to restore firmware from kdz file via download mode.(download mode = plug in usb plus volume up(?)... You should see a "Download" logo, brightness mat be very low and you have to squint )
Thanks
Yes thanx i figured it out from reading threw the forums but your help was much appreciated now to find out why my vk810 will not upgrade to 4.4.2 keep getting a error message
paperWastage said:
If this error shows up because of bad recovery, boot into normal ROM, root and flash stock recovery or twrp
If this error shows up because of bad boot.IMG, then you'll have to restore firmware from kdz file via download mode.(download mode = plug in usb plus volume up(?)... You should see a "Download" logo, brightness mat be very low and you have to squint )
Click to expand...
Click to collapse
Solematrix said:
Yes thanx i figured it out from reading threw the forums but your help was much appreciated now to find out why my vk810 will not upgrade to 4.4.2 keep getting a error message
Click to expand...
Click to collapse
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
i did post it in another thread i started but never really got answers
paperWastage said:
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
Click to expand...
Click to collapse
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
i wiped it clean and started from new and it still say the same thing i tried it on wifi same time. i even took out my t mobile sim thinking it was that
paperWastage said:
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
Click to expand...
Click to collapse
Hi,
Just to know if this problem is solved...
If it is, then this is most probably useless... unless somebody else stumps into the same problem.
If I can guess it correctly, this message typically display when you have rooted your V500, installed a custom recovery from an app flasher (i.e. Flashify, ROMToolBox...) and the recovery isn't compatible with your device and you tried a hard reset.
This means that you are able to boot into fastboot and that is what's going to save you
Why ? Simply put : because you can flash some files using the fastboot command line
Try to flash bootloaders, aboot, boot and recovery just for a try. You can find those I guess.
Regards.
Stuck with "Fastboot mode started"
I was currently on Altev vk81035b-rooted-SU installed but no custom recovery. I followed Altev-Hnk1 instructions for flashing aboot.4.2.2 & commands (dd if=/......Etc) you know the rest) which successfully copied the file. Then when I typed "reboot recovery" BAM, that's when my gPad slapped me in the face with the following--> Fastboot mode started udc_start()
I press & constantly hold "power & down" buttons which always brings me to "System Recovery" screen listing 4 options, "Continue reboot"-"Factory data reset"-"Wipe Cache"-"Safe mode boot". Anytime I have a problem I'll choose "safemode" which always got me back in after any "Boot Verification Errors", but now it doesn't & I'm stuck no matter what I chose. I'm starting to think I may need to connect my laptop and flash the KDZ starting from scratch with plain-Jane Verizon stock!?!? Whatcha think, yes-no-maybe so!?!? LOL
My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.
:crying: This problem started when I tried to install ResurrectionRemix Rom for the The LS980, I had a ZVE Radio on my phone, before I rooted my device, I used StumpRoot to root my phone, then after that I installed autorec to be able to use TWRP, then after that i backed up my device so that I can start flashing the Rom, so after that I wiped Dalvik/Cache/Data, etc, except for internal storage, then i install the Rom, and after that I installed the Gapps for the Rom, and after that I wiped Dalvik and Cache and restarted my device, and its now going into a bootloop, so at this point I'm still able to go into TWRP so that I can be able to restore my backup, but it wasn't there, so I went back to the Install tab and it looked different like it was less files than before, it's like the system on my phone re-wrote itself, idk, so then I went into the file manager that is in TWRP to search for my backup file, I found it along with all my other files, but I didn't know how to be able to restore it, so (I think this is were I made things worse for myself) I went to the Install Tab to install the ZVC Radio, because I thought the Rom wasn't working because of the different Radios my device had, so then I restart my phone, and now it's just a blank screen, that keeps looping, so I started searching on XDA if anyone else is facing this issue, and I found this thread http://forum.xda-developers.com/showthread.php?t=2582142 it helped me get out of the deep brick whereas there was no recovery mode before, But I'm still in a Hard Brick whereas the LG Logo is shown for several seconds and then it says LG Security Error and shuts down and I still dont have download mode, but if I'm connected to a computer it just goes into a bootloop with the same message on the screen, so I installed LG drivers and ADB Drivers for my phone to be recognized on the computer, and the computer recognizes the device when I'm in recovery mode, but at this point I don't know what to do, and I certainly don't want to spend 150.00$ for a replacement, so if anyone can help me, I will very much appreciate it.
Images Below (Forgive me if the image quality is a little fuzzy, these images were taken using my Nexus 4)
TechGirl90 said:
:crying: This problem started when I tried to install ResurrectionRemix Rom for the The LS980, I had a ZVE Radio on my phone, before I rooted my device, I used StumpRoot to root my phone, then after that I installed autorec to be able to use TWRP, then after that i backed up my device so that I can start flashing the Rom, so after that I wiped Dalvik/Cache/Data, etc, except for internal storage, then i install the Rom, and after that I installed the Gapps for the Rom, and after that I wiped Dalvik and Cache and restarted my device, and its now going into a bootloop, so at this point I'm still able to go into TWRP so that I can be able to restore my backup, but it wasn't there, so I went back to the Install tab and it looked different like it was less files than before, it's like the system on my phone re-wrote itself, idk, so then I went into the file manager that is in TWRP to search for my backup file, I found it along with all my other files, but I didn't know how to be able to restore it, so (I think this is were I made things worse for myself) I went to the Install Tab to install the ZVC Radio, because I thought the Rom wasn't working because of the different Radios my device had, so then I restart my phone, and now it's just a blank screen, that keeps looping, so I started searching on XDA if anyone else is facing this issue, and I found this thread http://forum.xda-developers.com/showthread.php?t=2582142 it helped me get out of the deep brick whereas there was no recovery mode before, But I'm still in a Hard Brick whereas the LG Logo is shown for several seconds and then it says LG Security Error and shuts down and I still dont have download mode, but if I'm connected to a computer it just goes into a bootloop with the same message on the screen, so I installed LG drivers and ADB Drivers for my phone to be recognized on the computer, and the computer recognizes the device when I'm in recovery mode, but at this point I don't know what to do, and I certainly don't want to spend 150.00$ for a replacement, so if anyone can help me, I will very much appreciate it.
Images Below (Forgive me if the image quality is a little fuzzy, these images were taken using my Nexus 4)
Click to expand...
Click to collapse
All non stock require zv8 radio. If your highlighted image in recovery says update by adb. You may be able to grab official zve update from sprint g2 general.
Or hit the wipe data and see if it goes to TWRP.
secret.animal said:
All non stock require zv8 radio. If your highlighted image in recovery says update by adb. You may be able to grab official zve update from sprint g2 general.
Or hit the wipe data and see if it goes to TWRP.
Click to expand...
Click to collapse
It didn't go through.[emoji20] Installation aborted, I think I messed up big time.[emoji20] I appreciate the help though.
Sent from my Nexus 4 using Tapatalk
TechGirl90 said:
It didn't go through.[emoji20] Installation aborted, I think I messed up big time.[emoji20] I appreciate the help though.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Which part or both fail? The wipe data to TWRP, is a shot in the dark in going to recovery. Adb side load official update was also.
I read somewhere of repairing the partitions by pushing them. I'll see if I can find that thread.
secret.animal said:
Which part or both fail? The wipe data to TWRP, is a shot in the dark in going to recovery. Adb side load official update was also.
I read somewhere of repairing the partitions by pushing them. I'll see if I can find that thread.
Click to expand...
Click to collapse
Both failed, the wipe data just freezes and goes no further, and I can't get to twrp, I just have the basic recovery mode.
Sent from my Nexus 4 using Tapatalk
TechGirl90 said:
Both failed, the wipe data just freezes and goes no further, and I can't get to twrp, I just have the basic recovery mode.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Let's hope I find that thread.
---------- Post added at 04:04 PM ---------- Previous post was at 03:48 PM ----------
TechGirl90 said:
Both failed, the wipe data just freezes and goes no further, and I can't get to twrp, I just have the basic recovery mode.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2681089
Try this one which I got from
http://forum.xda-developers.com/sprint-g2/help/ls980-bricked-black-screen-fastboot-t2976744
He quoted 2 threads he tried. I clicked the one I have above first and looked like a good help.
TechGirl90 said:
Both failed, the wipe data just freezes and goes no further, and I can't get to twrp, I just have the basic recovery mode.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Have you been able to resurrect your phone?
secret.animal said:
Have you been able to resurrect your phone?
Click to expand...
Click to collapse
Nope, the phone's dead, I really damaged the phone's software really bad, I didn't follow the instructions correctly as stated on the RessurectionRemix Rom Thread , so I've brought this upon myself, Thankfully I've received a replacement today, but now I'm feeling iffy about rooting my phone and flashing roms again, because I don't want to go through this predicament again.
Update: Thank You for helping me try to get the device back into a functional state, I really appreciate it
on same boat
hey, techgirl90,
on same boat only have stock recovery
pls help me if you have find anyone