Related
so i just ran LGNPST to get to ZV7, then i updated to ZV8
once i was on ZV8, i rooted and unlocked bootloader successfully using GAIO v1.50
i'm having problems booting into my custom recovery TWRP, after i install the custom recovery using GAIO
i try to shutdown the phone and boot into recovery, but every time i try i get a quick screen of the lg logo then it goes black and it doesn't load the os.
i cant even get to fast boot, so what i've done from here (the past 5 times) is i run LGNPST again and start all over again.
i tried the FreeGee method of installing the custom recovery but the results are the same..
any ideas?
avpmusic said:
so i just ran LGNPST to get to ZV7, then i updated to ZV8
once i was on ZV8, i rooted and unlocked bootloader successfully using GAIO v1.50
i'm having problems booting into my custom recovery TWRP, after i install the custom recovery using GAIO
i try to shutdown the phone and boot into recovery, but every time i try i get a quick screen of the lg logo then it goes black and it doesn't load the os.
i cant even get to fast boot, so what i've done from here (the past 5 times) is i run LGNPST again and start all over again.
i tried the FreeGee method of installing the custom recovery but the results are the same..
any ideas?
Click to expand...
Click to collapse
the same thing happened to me a while ago. if i remember correctly, what i did was after lgnst, i rerooted my phone, install cloworkrecovery from the play store. use the app to boot into recovery, then wipe cache and dalvik cache or whatever its called. hope this helps!
javskies said:
the same thing happened to me a while ago. if i remember correctly, what i did was after lgnst, i rerooted my phone, install cloworkrecovery from the play store. use the app to boot into recovery, then wipe cache and dalvik cache or whatever its called. hope this helps!
Click to expand...
Click to collapse
I downloaded rom manager from play store and it says my phone was unsupported
Any ideas?
avpmusic said:
I downloaded rom manager from play store and it says my phone was unsupported
Any ideas?
Click to expand...
Click to collapse
If it says your phone is unsupported then you are trying to load cwm on your phone which shouldn't be needed as free gee should load it on your device(if I remember correctly. Been a while since I unlocked). He is saying that he used it to boot into recovery not load cwm.
I assume that's what he is saying and you are doing if I'm wrong feel free to correct.
You could also install ROM toolbox scroll to the very bottom of the first page click Rebooter and click reboot recovery. That should hopefully take you to cwm where you can flash recovery.
Sent from my LG-LS970 using xda app-developers app
AOKPBrownNoser said:
If it says your phone is unsupported then you are trying to load cwm on your phone which shouldn't be needed as free gee should load it on your device(if I remember correctly. Been a while since I unlocked). He is saying that he used it to boot into recovery not load cwm.
I assume that's what he is saying and you are doing if I'm wrong feel free to correct.
You could also install ROM toolbox scroll to the very bottom of the first page click Rebooter and click reboot recovery. That should hopefully take you to cwm where you can flash recovery.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
i tried using rom manager to kick me into recovery (chosing trwp recovery before hand with freegee) before and it did the same thing,
rebooted, showed lg logo for a split second, then black screen. i just did the whole process again of using LGNPST to get to ZV7, then i updated to ZV8 then free gee to give me twrp then rom toolbox to kick me into recovery and its the same thing! black screen!
i also tried BEFORE doing freegee to go into recovery after the LGNPST to see what happens, and it just took me to normal recovery.
so my issue has to be with freegee..
should i LGNPST again to get me back up and running and THEN uninstall freegee, reinstall it, and choose clockworkmod as my reovery?
maybe is trwp just failing to load? what are you guys using?
{guide} soft-brick fix
Happened to myself as well. Follow these steps from AdriVelazquez.
Fixed it in a jiffy!
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.
My issue is after I use freegee to unlock the bootloader and to put on twrp recovery
At that moment when I restart my phone won't boot into the android os or fast boot
When I try to enter fast boot by holding power and volume up I never see any text at the bottom of screen it just shows the lg logo then a compete black screen
at this point I'm unable to even enter the OS. So the only thing I can access thankfully is Download mode.
I had the same problem. The way I fixed it was to lgnpst back. Root the phone and then run freegee. Then when I entered the bootloader it did the same lg symbol black screen thing. I held the volume up and down along with power while it was at the black back lit screen for about 20 seconds till it was completely off. Then I plugged it into my computer or you can use a charger to. Wait a few seconds and a battery animation should show up. Leave it on charge for a few minutes and then take it off and turn it on and you should be good to go. I can't guarantee it is going to work but it worked for me and I found it just by trying different things. I also read about someone else mentioning what I did in another soft brick post. I also read that shelnut2 has a special freegee version that you can only get from him. You can try him in irc. I read he dose not want it posted because it could permanently brick the phone.
-Frank
yeah... this is exact same problem that I had before..
You nees to go optimus g IRC channel and talk to shelnutt2 that you are having problem with unlocking bootloader. He will help you nicely cause he is super nice!
irc: http://webchat.freenode.net
channel: #lg-optimus-g
He told me it is very rare issue but I can tell there are several people having this issue now..
Sent from my LG-LS970 using xda app-developers app
issue resolved!
Shellnutt2 helped me out, i had to flash a special freegee to get everything working!
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
Hello!
I have the LG Optimus G Pro E980 AT&T version. My phone was rooted and I had TWRP recovery on it. I installed freegee from the play store, used it to unlock the phone, and had it install TWRP 2.6.0. After I unlocked it with freegee I noticed the OTA update began popping up asking me to update. I kept postponing it for 4 hours because I didn't have an option to cancel to update completely.
After not looking at my phone for a few hours I noticed it had restarted and entered TWRP recovery on its own. I attempted to reboot into the system but the phone would just enter back into recovery. I attempted to shut it off and turn it back on but once again it entered recovery.
Currently I'm not sure as to what happened or why I can't enter the regular system. I'm not sure if the phone attempted to do the OTA update and if that caused some type of problem, such as a soft brick, but currently I'm stuck and don't know what to do or how to fix this problem.
Does anyone know what happened, and how I can fix this problem?
Also, I am currently on TWRP 2.5.0, in case this information is helpful.
You could try adb reboot on your computer. Or you might just have to lgdlashtool back to stock.
http://forum.xda-developers.com/showthread.php?t=2302660
Sent from my LG-E980 using xda app-developers app
Thanks for the advice. I'll try it and let you know what happens.
Okay good luck.
Sent from my LG-E980 using xda app-developers app
In recovery open an adb shell and run the following:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/data/media/misc-bad-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
That will clear the flag set in misc to reboot to recovery and apply the update. You'll be able to reboot normally then.
Jammol: my phone wasn't recognized by adb, most likely because it's in recovery, and I attempted to install LGFlashTool but it asks me for an ID and Password so how do I get around that?
Shelnutt2: How do I enter adb shell while in recovery?
nemanja1990 said:
Jammol: my phone wasn't recognized by adb, most likely because it's in recovery, and I attempted to install LGFlashTool but it asks me for an ID and Password so how do I get around that?
Shelnutt2: How do I enter adb shell while in recovery?
Click to expand...
Click to collapse
You should use they guide madmack created just a few threads down.
http://forum.xda-developers.com/showthread.php?t=2302660
Sent from my LG-E980 using xda app-developers app
Use LG Mobile Support Tool instead
Put Optimus G Pro in Download Mode (press and hold Volume Up and Down, insert USB Cable to PC and handset)
Run LG Mobile Support Tool
Click Help => Country and Languange => Set the correct Country and Languange => OK.
Click Options => Upgrade Recovery => IMEI/ESN/MEID => OK.
Just wait till 100%, LG will flash it for you (depending on your internet connection, usually 1.7 GB will take about 2-3 hours).
I hope this might help
KDZ Updater (for F240x)
Run this attachment step by step, if LG Mobile Support Tool won't help.
Since the tutorial is for F240x, you need to find the E980 AT&T .KDZ file. The rest steps is all the same.
Thank you everyone for the help!!!!!!
I used the LG FlashTool and installed the original firmware, and everything worked perfectly
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
cjkline83 said:
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
Click to expand...
Click to collapse
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
Sent from my SPH-L900 using XDA Premium 4 mobile app
Pending Testing
jlmancuso said:
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Click to expand...
Click to collapse
Yeah, I wiped everything when I got home from work (don't know what I was thinking, really). TWRP even warned me no OS was installed, and I was like "so?". Anyway, as soon as it got stuck on the Samsung Galaxy Note II screen, I started the download of that rom you linked to. Still has 10 minutes left (big file is big). I'll come back with an update once I complete these first set of steps.
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
====================================
ADB Sideload
Since the device is not bootable, and I don't have an adapter to copy to my SD card via a usb reader, I struggled, but got the ADB Sideload function of the Android Development Toolkit to work once I upgrade to Team Win Recovery 2.7.0.0 via ODIN.
sideload log is as follows:
Code:
Updating partition details...
Full SELinux support is present.
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
UnRooted MC2 Stock Restore by blizzard412
Formatting /system and installing..
This will take a while
...Flashing temp special recovery
...Again just in case
Installing Radio...
Flashing firmware...
Flashing garwrnn & -EViL-KoNCEPTz- carrier partition fix...
You will automatically reboot to twrp to finish up...
[COLOR="Red"]E:Unable to mount '/preload'[/COLOR]
Should I be worried about the preload error?
Edit: rebooted but currently in a reboot loop without the startup sound. I'm going to let this go for about 10 minutes before I try to wipe and re-sideload? Before TouchWin rebooted it asked me if I wanted to install SU-SuperUser for root. Should I not install the root at this time?
Edit 2 THANK YOU!
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin.
Click to expand...
Click to collapse
I could not get this to flash via ODIN. The stock recovery kept loading instead
Decided to just try and move down the list.
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Click to expand...
Click to collapse
Phone is now out of reboot loop once I cleared the data and cache. Text messages immediately came in after OTA activation and PRL update. I am now running stock rooted 4.1.2 without KNOX.
Reboot into recovery
Flash your 4.4 rom
Click to expand...
Click to collapse
Might wait on that for a minute. So thankful to at least have a working device again. Thanks for your help. Would you like the bounty? Please PM me a paypal address or your preferred methods.
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Systems nominal
jlmancuso said:
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I had a rooted stock rom, replied to my texts from the day, then loaded rom manager, installed clockwork recovery. downloaded omni directly to the phone from their website, rebooted into clockwork, flashed, and things were fine. Booted into rooted kitkat 4.4.2, and now I'm flashin the gapps update to enable google services. network and wifi working fine under omni.
Can't thank you enough for helping me out of that hole from earlier.
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I flashed SuperSU in CWM and fixed that. Things are running great. Just need to see what the battery life is like now on a new rom.
Hey guys, new to the forum and am looking for some guidance here. I've had my LGOG going great with CM11 and one day I put it on the charger when the battery got down to 1%. The next morning I grabbed my phone and it was off and refused to turn on. I was able to get it on by holding volume up + power and plugging it into a charger or PC but only when it was plugged in. I replaced the battery already to rule that part out. So now i've followed this guide and everything went fine,I flashed Teenybin SBLunlockhttp://forum.xda-developers.com/showthread.php?t=2230106. Only thing is for some reason i cannot boot into recovery mode, fastboot and download mode work fine but when i choose recovery from fastboot the phone shows a google logo and a small lock on the bottom of the screen and then turns off and show's the charging icon. I've been at it for hours and cannot get into recovery to flash a new rom.
My question for yall is am I wasting my time with this? I'm still not convinced that this is not a hardware failure since nothing on the phone works unless plugged into power. Any thoughts would help a ton otherwise i'll have to just cough up the cash for a new one. Thanks in advance guys.
Nex
nextelhalo said:
Hey guys, new to the forum and am looking for some guidance here. I've had my LGOG going great with CM11 and one day I put it on the charger when the battery got down to 1%. The next morning I grabbed my phone and it was off and refused to turn on. I was able to get it on by holding volume up + power and plugging it into a charger or PC but only when it was plugged in. I replaced the battery already to rule that part out. So now i've followed this guide and everything went fine,I flashed Teenybin SBLunlockhttp://forum.xda-developers.com/showthread.php?t=2230106. Only thing is for some reason i cannot boot into recovery mode, fastboot and download mode work fine but when i choose recovery from fastboot the phone shows a google logo and a small lock on the bottom of the screen and then turns off and show's the charging icon. I've been at it for hours and cannot get into recovery to flash a new rom.
My question for yall is am I wasting my time with this? I'm still not convinced that this is not a hardware failure since nothing on the phone works unless plugged into power. Any thoughts would help a ton otherwise i'll have to just cough up the cash for a new one. Thanks in advance guys.
Nex
Click to expand...
Click to collapse
Your battery was probably fine so I would keep it around. That just seems to happen sometimes.
The recovery that teenybins installs is not CM11 compatable. So you need to install a KK recovery, or ADB sideload a Stockish ROM.
For ADB sideload to install a Stockish Rom go here. http://forum.xda-developers.com/showthread.php?p=36270473
To install a recovery through fastboot, DL it from here. http://downloads.codefi.re/shelnutt2/freegee/LG-LS970/ These are for KK
And to install it using fastboot.
fastboot erase recovery
fastboot flash recovery recovery.img
You may need to do a factory reset to get it to boot.
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Forgot to tell ya, just pull the recovery image from the zip and use it with fastboot.
engine95 said:
Your battery was probably fine so I would keep it around. That just seems to happen sometimes.
The recovery that teenybins installs is not CM11 compatable. So you need to install a KK recovery, or ADB sideload a Stockish ROM.
For ADB sideload to install a Stockish Rom go here. http://forum.xda-developers.com/showthread.php?p=36270473
To install a recovery through fastboot, DL it from here. http://downloads.codefi.re/shelnutt2/freegee/LG-LS970/ These are for KK
And to install it using fastboot.
fastboot erase recovery
fastboot flash recovery recovery.img
You may need to do a factory reset to get it to boot.
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Forgot to tell ya, just pull the recovery image from the zip and use it with fastboot.
Click to expand...
Click to collapse
Thanks for the reply, this helped me get along with ADB and SDK but i'm still not clear on it. I've got the recovery image needed and ADB running but not sure how to flash the recovery image to the phone. I tried following the guide in the link you provided but it wants you to get into recovery mode on the phone and enable ADB mode but I cant get into my recovery on the phone. Problem. Again though thanks for you help, much appreciated. This learning process brings me back to my days of modding the old Xbox.
So just thinking about your last post, did you recommend installing a stock rom first and then try to install the new recovery image? I am able to put the phone into download mode and i've used LGNPST to push a full stock ZVB rom to it, seemed to work but I didnt know if that was the right way to go and flashed the Teenybin SBL unlock again.
nextelhalo said:
Thanks for the reply, this helped me get along with ADB and SDK but i'm still not clear on it. I've got the recovery image needed and ADB running but not sure how to flash the recovery image to the phone. I tried following the guide in the link you provided but it wants you to get into recovery mode on the phone and enable ADB mode but I cant get into my recovery on the phone. Problem. Again though thanks for you help, much appreciated. This learning process brings me back to my days of modding the old Xbox.
So just thinking about your last post, did you recommend installing a stock rom first and then try to install the new recovery image? I am able to put the phone into download mode and i've used LGNPST to push a full stock ZVB rom to it, seemed to work but I didnt know if that was the right way to go and flashed the Teenybin SBL unlock again.
Click to expand...
Click to collapse
You said you had fastboot. So you can use fastboot to load the kk recovery using those commands. If unsure just google it. Lots of info on fastboot.
As for sideload that was just to get a stock ROM on your SD.
If you lgnpst zvb then your phone should boot up and needs to update to zvc before you do anything else.
But if you flashed teenybins then you should have recovery and be able to flash the kk recovery. Power+ vol up gets recovery. Dn twice on vol button, then power gets you to recovery.
Check the FAQ and root guide. All this info is in there if it's confusing.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
You said you had fastboot. So you can use fastboot to load the kk recovery using those commands. If unsure just google it. Lots of info on fastboot.
As for sideload that was just to get a stock ROM on your SD.
If you lgnpst zvb then your phone should boot up and needs to update to zvc before you do anything else.
But if you flashed teenybins then you should have recovery and be able to flash the kk recovery. Power+ vol up gets recovery. Dn twice on vol button, then power gets you to recovery.
Check the FAQ and root guide. All this info is in there if it's confusing.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got ya, so I'm making sense of it all after a bit and I have more info if it helps. I've been able to get ZVB on there (via LGNPST) and i'll update to ZV9 just in case yet no matter what i do i cannot get recovery to boot. I get into fastboot and choose Recovery ( locked and unlocked) but when i hit the power button to choose recovery I get nothing, it shuts down. I'll keep at it and give a progress report if I make any.
UPDATE: Ok so I can only access (on phone) Fastboot when i flash one of the Teenybin files. The stock ZV9 and ZVB just show me the LG logo and go back to the battery icon. So, I flashed teenybin SBL unlock again got the phone into fastboot. I opened a terminal on my PC with ADB running and my phone in Fastboot connected to my PC (LG Drivers installed). When i choose adb sideload recovery.img and it says "device not found". Still working on it but havent gotten past this yet.
Im still wondering if there is hardware failure since I flashed ZVB and the phone still will not boot up period unless it's connected to PC/charger.
Do this then. Grab the zvc bin from the root guide. That is the most current and it has the right modem. Zvb and zv9 have the wrong modem.
Also it sounds like you have stock recovery. Which you will if your using zv? bins.
Then after using zvc bin, use teeny bin. That'll get you to twrp recovery. In twrp flash the kk recovery and you should be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Do this then. Grab the zvc bin from the root guide. That is the most current and it has the right modem. Zvb and zv9 have the wrong modem.
Also it sounds like you have stock recovery. Which you will if your using zv? bins.
Then after using zvc bin, use teeny bin. That'll get you to twrp recovery. In twrp flash the kk recovery and you should be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gave it a shot, flashed ZVC and then after that did Teenybin SBL unlock and same thing. I get it into fastboot, choose recovery and then the phone show's a google logo with alittle lock on the bottom and then goes to black screen then to charging icon. :silly: I'll keep at it.
Update, a friend gave me some help and I was able to flash the recovery image you linked to me via ADB but still no change in the phone. On teenybin in fastboot, select recovery and still get the same google logo and small lock, then goes to power screen.
Haha, seems you've been down this road before. Found this while searching around, I'm giong to try the steps in the last two post's of the thread. Thanks for the help Engine.
http://forum.xda-developers.com/showthread.php?t=2535874&page=3
UPDATE: unfortunately no change, left the phone on the charger for a few hours but still stuck with no usable recovery mode and phone only responds while plugged in. Think i'll chalk this up to some type of hardware failure.
Will your phone even boot to the stock ROM? If it does, try installing Quickboot from the PlayStore. See if that'll get you into recovery.
I can't remember if it's in the root guide or the FAQ, but I posted another option for a battery issue like yours. Try it and see if it'll do more.
There's some commands that'll wipe through adb. I'll see if I can find them.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Wont boot into stock Rom yet, man i wish i was that far along and i'd be done probably. Thanks for looking at it for me.
nextelhalo said:
Wont boot into stock Rom yet, man i wish i was that far along and i'd be done probably. Thanks for looking at it for me.
Click to expand...
Click to collapse
There's something we're missing here, so lets start at the beginning
LGNPST ZVC again. This SHOULD get you going.
Now you will have stock recovery. To enter stock recovery, press vol down+power The LG logo will come on, then the capacitive lights. Immediately let go when the capacitive lights turn on. It takes a few seconds to work. And maybe a few tries to get it.
IF that all happens, then in stock recovery, do a Factory reset. IT WILL WIPE YOUR SD/INTERNAL STORAGE!!
Now your phone should boot up to stock ROM.
If that doesn't work, go to ADB and issue these:
adb shell
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/cache"
adb shell
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/userdata"
These will zero out /cache and /data
Reboot your phone and it should boot up
If not, you may need to LGNPST ZVC one more time and you should be good to go
If no dice again, you might need to try a battery pull, which you should know seeing as how you replaced the battery.
That's about all I got....you could also try getting on the irc and see if someone there has more idea's
Good luck! :fingers-crossed:
Edit: I forgot to tell you that in Stock recovery, use the capacitive menu key to select. The Power button doesn't do it in Stock recovery. Menu is the bottom right of the display and I don't think it's lit, but I'm not sure.
Thank you sir, i'll give this a shot tonight when i get back home. I'll keep my fingers crossed but i've located another LGOG on Craigslist for 80$, might not be able to pass up that deal.
Update: still no go, I agree there is something missing here. When i flash ZVC all goes like it should but the phone still just flatout wont do anything unless on external power. I went ahead and did a battery pull but no change. It's like we're doing everything correctly here but it wont let us past fastboot or download mode. Either it's software or this thing may have fried. I'm going to bring it to a friend here in town and see what he can do, he's a guru in this department but I wanted to figure this out on my own. If we get this back up and running I will for sure update this thread, hopefully it can help some folks out there. Thanks again for the help Engine, I wont give up until i know exactly what happened and i'll pass it along.