Develop Bugs

[Q] Werid issue where my GS3 is stuck in Factory Mode

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

Boot Looped - reboot nvbackup

So, I was working with a friends SIII and I read about running reboot nvbackup. Like a dumba$$ I decided to run it on my N900T in terminal and now I'm boot looping. I've Odin'd back to the stock ROM with no resolve. What did I do and how can I fix it?
TIA

re: boot loop
zonly1 said:
So, I was working with a friends SIII and I read about running reboot nvbackup. Like a dumba$$ I decided to run it on my N900T in terminal and now I'm boot looping. I've Odin'd back to the stock ROM with no resolve. What did I do and how can I fix it?
TIA
Click to expand...
Click to collapse
Before you Odin'ed back to stock did you do a full wipe using TWRP/CWM which includes:
"Wipe Data", "Wipe System", "Wipe Cache", "Wipe Dalvik Cache" and last but not least did
you do a full "Factory Reset" in TWRP/CWM ?
After doing all the above your phone should no longer boot loop, what it should do after doing
the all the above is to go into download mode and or recovery mode.
If it boots into download mode then odin flash the official stock rom which must match the specific
model number of your phone. After doing that you should be good to go.
Best place to find and download the official stock rom is at " SamMobile.com ".
The only roms that SamMobile.com has are the official stock odin flash firmwares which
displays exact baseband (model numbers) which needs to match your phone's baseband.
Good luck!

Thanks for the reply. I've done what you have mentioned, but still boot looping. Trying other methods that I've found and will report back unless someone has any other suggestions. Primarily, I'd like to know what the reboot nvbackup actually did.

zonly1 said:
Thanks for the reply. I've done what you have mentioned, but still boot looping. Trying other methods that I've found and will report back unless someone has any other suggestions. Primarily, I'd like to know what the reboot nvbackup actually did.
Click to expand...
Click to collapse
I skimmed through the thread on nvbackup and it seems like you borked your efs/IMEI. Could be wrong, I only scanned the thread... This was made for the S3, why would you do this to your Note 3?? Anyways try this thread here: let me grab it real quick..
Sent from my SM-N900T using Tapatalk 2
---------- Post added at 11:31 AM ---------- Previous post was at 11:19 AM ----------
EDIT:
Could not find the thread but your welcome to try this:
Note* I'm not responsible from this point on for further damage to your device*
-----
Originally Posted by*bakachu*
I fixed my brickloop by doing the following:
(I would backup your efs partition before doing this, just for completeness sake)*
Installed Stock firmware via Odin,*
Installed TWRP 2.6.3.2 via odin, rebooted to recovery
Did an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12*
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Did a Factory Reset*
Then... reboot to system
Afterwards, no more boot looping, the phone successfully registered on the mobile network, and my IMEI is there and correct. Seems like the EFS partition can rebuild itself now I guess...
----
Sent from my SM-N900T using Tapatalk 2

lm that guy said:
I skimmed through the thread on nvbackup and it seems like you borked your efs/IMEI. Could be wrong, I only scanned the thread... This was made for the S3, why would you do this to your Note 3?? Anyways try this thread here: let me grab it real quick..
Sent from my SM-N900T using Tapatalk 2
---------- Post added at 11:31 AM ---------- Previous post was at 11:19 AM ----------
EDIT:
Could not find the thread but your welcome to try this:
Note* I'm not responsible from this point on for further damage to your device*
-----
Originally Posted by*bakachu*
I fixed my brickloop by doing the following:
(I would backup your efs partition before doing this, just for completeness sake)*
Installed Stock firmware via Odin,*
Installed TWRP 2.6.3.2 via odin, rebooted to recovery
Did an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12*
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Did a Factory Reset*
Then... reboot to system
Afterwards, no more boot looping, the phone successfully registered on the mobile network, and my IMEI is there and correct. Seems like the EFS partition can rebuild itself now I guess...
----
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
I did it because I'm a dumba$$...no, really...it seemed innocent enough to me...no files to load, etc. Lesson learned.
Anywho, yes, I've also tried that one too to no avail. Just since it is already borked, I ran the reboot nvrestore and that locked it right up to the Samsung Galaxy Note 3 screen. I then Odin'd back the original factory rom and tried the above steps again. Back to boot looping. I would imagine there is an answer since I'm able to get into recovery, but I just need that silver bullet.
Thanks for trying though.

zonly1 said:
I did it because I'm a dumba$$...no, really...it seemed innocent enough to me...no files to load, etc. Lesson learned.
Anywho, yes, I've also tried that one too to no avail. Just since it is already borked, I ran the reboot nvrestore and that locked it right up to the Samsung Galaxy Note 3 screen. I then Odin'd back the original factory rom and tried the above steps again. Back to boot looping. I would imagine there is an answer since I'm able to get into recovery, but I just need that silver bullet.
Thanks for trying though.
Click to expand...
Click to collapse
i have the note 3 i odin back to stock got stuck bootloop then i tried to clear everything still not working . also did recovery from back up no good . i also did fresh install via kias samsung desktop software it loaded everything good but was still stuck in bootloop. i did install jedi 3.1 ithink it loaded and booted up after 5 reboots . when it did load it was slow then i checked options and settings and clicked about or status i say imei missing and baseband missing so i have a brick.

MERK77 said:
i have the note 3 i odin back to stock got stuck bootloop then i tried to clear everything still not working . also did recovery from back up no good . i also did fresh install via kias samsung desktop software it loaded everything good but was still stuck in bootloop. i did install jedi 3.1 ithink it loaded and booted up after 5 reboots . when it did load it was slow then i checked options and settings and clicked about or status i say imei missing and baseband missing so i have a brick.
Click to expand...
Click to collapse
You can try here: http://forum.xda-developers.com/showthread.php?t=2471421
I cannot get adb to see my device, but maybe it will help you.

zonly1 said:
You can try here: http://forum.xda-developers.com/showthread.php?t=2471421
I cannot get adb to see my device, but maybe it will help you.
Click to expand...
Click to collapse
You may want to look here too...just found this: http://forum.xda-developers.com/showthread.php?p=46331142

zonly1 said:
You may want to look here too...just found this: http://forum.xda-developers.com/showthread.php?p=46331142
Click to expand...
Click to collapse
Hey zonly1, were you able to fix your note 3? I'm did what you did.

No, I'm still dead in the water.
Sent from my DROID RAZR HD using Tapatalk

Hey guys, I did the same thing on my note 3 and I tried everything to fix it but in the end I was still within my 14 days and I took it to the store I bought it and swapped it out. At this point you have a couple of options, call Tmobile and do a warranty swap or go through samsung directly. If you go through samsung expect to not have your note for about 1-2 weeks.
Sent from my SM-N900T using Tapatalk 2

Did you ever figured out the solution?

Solved
This thread might help. I had the same problem
http://forum.xda-developers.com/showthread.php?t=2657519

Funny, replying to a thread 2 months old...

krelvinaz said:
Funny, replying to a thread 2 months old...
Click to expand...
Click to collapse
Broken note3's aren't funny. Mine was broken for over 6 weeks, I didn't give up, and today I figured out how to fix the FSG partition that Samsung left vulnerable by the toxic "reboot nvbackup" command. Hope one or two of the guys read my fix and get their note3' gowning again

It wasn't meant to be funny as in ha ha, but rather a doubtful funny that anyone in the thread still has this as a problem. They would most likely of had the issue fixed or replaced their phone by now. Going on now more than 60 days is a but long for most here for a working phone.
I do commend you on coming up with a solution, most don't have that kind of patience.

this is no joke as you all have stated, it's an easily caused brick, but it would have equally been as easy to look up if this unfamiliar command (at least to me) would cause a brick/loop. I'm familiar with adb but had no idea that's a problem samsung left. please let me know of a fix or provide me with a device dump for those partitions, I think it's mmcblk0p's 12,13..17,18, thanks in advance

Think i am bricked... Help... Sprint LG G2

HAS BEEN FIXED...
I have TWRP recovery, and wiped EVERYTHING before trying to install the Rom, never had a phone that didn't really have a MicroSD, and I guess I wiped the internal memory also... meaning I have no rom to flash...
"adb devices" is not recognizing the phone so I can't Push/Sideload...
I can boot into recovery, but can't do much else without being able to use adb
HELP... any suggestions.

lexknight said:
I have TWRP recovery, and wiped EVERYTHING before trying to install the Rom, never had a phone that didn't really have a MicroSD, and I guess I wiped the internal memory also... meaning I have no rom to flash...
"adb devices" is not recognizing the phone so I can't Push/Sideload...
I can boot into recovery, but can't do much else without being able to use adb
HELP... any suggestions.
Click to expand...
Click to collapse
Have you tried mounting the usb storage via recovery and copying the rom from there?

Payton95 said:
Have you tried mounting the usb storage via recovery and copying the rom from there?
Click to expand...
Click to collapse
I see the mount button, but when I go in there I dont see anything about usb storage?
Am I missing something?

install the driver on your computer again and try ADB...
if not...gluck man I dont think there is another way.

lexknight said:
I see the mount button, but when I go in there I dont see anything about usb storage?
Am I missing something?
Click to expand...
Click to collapse
No. Sorry, I believe it is just Cwm that allows usb storage in recovery.(I could be wrong) As stated above, install the drivers to try to fix adb if that fails then you may need to take a look at this. Good Luck:good:
http://forum.xda-developers.com/showthread.php?t=2471370

[Guide] Unroot/Unbrick - flash official factory firmware with LG Launcher
Payton95 said:
No. Sorry, I believe it is just Cwm that allows usb storage in recovery.(I could be wrong) As stated above, install the drivers to try to fix adb if that fails then you may need to take a look at this. Good Luck:good:
http://forum.xda-developers.com/showthread.php?t=2471370
Click to expand...
Click to collapse
I tried that "[Guide] Unroot/Unbrick - flash official factory firmware with LG Launcher"
It seems to see the phone, and all, but when it goes to download the firmware from LG, it just hangs, reading the posts there, looks like others have it hang at the same place mine did...
I think I am just SOL, till someone figures out how to make a tool that will fix this...
I am sure I am not the only one that will accidently wipe everything leaving it in a state where you don't have a rom to flash back on it...
so I am sure someone will make something soon...
till then will just have to go back to my old phone.
Thanks.

I would assume you need to try to get fastboot working, but I have never tried to get into the G2's bootloader. But you'll get ADB - Fastboot working, you will, you just need to keep trying. Try someone else's computer if you have to.

I really need to just find the kdz firmware for the Sprint LG G2... I think I have a way of flashing it... just need to find it...
I have found about every G2 except the Sprint one...

lexknight said:
I really need to just find the kdz firmware for the Sprint LG G2... I think I have a way of flashing it... just need to find it...
I have found about every G2 except the Sprint one...
Click to expand...
Click to collapse
I found it herehttp://forum.xda-developers.com/showthread.php?t=2432476 and am in the exact same boat as you. I was about to flash a recovery I made and accidentally wiped EVERYTHING including my recovery image. I'm downloading the Sprint kdz as we speak and please let me know what else you are thinking as a way of flashing that file. I can get into TWRP, stock hard reset mode (which doesn't seem to do anything) and download mode.

InsanePostman said:
I found it herehttp://forum.xda-developers.com/showthread.php?t=2432476 and am in the exact same boat as you. I was about to flash a recovery I made and accidentally wiped EVERYTHING including my recovery image. I'm downloading the Sprint kdz as we speak and please let me know what else you are thinking as a way of flashing that file. I can get into TWRP, stock hard reset mode (which doesn't seem to do anything) and download mode.
Click to expand...
Click to collapse
You are looking at doing the same thing I am going to try, but when I went to where you download... the only Sprint image I see is a .zip... not a .kdz... and that program they use only recognizes .kdz's...
In reading that feed, they said that in the US they don't use .kdz's... so still looking into that, I have a post in that thread and maybe we can get more help...
But your in the EXACT spot I am in, I can get into TWRP, hard reset, and download
If you can figure it out PLEASE post here, and I will be doing the same, I am sure there will be a lot of people doing what we did without thinking, and I guess we were the first, and will be the leaders... LOL
Thanks.

lexknight said:
You are looking at doing the same thing I am going to try, but when I went to where you download... the only Sprint image I see is a .zip... not a .kdz... and that program they use only recognizes .kdz's...
In reading that feed, they said that in the US they don't use .kdz's... so still looking into that, I have a post in that thread and maybe we can get more help...
But your in the EXACT spot I am in, I can get into TWRP, hard reset, and download
If you can figure it out PLEASE post here, and I will be doing the same, I am sure there will be a lot of people doing what we did without thinking, and I guess we were the first, and will be the leaders... LOL
Thanks.
Click to expand...
Click to collapse
well ****. I'm going to try the method listed in that thread but I don't know if it's going to work. Nothing seems to identify my phone properly. The LG mobile support tool recognizes it as "testdevice" and when I try updating recovey through the program it hangs once it says "downloading files". I'll post anything I can find as soon as I find anything. Please do the same. I just bought this phone yesterday and already managed to f it up.

InsanePostman said:
well ****. I'm going to try the method listed in that thread but I don't know if it's going to work. Nothing seems to identify my phone properly. The LG mobile support tool recognizes it as "testdevice" and when I try updating recovey through the program it hangs once it says "downloading files". I'll post anything I can find as soon as I find anything. Please do the same. I just bought this phone yesterday and already managed to f it up.
Click to expand...
Click to collapse
Mine does the same with the hanging in "downloading files" I sort of think they might not actually have the file up for Sprint yet... I think its just to new... I bought mine 2 days ago also, just long enough to say, what a cool phone, let me BRICK IT... LOL
Will keep you posted on anything I find...
thanks again.

lexknight said:
Mine does the same with the hanging in "downloading files" I sort of think they might not actually have the file up for Sprint yet... I think its just to new... I bought mine 2 days ago also, just long enough to say, what a cool phone, let me BRICK IT... LOL
Will keep you posted on anything I find...
thanks again.
Click to expand...
Click to collapse
I got adb to recognize my device as "02f1a913c6922256" but it says it's offline. if I can get it online somehow you think i could sideload a zip?
Also where do I get the "LGE Android MTP Device" drivers? They say failed and I'v tied the newest available drivers package. Or iss this just an error cause of the state of the phone?

InsanePostman said:
I got adb to recognize my device as "02f1a913c6922256" but it says it's offline. if I can get it online somehow you think i could sideload a zip?
Click to expand...
Click to collapse
You should be able to, as long as you can get adb to see it, you are good, you can even just adb push a rom over to the "NON" SDCard... and then just flash from TWRP...
The main problem we have is that without a SDCard that you can take out and put a rom on, we are stuck.

lexknight said:
You should be able to, as long as you can get adb to see it, you are good, you can even just adb push a rom over to the "NON" SDCard... and then just flash from TWRP...
The main problem we have is that without a SDCard that you can take out and put a rom on, we are stuck.
Click to expand...
Click to collapse
wonderful... i guess i'll have to activate my old phone for the time being
---------- Post added at 07:47 PM ---------- Previous post was at 06:48 PM ----------
InsanePostman said:
wonderful... i guess i'll have to activate my old phone for the time being
Click to expand...
Click to collapse
I'm guessing there's no way to unroot either in order to try and get it covered by the warranty?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
I think I figured it out dude. Follow these instructions from this guide. http://forum.xda-developers.com/showthread.php?t=2448960 Only using the Sprint files located in this thread. http://forum.xda-developers.com/showthread.php?t=2432476
EDIT: The flash program, DLL's, and Sprint .tot file are located here in this link to avoid confusion http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2FSprint+LS980%2F. These are the only files you need. So get that zip and extract it then use those files with the instructions in the first link I posted.[/URL]
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
It worked!!!! I"m back baby.

InsanePostman said:
wonderful... i guess i'll have to activate my old phone for the time being
---------- Post added at 07:47 PM ---------- Previous post was at 06:48 PM ----------
I'm guessing there's no way to unroot either in order to try and get it covered by the warranty?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
I think I figured it out dude. Follow these instructions from this guide. http://forum.xda-developers.com/showthread.php?t=2448960 Only using the Sprint files located in this thread. http://forum.xda-developers.com/showthread.php?t=2432476
EDIT: The flash program, DLL's, and Sprint .tot file are located here in this link to avoid confusion http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2FSprint+LS980%2F. These are the only files you need. So get that zip and extract it then use those files with the instructions in the first link I posted.[/URL]
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
It worked!!!! I"m back baby.
Click to expand...
Click to collapse
Downloaded it all, installed the LGFlashTool, put into download mode, changed to port 41, and when I try to run the LGFlashTool program after saying yes to ??? Korean camp, I get "LG USB/Paralle Lock Key is not detected"... when I hit the "OK" I then get a Login screen with Country Republic of Korea, ID, PASSWORD ...

lexknight said:
Downloaded it all, installed the LGFlashTool, put into download mode, changed to port 41, and when I try to run the LGFlashTool program after saying yes to ??? Korean camp, I get "LG USB/Paralle Lock Key is not detected"... when I hit the "OK" I then get a Login screen with Country Republic of Korea, ID, PASSWORD ...
Click to expand...
Click to collapse
you have to extract the megalock.dll from its archive and overwrite the existing one in the LG flash tool directory. Then launch the program.

InsanePostman said:
you have to extract the megalock.dll from its archive and overwrite the existing one in the LG flash tool directory. Then launch the program.
Click to expand...
Click to collapse
Ahhhhhhhhhhhhhhhhhhhhhhh... I HAVE A PHONE AGAIN... NOT JUST A COOL BRICK !!!...
IF YOU WERE A WOMAN, I WOULD GIVE YOU A BIG KISS !!!!!!!
THANKS MORE THAN YOU WILL EVER KNOW...
Now, time to root and try to brick it again... LOL

lexknight said:
Ahhhhhhhhhhhhhhhhhhhhhhh... I HAVE A PHONE AGAIN... NOT JUST A COOL BRICK !!!...
IF YOU WERE A WOMAN, I WOULD GIVE YOU A BIG KISS !!!!!!!
THANKS MORE THAN YOU WILL EVER KNOW...
Now, time to root and try to brick it again... LOL
Click to expand...
Click to collapse
Haha no problem. Many others deserve credit for the files and instructions. I just did the heavy searching.

InsanePostman said:
Haha no problem. Many others deserve credit for the files and instructions. I just did the heavy searching.
Click to expand...
Click to collapse
Just read the info in the links - thanks for posting about your success. Good to know there's a way out if I get into the same situation flashing a ROM on my G2.

[FIX] Are You Stuck on a Boot Loop to Recovery and cant find a fix?

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..

Bootloop after OTA update

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.