Database Users

Help trying to get back into custom recovery

I did research for this for a couple of hours but didn't find anything too helpful besides flashing back to stock. I also saw I could install the TWRP img file by the command line but that makes me a little nervous for the brick warnings posted.
I have the Goldeneye rom on my phone and I had TWRP 2.5.0.2 and everything was working great. I also updated the Modem to the MF3 one. I flashed TWRP up to 2.6 and loki-doki and everything seemed to go OK until I rebooted the phone.
I rebooted the phone and got the error of System software not authorized by ATT has been found on your phone and the SECURE FAIL: KERNEL message at the top.
I am now unable to boot into recovery with the buttons or using the reboot menu from the Goldeneye rom. Every time I try to reboot it goes to the error message above.
Now I am able to have the phone boot up fully if I go into download mode and then press the volume down key to cancel/restart the phone and then it will boot up with out issue. Any time I reboot though with out going into download mode I get the secure kernel error.
Is there a way to recover the device without going through ODIN and reflashing it back to stock? Also, my baseband shows MF3 now since I flashed the modem, is that going to cause any issues?
Any advice would be appreciated. Thanks

Can you try reinstalling the twrp recovery through goomanager when you get it to boot.. Then retrying to get into recovery?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta

bump
Sent from my SAMSUNG-SGH-I337 using xda premium

rcklss1 said:
Can you try reinstalling the twrp recovery through goomanager when you get it to boot.. Then retrying to get into recovery?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I go to install OpenRecoveyScript in goomanager and it tells me that no recoveries were found for my device

lyrad12 said:
bump
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Why are you bumping this--
---------- Post added at 11:52 PM ---------- Previous post was at 11:47 PM ----------
dibe said:
I go to install OpenRecoveyScript in goomanager and it tells me that no recoveries were found for my device
Click to expand...
Click to collapse
Why not Odin
I haven't looked for awhile, but if you example of command to put recovery on phone by adb, try it. If you have the command line from a dev thread then just copy/paste the line. No chance of typing error. Still double check all. And any bu's you can do prior, do them and put copy on pc. Know you can't nandroid, but maybe MyBackUp Pro.

I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin

dibe said:
I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin
Click to expand...
Click to collapse
Good Luck--:good:

dibe said:
I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin
Click to expand...
Click to collapse
Lol, odin is much easier.
Sent from my HTC One X using xda premium

rugmankc said:
Good Luck--:good:
Click to expand...
Click to collapse
Thanks.
I installed the TWRP 2.5.0.2 img file using Android Terminal Emulator and the command line. Everything is working fine now with the phone and I didn't have to reflash or lose any data.
Thanks for everyone's help.

convict_moody said:
Lol, odin is much easier.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Odin is last resort for me since you lose everything--
---------- Post added at 02:47 AM ---------- Previous post was at 02:46 AM ----------
dibe said:
Thanks.
I installed the TWRP 2.5.0.2 img file using Android Terminal Emulator and the command line. Everything is working fine now with the phone and I didn't have to reflash or lose any data.
Thanks for everyone's help.
Click to expand...
Click to collapse
Glad you got it--:good:

rugmankc said:
Odin is last resort for me since you lose everything--
I would have to fully agree with you there. I am very glad installing the img worked.
Click to expand...
Click to collapse

[Q] There is no SU binary installed and Super su cannot isntall it

hi i bought my phone yesterday and rooted today using this method http://nexus4root.com/nexus-4-root/how-to-root-nexus-4-windowsmac-osxlinuxubuntu/
and as for 4.3.3 i updated before root i downlaoded su 1.4 verison everything went fine untill i opened super su and i got this! There is no SU binary installed and Super su cannot isntall it
plz heeelp me so angry so daamn!!!
i tryed downloading the cwm zip 1.65 ver from xda thread and flashed it! still same i tried twice still same!!! i did the update after restoring backup!
also after that my psiphon app gives force close everytime i stop it!!!

plz help

i disabled supersu app and got superuser and i went to udpate binary i got this(!!!!
downloading manifest..okay
parsing manifest ok
lastes ver 3.1.1
isntalled ver 1.61 super su fix database ok
unpacking sutools ok
checking current isntall patch /system/xbin/su
downloading new binary ok
gaining root accses faild
try agin button

whit su enabled this time it said me something and cool do it again buttom!!! but still super su error
each re enabling i can do this this time gaining rott accses ...
remoutnting /system as rw.. 1.61 super su copying su to /system ok

http://download.chainfire.eu/supersu
download this supersu file(latest, 1.65), then flash in recovery.what you were flashing is out of date.

already did 3 times didnt work! still same

to amke sure file is is also 1008kb

simms22 said:
http://download.chainfire.eu/supersu
download this supersu file(latest, 1.65), then flash in recovery.what you were flashing is out of date.
Click to expand...
Click to collapse
dude, your my hero. I was having the same problem... was just about at the point where I flashed it back to stock.

burnski said:
dude, your my hero. I was having the same problem... was just about at the point where I flashed it back to stock.
Click to expand...
Click to collapse
lucky u

simms22 said:
http://download.chainfire.eu/supersu
download this supersu file(latest, 1.65), then flash in recovery.what you were flashing is out of date.
Click to expand...
Click to collapse
just quenot to makee sure u get notfication i already did 3 times
btw i rmmber i had exactly same problem on my s4 wich made me raage angryy! lol i guess it got fixed by updating the supersu file but i did same nothing happened atm

kamranhaghighi said:
just quenot to makee sure u get notfication i already did 3 times
btw i rmmber i had exactly same problem on my s4 wich made me raage angryy! lol i guess it got fixed by updating the supersu file but i did same nothing happened atm
Click to expand...
Click to collapse
after flashing it, open the supersu app.. does it ask you to update the binaries? if so press yes.

simms22 said:
after flashing it, open the supersu app.. does it ask you to update the binaries? if so press yes.
Click to expand...
Click to collapse
nope just the error

kamranhaghighi said:
nope just the error
Click to expand...
Click to collapse
to be exact there is no su binary isntalled and supersu cannot isntall it theres a problem if u jsut upgraded to andorid 4.3.3 u need to manually re root - consult the reveant forums for your device

kamranhaghighi said:
just quenot to makee sure u get notfication i already did 3 times
btw i rmmber i had exactly same problem on my s4 wich made me raage angryy! lol i guess it got fixed by updating the supersu file but i did same nothing happened atm
Click to expand...
Click to collapse
have you tried a factory reset?
if its still not working, factory reset(wipe user data only in recovery), then flash the supersu zip again. btw, what rom are you using?

jsut bought it yester day 4.3.3 fully stock doing it

simms22 said:
have you tried a factory reset?
if its still not working, factory reset(wipe user data only in recovery), then flash the supersu zip again. btw, what rom are you using?
Click to expand...
Click to collapse
factory reset in recovery or andorid settings?

kamranhaghighi said:
nope just the error
Click to expand...
Click to collapse
try starting over.. flash the factory img with fastboot, flash a custom recovery(i use twrp recovery) with fastboot, then flash the supersu i linked in your recovery.
---------- Post added at 04:25 PM ---------- Previous post was at 04:25 PM ----------
kamranhaghighi said:
factory reset in recovery or andorid settings?
Click to expand...
Click to collapse
recovery

simms22 said:
try starting over.. flash the factory img with fastboot, flash a custom recovery(i use twrp recovery) with fastboot, then flash the supersu i linked in your recovery.
---------- Post added at 04:25 PM ---------- Previous post was at 04:25 PM ----------
recovery
Click to expand...
Click to collapse
flash factory img? what is it? can u give me i did another way jsut adb to flash recovery in Ubuntu and flashed super su .zip

kamranhaghighi said:
flash factory img? what is it? can u give me i did another way jsut adb to flash recovery in Ubuntu and flashed super su .zip
Click to expand...
Click to collapse
oh ok i udnerstand i alrady got cwm i did fatory reset btw if didnt work i flash over recovery and do allll again:| waiting for boot

did factory and stuff this time frist a massage apeard the in top of that massage the error apeard a 3 option question!

Help can't put rom on phone in TWRP, cant boot

Hello I was going to flash a rom from stock firmware with TWRP recovery installed when I accidentally wiped the system partition as well so there is now no rom on the internal storage and i cannot boot back into the normal firmware cause it just hangs at the LG logo on startup. I tried a USB OTG device in TWRP but it is not being detected and I don't know how to use the phone in mass storage mode inside TWRP. :crying:
Help would be much appreciated!

bump

Have you tried adb sideload? I did the same, wiped everything, system and internal , bacups and all. I managed to sideload a flashable rom, flashed it and managed to boot up. So: ADB Sideload through twrp is your answer.
Sent from my LG-D802 using XDA Premium 4 mobile app

KapteinKing said:
Have you tried adb sideload? I did the same, wiped everything, system and internal , bacups and all. I managed to sideload a flashable rom, flashed it and managed to boot up. So: ADB Sideload through twrp is your answer.
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Was about to try sideload but then just used the flashtool and went back to stock. Thanks anyway!

KiLLa007 said:
Was about to try sideload but then just used the flashtool and went back to stock. Thanks anyway!
Click to expand...
Click to collapse
I'm stuck with the same problem didn't make a back up. I have a ROM but it won't flash because of 12B OTA on G2. So i'm stuck on twrp. Can you send me a link to get flashtool? What else do I need beside flashtool to go back to stock? Thank you

its not system thats the problem, you wiped internal..
adb push the rom to internal. many accurate how to do that with search. dont know top of head
Sent from my LG-D802 using xda app-developers app

Well if you do end up fixing it upgrade to TWRP 2.6.3.4 because it has OTG support!
Sent from my LG-VS980 using xda app-developers app

I'm in the same boat here except I've already tried adb sideload with twrp 2.6.3.3 and it returns an error "cannot read rom.zip" I've tried 3 different zips, many combinations of renaming the zip files. My machine is set to always show file extensions. I've also tried both ways of trying to flash back to stock in download mode. One of them just hangs at BIN CRC check the other will get to 49% and error out. Any suggestions?
Sent from my Galaxy Nexus using xda app-developers app

files and carrier
simonsez2die said:
I'm in the same boat here except I've already tried adb sideload with twrp 2.6.3.3 and it returns an error "cannot read rom.zip" I've tried 3 different zips, many combinations of renaming the zip files. My machine is set to always show file extensions. I've also tried both ways of trying to flash back to stock in download mode. One of them just hangs at BIN CRC check the other will get to 49% and error out. Any suggestions?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
what carrier and flies are you using? What com port is your G2 using? Have you tried using the LG mobile support tool?
I have tried but cant brick this phone, so many ways to communicate

geosnipe said:
what carrier and flies are you using? What com port is your G2 using? Have you tried using the LG mobile support tool?
I have tried but cant brick this phone, so many ways to communicate
Click to expand...
Click to collapse
VS980 Verizon. I've tried Lg flashtool with "LGVS980_20130902_LGFLASHv151.dll"
and VS98010B_13.tot. on com port 41. This one hangs at BIN CRC Check for hours. Won't go any further. I've also tried the uptest method found here in the forums with the files that are in the OP. It gets to 49% and stops and tells me to retry. When I retry it will always stop at 49%\
I can get into download mode and TWRP .While in TWRP, adb recognizes my device and shows recovery next to it. When I go to adb sideload and type adb devices again it will show that I'm in sideload mode but no files will transfer. It just returns error cannot read filename.extension. I've to sideload all kinds of files with different extension types and it always returns the same thing.
---------- Post added at 11:41 AM ---------- Previous post was at 11:27 AM ----------
I just remembered that I had a backup made from a week or 2 ago when I was using cwm recovery. Which isnt recognized in twrp. I didn't loose all of my sdcard content with all this. I was just a moron and forgot to make a twrp backup before wiping my system. And the only rom I have on my sdcard aborts about halfway through.
Sent from my Galaxy Nexus using xda app-developers app

Ok...so I was able to adb push a file to my sdcard using "adb push filename.zip /sdcard/filename.zip. It returned the size and time it took to transfer. But adb push ROM.zip /sdcard/ROM.zip gives me nothing and seems as tho it may have froze up the command prompt. GRR!
---------- Post added at 12:19 PM ---------- Previous post was at 11:52 AM ----------
Got it...thanks anyway.

simonsez2die said:
VS980 Verizon. I've tried Lg flashtool with "LGVS980_20130902_LGFLASHv151.dll"
and VS98010B_13.tot. on com port 41. This one hangs at BIN CRC Check for hours. Won't go any further. I've also tried the uptest method found here in the forums with the files that are in the OP. It gets to 49% and stops and tells me to retry. When I retry it will always stop at 49%\
I can get into download mode and TWRP .While in TWRP, adb recognizes my device and shows recovery next to it. When I go to adb sideload and type adb devices again it will show that I'm in sideload mode but no files will transfer. It just returns error cannot read filename.extension. I've to sideload all kinds of files with different extension types and it always returns the same thing.
---------- Post added at 11:41 AM ---------- Previous post was at 11:27 AM ----------
I just remembered that I had a backup made from a week or 2 ago when I was using cwm recovery. Which isnt recognized in twrp. I didn't loose all of my sdcard content with all this. I was just a moron and forgot to make a twrp backup before wiping my system. And the only rom I have on my sdcard aborts about halfway through.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
The LG Flash Tool and Mobile Support Tool are 2 different utilities for the phone.
Glad to hear you are back up and running!

geosnipe said:
The LG Flash Tool and Mobile Support Tool are 2 different utilities for the phone.
Glad to hear you are back up and running!
Click to expand...
Click to collapse
I actually tried both utilities but both resulted in error. I ended up getting it with "adb push ROM.zip /sdcard/ROM.zip" . It took a really long time, I ended up just trying one last time and left it alone for about 10 mins. When I came back to it, it showed the size of file and time it took to push. I figured I'd post all of this on the off chance it may help someone who has a Custom recovery but no backup or Rom zips to flash on the device.

simonsez2die said:
I actually tried both utilities but both resulted in error. I ended up getting it with "adb push ROM.zip /sdcard/ROM.zip" . It took a really long time, I ended up just trying one last time and left it alone for about 10 mins. When I came back to it, it showed the size of file and time it took to push. I figured I'd post all of this on the off chance it may help someone who has a Custom recovery but no backup or Rom zips to flash on the device.
Click to expand...
Click to collapse
Man you are a life saver. Thanks for coming back and posting your solution for this problem. I had the exact same issue and after hours of trying to install different "rom.zip" files with the same "cannot read rom.zip" error, this finally worked.
I cannot stress enough, how helpful it is when someone like you finds an answer to a problem and takes the time to come back and post the solution.
Thanks again!!!

[Q] Why is this so hard to install recovery!

Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?

paryguy said:
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
Click to expand...
Click to collapse
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud

TWRP
Follow the install instructions for TWRP 2.6.3.2. Then after you've confirmed you can boot the OS from the recovery, place the 2.6.3.3 on the root of your SD. Reboot into recovery and flash 2.6.3.3. Reboot into recovery again and you'll be good to go.
Version 2.6.3.2 won't flash 4.4 ROMs but 2.6.3.3 will flash 4.2 (I'm assuming), 4.3, and 4.4.

Download FreeGee app from the play store and install TWRP recovery from it. It was the only way I could install it on my LG G2.

So many
simon_lefisch said:
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.

paryguy said:
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
Click to expand...
Click to collapse
What build number are you on?
Sent from chdhsheh fhhdud

vnrse Theologisch
simon_lefisch said:
What build number are you on?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I used RussGJohnson solution and it worked in a matter of seconds. Now I'm stuck though. I wiped everything and can boot into TWRP but I have no ability to sideload anything. I have all the latest LG drivers, even the lastest android sdk drivers, nothing is working. If I boot up normally the LG logo comes up and just sits there.
I can boot into recovery using the whole volume down + power button combo but then when I go to sideload my computer isn't seeing the device. I'm on a Win 8 machine using the stock cable. I've tried both USB 2 and 3 ports

It's done
Using RussGJohnson's suggestion worked great.
The issue I had with being unable to sideload a ROM wasn't resolved but I just used my Mac to do it instead. That worked just fine. Win8 couldn't recognize the device while in recovery. Go figure.

free gee very fast

Use Flashify u n00b.

TWRP fails to flash rom

I was running the CM 10.2 Stable on my LG G2. I downloaded the CM 11 snapshot and 4.4 gapps in my phone.
Then went to TWRP recovery and wiped the dalvic, cache, data and system. Then went forward to install and selected the CM11 rom and gapps zip files. The flashing starts but it fails after about 10 seconds.
Here is the log:
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/rom/cm-11.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signatures...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/rom/cm-11.zip'
Error flashing zip '/sdcard/rom/cm-11.zip'
Updating partition details...
Please help me. Thank You
Note:I have TWRP 2.6.3.2 installed.My rom before starting this process was CM 10.2 Stable

in_core said:
I was running the CM 10.2 Stable on my LG G2. I downloaded the CM 11 snapshot and 4.4 gapps in my phone.
Then went to TWRP recovery and wiped the dalvic, cache, data and system. Then went forward to install and selected the CM11 rom and gapps zip files. The flashing starts but it fails after about 10 seconds.
Here is the log:
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/rom/cm-11.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signatures...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/rom/cm-11.zip'
Error flashing zip '/sdcard/rom/cm-11.zip'
Updating partition details...
Please help me. Thank You
Note:I have TWRP 2.6.3.2 installed.My rom before starting this process was CM 10.2 Stable
Click to expand...
Click to collapse
It looks a bit like a bad download. Did you check MD5 after downloading?

doom_71 said:
It looks a bit like a bad download. Did you check MD5 after downloading?
Click to expand...
Click to collapse
Sorry I am new to these stuffs. How to check the MD5 after downloading? Please explain

doom_71 said:
It looks a bit like a bad download. Did you check MD5 after downloading?
Click to expand...
Click to collapse
OK i found out hoe to check MD5. Yes it matches. So no error in the download.

TWRP 2.6.3.2 can't flash 4.4 ROMS. You need to update to 2.6.3.3 or 2.6.3.4 for that. You should be able to search to find a link, because I don't think there's a dedicated topic to anything above 2.6.3.2.

symphonic-volenska said:
TWRP 2.6.3.2 can't flash 4.4 ROMS. You need to update to 2.6.3.3 or 2.6.3.4 for that. You should be able to search to find a link, because I don't think there's a dedicated topic to anything above 2.6.3.2.
Click to expand...
Click to collapse
The thing is i am stuck at TWRP as I wiped the davic, cache, system and data. Can i install the Latest version from the TRWP recovery itself?
If YES then how can i copy the latest version files into my phone?
If NO then what should i do? I am stuck in the TWRP after all.

Do you have a backup? I would think the easiest way would be to restore and then download and flash.
Or just flash an old ROM if you have one on the phone.
I'm not too experienced otherwise, but i think download mode would work? I haven't actually used that before though.
Sent from my LG-LS980 using xda app-developers app

in_core said:
The thing is i am stuck at TWRP as I wiped the davic, cache, system and data. Can i install the Latest version from the TRWP recovery itself?
If YES then how can i copy the latest version files into my phone?
If NO then what should i do? I am stuck in the TWRP after all.
Click to expand...
Click to collapse
I think you have two choices.
1. flash back the CM10.2 and start from there
2. flash new recovery image via adb then flash new firmware

symphonic-volenska said:
Do you have a backup? I would think the easiest way would be to restore and then download and flash.
Or just flash an old ROM if you have one on the phone.
I'm not too experienced otherwise, but i think download mode would work? I haven't actually used that before though.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately i dont have anything other than the CM11 file in my phone's memory.
Any idea how i can copy files from my PC to phone while stuck in recovery mode?

Do you have any experience with ADB? As Votinh brought up, you can push the new recovery image over through the shell on the computer. There's tutorials for pushing a recovery through ADB on here somewhere also.
Sent from my LG-LS980 using xda app-developers app

symphonic-volenska said:
Do you have any experience with ADB? As Votinh brought up, you can push the new recovery image over through the shell on the computer. There's tutorials for pushing a recovery through ADB on here somewhere also.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
I used the adb when I first installed the custom recovery. I followed forum instructions/you tube video to do that. They require the phone to be in a working state. But as my phone now can only go to the currently installed recovery (TWRP). I am not sure how to do anything that needs to be done.
Please help me

How do I copy files to my internal storage when my phone is stuck in recovery mode? When i connect my phone to PC the PC does not recognize it.
So how can i copy any files either a new custom recovery or an older rom?

in_core said:
How do I copy files to my internal storage when my phone is stuck in recovery mode? When i connect my phone to PC the PC does not recognize it.
So how can i copy any files either a new custom recovery or an older rom?
Click to expand...
Click to collapse
uninstall lg drivers and download and install PdaNet to your pc and install the drivers for an android device when it asks.
now plug in your phone and pdanet will install the drivers and you will then you should be able to access your phone via adb
---------- Post added at 10:57 AM ---------- Previous post was at 10:50 AM ----------
this happend to me with the OTA, even after flashing a stock rom i was still stuck unitl i followed these instructions
http://forum.xda-developers.com/showthread.php?t=2451696

rawb123456 said:
uninstall lg drivers and download and install PdaNet to your pc and install the drivers for an android device when it asks.
now plug in your phone and pdanet will install the drivers and you will then you should be able to access your phone via adb
---------- Post added at 10:57 AM ---------- Previous post was at 10:50 AM ----------
this happend to me with the OTA, even after flashing a stock rom i was still stuck unitl i followed these instructions
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Ok i have managed to do the stuffs and can now copy files to my phone. My installed TWRP version is 2.3.6.2. I downloaded the 2.3.6.3 and tried installing it from recovery but it shows some error. Could anyone give me a file of recovery that can be used? either TWRP or CWM.
Thank you

You don't have to flash a new recovery with adb. Just find the image file for your phone then download an app called flashify. It takes less than a sec to flash then your done.
Sent from my LG-LS980 using Tapatalk
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
http://forum.xda-developers.com/showthread.php?t=2469995
Sent from my LG-LS980 using Tapatalk

hellot1M said:
You don't have to flash a new recovery with adb. Just find the image file for your phone then download an app called flashify. It takes less than a sec to flash then your done.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I have somehow managed to brick my phone.
I made a separate thread:
http://forum.xda-developers.com/showthread.php?t=2632892
Please look into it and share your thoughts about what to do.
Thank You

hi all,
I get this too when flashing my first rom on tab3
ive got latest twrp on it and have rooted it ... I think :/ although twrp says it has root issues - actual apps are ok with root though
restored from back up ok
odd :/
anyone sorted this?
thanks
dan