This is the new OTA update of droid 2 global.
winoz said:
This is the new OTA update of droid 2 global.
Click to expand...
Click to collapse
No known official root method is out at the moment. In the meantime you can try SuperOneClick or MotoFail
Seemingly does not work, but to no avail motofail
so I m guessing you HAD root, and lost it after updating? Can you confirm this?
More Info
I can confirm that. I had root and now, after receiving the update this morning, I do not.
I opened Superuser, entered Preferences, and scrolled down to the General section to tap on Su binary to check for updates (or even reapply my current binary, which is v3.0.3.2). Since my version is the latest version I clicked the button Update anyway. Superuser reports the following:
This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager.
Click to expand...
Click to collapse
I tried Pete's Motorola Root Tools (v1.06) to see if I could re-root, but no joy. Step three (the step that adds su, busybox and superuser) fails with the following message:
ERROR: adb could not be granted root access via local.prop method
Try again from the start, but if the problem continues, check your version of Gingerbread -- hopefully you don't have a version where this exploit was fixed.
Click to expand...
Click to collapse
It seems like perhaps the exploit has been patched. Here is the log from Pete's Tools at that point:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
$ su
rm /data/local/12m.bak
$ /system/xbin/su
fi
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local/12m /data/local/12m.bak
(success)
> ln -s /data /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local/12m.bak /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local.prop /data/local.prop.bak
> echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
> echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
$ mv /data/local.prop /data/local.prop.bak
failed on '/data/local.prop' - Permission denied
$ echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /system/bin/su ];
> then
> rm /system/bin/su
> fi
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /system/bin/su ];
> then
> rm /system/bin/su
> fi
$ exit
$ exit
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /system/sbin/su ];
> then
> rm /system/sbin/su
> fi
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /system/sbin/su ];
> then
> rm /system/sbin/su
> fi
$ exit
$ exit
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ exit
$ exit
$ exit
(success)
Anybody have any other ideas?
The phone is asking constantly to update. It just releases a timer that, if you are not watching it, will update without user consent. I disabled background data to no avail.
Is there any way to block the phone from installing the OTA automatically? I really prefer having root than to update.
XT311 3.2.4 Almost cracked it !! ??
I'm New around here and would love to get this sorted for the XT311. I got mine today and spent 6hrs trying all sorts.. Im a unix boy.... Old school and kinda liked getting back into it.. Ok i have some info
''The ro.sys.atvc_allow_all_adb property is a Motorola-specific configuration that prevents ADB from dropping its root privileges. Reboot the device one final time, and on logging in with “adb shell”, you should be presented with a root prompt''
Is this specific param our problem on Motorola device and not completing for all the same reasons.. All these root tools are failaing over the same lame Mount issue...
Im on SuperOneClick and the Exploit Pluggin for Motofail lol...
Hope we get the 311 rooted again soon.... those infamous Jap files are hard to track .....
barbaroja said:
Is there any way to block the phone from installing the OTA automatically? I really prefer having root than to update.
Click to expand...
Click to collapse
The list of files responsible for OTA updates:
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
/system/etc/security/otacerts.zip
Got it rooted !!
Model: Moto XT311
Ver: UK Motorola 'Fire'
Running: v2.3.4
Kernel: Apps_2.6.32.9
Build Number: 4_40C_4067
Here is how i did it to the letter... Even at times i questioned the sequence but it worked.. These instructions are formulated from various sources.. Before you begin unzip the main Zip file I have uploaded and then unzip all the contained zips to one folder. Call the folder Root and put it on your main drive ie(C:/). Ensure that the infamous FXX_PR3_NV.xml is in the root folder..
INSTRUCTIONS:-
Before Rooting:
Prepare your phone by doing the following:
- Go to Settings > Applications > CHECK "Unknown Sources"
- Go to Settings > Applications > Developer > CHECK "USB Debugging" and "Stay Awake"
- Connect your phone via USB, when prompted DO NOT select USB Mass Storage.
1. download and UN-compress all files. on your phone, choose application setting->development->enable "USB debugging", then connect your phone with your pc with USB cable and install driver automatically.
2. install SUT1.75 & RSD LiTE by Motorola which include drivers.
3. Run SUT1.75, choose FXX_PR3_NV.xml. Make sure you select file open option XML from drop down in file open menu.
4. Run cmd > adb shell (if your ROOT folder is located in c:\, then change directly to c:\ROOT, type adb shell), wait untill "#" appear, then you can minimise the cmd window.
5. Open RootD3 folder, run RootD3_zhCN.cmd,
Phone will reboot 3 times. After the 1st reboot, please check if the 2nd reboot starts automatically, if not, unplug the USB cable and plug it again, Goto step 5 again and complete when the 3rd reboot is done.
6. Go into SuperOneClick folder, run SuperOneClick.exe, press Root.
Force a connection with USB drivers. The software will automaticaly do this. The program will now executed and run with NO ERRORS.
After it says it is completed, check if you have the Skull Android icon ( Get SUuperUser APP) Now look in the menu, if Confirmed, your phone has been rooted.
I can't upload any files or provide links as im new round here..
I HAVE ALL FILES/SOFTWARE NEEDED FOR THIS PROCEDURE !!!
79.5 MB (83,442,583 bytes)..
BrB in next few ours with a link up to the DL Locations..
Hack build.prop
I'm trying to prevent this update OTA currently.
Is there a way to modify build.prop to trick the phone in to thinking it has already been updated?
Perhaps if someone who has had the update can post their build.prop we can figure out which properties have changed.
If you edit build.prop phone cant update. All i did was change 0 to 1 so I can have 5 bars for gsm signal and it didn't want to finish the update.
Maybe matie... This is my next job on my XT311 before i plug it into the web..
I found this may be of some use..
down vote accepted
TO STOP AUTO UPDATES
Remove SystemUpdater.apk from /system/app. From terminal (with ADB)
Code:
adb pull /system/app/SystemUpdater.apk C:/Path/to/your/desktop //Backup the file (just in case)
adb remount //Remount the system partition to read-write
adb shell rm /system/app/SystemUpdater.apk //Remove the apk
Warning - this will permanently disable system updates, until you push SystemUpdater back to /system/app
OR If your running different motorola look in the app for Updaters
Code:
adb pull /system/app/Upgrader.apk C:/Path/to/your/desktop //Backup the file (just in case)
adb remount //Remount the system partition to read-write
adb shell rm /system/app/Upgrader.apk //Remove the apk
This is MotoIII example..
Hope this helps....
Well I figured myself how to prevent the phone from upgrading. In fact it was easy.
1. You need titanium backup.
2. Freeze "upgrader" app.
3. Wipe its data. If you do not wipe, the order remains alive (in my case it already had started to download) and is taken by the downloader and it will continue to download and update the phone.
Thats it. Hope it helps.
It seems its similar to the solution above, only without involving adb.
UberSteiner said:
Got it rooted !!
Model: Moto XT311
Ver: UK Motorola 'Fire'
Running: v2.3.4
Kernel: Apps_2.6.32.9
Build Number: 4_40C_4067
Click to expand...
Click to collapse
Do you realise that you're in the DROID2 GLOBAL forum section?
Super One Click root method does not work for 4.5.629.
Rootkeeper
Just tested this. Install voodoo rootkeeper from market before updating. Root seems to work so far.
bummer that there's no way to SBF back. My device auto-updated on me.
i'm assuming that none of this matters if you're on a different rom. i'm using miui so my phone won't auto update right?
Custom ROMs naturally do not support VZW's OTA update mechanism as they're incompatible.
Stock ROM with /system/app/BlurUpdater_VZW.apk renamed also doesn't.
Stock ROM with CWM installed or bloatware frozen is incompatible with the update, however the phone will download and try to install it, only to fail and repeat that again 2 hours later.
Tried freezing 'Upgrader'
I tried freezing 'Upgrader' from titanium backup and wiping the data - this did not work for me.
The update was still downloaded. It has, however, not yet been installed.
Can anyone help me to
1. remove the download before it installs.
2. block this OTA upgrade after removal
I'd appreciate the help to prevent this thing from being unrooted.
Thanks
The update is downloaded to /cache. You can delete it from there.
To disable automatic updates, rename the following files:
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
/system/etc/security/otacerts.zip
by adding .bak on the end of their names.
phone: LG esteem ms910
Rooted: Yes
I'm trying to adb push a .apk file into my phones /system/app folder. These are the steps I am taking in trying to do this, but I am getting a permission denied response at the "adb push" part. Oh and my phone is under the "internet connection" setting. The other two (mass storage, charge only) wont let my phone enter debugging mode.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push C:\Myfile.apk /system/app
Also when I enter the "mount -o remount,rw /dev/block/stl9 /system" command, It pops up twice but without the # symbol, not sure if there is an error there but it ends up looking like this:
Code:
C:\Android\android-sdk\platform-tool>adb shell
$ su
# mount -o remount,rw /dev/block/stl9 /system
mount -o remount,rw /dev/block/stl9 /system
# exit
exit
$ exit
exit
C:\Android\android-sdk\platform-tool>
I think you would want it to be on charge only, as the other options are utilizing the USB while charge only does not. That is how my setup functions... I did have the permission denied error before when I was using Ubuntu 10.04. Are you sure you have an up to date version of JDK? And the USB rules?
your command should be
adb push C:\Myfile.apk /system/app/myfile.apk
you have also to run adb as root or enable rw for /system/app
Basically:
______________________________________________
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
chmod 777 /system/app
exit
exit
adb push C:\Myfile.apk /system/app/myfile.apk
________________________________________________
should do the job
@imheroldman- I tried leaving it on charge only, but the devices wasnt found when I ran the adb devices command, and yes the JDK is the latest.
@djodjoni -Hey I tried your suggestions and it worked.
Thanks to the both of you for helping.
FWIW, I got permission denied errors when I tried to push busybox via adb. I just downloaded a busybox .zip and flashed it via TWRP, it seems to have worked, and the busybox app recognizes it as installed.
I can't use adb push. It says Read Only file system when I try to push things to /sdcard. Don't know why
kavinzhao said:
I can't use adb push. It says Read Only file system when I try to push things to /sdcard. Don't know why
Click to expand...
Click to collapse
Use this:
Code:
[path] > adb shell
# mount -o rw,remount rootfs /
# chmod 777 /sdcard
# exit
[path] > adb push [file path on your PC] /sdcard
ИΘΘK¡€ said:
Use this:
Code:
[path] > adb shell
# mount -o rw,remount rootfs /
# chmod 777 /sdcard
# exit
[path] > adb push [file path on your PC] /sdcard
Click to expand...
Click to collapse
Thanks. I was using the recovery to receive before this. I think that should save me some time.
hello, I am having same problem, can you please help me out?
[email protected]_himaulatt:/data/local # adb push C:\firewater /data/local/temp
adb push C:\firewater /data/local/temp
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/local/
adb push C:\firewater /data/local/
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/l
adb push C:\firewater /data/l
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/
adb push C:\firewater /data/
error: device not found
1|[email protected]_himaulatt:/data/local # cd ..
cd ..
[email protected]_himaulatt:/data # cd ..
cd ..
[email protected]_himaulatt:/ # exit
exit
[email protected]_himaulatt:/ $ exit
exit
C:\Users\Winpc\Downloads\fastboot-win>adb push C:\firewater /data/local/temp
failed to copy 'C:\firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>adb wait-for-devices push firewater /data/local/temp
failed to copy 'firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>adb shell
[email protected]_himaulatt:/ $ su
su
[email protected]_himaulatt:/ # mount -o rw,remount rootfs/
mount -o rw,remount rootfs/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_himaulatt:/ # mount -o rw,remount rootfs /
mount -o rw,remount rootfs /
[email protected]_himaulatt:/ # chmod 777 /sdcard
chmod 777 /sdcard
[email protected]_himaulatt:/ # exit
exit
[email protected]_himaulatt:/ $ adb push C:\firewater /data/
adb push C:\firewater /data/
error: device not found
1|[email protected]_himaulatt:/ $ exit
exit
C:\Users\Winpc\Downloads\fastboot-win>adb wait-for-devices push firewater /data/local/temp
failed to copy 'firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>
Make sure you have phone detected and correct drivers and adb installed.
Once ADB is functioning properly, then let's PUSH files!
First let's make sure adb is running and make sure adb see's the phone. Please run these commands:
Code:
adb kill-server
adb start-server
adb devices
The output after devices will be a serial number, if this looks good, move on. First you need to make
sure the apk you want to push is in the same directory as adb.exe
once you have moved the apk to the adb.exe directory, then run the following:
Code:
[FONT=Verdana]adb remount
adb push myfile.apk /system/app/
adb shell chmod 644 /system/app/myfile.apk
adb reboot[/FONT]
adb remount mounts the phone as read write so you can write thru adb, it will be automatically unmounted when phone disconnected or rebooted
assuming your APK you want moved is called "myfile.apk"
adb push file_myfile.apk /system/app/ this command moves the "myfile.apk" (the apk you want moved) to the /system/app/ directory on your phone
adb shell chmod 644 /system/app/myfile.apk this command sets the correct file permissions for APKs
adb reboot this reboots the phone so that the new apk can be detected
Good luck
hi:
phone is rooted;
android 5.0 ;
adb start-server is OK;
adb devices is OK;
adb root is adbd is already running as root;
system and system/app are "chomd is 777 ";
I want to "adb push myfile /system/app/ "
Question: Permission denied .
- -
thx
other:
adb remount is Permission denied too.
"adb push ./build.gradle /storage/sdcard0/ " is OK.
opalescent said:
hi:
phone is rooted;
android 5.0 ;
adb start-server is OK;
adb devices is OK;
adb root is adbd is already running as root;
system and system/app are "chomd is 777 ";
I want to "adb push myfile /system/app/ "
Question: Permission denied .
- -
thx
other:
adb remount is Permission denied too.
"adb push ./build.gradle /storage/sdcard0/ " is OK.
Click to expand...
Click to collapse
sounds like you possibly do not have proper permission for the user you are logged into your computers operating system with. make sure you have the proper permissions and rights to access the folders you are trying to access. For a quick fix you can try loging into the system using the root user or administrator of the system that you are using and then try the adb commands. and you can just do a quick su switch from the Computer OS's konsole/terminal.
XeoNoX said:
First you need to make sure the apk you want to push is in the same directory as adb.exe
Click to expand...
Click to collapse
OMG thanks, mine wasn't working because something as simple as that!
Recently was running ParanoidKANGdroid and then updated to ParanoidKANGdroid 2.30 (4/5) but phone got stuck in samsung logo. (phone wouldnt boot up). I then had to use this method to restore my phone http://forum.xda-developers.com/showthread.php?t=1762204
It was the only way to get my phone to get bootup and have su.
I finally got it back to working but now it shows factory test mode has stopped working and keeps popping up on my verizon galaxy s3. I ve tried every possible solution. I am on rooted stock rom and i cannot install any other rom. I have my IMEI number but when I look in the /efs folder there are no files. I did not create a backup. Please help
Oh and I tried the following but it did not help it just says it cannot create folder.
Open a terminal emulator
Type su
Then enter the following after the #
echo -n ON > /efs/FactoryApp/factorymode
i found this
Open terminal emulator and type as ;
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
I tried that but right after I enter
rm /efs/FactoryApp/keystr
It gives me the following:
rm failed for /efs/FactoryApp/keystr, No such file or directory
Same problem with me
psychojv said:
I tried that but right after I enter
rm /efs/FactoryApp/keystr
It gives me the following:
rm failed for /efs/FactoryApp/keystr, No such file or directory
Click to expand...
Click to collapse
same problem is coming with me..
some one help..
i have same here, solutions?
I have copyied a damaged file in /system/app folder and now my phone is in the Bootloop. I wanna acces that file and replace it with the original. Can I do that?
I managed to solve it by deleting the 2 damaged files with this piece of code
Code:
echo " "
echo "Waiting for device..."
adb wait-for-device
echo " "
adb -d shell su -c "mount -o rw,remount /system"
adb -d shell su -c "ls /system"
adb -d shell su -c "rm /system/app/AudioEffectService.apk"
adb -d shell su -c "rm /system/app/SoundEnhancement.apk"
(of course the boot-loop forced me to find the right moment in the boot sequence to run the script)
Hi
I recently rooted my device and found out I got the no deep sleep bug.
I installed ADB, followed this guide.
http://forum.xda-developers.com/showthread.php?t=2141817
and when done, I copy/pasted
http://forum.xda-developers.com/showpost.php?p=60383471&postcount=49
su
mount -o rw,remount /system /system
mkdir /system/su.d
chmod 0700 /system/su.d
echo "#!/tmp-mksh/tmp-mksh" > /system/su.d/000000deepsleep
echo "echo 'temporary none' > /sys/class/scsi_disk/0:0:0:1/cache_type" >> /system/su.d/000000deepsleep
echo "echo 'temporary none' > /sys/class/scsi_disk/0:0:0:2/cache_type" >> /system/su.d/000000deepsleep
chmod 0700 /system/su.d/000000deepsleep
reboot
Click to expand...
Click to collapse
But nothing happens. I'm kind of new to ADB, so could anyone please explain further what to do? USB debugging is on, yes.
Thanks in advance