- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
PSA for LG G3 owners (update---FIXED!!!)
Posted on 11/19/14 at 11:19 pm
Posted on 11/19/14 at 11:19 pm
UPDATE---
Thanks for the encouragement and advice everyone. Was able to return to stock as soon as I got a PC to run the flash tool.
Just thought I would post this here so nobody ends up in the shitty situation I have going on, if it helps someone Ill be very happy
So the day I got my G3 I ran Towelroot on it and installed TWRP recovery. I never did anything else with root, and had honestly forgotten I had run the root program.
This week, an ATT LG update got pushed OTA, and me not even thinking about root went ahead and installed it. Once the phone rebooted, it went straight to TWRP recovery, and now has no OS installed so is constantly stuck in recovery.
I have found some threads on XDA regarding a Flash tool to return to stock firmware, but have not been able to run it yet as I only have a macbook, and it is PC only.
Im just hoping that I can get it figured out, and don't end up with a totally bricked brand new phone.
Thanks for the encouragement and advice everyone. Was able to return to stock as soon as I got a PC to run the flash tool.
Just thought I would post this here so nobody ends up in the shitty situation I have going on, if it helps someone Ill be very happy
So the day I got my G3 I ran Towelroot on it and installed TWRP recovery. I never did anything else with root, and had honestly forgotten I had run the root program.
This week, an ATT LG update got pushed OTA, and me not even thinking about root went ahead and installed it. Once the phone rebooted, it went straight to TWRP recovery, and now has no OS installed so is constantly stuck in recovery.
I have found some threads on XDA regarding a Flash tool to return to stock firmware, but have not been able to run it yet as I only have a macbook, and it is PC only.
Im just hoping that I can get it figured out, and don't end up with a totally bricked brand new phone.
This post was edited on 11/28/14 at 9:44 pm
3
Posted on 11/19/14 at 11:44 pm to J311slx
quote:
Im just hoping that I can get it figured out, and don't end up with a totally bricked brand new phone
It's not possible to brick an Android phone, especially if you can still get to recovery.
Your problem is having a Mac and not a PC, otherwise flashing the stock image in LG Flash Tool would take a matter of minutes.
This post was edited on 11/19/14 at 11:50 pm
Posted on 11/20/14 at 2:27 am to UltimateHog
quote:
It's not possible to brick an Android phone, especially if you can still get to recovery
Yea...my bad I worded that wrong, Just worried about being stuck in an infinite boot loop to recovery. I will be trying it on my in laws PC when I go down for thanksgiving, just pray everything works smoothly with the drivers and flash tool from the steps I saw. shite always gave me trouble when I would us ODIN on my old Sammie phones. I tried getting a copy of Windows to use in boot camp, but had issues with the ISO file and not worth buying a legit copy just for this.
Im going to see if I can find someone else's PC to use before next week. The suspense is killing me, and not doing well with using this shitty go phone in the meantime. Feel totally disconnected from everything.
Thanks for the encouragement though!
This post was edited on 11/20/14 at 2:28 am
Posted on 11/20/14 at 2:44 am to J311slx
Yeah I was about to say, if you can get to recovery you can fix it, boot loop or brick, whatever the case may be.
This post was edited on 11/20/14 at 2:55 am
Posted on 11/20/14 at 6:48 am to J311slx
What ultimate said. Damn near impossible to brick an android. Is definitely easier to reset it if you have a PC. Would running a win7 VM on your Mac work?
Might be handy to have a VM you can spin up when these situations arise.
Might be handy to have a VM you can spin up when these situations arise.
Posted on 11/20/14 at 7:17 am to J311slx
Lesson number one. First thing to do in twrp is make a backup. I'm assuming you did not do this. Woulda been cooler if you did. Still an easy fix. Also, you can turn auto updates off in the hidden menu using your phones dialer keypad.
Dial 3845#*850*
Navigate to WLAN test
Select OTA setting
Select DISABLE
Reboot
Profit
No more OTA auto updates
Dial 3845#*850*
Navigate to WLAN test
Select OTA setting
Select DISABLE
Reboot
Profit
No more OTA auto updates
Posted on 11/20/14 at 3:38 pm to whodatfan
quote:
whodatfan
Sweet thanks for that info on disabling, need that for sure.
AS far as backup I am confident I made one, but know that I never uploaded to my computer to get it off the card, and now I dont have it in the back up menu
Posted on 11/20/14 at 3:43 pm to tigerfan4793
quote:
tigerfan4793
Did you already return to stock? Cause there is a really simple fix for it. Mine was doing the same thing. Just follow these instructions and it will get your phone booting up like normal again.
Hey no I still have not had any luck, but havent tried on a PC to use the flash tool yet because I have not had access to one.
I tried the method you posted the other day without success, so I am thinking this is the problem
quote:
If you are still booting into TWRP/CWM then you may have accidentally flashed the custom recovery img to the boot partition slot instead of the recovery partition slot. Reflash the rom in TWRP/CWM which should fix the boot.img... or download the required boot.img, place on root of internal storage ( /sdcard/ ) and flash the boot.img in TWRP/CWM...
The problem is whenever I try transferring a ROM via MTP, it seems to be too big. Anything over about 400MB I get a message that it could not transfer, so cant try reflashing a full ROM
Posted on 11/21/14 at 6:49 am to J311slx
Android is a little strange at first to understand the fastboot/adb driver stuff and flashing the system but it's actually incredibly easy once you've done it a couple times.
Don't give up.. Read read read XDA and make sure you understand what's going on.
In fact.. I would strongly recommend once you fix it to reflash it a few more times before you set the phone up just to get more comfortable.
Seriously. Feeling confident in the process after you had such a bad experience is critical because eventually you'll want to change something down the road.
We're here to help.
Don't give up.. Read read read XDA and make sure you understand what's going on.
In fact.. I would strongly recommend once you fix it to reflash it a few more times before you set the phone up just to get more comfortable.
Seriously. Feeling confident in the process after you had such a bad experience is critical because eventually you'll want to change something down the road.
We're here to help.
Posted on 11/21/14 at 9:21 am to CAD703X
quote:
Android is a little strange at first to understand the fastboot/adb driver stuff and flashing the system but it's actually incredibly easy once you've done it a couple times.
Don't give up.. Read read read XDA and make sure you understand what's going on.
In fact.. I would strongly recommend once you fix it to reflash it a few more times before you set the phone up just to get more comfortable.
Seriously. Feeling confident in the process after you had such a bad experience is critical because eventually you'll want to change something down the road.
We're here to help.
This is 100% correct.
XDA can be very intimidating at first, especially due to their OT-style love of acronyms. I literally had to google almost every one to find out what the hell they were talking about. On the other hand, the people there are extremely willing to help if you post some questions. I switched to Android about a year ago, and now I am actually helping people in the galaxy S4 threads.
And the golden rule is always make a back-up because it is so easy just to flash the back up if you screw something up, and then presto its like nothing ever happened.
Posted on 11/21/14 at 9:33 am to guedeaux
quote:
And the golden rule is always make a back-up because it is so easy just to flash the back up if you screw something up, and then presto its like nothing ever happened.
This can't be stressed enough.
Posted on 11/22/14 at 11:14 pm to whodatfan
quote:
whodatfan
Quick question...my wife has a G3 as well. Could I potentially back hers up and then transfer the backup to my phone and use that to start fresh?
Posted on 11/23/14 at 1:20 am to J311slx
quote:
The problem is whenever I try transferring a ROM via MTP, it seems to be too big. Anything over about 400MB I get a message that it could not transfer, so cant try reflashing a full ROM
Are you 100% sure it is using MTP? Because Macs do not support MTP natively and you need to use an app like DriveDroid to disable the phone from automatically changing the USB Mode and force it to use MTP.
This post was edited on 11/23/14 at 1:21 am
Posted on 11/23/14 at 8:40 am to J311slx
quote:
Quick question...my wife has a G3 as well. Could I potentially back hers up and then transfer the backup to my phone and use that to start fresh?
While you could physically move the backup file from her phone to yours, I'm not sure you can restore another phones backup. Not sure what all information is contained in the backup. I'm doubtful it would work.
Posted on 11/23/14 at 5:41 pm to UltimateHog
quote:
ultimatehog
I'll have to check when I get home. I know it said it was MTP on the TWRP screen. Will check and report back. Thanks
Posted on 11/23/14 at 11:17 pm to UltimateHog
quote:
UltimateHog
It looks like MTP is enabled in the TWRP menu, but it is showing Android File Transfer on my macbook...it does not show up at all if I click on disable MTP...not sure what else to try
It is showing the following when trying to move a ROM over via ADB on the macbook
Last login: Sun Nov 23 23:12:08 on ttys000
FurnsMBP2:~ j311slx1986$ cd downloads
FurnsMBP2:downloads j311slx1986$ cd fastboot
FurnsMBP2:fastboot j311slx1986$ chmod 755 *
FurnsMBP2:fastboot j311slx1986$ ./adb-mac devices
List of devices attached
LGD8508fef8db6 sideload
FurnsMBP2:fastboot j311slx1986$ ./adb-mac push BIN_LGD850AT-01-V10d-310-410-JUN-19-2014-0.zip /sdcard/.
error: closed
FurnsMBP2:fastboot j311slx1986$
Using the ADB sideload feature in TWRP recovery, it stays on the screen that says "Starting ADB sideload feature", but obviously is connected as it is showing the device
Thanks for any input
This post was edited on 11/23/14 at 11:22 pm
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News