So like many, I took a stupid OTA on one of the roms (CleanROM) and got stuck in recovery boot loop. I tried all the methods I could find on xda but none worked. I then started reading all the way through threads and found the fix... wish they would update the original posts... so for those in this same predicament, here is how I fixed it so you don't have to read through everything.
so the FULL ADB method code looks like this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
exit
adb reboot
I of course take no responsibility if this doesn't work for you. I got the original and extra code in this thread http://forum.xda-developers.com/showthread.php?t=2451696 and all true credit goes to them. I'm simply putting ALL the information in the one original post of this thread in hopes of saving someone else a lot of time trying to find that extra line of code burried in the other thread.
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
DooLocsta said:
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
Click to expand...
Click to collapse
I personally switched to a ROM that was already based on the update. I haven't looked but I'm sure there is a way to turn them off.
DooLocsta said:
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
Click to expand...
Click to collapse
You can get rid of the notification by freezing the "Software Updater" app in Titanium Backup.
kuwlij said:
You can get rid of the notification by freezing the "Software Updater" app in Titanium Backup.
Click to expand...
Click to collapse
tried this didn't work? even wiped the data still have the icon.... Any other suggestions?
vegasdavek said:
I personally switched to a ROM that was already based on the update. I haven't looked but I'm sure there is a way to turn them off.
Click to expand...
Click to collapse
What ROM did you end up going with? Each time I try a ROM the WiFi calling does not work and in my area I have to use that more than I would like.
This is almost an exact repost of the other bootloop fix.
TheNetwork said:
This is almost an exact repost of the other bootloop fix.
Click to expand...
Click to collapse
Yup. This is a repost only. I have seen couple of Guides here in G2's thread.
Sent from my LG-D802 using XDA Premium 4 mobile app
TheNetwork said:
This is almost an exact repost of the other bootloop fix.
Click to expand...
Click to collapse
Agreed, which is why I said that the other thread is where I found the fix... but the original post in that thread didn't actually offer a fix when I got stuck in the loop. As a result I spent a lot of time trying other attempts to fix as well as combing through threads before finally finding the extra line of code to make it work.
So I posted a new thread so that someone else doesn't have to waste their time like I did trying to find a fix.
DooLocsta said:
What ROM did you end up going with? Each time I try a ROM the WiFi calling does not work and in my area I have to use that more than I would like.
Click to expand...
Click to collapse
I'm using this rom currently: http://forum.xda-developers.com/showthread.php?t=2595586 as I too need the WiFi Calling feature.
If you are on a T-mobile based rom, the way to 'freeze' the update is different than the others.
T-mobile roms use 'Google Services Framework' for the update, and obviously you can't freeze that app.
So, what you do is d/l a program called 'Autorun Manager'. Then inside that program, scroll down to 'Google Services Framework' and disable 1 receiver.
The one you want to disable is called 'com.google.gsf.update.SytemUpdateService$Receiver' Just disable that (by unchecking it) and then reboot. You will not receive a notification to update ever again.
Also, go into the folder /cache and delete the FOTA d/l. You will need R/W permissions in the root directory to do this. So use whichever file manager you prefer for that.
The FOTA d/l is easy to spot, it's a 150mb approximately zip file with a bunch of chars and should be the only file in that directory. There are a few folders as well, but, ignore them and just delete the 1 file.
I'm in the same situation - reverted back to stock rooted with twrp recovery and now boot back to recovery. I haven's used adb much, but do know how to open the cmd window in the adb directory on my computer and it appears I'm connected to my d800. However, when I run the adb devices command I see the device code and recovery listed. When I type the first line of the code in the first post, adb shell, I get ~ # ←[6n and can't type in any additional commands.
Am I missing a step - or just not understanding the process??
UPDATE - Nevermind - I just typed in the command dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota using TWRP's Terminal Command and the phone booted right up to Clean Rom.
Thanks vegasdavek for your repost on this fix!
vegasdavek said:
So like many, I took a stupid OTA on one of the roms (CleanROM) and got stuck in recovery boot loop...
original post of this thread in hopes of saving someone else a lot of time trying to find that extra line of code burried in the other thread.
Click to expand...
Click to collapse
Thanks, found this now, only after I already fixed my issue, but this is useful. Perhaps you should also update it to reflect it can be done with the Terminal in TWRP..
Related
Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.
l3l2ad said:
Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.
Click to expand...
Click to collapse
what commands did you use...? nothing in customizing bootscreen should damage anything on your phone...?
Last resort = RUU back to stock re-root and reflash..
So why did you feel you needed to make a new thread about this instead of just posting in the thread itself which is already dedicated to the rom and issues...
... ?
Tenny said:
So why did you feel you needed to make a new thread about this instead of just posting in the thread itself which is already dedicated to the rom and issues...
Click to expand...
Click to collapse
because it would get buried and no one would read it for days... hes hoping this way to get a speedy answer... im sure if you felt like you screwed up your phone somehow you'd be clicking on new thread to get as much help, as soon as possible... ???
if you cant help or are willing to help stop cluttering the forums with your "forum police" attitude...
i'm not going to answer your question specifically BECAUSE you made a new thread instead of posting in the existing one.
l3l2ad said:
Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.
Click to expand...
Click to collapse
wipe everything then try to reflash.
wrx4memp said:
what commands did you use...? nothing in customizing bootscreen should damage anything on your phone...?
Last resort = RUU back to stock re-root and reflash..
Click to expand...
Click to collapse
I used the 'mount' command while in shell.
Thanks for the help even though I posted WRONG.
I got my issue fixed by using a nAndroid backup..retsored and th issue was gone. I'm thinking the problem happened because I didn't have the droid SDK on my PC..fixed that too!
haha. mount by itself only displays the current mounted volumes. there isn't anything you can do with mount alone in order to render your system unusable.
-------------------------------------
Sent via the XDA Tapatalk App
geekykid said:
haha. mount by itself only displays the current mounted volumes. there isn't anything you can do with mount alone in order to render your system unusable.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Thanks for the info...well im not sure what happened then LOL I'm tryin to teach myself so go easy on me
Let me start by saying I've read through several other threads with a similar issue, but they all have a common connectivity problem that I'm NOT experiencing so I thought I'd ask this in a new thread. I was using AOKP build 5, and I decided to try out a more TW stock rom to see how devs have modified it. I chose Intergalactic v 2.8, wiped data/cache and installed like ya do. Almost immediately I got the pop up saying, "Unfortunately, Factory Test has stopped." I didn't think much of it, even though I had never seen it before. I restored my app data via Titanium Backup and starting fiddling with my settings. Made a couple calls, a few texts. Put my phone down to go about my morning. Later when I went to unlock my phone I realized I don't have a lockscreen. Thought that was funny so I went to boot into recovery but punching the power button just turned the phone off; So I investigated and I realize I'm in factory mode. and I can't seem to get out of it. I've tried running the terminal commands to turn it off, but that didn't work. It looks like my ESF folder is empty or doesn't exist.
So here's what I know after all of my research: My IMEI somehow seems to be intact since I can make calls and get on the network, but because my ESF is empty or gone can't turn off factory mode, which is causing all kinds of other buggy issues such as no lockscreen, no power menu, and the annoying Factory Test pop-up. If there is a thread out there that had a similar problem, I apologize that I couldn't find it. is there any way to recover this info, since the IMEI is still intact? Thanks.
Flash a stock rom
Sent from my SGH-I747 using Tapatalk 2
did that, no dice
peneoark said:
Flash a stock rom
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Tried to restore the stock JB with Odin and it didn't fix the problem. I'm attempting to flash the stock ICS, then attempt an OTA update to see if that does the trick. Will keep you posted.
So I flashed ics and then allowed AT&T to push my JB update to me OTA. Still in factory mode. I guess I'll just have to investigate this more thoroughly. I'm using widget locker as a work around for my lockscreen, but still no power menu and the popups are still showing up every now and then. Super annoying, but at least my phone is still functioning. If anyone has any other ideas I'd greatly appreciate it. Thanks.
Sent from my SAMSUNG-SGH-I747 using xda premium
drunkenscholar said:
So I flashed ics and then allowed AT&T to push my JB update to me OTA. Still in factory mode. I guess I'll just have to investigate this more thoroughly. I'm using widget locker as a work around for my lockscreen, but still no power menu and the popups are still showing up every now and then. Super annoying, but at least my phone is still functioning. If anyone has any other ideas I'd greatly appreciate it. Thanks.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Try taking and EFS folder from a stock ROM and push it to your current ROM and see if that helps
DamageSource said:
Try taking and EFS folder from a stock ROM and push it to your current ROM and see if that helps
Click to expand...
Click to collapse
How would I extract it from the EFS folder from the stock image? I figured I would need to do with through ADB, but I have no idea what commands I would have to execute.
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
---------- Post added at 10:05 AM ---------- Previous post was at 09:50 AM ----------
hednik said:
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
Click to expand...
Click to collapse
Is your efs folder completely gone ?
hednik said:
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
---------- Post added at 10:05 AM ---------- Previous post was at 09:50 AM ----------
Is your efs folder completely gone ?
Click to expand...
Click to collapse
I saw this fix, but frankly, I'm skittish to try it as my IMEI is still intact and I'm afraid of making the problem worse. My EFS folder is there, but it's empty.
drunkenscholar said:
I saw this fix, but frankly, I'm skittish to try it as my IMEI is still intact and I'm afraid of making the problem worse. My EFS folder is there, but it's empty.
Click to expand...
Click to collapse
Don't be skittish. It really and truly is the only way to get everything back to how it should be. Ton's of people have tried it and this allows you to push the IMEI back into your phone the way it came from the factory. It's not for spoffing or doing anything illegal.
Now its usually for replacng a lost IMEI from flashing a ROM. Sometimes happens when going from a non-stock type ROM (i.e. CM or AOKP) to stock type ROM (i.e TW)
Search on how to push files with ADB and you should be good to go
BE CAREFUL though and don't skip steps or go fast.
I meant to ask...can you use your phone ? does data work ? Have you tried to get into download mode ?
If you can then download good manager and select reboot into recovery or any other number of apps that let you boot into recovery without having a power menu
hednik said:
Don't be skittish. It really and truly is the only way to get everything back to how it should be. Ton's of people have tried it and this allows you to push the IMEI back into your phone the way it came from the factory. It's not for spoffing or doing anything illegal.
Now its usually for replacng a lost IMEI from flashing a ROM. Sometimes happens when going from a non-stock type ROM (i.e. CM or AOKP) to stock type ROM (i.e TW)
Search on how to push files with ADB and you should be good to go
BE CAREFUL though and don't skip steps or go fast.
I meant to ask...can you use your phone ? does data work ? Have you tried to get into download mode ?
If you can then download good manager and select reboot into recovery or any other number of apps that let you boot into recovery without having a power menu
Click to expand...
Click to collapse
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
drunkenscholar said:
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
Click to expand...
Click to collapse
I hate to ask but did yo factory reset the phone...like in stock recovery ?
drunkenscholar said:
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1703175
check out post #8
the user restored the backed up EFS folder with Root Explorer and his device is fixed now.
xBeerdroiDx said:
http://forum.xda-developers.com/showthread.php?t=1703175
check out post #8
the user restored the backed up EFS folder with Root Explorer and his device is fixed now.
Click to expand...
Click to collapse
Beer,
I'm not thinking he has a backup of his EFS though
Try his first but this might do the trick as well:
http://forum.xda-developers.com/showthread.php?t=1703175&page=2
post #14
Odia said:
# echo -n ON > /efs/FactoryApp/factorymode
(and yes ON is the correct setting to turn it off)
Click to expand...
Click to collapse
hednik said:
Beer,
I'm not thinking he has a backup of his EFS though
Try his first but this might do the trick as well:
http://forum.xda-developers.com/showthread.php?t=1703175&page=2
post #14
Click to expand...
Click to collapse
you are correct. i looked back over the thread. i had thought he posted something yesterday about having an EFS backup.
your find seems like it should do the trick
hednik said:
I hate to ask but did yo factory reset the phone...like in stock recovery ?
Click to expand...
Click to collapse
Yessir. When the phone booted back up it didn't go through the setup process. Just goes straight to the homescreen. Also when I boot into restore mode I see this under the menu options:
E:failed to mount /efs (Invalid Argument)
E:failed to mount /efs (Invalid Argument)
# MANUAL MODE #
--Applying Multi-CSC...
Applied CSC-code : unknown
Successfully applied multi-CSC.
I tried turning it off with terminal emulator at one point last night, but it didn't seem to work, I THINK because the EFS folder is empty. I'll have to re-root tonight and try it again since I've restored my stock firmware.
It may seem like I'm shooting down every suggestion you guys throw at me, but I really appreciate the input. XDA is a big place and I tried to be very thorough when searcing for a solution before posting this thread, but I'm sure there's something out there I've missed. Thank you for your efforts.
I think I found something that will allow me to restore a generic EFS here:
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
Asked the originator if it will work to restore my files. If so, gonna try it when I get off work tonight.
drunkenscholar said:
I think I found something that will allow me to restore a generic EFS here:
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
Asked the originator if it will work to restore my files. If so, gonna try it when I get off work tonight.
Click to expand...
Click to collapse
Ah exactly what I have been looking for on this one for you. I found a few that explained how to push your old EFS folder with ADB but none about making another. How crazy it was yesterday it popped up on a post. That looks like your best shot as you folder seems to be corrupted and although IMEI is intact you need a new one folder that is intact. Let us know how it turns out
Can you hit me with the stuff you found about pushing it through ADB? My efforts have been less than fruitful on that front. I'd rather be armed with as much information as possible.
drunkenscholar said:
Can you hit me with the stuff you found about pushing it through ADB? My efforts have been less than fruitful on that front. I'd rather be armed with as much information as possible.
Click to expand...
Click to collapse
Here is one I had found earlier:
http://forum.xda-developers.com/showthread.php?t=1169805
xaurion said:
[/COLOR]Problem fixed!! give read write permissions for user/group/others to the keystr file.[/QUOT
Have you looked at this ? (or is this just the same thing as turning it off)
- One more thing, what file explorer are you looking at the efs folder with ?
Click to expand...
Click to collapse
I can't for the life of me find any sort of documentation for this update, Nothing is listed on T-Mobile's website and I cant find any immediate changes in the UI. The only info I can find about the tmo G3 is that it should be at D85110c. Anyone else get this D85110m update?
I just installed this update but can't find anything about it either.
Here's a screenshot of the build number and the baseband, in case that changed too.
someone help please. I accidentally clicked update even though I was rooted. Now when I try to enter download mode, it goes straight to TWRP and when I turn off my phone and then press the volume up button as it's turning off, it shows a screen saying firmware update but the percentage bar doesn't move. HELP
Did this update lock me in custom recovery?
Late yesterday (20140909) I got a status bar notification that a T-Mobile Software Update had been downloaded, and that I should click on it to update. I left it alone for some hours but then, used to a couple of years of easy Cyanogenmod updates (I'm rooted stock on this phone), I went ahead and clicked on the update. It threw me into TRWP and just sat there. I went looking for the download, to update manually from there, and couldn't find it. Now I can't get the phone to boot to system, just the recovery. After a few attempts, I tried restoring a five week old backup, but it still dumps me in recovery. Can't seem to get out of it. I can't even verify that this is the same update you guys are talking about (can't get to settings), although the timing is right. What can I do from here?
LG_D851
Rooted stock
Ripped out Carrier IQ stuff
If this is the wrong spot for this post, Mods, please help me out.
Lawrence
With this update, I can launch camera app from the lock screen.
bemusedsamadhi said:
Late yesterday (20140909) I got a status bar notification that a T-Mobile Software Update had been downloaded, and that I should click on it to update. I left it alone for some hours but then, used to a couple of years of easy Cyanogenmod updates (I'm rooted stock on this phone), I went ahead and clicked on the update. It threw me into TRWP and just sat there. I went looking for the download, to update manually from there, and couldn't find it. Now I can't get the phone to boot to system, just the recovery. After a few attempts, I tried restoring a five week old backup, but it still dumps me in recovery. Can't seem to get out of it. I can't even verify that this is the same update you guys are talking about (can't get to settings), although the timing is right. What can I do from here?
LG_D851
Rooted stock
Ripped out Carrier IQ stuff
If this is the wrong spot for this post, Mods, please help me out.
Lawrence
Click to expand...
Click to collapse
after NUMEROUS attempts and deleting all my data, I found an incredibly simple solution...
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
DrakalDragon said:
I can't for the life of me find any sort of documentation for this update, Nothing is listed on T-Mobile's website and I cant find any immediate changes in the UI. The only info I can find about the tmo G3 is that it should be at D85110c. Anyone else get this D85110m update?
Click to expand...
Click to collapse
I've gotten what appears to be this update but I am rooted and TWRP so I know I cant select it to install like a few other users have done. Is there anyway to remove this update from the notification bar or maybe download it and apply through TWRP... I thought I turned off the call home feature when I bought the device and rooted a few months ago...
Heitem said:
With this update, I can launch camera app from the lock screen.
Click to expand...
Click to collapse
Ive had shortcuts on the lock screen to do this since the first week I had the phone... Im sure there has to be more to this update than this...
Long press on the notification and go into app info and turn off notifications to remove it from your notification bar
OhioDroid80 said:
Long press on the notification and go into app info and turn off notifications to remove it from your notification bar
Click to expand...
Click to collapse
Done... Any chance this decide to update on its own without any human intervention?? I dont have time to deal with fixing the phone if it does install and then fails because of TWRP right now...
I'm under the impression that human intervention is necessary for the update to apply itself on the phone. You don't chose yes it shouldn't load.
I think there is a battery life improvement.
tmo 10m update discussion is already going on in the tmo g3 general section: http://forum.xda-developers.com/tmobile-lg-g3/general/update-t2872755/post55357425
typicalgamer said:
someone help please. I accidentally clicked update even though I was rooted. Now when I try to enter download mode, it goes straight to TWRP and when I turn off my phone and then press the volume up button as it's turning off, it shows a screen saying firmware update but the percentage bar doesn't move. HELP
Click to expand...
Click to collapse
You can open the terminal emulator in TWRP and run "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota". That might help. Helped with the LG G2 all the time.
I'm on Sprint. I think I can speak for everyone with a locked bootloader that we wish we had this problem. Haha. You just need stock recovery installed probably.
try another command
typicalgamer said:
someone help please. I accidentally clicked update even though I was rooted. Now when I try to enter download mode, it goes straight to TWRP and when I turn off my phone and then press the volume up button as it's turning off, it shows a screen saying firmware update but the percentage bar doesn't move. HELP
Click to expand...
Click to collapse
anjini said:
You can open the terminal emulator in TWRP and run "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota". That might help. Helped with the LG G2 all the time.
Click to expand...
Click to collapse
Right .. then type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
and enjoy
tested on d851 t-mobile
DrakalDragon said:
I can't for the life of me find any sort of documentation for this update, Nothing is listed on T-Mobile's website and I cant find any immediate changes in the UI. The only info I can find about the tmo G3 is that it should be at D85110c. Anyone else get this D85110m update?
Click to expand...
Click to collapse
Beginning September 10, the LG G3 received a software update to D85110m. This update provides features and improvements (Hide)
New Features
•T-Mobile Free Inflight Texting support
Improvements
•NA
This goes along with the Uncarrier 7.0 announcement from today, that T-Mobile has partnered with GOGO inflight Wi-Fi and will allow text, MMS and visual voicemail support inflight
updated while rooted and dragon rom
typicalgamer said:
someone help please. I accidentally clicked update even though I was rooted. Now when I try to enter download mode, it goes straight to TWRP and when I turn off my phone and then press the volume up button as it's turning off, it shows a screen saying firmware update but the percentage bar doesn't move. HELP
Click to expand...
Click to collapse
I updated on accident also and now I cant boot phone I tried to install new rom and nothing just bots right back to twrp . I cant connect from sideload as it doesn't finish loading sideload on my phone can I reinstall twrp from my sdcard ?? want to try updating that and see what happens
I also cant get download to connect it doesn't even make a sound like its connected to the pc like where it would install a driver nothing
bassmek2 said:
I updated on accident also and now I cant boot phone I tried to install new rom and nothing just bots right back to twrp . I cant connect from sideload as it doesn't finish loading sideload on my phone can I reinstall twrp from my sdcard ?? want to try updating that and see what happens
I also cant get download to connect it doesn't even make a sound like its connected to the pc like where it would install a driver nothing
Click to expand...
Click to collapse
I had the same problem and using these two commands in TWRP terminal emulator should work (as stated above). It will give you a 'no space' error, but that is expected. After that the phone should boot back to normal.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Be sure to not make any typos - apparently you can completely mess up your device. It took me quite a while to find out about the misc command - just the fota one didn't do it for me...
I got the OTA yesterday.
I traded in my S4 on the jump program yesterday, (9.16.14), and got an LG G3. When I got home I noticed that an update was downloaded and ready to install and since I had barely got it and it wasn't rooted or anything I decided what the heck. I applied the update and my version is now 110m and like the other guy said there is a "camera slider" on the lockscreen that I don't think was there before. But I have had this phone for less that 24 hours so maybe I'm wrong.
Ok, so I'm rooted with TWRP, stock ROM. Wasn't thinking this morning and took the OTA, now I'm bootlooping back to TWRP. Download fresh stock ROM and go from there?
Carpe Noctem said:
Ok, so I'm rooted with TWRP, stock ROM. Wasn't thinking this morning and took the OTA, now I'm bootlooping back to TWRP. Download fresh stock ROM and go from there?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=55354859&postcount=20
Hallelujah
I am not a noobie but I was stuck in TWRP loop and the without ADB did the trick for me.
Flashed stock 10c and rooting again.
THANK YOU! This community ROCKS! Keep on modding!
Thanks all, got it fixed.
how do i
how do i get adb to work i cant get out of twrp
---------- Post added at 07:14 AM ---------- Previous post was at 07:13 AM ----------
hey this just happened to me this morning and i need my phone working today please tell me how you got the phone to boot out of twrp?
Carpe Noctem said:
Thanks all, got it fixed.
Click to expand...
Click to collapse
---------- Post added at 07:15 AM ---------- Previous post was at 07:14 AM ----------
hey how did you get it to work i cant get out of twrp
I've tried the without adb method, but mine is still boot looping to twrp. I've also tried a factory reset. Any ideas?
I tried the without ADB method, and I get no space left on device errors.
UrbanMuppet said:
I tried the without ADB method, and I get no space left on device errors.
Click to expand...
Click to collapse
Ditto. Not sure what to do. And this is a coworker's device :X
dcxgod said:
Ditto. Not sure what to do. And this is a coworker's device :X
Click to expand...
Click to collapse
Fixed it. Wipe misc as well. DD zeros out the device, and then it runs out of space. That's a normal response.
My phone is now fixed.
Now disable OTA updates..
1) Open Dialer and dial 3845#*851# for hidden menu.
2) wlan test > ota setting >Disable
3) Reboot
for guys still having issues you will have to go back to stock with lg tool. video with how to is at zedomax lg g3 webite.
UrbanMuppet said:
Fixed it. Wipe misc as well. DD zeros out the device, and then it runs out of space. That's a normal response.
My phone is now fixed.
Now disable OTA updates..
1) Open Dialer and dial 3845#*851# for hidden menu.
2) wlan test > ota setting >Disable
3) Reboot
Click to expand...
Click to collapse
Somehow I think I cleared the OS out of her device via Factory Restore. Not sure how that happened but now when I try to reboot it's telling me NO OS INSTALLED.
I'm a bit ****ed, aren't I?
dcxgod said:
Somehow I think I cleared the OS out of her device via Factory Restore. Not sure how that happened but now when I try to reboot it's telling me NO OS INSTALLED.
I'm a bit ****ed, aren't I?
Click to expand...
Click to collapse
lol dont freak out. lg tool and video helps with bricked and screwed up phones. just use pc where you first rooted device from that way you know all ur drivers are good.
UrbanMuppet said:
Fixed it. Wipe misc as well. DD zeros out the device, and then it runs out of space. That's a normal response.
My phone is now fixed.
Now disable OTA updates..
1) Open Dialer and dial 3845#*851# for hidden menu.
2) wlan test > ota setting >Disable
3) Reboot
Click to expand...
Click to collapse
I did this when i rooted and still my phone downloaded the update last night. I don't want to run it. Has anyone successfully gotten the notification to go away? I tried longpressing and it only gives me app info popup, which takes me to the app info for the play store... grrrr. I really dont want to accidently hit it while trying to wait it out.
BACARDILIMON said:
lol dont freak out. lg tool and video helps with bricked and screwed up phones. just use pc where you first rooted device from that way you know all ur drivers are good.
Click to expand...
Click to collapse
I seem to have a problem as I don't have a PC :X There doesn't seem to be a mac tool, is there?
Zella83 said:
I did this when i rooted and still my phone downloaded the update last night. I don't want to run it. Has anyone successfully gotten the notification to go away? I tried longpressing and it only gives me app info popup, which takes me to the app info for the play store... grrrr. I really dont want to accidently hit it while trying to wait it out.
Click to expand...
Click to collapse
Someone said you needed to freeze/remove the LGOTA.apk and clear the zipped update from /cache
Hey all,
I had this issue this morning but this post's exact instructions worked for me.
http://forum.xda-developers.com/showpost.php?p=55355406&postcount=27
Basically I had to run both those commands. The single one as noted in the previous post wasn't enough.
"Open Terminal Command in TWRP. On first page just hit The Advanced Button, Terminal Command, Select Current Folder, Then type the following.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot."
dcxgod said:
I seem to have a problem as I don't have a PC :X There doesn't seem to be a mac tool, is there?
Click to expand...
Click to collapse
Sorry bro I only know PC.
AWESOME G3
UrbanMuppet said:
Someone said you needed to freeze/remove the LGOTA.apk and clear the zipped update from /cache
Click to expand...
Click to collapse
That worked! Thanks
UrbanMuppet said:
Fixed it. Wipe misc as well. DD zeros out the device, and then it runs out of space. That's a normal response.
My phone is now fixed.
Now disable OTA updates..
1) Open Dialer and dial 3845#*851# for hidden menu.
2) wlan test > ota setting >Disable
3) Reboot
Click to expand...
Click to collapse
How do you Wipe misc? What did you do?
tehl3x said:
Hey all,
I had this issue this morning but this post's exact instructions worked for me.
http://forum.xda-developers.com/showpost.php?p=55355406&postcount=27
Basically I had to run both those commands. The single one as noted in the previous post wasn't enough.
"Open Terminal Command in TWRP. On first page just hit The Advanced Button, Terminal Command, Select Current Folder, Then type the following.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot."
Click to expand...
Click to collapse
yurdun said:
How do you Wipe misc? What did you do?
Click to expand...
Click to collapse
Read above quote.
Stock Tmobile G3 with TWRP and rooted. Woke up, and before I could think I applied the T-Mobile update. Now every time I reboot it instantly moves into the TWRP bootloader.
How do I fix this? I'm hoping not to lose any data as for some reason Titanium Backup wasn't backing up.
I just did the same thing. I'm trying to unroot now but NONE of the methods I am finding online are working.
I can't even use the OTA method cause the phone will not turn on, just keeps rebooting into TWRP.
I knew I shouldn't have rooted.
DudeThatsErin said:
I just did the same thing. I'm trying to unroot now but NONE of the methods I am finding online are working.
I can't even use the OTA method cause the phone will not turn on, just keeps rebooting into TWRP.
I knew I shouldn't have rooted.
Click to expand...
Click to collapse
Rooting is fine, it's just we shouldn't have updated. Most likely the boot is messed up, and it's trying to boot into the stock boot loader, and TWRP doesn't support the script.
I assume if you flash stock bootloader, and restart, it should try and update -- but then we'll run into the issues that other people are having where we lose root.
I figured it out! OMG IT IS WORKING! (10% right now)
youtube.com watch?v=1VVms7SdM04
Make sure your drivers are updated. Mine weren't. You can tell by going into the device manager. If there are yellow exclamation point triangles then you can visit the YouTube video I provided you above to download the updated drivers.
WOO HOO! No one has any idea how happy I am right now!
P.S. I can't post outside links so just replace the space with /
---------- Post added at 10:23 AM ---------- Previous post was at 10:15 AM ----------
UrbanMuppet said:
Rooting is fine, it's just we shouldn't have updated. Most likely the boot is messed up, and it's trying to boot into the stock boot loader, and TWRP doesn't support the script.
I assume if you flash stock bootloader, and restart, it should try and update -- but then we'll run into the issues that other people are having where we lose root.
Click to expand...
Click to collapse
I don't care about that. I want to lose root. It causes too many problems. IDK why I even did it in the first place.
So, it failed the first time and now I have restarted it... I'm hoping it doesn't fail this time.I got past the 10% I was at... I'm at 11% but it is taking a while...
Followed this guide: http://forum.xda-developers.com/showthread.php?t=2451696
Wiped fota and misc, and rebooted. Phone works 100% all settings saved...
UrbanMuppet said:
Followed this guide: http://forum.xda-developers.com/showthread.php?t=2451696
Wiped fota and misc, and rebooted. Phone works 100% all settings saved...
Click to expand...
Click to collapse
That post is for the G2. Will it also work for the G3?
Can't recover after OTA update
I tried the above fix and it didn't work. I can't even get my drivers to install properly. just a yellow bang in device manager. I don't know what to do. Is there a simple way to get back to stock? With an actual G3 guide? Thanks.
DudeThatsErin said:
I figured it out! OMG IT IS WORKING! (10% right now)
youtube.com watch?v=1VVms7SdM04
Make sure your drivers are updated. Mine weren't. You can tell by going into the device manager. If there are yellow exclamation point triangles then you can visit the YouTube video I provided you above to download the updated drivers.
WOO HOO! No one has any idea how happy I am right now!
P.S. I can't post outside links so just replace the space with /
---------- Post added at 10:23 AM ---------- Previous post was at 10:15 AM ----------
I don't care about that. I want to lose root. It causes too many problems. IDK why I even did it in the first place.
So, it failed the first time and now I have restarted it... I'm hoping it doesn't fail this time.I got past the 10% I was at... I'm at 11% but it is taking a while...
Click to expand...
Click to collapse
Can you post an update when it's complete?
DudeThatsErin said:
I figured it out! OMG IT IS WORKING! (10% right now)
youtube.com watch?v=1VVms7SdM04
Make sure your drivers are updated. Mine weren't. You can tell by going into the device manager. If there are yellow exclamation point triangles then you can visit the YouTube video I provided you above to download the updated drivers.
WOO HOO! No one has any idea how happy I am right now!
P.S. I can't post outside links so just replace the space with /
---------- Post added at 10:23 AM ---------- Previous post was at 10:15 AM ----------
I don't care about that. I want to lose root. It causes too many problems. IDK why I even did it in the first place.
So, it failed the first time and now I have restarted it... I'm hoping it doesn't fail this time.I got past the 10% I was at... I'm at 11% but it is taking a while...
Click to expand...
Click to collapse
This wipes all of your data too. Is there a way to recover from soft-bricking the LG G3 after the OTA update without wiping all of your settings and data. I am stuck on the TWRP startup screen.
mhildebr said:
This wipes all of your data too. Is there a way to recover from soft-bricking the LG G3 after the OTA update without wiping all of your settings and data. I am stuck on the TWRP startup screen.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=55360818&postcount=5
vengurls said:
That post is for the G2. Will it also work for the G3?
Click to expand...
Click to collapse
Yes, it fully worked. Ignore the out of space message. Wipe both FOTA and MISC
UrbanMuppet said:
Followed this guide: http://forum.xda-developers.com/showthread.php?t=2451696
Wiped fota and misc, and rebooted. Phone works 100% all settings saved...
Click to expand...
Click to collapse
Thanks. I followed that guide and used both the ADB and non-ADB methods and neither worked. Can I just delete these files using the File Manager in TWRP?
Hey all, just to update, I tried the solution offered in this thread: http://forum.xda-developers.com/showthread.php?t=2451696. I tried the single line of code for the "terminal command" option. The first time it did not work. I saw in a thread on androidcentral that someone suggested running that line, followed by another line but replacing "fota" with "misc" I tried this and I am back in business.
In short:
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit Go
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit Go and reboot.
I just saw that UrbanMuppet replied confirming that both fota and misc should be done
Worst thing that happened to me is that i cant even turn on my phone and an error 43 on my computer
mhildebr said:
Thanks. I followed that guide and used both the ADB and non-ADB methods and neither worked. Can I just delete these files using the File Manager in TWRP?
Click to expand...
Click to collapse
Check my reply below your post. If using the non-ADB approach, you have to type the line twice, once with fota at the end and the once with misc. That guide only says to try the line once with fota at the end.
delete, had a typo in the script. please delete
All you have to do is wipe all, adb sideload a ROM and boom your golden.
vengurls said:
Hey all, just to update, I tried the solution offered in this thread: http://forum.xda-developers.com/showthread.php?t=2451696. I tried the single line of code for the "terminal command" option. The first time it did not work. I saw in a thread on androidcentral that someone suggested running that line, followed by another line but replacing "fota" with "misc" I tried this and I am back in business.
In short:
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit Go
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit Go and reboot.
I just saw that UrbanMuppet replied confirming that both fota and misc should be done
Click to expand...
Click to collapse
That worked for me too. Thanks to all for your help. The second line with "misc" at the end made the difference from the earlier instructions. Now I am going to figure out how to turn off automatic OTA updates. Lesson LEARNED!
Can I please have the camera.apk for G3?
If you long press the notification and click app info, there will be a box you can uncheck that says show notifications. After you uncheck that, no more ota notifications!
Sent from my LG-D851 using XDA Free mobile app