Develop Bugs

[Q] @ Standstill with phone after multiple LGNPST and LGFLASHTOOL attempts to fix

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

Nexus 7 2013 Wi-fi not booting

Hello
I think I made a big mistake.
I tried to flash stock MM image on my nexus 7 and I failed doing so by NTK (it said that the bootloader must be unlocked in order to proceed, but mine was already unlocked), so I went into TWRP and did the factory reset (tought it might help). so now N7 won't start, it's stuck on the boot animation of MM.
I tried this guide http://forum.xda-developers.com/showthread.php?t=1907796, and it says I need to check USB debugging, but I can't since I can't even get in to the system.
Is there any way to get my N7 back original state or am I having a plastic brick with a nice animation in my hand?

reso91 said:
Hello
I think I made a big mistake.
I tried to flash stock MM image on my nexus 7 and I failed doing so by NTK (it said that the bootloader must be unlocked in order to proceed, but mine was already unlocked), so I went into TWRP and did the factory reset (tought it might help). so now N7 won't start, it's stuck on the boot animation of MM.
I tried this guide http://forum.xda-developers.com/showthread.php?t=1907796, and it says I need to check USB debugging, but I can't since I can't even get in to the system.
Is there any way to get my N7 back original state or am I having a plastic brick with a nice animation in my hand?
Click to expand...
Click to collapse
I assume you didn't make a backup of your working OS before flashing. Since you don't give details of that OS, it's hard to guess at what might have gone wrong. But if you were on Lollipop, you can always flash one of those roms that's close to stock with TWRP and restart from there. If the process stalls at animation, it usually means you don't have a bad Emmc, which is good news.
BTW, the guide you posted was for the Nexus 7 2012. This is the forum for the Nexus 7 2013. Was it a mistake of yours?

graphdarnell said:
I assume you didn't make a backup of your working OS before flashing. Since you don't give details of that OS, it's hard to guess at what might have gone wrong. But if you were on Lollipop, you can always flash one of those roms that's close to stock with TWRP and restart from there. If the process stalls at animation, it usually means you don't have a bad Emmc, which is good news.
BTW, the guide you posted was for the Nexus 7 2012. This is the forum for the Nexus 7 2013. Was it a mistake of yours?
Click to expand...
Click to collapse
Thanks for zour reply. No I don't have backup (stupid, I know).
I was running Marshmallow, Cleanrom.
I found that I can mount usb via mount otg in TWRP, I will try to do so later today.

Ok, I solved the problem.
I tried to flash Cleanrom from OTG, installation completed normally that got stuck on reboot again, this time it went directly from google logo to TWRP, reporting "unable to mount /data".
Did a google search and found this thread: http://forum.xda-developers.com/showthread.php?t=2471341.
Followed the instructions and it worked.
I'm never flashing anything again without backup.

reso91 said:
Ok, I solved the problem.
I tried to flash Cleanrom from OTG, installation completed normally that got stuck on reboot again, this time it went directly from google logo to TWRP, reporting "unable to mount /data".
Did a google search and found this thread: http://forum.xda-developers.com/showthread.php?t=2471341.
Followed the instructions and it worked.
I'm never flashing anything again without backup.
Click to expand...
Click to collapse
Which fix in that thread helped you? I take it you did not replace the motherboard?

zphelj said:
Which fix in that thread helped you? I take it you did not replace the motherboard?
Click to expand...
Click to collapse
No, I didn't replace it.
I got it working with this tool:
http://forum.xda-developers.com/showthread.php?t=2381582

reso91 said:
No, I didn't replace it.
I got it working with this tool:
http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Ah, OK. Looks like that is a factory image installed via fastboot.

Please Help!!! Phone in bootloop after flashing TWRP.

Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please

gersrt said:
Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please
Click to expand...
Click to collapse
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)

felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
Cheers Mate, I'm sure I've already tried this, I will try again when I get home.
Thanks for your input.
Il let ya know.

felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app

Wired4Fun said:
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a common mistake.

Well, thank you again....
Sent from my SM-G900V using XDA-Developers mobile app

Tiny little explanation, When rooting and unlocking your bootloader via ADB, the script wipes your SD card and puts a special code in it to backup your phones original CID. This may be used to unbrick your phone one day. So your NEWLY unlocked phone is using a new CID and your SD card is on the old one. Hence the boot loop. So when reading the OP, I thought the same thing. I didn't seem his say he pulled out his SD card after rooting. Hopefully you guys got it working again.

Lol, Honestly I dint figure it out. I read somewhere in the forums about it. Dont remember exactly who suggested it. But, it worked for me.
Did it work for you?

I have same problem, was on BPA1, unlocked bootloader, flashed twrp, something went wrong had to flash stock again, CPL1 loads up fine but when flashing back to BPA1 runs into bootloop, help.

you rock
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
you rock mate ... itried this for 2 hrs and all i had to so is take the damn sd out...thanks

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app

title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.

Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app

Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.

Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk

Help, might have killed my device

Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?

ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.

like Fury said, your platform tools need to be updated, same thing happened to me.

What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app

fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.

Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.

Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.

Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.