Database Users

unrevoked + hosts editing "Directory not empty"

Hello, I rooted with unrevoked and then flashed the rom liberated_aria_FR006_signed.
I booted through clockwork and mounted /system /data /sdcard and then connected to my pc via usb, through the command prompt and adb I tried:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
when I do rm /system/etc/hosts it says:
rm: can't remove '/system/etc/hosts': Directory not empty
What's wrong? Is /system not full perms through clockwork or is it a unrevoked root problem.
Thanks!

G226 said:
Hello, I rooted with unrevoked and then flashed the rom liberated_aria_FR006_signed.
I booted through clockwork and mounted /system /data /sdcard and then connected to my pc via usb, through the command prompt and adb I tried:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
when I do rm /system/etc/hosts it says:
rm: can't remove '/system/etc/hosts': Directory not empty
What's wrong? Is /system not full perms through clockwork or is it a unrevoked root problem.
Thanks!
Click to expand...
Click to collapse
Lol...the error tells you exactly what's wrong...but kinda weird since the hosts is a file not a directory...so I can only assume that there are some permission issues...navigate to the /system/etc directory and do a "ls -al" and see what the permissions are for the hosts file...it'll be on the left side of the results of the ls.
Sent From My HTC Aria Using XDA App

Oh fyi...I'm dumb...are you already rooted? I dunno much about adb but you MIGHT have to run the above command through a terminal program on your phone...
Sent From My HTC Aria Using XDA App

I'm rooted but it's through unrevoked as mentioned, does that give me the proper permissions if I adb through clockwork recovery?
If not what would? I'll do a "ls -al" in a little.

G226 said:
I'm rooted but it's through unrevoked as mentioned, does that give me the proper permissions if I adb through clockwork recovery?
If not what would? I'll do a "ls -al" in a little.
Click to expand...
Click to collapse
I'm not sure...as I said im not too familiar with adb...I do know if you have a terminal program on your phone just open it, type the following:
su
cd /system/etc
ls -al
Once you so the ls, if you aren't familiar with *nix, you'll see the following:
-rw-r--r-- 1 root root 25 Aug 1 2008 hosts
Along with a bunch of other lines similar to this, this is the line I'd like to see though
Sent From My HTC Aria Using XDA App

Thanks for the help so far, I did what you said and after doing "ls -al" it said :
-al: No such file or directory
If I do a plain "ls" command it'll list all the files/folders in the system dir.

G226 said:
Thanks for the help so far, I did what you said and after doing "ls -al" it said :
-al: No such file or directory
If I do a plain "ls" command it'll list all the files/folders in the system dir.
Click to expand...
Click to collapse
1 are you doing this in adb or terminal?
2 are you typing "ls -al" with a space? And "al" as in alpha lima?
3 are you in the etc directory?
Sent From My HTC Aria Using XDA App

I did as you instructed, used the terminal program app and tried these commands through there, I'll try adb.
Thanks.

Well the only reason I asked was because ls -al is a legit command lol...I dunno of another way to view the permissions of files...I also don't know if there is a way or not through adb, Google may be your friend in regards to that...
Sent From My HTC Aria Using XDA App

This may be related to busybox on the phone. Can you do an "echo $PATH" from the adb shell and paste the results here?
So from the command prompt you would enter "adb shell" this should give you a new prompt like this #. At this prompt type "echo $PATH" without the quotes. Maybe you do not need all these instructions, sorry.

I see this all the time, from all the noobs (myself included)
First off the ARIA still has S-ON security, so if you are writing to /system/ you _NEED_ to be properly booted into recovery - otherwise you will not have write permissions. its in the FAQ but still completely overlooked. There is a post about this every day i swear.
STEP 1) UNPLUG THE USB <----- CRITICAL
STEP 2) POWER DOWN THE PHONE <----- AFTER STEP 1!!!!!!
STEP 3) HOLD VOLUME DOWN + PRESS POWER to load hboot
STEP 4) SELECT recovery to start clockwork
STEP 5) partitions --> mount --> /system/
STEP 6) connect USB
STEP 7) adb shell
edit: if you shortcut into recovery by just leaving the USB plugged in while you power down - you will not have full permissions.

dexmix said:
I see this all the time, from all the noobs (myself included)
First off the ARIA still has S-ON security, so if you are writing to /system/ you _NEED_ to be properly booted into recovery - otherwise you will not have write permissions. its in the FAQ but still completely overlooked. There is a post about this every day i swear.
STEP 1) UNPLUG THE USB <----- CRITICAL
STEP 2) POWER DOWN THE PHONE <----- AFTER STEP 1!!!!!!
STEP 3) HOLD VOLUME DOWN + PRESS POWER to load hboot
STEP 4) SELECT recovery to start clockwork
STEP 5) partitions --> mount --> /system/
STEP 6) connect USB
STEP 7) adb shell
edit: if you shortcut into recovery by just leaving the USB plugged in while you power down - you will not have full permissions.
Click to expand...
Click to collapse
3 sleepless nights later and dexmix comes to the rescue. This drove me crazy man, I just could not find the answer. Thanks!! Bed time!

Uninstall WaveSecure system app?

Hi I have been trying all evening to remove com.wsandroid.apk from my phone, using terminal but I simply cannot. I've tried many different commands and I'm just being told either permission denied, directory not found/not empty. I have a Wildfire which is obviously rooted. Please help me out, tearing my hair out here.

So you're using modaco custom rom?
Download the latest version of HTC Sync and install. This will also install the adb drivers. (I presume you use windows, if not, I apologise)
Download the Android SDK
Put the phone in fastboot mode (Power+Volume down) and plug it into your computer.
When the drivers are installed, use the command prompt to navigate to the tools folder within the android sdk folder.
Type the following commands, pressing enter at the end of each line:
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
cd app
rm -r com.wsandroid.apk
That should do it

I'm using the stock ROM but it is rooted with Unrevoked. I'll try these instructions anyway.

- Connect your phone to the PC
- Clear WaveScure's cache on the phone
- Open a command prompt
- go to run go to C:\androidSDK\tools and then run these 2 commands
1. adb remount
2. adb shell rm /system/app/*wsandroid*
Click to expand...
Click to collapse
I'm trying these settings, but when I get to adb remount, I get this error: remount failed: Operation not permitted
EDIT: I put the phone into recovery mode and mounted it and it said remount succeeded, I then followed step 2. both *wsandroid* and com.wsandroid.apk and it says that they cannot be found.
EDIT: Nevermind, deleted it

There's currently no write access to system partition using Unrevoked on Wildfire. So you can't remove it. You flashed it with update.zip? I'm not an expert (yet) but I assume the only way (or easiest way) to remove it is to flash your stock ROM again.

CM7.1 MyTouch Slide GPS fix

I am not a developer or even smart. I poked around until I found something that worked for me. Use at your own risk.
I rooted and installed CM 7.0.2 in the past and was pretty happy. When 7.1.0 came out I took the leap. Everything was great except for GPS. GPS did not connect at all. Nothing I did could bring it back other than going back to stock rom. After much frustration and fighting I have it working.
Many people said to make changes to the /system/etc/gps.conf. The problem I had was S-ON was preventing it and nothing I could find explained a work-around. Sorry if I missed it.
I am going to explain what I did to get it going.
Phone details:
- My phone is rooted and CM7.1 installed.
- S-ON
- GPS don't work (even after 30 minutes of waiting)
- Clockwork is on sdcard as update.zip (not permanent)
- Phone is connected to the computer (with adb installed and working)
Proceedure:
1. Unzip the gps.conf.zip file (attached) to the root of your sdcard
2. Turn off the phone
3. Press and hold the volume down and then press the power button
4. Choose "recovery" from the menu and press power (phone will reboot into recovery)
5. Press and hold volume up and press the power button (this may take a few seconds)
6. Choose "Apply sdcard:update.zip" and press power button (assumes clockworkmod is on the sdcard and named update.zip)
7. Choose "mounts and storage" and click the bottom middle button (trackball)
8. While mount /system is selected press the trackball. (sinkinglow suggested that you might need to mount /sdcard as well)
9. Switch to the computer now
10. At a command prompt (DOS) in the folder where adb.exe is located type "adb shell"
11. Type "cd /system/etc" (if you cant get in then you did not mount /system properly)
12. Type "cp /sdcard/gps.conf ."
13. Switch back to the phone.
14. Click the trackball again to unmount /system.
15. Click the back arrow (bottom right)
16. Choose "reboot system now"
Once the phone is back up, you should be all good.

GPS fix htc espresso
Is there anyway that you could maybe post a youtube video on how to do this, or send me a pm.I will give you my contact info.Maybe you could walk me through it.

ok im stuck at (12. Type "cp /sdcard/gps.conf .") i get this in cmd prompt :
C:\Users\Ryan>adb shell
~ # cd /system/etc
cd /system/etc
/system/etc # cp /sdcard/gps.conf
cp /sdcard/gps.conf
BusyBox v1.16.2androidminimal (2010-03-28 22:34:51 EDT) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
Options:
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Force overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
/system/etc #
then step 13/14 (14. Click the trackball again to unmount /system.) says on phone Error unmounting SYSTEM:!
confused on where to go in cmd prompt i think theres a step missing

Try this
Instead of "cp /sdcard/gps.conf", use :
"cp /sdcard/gps.conf /system/etc"
Worked for me and GPS locks within 15 seconds now.
boss2688 said:
ok im stuck at (12. Type "cp /sdcard/gps.conf .") i get this in cmd prompt :
C:\Users\Ryan>adb shell
~ # cd /system/etc
cd /system/etc
/system/etc # cp /sdcard/gps.conf
cp /sdcard/gps.conf
BusyBox v1.16.2androidminimal (2010-03-28 22:34:51 EDT) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
Options:
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Force overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
/system/etc #
then step 13/14 (14. Click the trackball again to unmount /system.) says on phone Error unmounting SYSTEM:!
confused on where to go in cmd prompt i think theres a step missing
Click to expand...
Click to collapse

Step 12 issue
I think what is being missed it the "." at the end of that comand. The "." is the second argument of the "cp" command and "." means the folder i'm currently in.
If you leave it out you are not telling the cp command where to put the file.
Sorry if I abandoned this post. It sat for weeks with no responses so I quit visiting. Hope it helped you guys out.

Is there anyway that you could post a youtube video on this process.I am missing something
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
Maybe you could send me a pm.Then I could give you my contact info.we could go from there.I just really want to use cm7, but this GPS nonsense is keeping me from doing this.

Assumptions
I made a list of assumptions at the top of the post.
- My phone is rooted and CM7.1 installed.
- S-ON (not required but if you have S-OFF you don't need these instructions)
- GPS don't work (even after 30 minutes of waiting)
- Clockwork is on sdcard as update.zip (not permanent because of S-ON)
- Phone is connected to the computer (with adb installed and working)
So you must have already rooted and installed clockwork as well as CM7. You must have the clockwork (update.zip) in the root of your sdcard. you must have ADB working on your computer and working with your phone (shows in devices list). If you have those then it should be following the steps. I am not currently using my slide and do not have equipment or and account to post videos so that would be difficult. if you can tell me where you get stuck I might be able to help.
Like mentioned before I really don't know what I'm doing. I just tried TONS of stuff till I got a feel for things and found a combination that worked for me.
If you are having issues with rooting or installing CM7 or clockwork then that is beyond this tutorial and there is lots of info out there for that.

My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).

My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).

captorofxxx said:
My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).
Click to expand...
Click to collapse
Try this out before you begin. http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Simply start from where it says Windows and you should be good to go.
Did this fix just a moment ago and it worked like a charm. Thanks reiter01

I wish someone would post a video or give (intricate-no detail left out) instructions on how to do this.I video would be the ticket.If I could follow someone or watch someone do it........

I wish someone would post a video or give (intricate-no detail left out) instructions on how to do this.I video would be the ticket.If I could follow someone or watch someone do it........

reiter01 said:
I think what is being missed it the "." at the end of that comand. The "." is the second argument of the "cp" command and "." means the folder i'm currently in.
If you leave it out you are not telling the cp command where to put the file.
Sorry if I abandoned this post. It sat for weeks with no responses so I quit visiting. Hope it helped you guys out.
Click to expand...
Click to collapse
yeah i think that was the problem i didnt see the ''." there and sorry if im being noob with adb i was never any good with cmd prompt, i prefer a GUI

ADB issues
There are countless posts and article about getting adb working. I use a Mac so it's never an issue for me. If you haven't already installed the USB drivers for your specific phone the first time you hook up then you will have issues. Windows will choose a generic driver that ADB can't use. You need to find instructions on removing the generic driver and install the right one.
I'm really glad some had had success with my little tutorial. I am sure there has to be easier ways but it's the best I could come up with.

Worked great
This worked great for me, my GPS now locks on within seconds. One note to add, I had to mount /system and /sdcard. Thank you for this fix.

GUIless
@boss2688: I agree with having a GUI when available. I have no phone programming skills and so I didn't try that. I am not sure if it would work anyway because the S_ON would be in place blocking by the time the GUI shows up. On the other hand, I am sure that someone could make a zip with scripts etc to do what I am doing manually. I tried and failed to make a zip. I wanted to have it work just like you install google apps from clockwork.
@sinkinglow: Not sure why you would have to mount /sdcard. It should be mounted already at that point (I think). I no longer use my slide so I can't go back and test. Thanks for the tip. I will see if I can figure out how to edit the original post and add that as a possible step.

reiter01 said:
@boss2688: I agree with having a GUI when available. I have no phone programming skills and so I didn't try that. I am not sure if it would work anyway because the S_ON would be in place blocking by the time the GUI shows up. On the other hand, I am sure that someone could make a zip with scripts etc to do what I am doing manually. I tried and failed to make a zip. I wanted to have it work just like you install google apps from clockwork.
@sinkinglow: Not sure why you would have to mount /sdcard. It should be mounted already at that point (I think). I no longer use my slide so I can't go back and test. Thanks for the tip. I will see if I can figure out how to edit the original post and add that as a possible step.
Click to expand...
Click to collapse
a much easier way if you don't have experience with ADB would be to use Android Commander. Please see http://androidcommander.com/ (of course you would still need to mount the system from clockwork if you don't have S-OFF) hopefully this helps for those still having issues.

CM7 1 MyTouch Slide GPS fix
Im going up on the 26th, and was hoping to try this slide then bop over to Gothics. Im going to get to the slide and then make the call as to how safe it seems....Backup plan is any other thing time permitting from that spot. Thats how I roll

* I have to run USBDeview.exe and delete everything sometimes. I think the devices get confused etc..
* I also have to use "Vista_x86" drivers as none of them work for me ..in XP SP3
Code:
C:\usb\ANDROID\Vista_x86\androidusb.cat
C:\usb\ANDROID\Vista_x86\androidusb.INF
C:\usb\ANDROID\Vista_x86\androidusb.sys
C:\usb\ANDROID\Vista_x86\htcrndis.cat
C:\usb\ANDROID\Vista_x86\htcrndis.inf
C:\usb\ANDROID\Vista_x86\WdfCoInstaller01007.dll

[HOWTO] ATT 4.5.91 Rooted, Unlocked Bootloader -> 4.5.141 Safe Manual Method

I could not find any resource here, to provide a step-by-step guide for going from ATT 4.5.91 rooted, with Unlocked Bootloader to the latest 4.5.141 without bricking. I put this together myself and tested it on my own Atrix. Use at your own risk!
It's kind of a technical guide, but you really get to learn about your phone doing it this way. I did assume you know some basics about Android and Atrix that you could learn from Swiftks great guide: http://forum.xda-developers.com/showthread.php?t=1154600
Thanks to all of the resources here on XDA, that I used to pull this info together.
REQUIREMENTS:
- ATT Atrix 4.5.91 with Unlocked Bootloader
- Custom Recovery (Romracers or Rom Manager)
PRE STEPS:
- Take a full Nandroid Backup with CWM
- Backup your apps with TiBu
- Backup Call and SMS Logs with My Backup Root
Files Needed:
- 4.5.141 Full SBF - http://atrix.tk/4.5.141/ or http://forum.xda-developers.com/showpost.php?p=22379866&postcount=393
- preinstall.img - for root - http://forum.xda-developers.com/showpost.php?p=15023022&postcount=2
- adb and moto-fdastboot - get anywhere
- Portable SBF Tool - http://forum.xda-developers.com/showthread.php?t=1059643
- .37P Radio zip (N_01.77.37P_usa_att_12dec2011.zip) - http://forum.xda-developers.com/showthread.php?t=1339047 or http://forum.xda-developers.com/showpost.php?p=22399253&postcount=171
- Nebtop for Webtop over HDMI - http://forum.xda-developers.com/showthread.php? t=1404625
Steps:
- Open full 4.5.141 SBF with Portable SBF Tool, to extract the smg files. Move the SMG folder, before closing the tool.
- Power off phone
- Power on while holding down the vol button
- Scroll to Fastboot with the vol down, vol up to select fastboot
- Connect to PC
- Cleanup:
moto-fastboot erase system
moto-fastboot erase boot
moto-fastboot erase webtop
- Flash new boot, system, webtop, preinstall
moto-fastboot flash boot CG59_0x00000130.smg
moto-fastboot flash system CG60_0x00000140.smg
moto-fastboot flash webtop CG61_0x00000150.smg
moto-fastboot flash preinstall preinstall.img
- Wipe and reboot
moto-fastboot -w
moto-fastboot reboot
- Turn on USB Debugging
- Root
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH
pm install /preinstall/Superuser.apk
*Make sure to accept the Superuser prompt on the phone when using it the first time.
- sqlite
cp /preinstall/sqlite3 /system/bin/sqlite3
chmod 6755 /system/bin/sqlite3
- Google Video over 3g
adb shell
su
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|true
update main set value='false' where name='gtalk_vc_wifi_only';
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|false
.exit
- Tether hack
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value='disabled' WHERE name='entitlement_check';"
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db
select * from settings WHERE name='entitlement_check';
*118|entitlement_check|disabled
.exit
- Radio
adb push N_01.77.37P_usa_att_12dec2011.zip /mnt/sdcard/
reboot into recovery and apply from sdcard
wipe cache
wipe dalvik cache
reboot
- Recover apps with TiBu
- Restore Call log and SMS data with My Backup Root
- Remove Annoying SDCARD Mount sounds
adb shell
su
setprop persist.service.mount.playsnd 0
- Install the Nebtop Apk for Webtop over HDMI
**Another method to try, using CWM: http://forum.xda-developers.com/showpost.php?p=22997305&postcount=22

Will this work?
you posted this a few days ago, but with all the bricking issues you have no posts saying, hey this works. Not trying to dismiss you here, but I'm very nervous about doing this update. I can' afford to brick my phone, but i really need the new updates 'cause ATT is messing with the towers in this area.
I had a Froyo phone, that I unlocked, rooted, and then installed a custom ROM.
I unlocked and rooted my phone with this link. And I am running Alien ROM #4 de-blurred. I never realized that doing that keep you from getting the OTA announcements till this big ball of snot dropped (4.5.141)
I'm also downloading NottachTrix 1.2.1. I thought if I change my ROMS with one that has the new updates, I would be ok, but again, nervous as hell about this.

As long as you are unlocked, you can simply download the 2.3.6 SBF and use sbf_flash -x to turn it into .IMG files. Then you can rename and flash the files with moto-fastboot and reboot into 2.3.6.
* CG59.img -> boot.img code:moto-fastboot flash boot boot.img
* CG60.img -> system.img code:moto-fastboot flash system system.img
* CG61.img -> webtop.img code:moto-fastboot flash webtop webtop.img
Make sure to wipe and reboot as said by OP and you will be fine after this. I have tried this on my unlocked Atrix and it works fine. Root however you want after and all is well.

fastboot method?that's safe,i tried many times.

zoness said:
you posted this a few days ago, but with all the bricking issues you have no posts saying, hey this works. Not trying to dismiss you here, but I'm very nervous about doing this update. I can' afford to brick my phone, but i really need the new updates 'cause ATT is messing with the towers in this area.
Click to expand...
Click to collapse
I'm happy to report that everything went perfectly for me!!! I'm so happy this worked. Thank you!
Getting the SBF tool was a little annoying having to sign up for another site where the OP found this app he doesn't own, so I made a mirror:
http://www.mediafire.com/?wo8g5hgeo9jtedq
Thanks a bunch Uncle!

Jason_Thames said:
As long as you are unlocked, you can simply download the 2.3.6 SBF and use sbf_flash -x to turn it into .IMG files. Then you can rename and flash the files with moto-fastboot and reboot into 2.3.6.
* CG59.img -> boot.img code:moto-fastboot flash boot boot.img
* CG60.img -> system.img code:moto-fastboot flash system system.img
* CG61.img -> webtop.img code:moto-fastboot flash webtop webtop.img
Make sure to wipe and reboot as said by OP and you will be fine after this. I have tried this on my unlocked Atrix and it works fine. Root however you want after and all is well.
Click to expand...
Click to collapse
Hi,
Where can I find sbf_flash -x? can I just rename it? or where exactly do I run this? under adb, rsd lite? any help appreciated thanks?
And also I was confused...how to the sqlite3 in the procedures? is that another program I need to have?..
---------- Post added at 04:44 AM ---------- Previous post was at 04:14 AM ----------
I have trouble following these steps:
moto-fastboot flash boot CG59_0x00000130.smg
moto-fastboot flash system CG60_0x00000140.smg
moto-fastboot flash webtop CG61_0x00000150.smg
with cg60 and cg61
image is too big, use 0x10000000 bytes chunks FAILED <remote: <00000006>>
so what does this mean?

I definitely tested this on my ATT atrix without any issues. Spent a few hours putting this together mostly for myself, but thought i would share it.
zoness said:
you posted this a few days ago, but with all the bricking issues you have no posts saying, hey this works. Not trying to dismiss you here, but I'm very nervous about doing this update. I can' afford to brick my phone, but i really need the new updates 'cause ATT is messing with the towers in this area.
I had a Froyo phone, that I unlocked, rooted, and then installed a custom ROM.
I unlocked and rooted my phone with this link. And I am running Alien ROM #4 de-blurred. I never realized that doing that keep you from getting the OTA announcements till this big ball of snot dropped (4.5.141)
I'm also downloading NottachTrix 1.2.1. I thought if I change my ROMS with one that has the new updates, I would be ok, but again, nervous as hell about this.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

The filesize issue probably means that you were using the wrong fastboot. You need moto-fastboot, since it was specifically modified to allow for larger file sizes. Dont use the regular fastboot. As far as sqlite3, it is part of the preinstall and you will need it for some of the last steps, but you can skip those if you dont care for them.
vastelectron said:
Hi,
Where can I find sbf_flash -x? can I just rename it? or where exactly do I run this? under adb, rsd lite? any help appreciated thanks?
And also I was confused...how to the sqlite3 in the procedures? is that another program I need to have?..
---------- Post added at 04:44 AM ---------- Previous post was at 04:14 AM ----------
I have trouble following these steps:
moto-fastboot flash boot CG59_0x00000130.smg
moto-fastboot flash system CG60_0x00000140.smg
moto-fastboot flash webtop CG61_0x00000150.smg
dunno what i'm doing wrong..
after I extracted to folder.. my files don't have the same names as above.. it's only cg59.smg, cg60.smg, ect.. so I flash these but with cg60.smg it won't flash saying the size is too big? I tried putting 0x00000140 before and after but doesn't work..
Could you help be how to do it properly? I used MotoAndroidDepacker to extract.. am I not extracting properly? I did the split to folder or is there something else? and there's no difference if I move the extracted folder before or after the program is closed.? the contents are the same
wait i noticed i used the wrong program...
-so do I run adb shell on the phone or on the computer?
thanks
-yeah still getting errors..
with cg60 and cg61 now..
image is too big, use 0x10000000 bytes chunks FAILED <remote: <00000006>>
so what does this mean?
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

Thank you
Thank you I got it to work but i'm not so clear about these 2 parts:
- Google Video over 3g
adb shell
su
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|true
update main set value='false' where name='gtalk_vc_wifi_only';
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|false
.exit
- Tether hack
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value='disabled' WHERE name='entitlement_check';"
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db
select * from settings WHERE name='entitlement_check';
*118|entitlement_check|disabled
.exit
so what are the command lines? you do this still in command prompt correct?
so example after I enter "sqlite3 /data/data/com.google.android.gsf/databases/gservices.db"
how do you select (((select * from main where name='gtalk_vc_wifi_only')) ? I don't see how I can do a select and the * means what? does it mean not a command line?
Sorry a video tutorial would help.. please clarify if you can thanks a lot.

I noticed under the files needed section the first mirror link to the sbf not only does it show the update sbf file but it also shows in the dir the individual parts (img.gz's) are those the extracted smg files from the sbf? they have the same date, and roughly time on them.

You do both of these from the command line using adb. Just copy paste each line individually and that should do it. The star in the beginning of the line indicates the output i would expect you to see and not commands you have to run.
vastelectron said:
Thank you I got it to work but i'm not so clear about these 2 parts:
- Google Video over 3g
adb shell
su
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|true
update main set value='false' where name='gtalk_vc_wifi_only';
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|false
.exit
- Tether hack
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value='disabled' WHERE name='entitlement_check';"
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db
select * from settings WHERE name='entitlement_check';
*118|entitlement_check|disabled
.exit
so what are the command lines? you do this still in command prompt correct?
so example after I enter "sqlite3 /data/data/com.google.android.gsf/databases/gservices.db"
how do you select (((select * from main where name='gtalk_vc_wifi_only')) ? I don't see how I can do a select and the * means what? does it mean not a command line?
Sorry a video tutorial would help.. please clarify if you can thanks a lot.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

They are maybe the same files, but i didn't want to risk it, and just extracted them myself.
eclypse3demons said:
I noticed under the files needed section the first mirror link to the sbf not only does it show the update sbf file but it also shows in the dir the individual parts (img.gz's) are those the extracted smg files from the sbf? they have the same date, and roughly time on them.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

I wanted to Reply to this thread saying i was running Nottatrix ROM the new one with 4.1.141. My phoen would not run CM9 so i decided to do an sbf flash. IT failed leaving me at rebooting loop. i then followed this thread got the scf extracted the files from it flashed manually with and installed with fastboot and now its working even though it says things do not flash properly its working and i am so thankful for this thread. I still get a warranty replacement but i got it working.

moneyman1978 said:
I wanted to Reply to this thread saying i was running Nottatrix ROM the new one with 4.1.141. My phoen would not run CM9 so i decided to do an sbf flash. IT failed leaving me at rebooting loop. i then followed this thread got the scf extracted the files from it flashed manually with and installed with fastboot and now its working even though it says things do not flash properly its working and i am so thankful for this thread. I still get a warranty replacement but i got it working.
Click to expand...
Click to collapse
I am glad it worked for you! I just think that doing it this way, you learn about your phone to prepare you for flashing other ROMS and recovering from various situations.

running into a problem here. I can't find the file called N_01.77.37P_usa_att_12dec2011.zip inside that directory. there is one in there called N_01.77.36P_usa_att_.zip but not .37P

that__guy said:
running into a problem here. I can't find the file called N_01.77.37P_usa_att_12dec2011.zip inside that directory. there is one in there called N_01.77.36P_usa_att_.zip but not .37P
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/showpost.php?p=22399253&postcount=171

thanks! one more thing, what exactly is being modified regarding tethering with the code in the instructions?

that__guy said:
thanks! one more thing, what exactly is being modified regarding tethering with the code in the instructions?
Click to expand...
Click to collapse
A setting that forces the phone to do some type of a check on whether you have the tether plan or not with ATT is disabled. By not doing the check the hot spot functionality will work, but ATT might still be able to track your data usage and give you a warning. Use at own risk.

Hi, N00b question
I have an ATT 4.5.91 Rooted Atrix but I don't know if it is unlocked or not... how can I find out that? in order to know the best way for me to update to .141?
I tried to unlock the bootloader using fastboot: "fastboot oem unlock" but I got an error that says that it is not implemented...
Can anyone help me to figure out which could be the best way to apply the .141 update?
Thanks

EDIT: Never mind that, I figured out what the problem was and it was unrelated. I just happened that something updated at the same time I ran the code and I thought it was the code that did it. (uninstalled updates to google search to fix) Sorry.
ok, so I have the update installed and am rooted. But now anytime I try to search in the application tray I get a message box saying that "process com.motorola.home has stopped unexpectedly". It didn't do that before I ran the root part of the code so I suspect it is because of that. This is what I ran and got back from the cmd prompt
C:\fastboot>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
[email protected]:/# PATH=/system/bin:$PATH
PATH=/system/bin:$PATH
[email protected]:/# pm install /preinstall/Superuser.apk
pm install /preinstall/Superuser.apk
pkg: /preinstall/Superuser.apk
Success

Is there a way to stop H91810p schedule update?

As title says... Just found out about H91810p will make the phone unrootable which is something im planning later on. Sadly the update is scheduled for next restart.
Anything i can do to prevent that?

TempezT said:
As title says... Just found out about H91810p will make the phone unrootable which is something im planning later on. Sadly the update is scheduled for next restart.
Anything i can do to prevent that?
Click to expand...
Click to collapse
if you're rooted, go to /cache and rename update.zip to something else. then create a zero length file using the name update.zip. lastly set the permissions on that file to read only

Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on:
Also if you are already flashed and rooted, jump to step #8 for the info regarding OTAs...
====================================================
Specifically for T-Mobile LG V20 H918
Firmware(s) 10I & 10J
====================================================
BOOTLOADER
SOURCES:
*** https://forum.xda-developers.com/v20/how-to/guide-unlock-bootloader-t3488878
*** https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/page2
*** https://forum.xda-developers.com/showpost.php?p=69897433&postcount=1060
*** https://forum.xda-developers.com/pi...e-pixel-xl-t3466185/post69239012#post69239012
====================================================
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
*Turn on developer mode:
Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
*Turn on OEM unlock and USB debugging:
Settings -> Developer options -> OEM unlock & USB Debugging. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
*Install LG drivers
WIN:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
MAC:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
You may need to get an additional .dll for adb to work, if so you can pull it from the pixel add compilation here:
https://xenserver.underpants-gnomes.biz/~romracer/fastboot_adb_pixel.zip
*In Terminal navigate to ADB root:
Type
Code:
adb devices
and authorize your computer on the phone
Type
Code:
adb reboot bootloader
Type
Code:
fastboot devices
and make sure your phone shows up
Type
Code:
fastboot oem unlock
Type
Code:
fastboot getvar all
Should say (bootloader) unlocked:yes
Type
Code:
fastboot reboot
====================================================
TWRP & ROOT:
SOURCES:
http://www.droidviews.com/install-twrp-root-t-mobile-lg-v20/
https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
https://build.nethunter.com/android-tools/dirtycow/arm64/
https://github.com/jcadduono/android_external_dirtycow#running
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
https://download.chainfire.eu/supersu
====================================================
*Prerequisites:
Your LG driver must be up to date. You can have problems with USB 3.1 if so grab latest drivers.
ADB installed, put all 4 recowvery files into the folder:
https://build.nethunter.com/android-tools/dirtycow/arm64/
Download the TWRP “twrp-3.0.2-1-h918” image:
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
Rename TWRP file to twrp.img and put it into internal storage (sdcard)
Download SuperSU:
https://download.chainfire.eu/supersu
Copy SuperSU onto external memory card (or keep in root of adb, and you could push it back, after formating).
You must be on a 100% stock ROM. Rooted or not.
USB Debugging & OEM unlock allowed in Developer Settings
Bootloader unlocked
Make sure all security/locks are off. No pins, fingerprint, etc…
Steps:
1. Plug your phone to your host computer. Make sure it's in MTP mode.
2. Open your command prompt:
Code:
cd\
cd (right click your mouse and paste the ADB platform-tools address, if using portable pack, where you put the adb folder)
Code:
adb devices
This will show your connected phone
3. Enter the following prompt: (you can simply highlight, copy, right click on command prompt and choose paste):
Code:
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0777 *
./dirtycow /system/bin/applypatch recowvery-applypatch
* On ADB shell mode, you should see $ on the front. Wait for few…
Code:
./dirtycow /system/bin/app_process64 recowvery-app_process64
* Your phone screen may look weird. Wait for another few minutes. Once finished exit.
Code:
exit
4. Type:
Code:
adb logcat -s recowvery
You should see a lot of lines comes across your screen.
Once you see the ASCII box with the message about giving jcadduomo a hug you can press CTRL+C to exit logcat.
Reboot to the stock recovery:
Code:
adb shell reboot recovery
Restart a session:
Code:
adb shell
You will see a $ sign. Now to check…
Code:
getenforce
It should show Permissive. Thanks Dirty COW!!!
5. Temp Root. Lets patch the boot image:
Code:
cd /data/local/tmp
./dirtycow /system/bin/run-as recowvery-run-as
run-as exec ./recowvery-applypatch boot
Lets run as root
Code:
run-as su
You should have a #, indicating you have root. Ahh my little nix…
6. Flash TWRP
Code:
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
exit
reboot recovery
The phone should have flashed TWRP and rebooted into recovery.
7. TWRP:
In TWRP swipe to allow modifications. Or TWRP will be replaced next boot!
To disable any encryption perform the factory reset, and the Format Data options.
Install SuperSU from the external SD location.
If you didn’t do a full wipe and reset, you probably want to wipe cache and dalvik.
Reboot to system.
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Also in titanium backup (buy it already if you haven’t lol), freeze:
FOTA Update 7.0
Update Center 5.30.12
(I also disabled the com.lge.updatecenter.xxx overlay and themes, cuz whatever... lol)
Reboot and swipe away the notification if its still there. Should have stopped by this point.
======================
There ya go, good luck!

Damn I dont have a computer in hand. Guess i have to wait until im back home in October. Cross fingers this thing don't restart cause that freaking patch is already scheduled.

MDMAchine said:
Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on:
Also if you are already flashed and rooted, jump to step #8 for the info regarding OTAs...
====================================================
Specifically for T-Mobile LG V20 H918
Firmware(s) 10I & 10J
====================================================
BOOTLOADER
SOURCES:
*** https://forum.xda-developers.com/v20/how-to/guide-unlock-bootloader-t3488878
*** https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/page2
*** https://forum.xda-developers.com/showpost.php?p=69897433&postcount=1060
*** https://forum.xda-developers.com/pi...e-pixel-xl-t3466185/post69239012#post69239012
====================================================
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
*Turn on developer mode:
Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
*Turn on OEM unlock and USB debugging:
Settings -> Developer options -> OEM unlock & USB Debugging. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
*Install LG drivers
WIN:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
MAC:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
You may need to get an additional .dll for adb to work, if so you can pull it from the pixel add compilation here:
https://xenserver.underpants-gnomes.biz/~romracer/fastboot_adb_pixel.zip
*In Terminal navigate to ADB root:
Type
Code:
adb devices
and authorize your computer on the phone
Type
Code:
adb reboot bootloader
Type
Code:
fastboot devices
and make sure your phone shows up
Type
Code:
fastboot oem unlock
Type
Code:
fastboot getvar all
Should say (bootloader) unlocked:yes
Type
Code:
fastboot reboot
====================================================
TWRP & ROOT:
SOURCES:
http://www.droidviews.com/install-twrp-root-t-mobile-lg-v20/
https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
https://build.nethunter.com/android-tools/dirtycow/arm64/
https://github.com/jcadduono/android_external_dirtycow#running
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
https://download.chainfire.eu/supersu
====================================================
*Prerequisites:
Your LG driver must be up to date. You can have problems with USB 3.1 if so grab latest drivers.
ADB installed, put all 4 recowvery files into the folder:
https://build.nethunter.com/android-tools/dirtycow/arm64/
Download the TWRP “twrp-3.0.2-1-h918” image:
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
Rename TWRP file to twrp.img and put it into internal storage (sdcard)
Download SuperSU:
https://download.chainfire.eu/supersu
Copy SuperSU onto external memory card (or keep in root of adb, and you could push it back, after formating).
You must be on a 100% stock ROM. Rooted or not.
USB Debugging & OEM unlock allowed in Developer Settings
Bootloader unlocked
Make sure all security/locks are off. No pins, fingerprint, etc…
Steps:
1. Plug your phone to your host computer. Make sure it's in MTP mode.
2. Open your command prompt:
Code:
cd\
cd (right click your mouse and paste the ADB platform-tools address, if using portable pack, where you put the adb folder)
Code:
adb devices
This will show your connected phone
3. Enter the following prompt: (you can simply highlight, copy, right click on command prompt and choose paste):
Code:
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0777 *
./dirtycow /system/bin/applypatch recowvery-applypatch
* On ADB shell mode, you should see $ on the front. Wait for few…
Code:
./dirtycow /system/bin/app_process64 recowvery-app_process64
* Your phone screen may look weird. Wait for another few minutes. Once finished exit.
Code:
exit
4. Type:
Code:
adb logcat -s recowvery
You should see a lot of lines comes across your screen.
Once you see the ASCII box with the message about giving jcadduomo a hug you can press CTRL+C to exit logcat.
Reboot to the stock recovery:
Code:
adb shell reboot recovery
Restart a session:
Code:
adb shell
You will see a $ sign. Now to check…
Code:
getenforce
It should show Permissive. Thanks Dirty COW!!!
5. Temp Root. Lets patch the boot image:
Code:
cd /data/local/tmp
./dirtycow /system/bin/run-as recowvery-run-as
run-as exec ./recowvery-applypatch boot
Lets run as root
Code:
run-as su
You should have a #, indicating you have root. Ahh my little nix…
6. Flash TWRP
Code:
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
exit
reboot recovery
The phone should have flashed TWRP and rebooted into recovery.
7. TWRP:
In TWRP swipe to allow modifications. Or TWRP will be replaced next boot!
To disable any encryption perform the factory reset, and the Format Data options.
Install SuperSU from the external SD location.
If you didn’t do a full wipe and reset, you probably want to wipe cache and dalvik.
Reboot to system.
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Also in titanium backup (buy it already if you haven’t lol), freeze:
FOTA Update 7.0
Update Center 5.30.12
(I also disabled the com.lge.updatecenter.xxx overlay and themes, cuz whatever... lol)
Reboot and swipe away the notification if its still there. Should have stopped by this point.
======================
There ya go, good luck!
Click to expand...
Click to collapse
Okay someone in my base lend his laptop but its low end(sony viao core2 duo) dunno how well this work for flashing purposes, also I wanted to point before doing the process that my phone was unlocked permanently by tmobile unlock app and wanted to know if this can affect the unlocking or any other function of my v20.

Following those instructions to root will not gid rid of your carrier unlock.

You might be able to go to Settings>>Storage and delete Cached data.

Zacharee1 said:
You might be able to go to Settings>>Storage and delete Cached data.
Click to expand...
Click to collapse
Thank you! Now my other concern is that Im paying Jump! and root would void the warranty so I dont know if I should go ahead and do it regardless cause that silly update is already scheduled.

TempezT said:
Thank you! Now my other concern is that Im paying Jump! and root would void the warranty so I dont know if I should go ahead and do it regardless cause that silly update is already scheduled.
Click to expand...
Click to collapse
You can always restore to stock with the H918. Backup and root.

Zacharee1 said:
You can always restore to stock with the H918. Backup and root.
Click to expand...
Click to collapse
Thanks!
The issue Im having now is that I cant find how to root H91810k which is the current version my phone has besides the schedule update. Any info on that?

You have to find the KDZ for 10d and flash it with LGUP. Then you can use EasyRecowvery to root.
Flashing KDZs will wipe your data, so use LG Bridge to make a backup.

MDMAchine said:
Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on.......
Click to expand...
Click to collapse
This is awesome! Thank you!!! You may want to make this its own post it's so helpful. Thanks again!!!!!!!!!

wewantutopia said:
This is awesome! Thank you!!! You may want to make this its own post it's so helpful. Thanks again!!!!!!!!!
Click to expand...
Click to collapse
No problem! Glad it helped, I will probably update the post a bit, and then I'll re-post it to its own thread in a few days. As I noticed this section is a bit disorganized...

MDMAchine said:
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Click to expand...
Click to collapse
just wanted to add that SOMETIMES the update.zip is not in /cache. had this happen to me when I had the LGV10 and it just happened to me now. I had recently wiped my device to start from scratch and after initially setting up my device I got the update icon and indeed /cache/update.zip existed. a few reboots later for various reasons the update icon/notification disappeared, as did /cache/update.zip. I thought I was in the clear until last night when I got the update icon/notification again, but this time it was not in /cache. it somehow changed to /data/data/com.google.android.gms/app_download. so if you can't find it in /cache, look there!