Related
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
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
clown6198 said:
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Click to expand...
Click to collapse
stathis95194 said:
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
Click to expand...
Click to collapse
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
clown6198 said:
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
Click to expand...
Click to collapse
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Yet another user stuck because they followed a tutorial or video guide, instead of taking the time to learn, read, and really understand the steps and concepts. This is exactly why I discourage such tutorials or YouTube guides (and Toolkits as well), as they leave you completely unequipped to recover if you have a problem, leaving your buddies at XDA to clean up the mess.
YouTube video or not, you shouldn't be doing anything you don't understand, and you shouldn't be wiping anything if you don't understand what the result will be.
You will need to troubleshoot the USB connectivity issue first. From there, unlock the bootloader again, install custom recovery and flash a ROM (as stathis95194 has already stated).
stathis95194 said:
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Click to expand...
Click to collapse
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
clown6198 said:
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
Click to expand...
Click to collapse
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
redpoint73 said:
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
Click to expand...
Click to collapse
will this work even with the S-ON?
clown6198 said:
will this work even with the S-ON?
Click to expand...
Click to collapse
Of course. I wouldn't be telling you to do it, otherwise.
redpoint73 said:
Of course. I wouldn't be telling you to do it, otherwise.
Click to expand...
Click to collapse
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Honestly, I would just install Philz recovery instead of TWRP and try to either install the ROM zip directly (after a full wipe), or sideload the ROM zip from your PC.
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time. Find a ROM for your device that is based off of the 1.x firmware and download that. To get your device out of the bootloop and back into boot loader/recovery, hold power and volume up for quite some time until the screen shuts off. Then, hold power down while the screen is black and you'll be in the boot loader. From there you can use the arrow keys to select recovery. Of it isn't there, first select fastboot or hboot and look for it there. You should be in recovery, now you can go ahead and push the file to your phone. Ensuring it is a sense ROM based off of the 1.x firmware, go to wipe and do the standard swipe to wipe (will erase app data not pictures or downloads), then go into install and select your ROM and swipe. Be patient while your device turns on for the initial boot, it might take a while but your phone should be functional after that.
wtoj34 said:
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time.
Click to expand...
Click to collapse
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
Hi so Im in TWRP. I pushed a ROM called Android_Revolution_HD-One_M8_11.1 which is supposedly the closest rom to a stock one. I tried flashing the ROM many times, Im in the process of flashing it again after whiping like you said. The result is the same. After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Thanks,
clown6198
clown6198 said:
After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Click to expand...
Click to collapse
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
redpoint73 said:
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
Click to expand...
Click to collapse
ahahaha THANK you so much!!!! I got the phone to work but now the problem is, I cant get the sound to work when Im playing music. I installed the harman kardon software and I cant get the music to work at all
clown6198 said:
I installed the harman kardon software and I cant get the music to work at all
Click to expand...
Click to collapse
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
redpoint73 said:
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
Click to expand...
Click to collapse
Damn. Apparently I need to get s-off in order for the harman kardon to work. Just need to uninstall harman kardon now... But yea sorry all I needed was to flash the rom. I didn't know the booting was going to take 5 mins and over. I thought that I was just stuck on the HTC logo. all I needed was to be patient ahaha Thanks a lot guys
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
MrDelicious said:
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
Click to expand...
Click to collapse
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
Click to expand...
Click to collapse
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
Click to expand...
Click to collapse
Thanks! I shall look into this.
: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
Okay. I'm desperate... I bricked my OP3 and have no money for a new one!
Here's what happened:
I was running the latest stable version of FreedomOS and everything worked perfectly. I got bored and decided it'd be a good idea to install CM 13. I booted into TWRP and flashed the rom then realized "oh wait i could install CM14" . I went to the XDA thread which said i first had to install a version of Oxygen OS.
Instead of just flashing the O2OS zip through TWRP like a normal person I decided to revert fully to factory settings. I found some instructions on how to do so. They said:
1 - flash stock Recovery
2 - run "fastboot oem lock"
I got this far and reaized that i F***ed up. My OP3 won't boot into recovery or system and i can't run "fastboot oem unlock" (it says remote unlock isn't allowed).
I tried the "Mega Unbrick Guide" but the msn download always fails and says "sahara connection failed"
Is there any way to restore my OP3?
Please say there is... I'm broke and can't afford a new phone... ?
Well, keep trying with that unbrick guide ... It's your best bet.
Btw, re-locking bootloader is not necessary, even if you're reverting to fully stock. It's pointless and can only cause problems, no benefits whatsoever. But now you know that already ...
Sent from my OnePlus 3 using Tapatalk
dmdylan said:
Okay. I'm desperate... I bricked my OP3 and have no money for a new one!
Here's what happened:
I was running the latest stable version of FreedomOS and everything worked perfectly. I got bored and decided it'd be a good idea to install CM 13. I booted into TWRP and flashed the rom then realized "oh wait i could install CM14" . I went to the XDA thread which said i first had to install a version of Oxygen OS.
Instead of just flashing the O2OS zip through TWRP like a normal person I decided to revert fully to factory settings. I found some instructions on how to do so. They said:
1 - flash stock Recovery
2 - run "fastboot oem lock"
I got this far and reaized that i F***ed up. My OP3 won't boot into recovery or system and i can't run "fastboot oem unlock" (it says remote unlock isn't allowed).
I tried the "Mega Unbrick Guide" but the msn download always fails and says "sahara connection failed"
Is there any way to restore my OP3?
Please say there is... I'm broke and can't afford a new phone...
Click to expand...
Click to collapse
Well first off, factory settings is just a wipe from TWRP I have no idea why you would install Stock Recovery and relock the device. That's like...LITERAL restore back to stock like before you even got the device.
Next is that your phone needs to be in fastboot mode in order to run OEM unlock.
Plug the phone into a different USB port and try it if not do a little more digging in the OP forums
No need to panic for as long as you have fastboot, you're all good..
Go here; http://forum.xda-developers.com/oneplus-3/how-to/untouched-oxygen-os-3-2-5-img-boot-img-t3460975
Download the boot and system images and flash through fastboot.. I've done this myself and once your phone boots, install twrp etc..
hagar006 said:
No need to panic for as long as you have fastboot, you're all good..
Go here; http://forum.xda-developers.com/oneplus-3/how-to/untouched-oxygen-os-3-2-5-img-boot-img-t3460975
Download the boot and system images and flash through fastboot.. I've done this myself and once your phone boots, install twrp etc..
Click to expand...
Click to collapse
Thanks for your help but it didn't work because my bootloader is locked
dmdylan said:
Thanks for your help but it didn't work because my bootloader is locked
Click to expand...
Click to collapse
resolveste have the problem ????
Excuse my English, I am Portuguese
---------- Post added at 11:02 AM ---------- Previous post was at 10:57 AM ----------
Excuse my English, I am Portuguese[
---------- Post added at 11:05 AM ---------- Previous post was at 11:02 AM ----------
there is a way to solve this, you have windows 10 ????
When you cannot afford another phone ..why the f you touch your current phone. Leave it as it is... The stock is the most stable. The most battery friendly most performance.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
unbrick tool
hello,
you need the OnePlus3_Unbrick_Tool_Full.rar to unbrick your phone, i was also in your situation,
you need also the Qualcomm_Diag_QD_Loader_2016_driver.exe with this two tools you can flash to restore the OP3
me helped al lot this thread http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
a had a success with this part How to Make the device show as Qualcomm 9008
it is important that you have the correct driver installed on your pc that the phone will be recognized as Qualcomm 9008
if you need help you can pn me if you want
try this also http://www.androidbrick.com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008/
1. download one plus rom from the official oneplus website -> s3.amazonaws.com/oxygenos.oneplus.net/OnePlus3Oxygen_16_OTA_015_all_1609141252_c38077177cfc4e74.zip
2. boot in recovery and select install rom from adb -> downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.6 (follow the Flash Instructions)
3. be happy