Develop Bugs

[Q] OTA 4.1.2 Failed! No new OTA notification!

Hello,
I kind of messed this myself.
I have GN 4.1.1 takju - maguro JR003C - rooted, unlocked bootloader through GN ToolKit.
Now today got OTA notification of 4.1.2.
Installed OTA Rootkeeper, opted for "Reboot and Install" in OTA screen.
Phone booted into CWM Recovery and then update failed due to signature verification.
Now I am not getting the update notification back in System Update screen.
So the big question - how to get the OTA back and even bigger question - what do I need to do to have 4.1.2 in my phone?

I have the same problem and would like to know the answer.

PeteT said:
I have the same problem and would like to know the answer.
Click to expand...
Click to collapse
i think you should manually download the rom from google when it will be available and use for easy of use gnexusToolKit to install it.
I did like this last time for the same problem and got the problem also now...
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
PeteT said:
I have the same problem and would like to know the answer.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images

MaxDNet said:
i think you should manually download the rom from google when it will be available and use for easy of use gnexusToolKit to install it.
I did like this last time for the same problem and got the problem also now...
Click to expand...
Click to collapse
I can see for takju-maguro, there is an image for 4.1.2 at https://developers.google.com/android/nexus/images#takjujzo54k
But need some one to confirm if thats the one we need to manually install.
Also any help on my original questions will be helpful!

royzlife said:
I can see for takju-maguro, there is an image for 4.1.2 at https://developers.google.com/android/nexus/images#takjujzo54k
But need some one to confirm if thats the one we need to manually install.
Also any help on my original questions will be helpful!
Click to expand...
Click to collapse
I'm going to use that as i did last time for the 4.1.1.
Let you know.

Thank you
I hope it works. I would like to use the upgrade though and not a clean install.

PeteT said:
Thank you
I hope it works. I would like to use the upgrade though and not a clean install.
Click to expand...
Click to collapse
Done, so quick and easy. Google released a bat files inside the rom that will do it all (yeah it'll erase all your data but i like a full format sometimes so its ok for me).
So if you wanna to follow this procedure :
1 - Verify you have adb drivers installed and working
2 - power off mobile
3 - launch "flash_all.bat" files inside google rom
4 - power on the mobile in bootloader mode (menu down + menu up together and power)
This will start all the procedure.
Wait..
Done

You can open the flash-all.bat in Notepad++ and remove the -w switch and it won't wipe the data when flashed

MaxDNet said:
i think you should manually download the rom from google when it will be available and use for easy of use gnexusToolKit to install it.
I did like this last time for the same problem and got the problem also now...
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
MaxDNet said:
Done, so quick and easy. Google released a bat files inside the rom that will do it all (yeah it'll erase all your data but i like a full format sometimes so its ok for me).
So if you wanna to follow this procedure :
1 - Verify you have adb drivers installed and working
2 - power off mobile
3 - launch "flash_all.bat" files inside google rom
4 - power on the mobile in bootloader mode (menu down + menu up together and power)
This will start all the procedure.
Wait..
Done
Click to expand...
Click to collapse
Thanks but could you please help with a bit more detailed for noobs like me!
1. How will we come to step 3? is it through genx toolkit?
2. delete all user data - you mean everything under /sdcard/ ? Means will need a backup of "everything" of my nexus!
Thanks again!

It's in the factory image you download from Google

royzlife said:
Thanks but could you please help with a bit more detailed for noobs like me!
1. How will we come to step 3? is it through genx toolkit?
2. delete all user data - you mean everything under /sdcard/ ? Means will need a backup of "everything" of my nexus!
Thanks again!
Click to expand...
Click to collapse
Hi i dont used GNexus toolkit.
The step i did are the following :
1 - Download the GNexus image (i downloaded the one without Google Wallet) from here https://developers.google.com/android/nexus/images#takjujzo54k and extract the content wherever you want on your pc.
2 - verify that your ADB drivers are installed and your mobile is recognized succesfully (you can do this by installing the gNexus toolkit and follow the inline instructions).
3 - Download if you dont have the fastboot (attacched) and for easy of use extract the content inside the folder of the downloaded ROM (would be better to install in a global folder and set it into windows global variables)
4 - Once extraced go into the folder where you have the extracted ROM and open the file "flash_all.bat" with a notepad
5 - update this line "fastboot -w update image-takju-jzo54k.zip" with this "fastboot update image-takju-jzo54k.zip" if you dont want to wipe your data and save the file.
6 - Inside this folder SHIFT + RIGHT MOUSE CLICK and select "Open Command Prompt from here"
7 - write flash_all.bat and it'll say it's waiting for device to be connected
8 - Power OFF your Mobile if you didnt do yet
9 - POwer ON your mobile in bootloader mode using the combination of VOLUME UP + VOLUME DOWN + POWER (all together at the same time)
The procedure will starts and your mobile will be updated in less than 2 minutes.
Hope this is clear.

It works perfectly!! Thank you.

It couldn't have been put more lucidly! Thanks.
But after installing 4.1.2, Titanium Pro stopped working! I uninstalled and then tried to reinstall but got "no space" error though 9GB is left free!
Any help!
---------------------------------
Solved from this post - http://forum.xda-developers.com/showthread.php?t=1717897
-------------------------------------
Moderators, please mark this thread as SOLVED

[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

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

Softbricked my T-Mobile G3

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