Hi all, I have a problem with my Samsung I9300. When I press the off button does not show the menu (shutdown, restart, airplane mode) and power off directly. How I can recover it?
Thank you very much.
Certainly not enough I fo to go off of to help with you problem. Rooted or not rooted? What rom you running? Did u flash any mods or theme from other rom? This is the development section only. This belongs in Q & A my friend. Little more info would be helpful. It's to early to guess
Sent from my SPH-L710 using Tapatalk 2
reverepats said:
Certainly not enough I fo to go off of to help with you problem. Rooted or not rooted? What rom you running? Did u flash any mods or theme from other rom? This is the development section only. This belongs in Q & A my friend. Little more info would be helpful. It's to early to guess
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Hello friend, thanks for answering so fast. The problem begins when the phone unlock and repair IMEI Octopusbox. I have version 4.0.4.
Greetings.
Solution:
Hello
easy to fix posted by me in other section.
root your phone.
and use this commands FOR I9300 only
Quote:
adb shell "rm /efs/FactoryApp/keystr"
adb shell "rm /efs/FactoryApp/factorymode"
adb shell "echo -n ON >> /efs/FactoryApp/keystr"
adb shell "echo -n ON >> /efs/FactoryApp/factorymode"
adb shell "chown 1000.1000 /efs/FactoryApp/keystr"
adb shell "chown 1000.1000 /efs/FactoryApp/factorymode"
adb shell "chmod 0744 /efs/FactoryApp/keystr"
adb shell "chmod 0744 /efs/FactoryApp/factorymode"
or if you have secureroot then
Quote:
adb shell su -c "rm /efs/FactoryApp/keystr"
adb shell su -c "rm /efs/FactoryApp/factorymode"
adb shell su -c "echo -n ON >> /efs/FactoryApp/keystr"
adb shell su -c "echo -n ON >> /efs/FactoryApp/factorymode"
adb shell su -c "chown 1000.1000 /efs/FactoryApp/keystr"
adb shell su -c "chown 1000.1000 /efs/FactoryApp/factorymode"
adb shell su -c "chmod 0744 /efs/FactoryApp/keystr"
adb shell su -c "chmod 0744 /efs/FactoryApp/factorymode"
for i9100 /efs/imei/keystr
Regards,
Chevli
Related
I am on aospCM's rom for my Hero and as such the market has some problems. To fix it, s0be found a way to do it. The commands are such:
1. adb shell
2. su
3. mkdir /cache/download
4. chown system:cache /cache/download
5. chmod ug+rwx /cache/download
6. chmod a+x /cache/download
Click to expand...
Click to collapse
I don't need step 3 since the directory exists.
Since I am flashing nightlies (or near nightlies as the case may be) typing all of these commands gets super tedious. I figured there has to be a way to do this in a .bat from Windows.
I have adb worked into my system shell (did this so I could use the SendTo menu to push to my phone) and I came up with this:
Code:
@echo off
adb connect 192.168.1.66
echo Time to fix the market
pause
adb shell su
adb shell chown system:cache /cache/download
adb shell chmod ug+rwx /cache/download
adb shell chmod a+x /cache/download
echo Done
pause
This didn't work, nor did a few iterations previous to it where I was taking out the repetitive 'adb shell' commands. I don't know enough about batch/dos programming to get this to work, so I am turning to the community. Help please?
i think you must need superuser permision
not "adb shell" try "adb shell -c"
dateno1 said:
i think you must need superuser permision
not "adb shell" try "adb shell -c"
Click to expand...
Click to collapse
Does that mean I need to put "adb shell -c" on each line? Just once?
just replace 'adb shell' to 'adb shell su -c' and retry
dateno1 said:
just replace 'adb shell' to 'adb shell su -c' and retry
Click to expand...
Click to collapse
Got it! Thanks!
I got it to work too (well, I think anyway). If anyone's interested, here's my code (and if anyone sees any problems, let me know!):
Code:
@echo Begin s0be's market fix
@echo off
PAUSE
adb connect 192.168.1.66
adb shell "su -c 'sleep 1'"
adb start-server
@echo on
@echo Working...
@echo off
SET /P ANSWER=Create /cache/download?
echo (y/y): %ANSWER%
if /i {%ANSWER%}=={y} (goto :yes)
goto :no
:yes
adb shell "su -c 'sleep 2'"
@echo Creating Market Directory in Cache
@echo off
adb shell "su -c 'mkdir /cache/download'"
goto :no
:no
adb shell "su -c 'sleep 2'"
@echo Assigning Logical Link
@echo off
adb shell "su -c 'chown system:cache /cache/download'"
adb shell "su -c 'sleep 2'"
@echo Setting Permissions for Logical Link
@echo off
adb shell "su -c 'chmod ug+rwx /cache/download'"
adb shell "su -c 'chmod a+x /cache/download'"
adb shell "su -c 'sleep 2'"
@echo asop Market Fix complete!
PAUSE
RVDigital gave me some help as well
nathanielray said:
Does that mean I need to put "adb shell -c" on each line? Just once?
Click to expand...
Click to collapse
thank you very much, after so many years after your publication, I am now in 2020 also helped a lot)))) Hello from Russia with love )))
Excellent! It also came in handy for me. Thank you!
I love command line interface. Two years ago, when I got my OG EVO on launch day, the only way to root was through toast's cryptic instructions here and here. Even for an old DOS guy like me, they were daunting as an Android newb, but after several days of poking around and reading everything I could find, the process went smoothly. Fast-forward to today.....I'm ready to root my new EVO LTE and would love to do it myself. I have the SDK installed on both my work and home computers and feel like all I need to do is execute the commands contained in the one-click solution posted by zedomax.
Code:
@echo Rooting...
@adb wait-for-device
@echo Start Rooting...
@adb shell mv /data/local/tmp /data/local/tmp.bak
@adb shell ln -s /data /data/local/tmp
@adb reboot
@echo reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
@PING 1.1.1.1 -n 1 -w 9000 >NUL
@adb wait-for-device
@adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
@adb reboot
@echo reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
@PING 1.1.1.1 -n 1 -w 9000 >NUL
@adb wait-for-device
@adb remount
@PING 1.1.1.1 -n 1 -w 3000 >NUL
@adb push su /system/bin/su
@adb shell "chown root.shell /system/bin/su"
@adb shell "chmod 06755 /system/bin/su"
@adb shell "rm /system/xbin/su"
@adb shell "ln -s /system/bin/su /system/xbin/su"
@adb push Superuser.apk /system/app/.
@adb shell rm /data/local.prop
@adb shell rm /data/local/tmp
@adb shell mv /data/local/tmp.bak /data/local/tmp
@adb push busybox /data/local/tmp/.
@adb shell "chmod 755 /data/local/tmp/busybox"
@adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
@adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@adb shell "chown root.shell /system/xbin/busybox"
@adb shell "chmod 04755 /system/xbin/busybox"
@adb shell "/system/xbin/busybox --install -s /system/xbin"
@adb shell "rm -r /data/local/tmp/busybox"
@echo rebooting
@adb reboot
@echo All Done rooting Evo 4G LTE, check out OneXRoot.com for more cool stuff like ROMs, hacks, tips, and more!
So here's my question, will running each of these commands (minus the @echo and "wait-for-device" ones), accomplish the same thing as executing the batch file or does the automated nature of the script add something else to the process??? Obviously, I know that I need to put the busybox and su files in the appropriate folder, but other than that, is there something else I would need to do?
Thanks for any input!
Is there any way to root in fastboot mode???
If so, using what utility?
Thanks in advance.
I guess I am asking if issuing the following commands on a RAZR through adb while in fastboot result in root? This is for ICS.
These command are from DroidRAZRUtility .bat file.
echo [*] Waiting for device...
adb wait-for-device
echo [*] Device found.
adb shell "rm -r /data/local/12m/batch 2>/dev/null"
adb shell "ln -s /data /data/local/12m/batch"
echo [*] Rebooting device...
adb reboot
echo [*] Waiting for device to reboot...
adb wait-for-device
adb shell "rm /data/local.prop"
adb shell "echo 'ro.sys.atvc_allow_all_adb=1' > /data/local.prop"
echo [*] Rebooting device again...
adb reboot
echo [*] Waiting for device to reboot...
adb wait-for-device
echo [*] Attemping persistence...
adb remount
adb push su /system/bin/su
adb shell "chmod 6755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su 2>/dev/null"
adb push busybox /system/xbin/busybox
adb shell "chmod 755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install /system/xbin"
adb push Superuser.apk /system/app/Superuser.apk
echo [*] Cleaning up...
adb shell "rm /data/local.prop"
adb shell "rm /data/local/12m/batch"
adb shell "chmod 771 /data"
adb shell "chown system.system /data"
echo [*] Rebooting...
adb reboot
adb wait-for-device
echo [*] Exploit complete!
Click to expand...
Click to collapse
Okay, So I am working on a project for my work. We need to locate and test a tablet to sell to a client. The client needs it rooted. So We got in this Pipo M1. Nice unit for the price. I rooted it via VonDroid-Root and changed the default storage location from the ROM to the internal storage. I let the battery die on it to test battery life, now it will not charge. Two chargers and it never seems to detect a charger, and will not charge. Just boots, shuts down, and repeats. Anyone have any thoughts or Ideas?
Here is the Root script that I ran on it.
Code:
echo off
cls
echo *---* VonDroid.com N101 II Root Tool based on work by sunnydavid *---*
echo --- Plug in your device, make sure debugging is enabled in Developer Options
echo --- This script will now copy files over to your N101 II
echo.
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
echo --- Reboot 1/3 - Press Space Bar once the device has rebooted
pause
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
echo --- Reboot 2/3 - Press Space Bar once the device has rebooted
pause
adb shell id
echo --- If the ID shows as 0/root then continue, otherwise CTRL+C to cancel and start over
pause
adb remount
adb push su /system/bin/su
adb shell chown root.shell /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chown root.shell /system/bin/busybox
adb shell chmod 0755 /system/bin/busybox
echo --- Installing SuperSU
adb shell chown root.root /system/app/SuperSU.apk
adb shell chmod 0644 /system/app/SuperSU.apk
adb push RootExplorer.apk /system/app/RootExplorer.apk
adb shell chown root.root /system/app/RootExplorer.apk
adb shell chmod 0644 /system/app/RootExplorer.apk
echo Completing Root
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
echo echo --- Reboot 3/3 - Your N101 II should now be rooted
pause
echo on
i cant install su in system i test all many option and still cant please tell me
stargam said:
i cant install su in system i test all many option and still cant please tell me
Click to expand...
Click to collapse
Try this
Code:
adb devices
adb disable-verity
adb reboot
adb devices
adb shell "mkdir -p /data/local/tmp > 2/dev/null"
adb push c:\su /data/local/tmp > nul
adb shell "chmod 0777 /data/local/tmp/su"
adb shell "-c '/data/local/tmp/su'"
adb shell "setenforce 0"
adb shell "cd /"
adb shell "mount -o rw,remount -t auto /system"
adb shell "cp /data/local/tmp/su /system/bin"
adb shell "mount -o ro,remount -t auto /system"
adb reboot
adb devices
adb enable-verity
adb reboot
Ok I try
jwoegerbauer said:
Try this
Click to expand...
Click to collapse
When I test adb "mkdir-p/data/local/tmp>2/dev/null" he say no such file or directory
stargam said:
When I test adb "mkdir-p/data/local/tmp>2/dev/null" he say no such file or directory
Click to expand...
Click to collapse
1. I think you forgot to type a simple "space" between Command: "mkdir -p" and Dirname: "data/local/tmp > 2 /dev/null"
2. And the last part "> 2 /dev/null" means redirect stdout (or error stream) and ignore it.
Conclusion, maybe just a typo? or err. mssge isn't what you think --> redirection made it dissappear.
Hopefully this works...
otherwise use this code:
adb devices
adb shell "mkdir -p /data/local/tmp" 2>nul >nul
adb shell "chmod 0755 /data/local/tmp"
adb push C:\su /data/local/tmp > nul
adb shell "chmod 0777 /data/local/tmp/su"
adb shell "/data/local/tmp/su -c 'cd / && mount -o rw,remount -t auto /system'"
adb shell "cp /data/local/tmp/su /system/bin"
adb shell "/data/local/tmp/su -c 'setprop ro.build.type user-debug'"
adb reboot
Click to expand...
Click to collapse
Cheerz!
webbex said:
1. I think you forgot to type a simple "space" between Command: "mkdir -p" and Dirname: "data/local/tmp > 2 /dev/null"
2. And the last part "> 2 /dev/null" means redirect stdout (or error stream) and ignore it.
Conclusion, maybe just a typo? or err. mssge isn't what you think --> redirection made it dissappear.
Hopefully this works...
otherwise use this code:
Cheerz!
Click to expand...
Click to collapse
Thanks it work ?