OK i got given a file to supposedly root a phone and without thinking to question it i went along and ran it
The root did work but it has now seemed to have enabled dual sim options on the phone, but the phone no longer detects the sim in slot 1 or 2 software side.
As android was booting i got the updating android message and then seen the 2 sim slots near the clock
Can't figure out what it's done but heres the batch file after changing the extension from exe to rar
Code:
ÿþ::%%a %%a
ECHO OFF
TITLE ÖÐÐËV956 Ò??üROOT???ß By ?ã?úÈ?-?ÁÄ?Ö?ÐÇ
color 3f
:STARTS
CLS
ECHO. ÖÐÐËV956 Ò??üROOT???ß
ECHO. =============================================================================
ECHO. ??Òâ?º
ECHO. 1.ÇëÏÈ????ºÃÊÖ?úÇý??
ECHO.
ECHO. 2.ϵÍ?ÉèÖÃ----???ª??ÕßÑ?Ïî---???ª??ÕßÑ?Ïî ?ò?ª----??USBµ?ÊÔ ??Ñ?
ECHO.
ECHO. 3.ROOTÊ?ÊÖ?úÓ???ÓÚ?ª?ú??Ì???Çë?Ø?ÕµçÄÔ?˵ÄÊÖ?ú?ÜÀíÈí?þ
ECHO.
ECHO. 4.ROOTÇ???Ö?µç?صçÁ?ÔÚ ?µ???? ÒÔÉÏ????ÇÒµçÄÔÕýÈ?????V956µÄÇý????
ECHO. Õû?ö?ý?ÌV956??ÖØÆôÁ??Î
ECHO.
ECHO.
ECHO. ??ÊõÖ??Ö?º?ÁÄ?Ö?ÐÇ
ECHO.
ECHO. ??Ó??ÃÎÊ?ã?úÈ?ÂÛÌ??ºwww.gaojiquan.com
ECHO. =============================================================================
pause
:ROOT
CLS
adb kill-server >NUL 2>NUL
ECHO. --- µÈ?ýÉè??
ECHO. Èç?û??ÔÚÕâ?ß:
ECHO. ÇëÈ???ÒÑ?ò?ªµ?ÊÔ?òÕß????Çý??
adb wait-for-device >NUL 2>NUL
ECHO. --- ??ÏÖÉè??
ECHO. ÉÔºóÊÖ?ú?á?øÈëfastboot
adb reboot bootloader
ECHO. --- µÈ?ýÉè??
ECHO ***************************************************************************
ECHO * Èç?ûÒ?Ö???ÔÚ??waiting for device?? *
ECHO * ÇëÔÚ?ËÊ?ÓÃÍã???Ô?òÕßÊÖ?úÖúÊÖÁ??Ó *
ECHO * ?áÌáÊ?ÏÂÔØ??????Çý?? *
ECHO ***************************************************************************
fastboot boot Superboot.img
ECHO. --- ÊÖ?úÕýÔÚÖØÆô??µÚ1?Î????2?Î??????
ECHO. ÖØÆôÍê?ɺó?á?Ô???ÌÐø
ECHO. --- µÈ?ýÉè??
ping 127.0.0.1 -n 15 >NUL
adb kill-server >NUL 2>NUL
adb wait-for-device >NUL 2>NUL
ping 127.0.0.1 -n 5 >NUL
ECHO. --- ??ÏÖÉè????ROOTÖÐ
adb remount
adb shell rm /system/bin/su >NUL 2>NUL
adb shell rm /system/xbin/su >NUL 2>NUL
adb shell rm /system/app/Superuser.apk >NUL 2>NUL
adb shell rm /system/app/superuser.apk >NUL 2>NUL
adb push su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chown 0.0 /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
ECHO. --- ÊÖ?úÕýÔÚÖØÆô??µÚ2?Î????2?Î??????
ECHO. --- ÖØÆôÍê?ɺó??ROOTÍê?É
adb reboot
adb kill-server >NUL 2>NUL
ECHO.
ECHO.
ECHO. ??ÈÎÒâ?üÍË?ö?ÌÐò...
pause >NUL
EXIT
any help at all, never normally so naive but got stupid for all of 30 seconds
ando_uk said:
OK i got given a file to supposedly root a phone and without thinking to question it i went along and ran it
The root did work but it has now seemed to have enabled dual sim options on the phone, but the phone no longer detects the sim in slot 1 or 2 software side.
As android was booting i got the updating android message and then seen the 2 sim slots near the clock
Can't figure out what it's done but heres the batch file after changing the extension from exe to rar
Code:
ÿþ::%%a %%a
ECHO OFF
TITLE ÖÐÐËV956 Ò??üROOT???ß By ?ã?úÈ?-?ÁÄ?Ö?ÐÇ
color 3f
:STARTS
CLS
ECHO. ÖÐÐËV956 Ò??üROOT???ß
ECHO. =============================================================================
ECHO. ??Òâ?º
ECHO. 1.ÇëÏÈ????ºÃÊÖ?úÇý??
ECHO.
ECHO. 2.ϵÍ?ÉèÖÃ----???ª??ÕßÑ?Ïî---???ª??ÕßÑ?Ïî ?ò?ª----??USBµ?ÊÔ ??Ñ?
ECHO.
ECHO. 3.ROOTÊ?ÊÖ?úÓ???ÓÚ?ª?ú??Ì???Çë?Ø?ÕµçÄÔ?˵ÄÊÖ?ú?ÜÀíÈí?þ
ECHO.
ECHO. 4.ROOTÇ???Ö?µç?صçÁ?ÔÚ ?µ???? ÒÔÉÏ????ÇÒµçÄÔÕýÈ?????V956µÄÇý????
ECHO. Õû?ö?ý?ÌV956??ÖØÆôÁ??Î
ECHO.
ECHO.
ECHO. ??ÊõÖ??Ö?º?ÁÄ?Ö?ÐÇ
ECHO.
ECHO. ??Ó??ÃÎÊ?ã?úÈ?ÂÛÌ??ºwww.gaojiquan.com
ECHO. =============================================================================
pause
:ROOT
CLS
adb kill-server >NUL 2>NUL
ECHO. --- µÈ?ýÉè??
ECHO. Èç?û??ÔÚÕâ?ß:
ECHO. ÇëÈ???ÒÑ?ò?ªµ?ÊÔ?òÕß????Çý??
adb wait-for-device >NUL 2>NUL
ECHO. --- ??ÏÖÉè??
ECHO. ÉÔºóÊÖ?ú?á?øÈëfastboot
adb reboot bootloader
ECHO. --- µÈ?ýÉè??
ECHO ***************************************************************************
ECHO * Èç?ûÒ?Ö???ÔÚ??waiting for device?? *
ECHO * ÇëÔÚ?ËÊ?ÓÃÍã???Ô?òÕßÊÖ?úÖúÊÖÁ??Ó *
ECHO * ?áÌáÊ?ÏÂÔØ??????Çý?? *
ECHO ***************************************************************************
fastboot boot Superboot.img
ECHO. --- ÊÖ?úÕýÔÚÖØÆô??µÚ1?Î????2?Î??????
ECHO. ÖØÆôÍê?ɺó?á?Ô???ÌÐø
ECHO. --- µÈ?ýÉè??
ping 127.0.0.1 -n 15 >NUL
adb kill-server >NUL 2>NUL
adb wait-for-device >NUL 2>NUL
ping 127.0.0.1 -n 5 >NUL
ECHO. --- ??ÏÖÉè????ROOTÖÐ
adb remount
adb shell rm /system/bin/su >NUL 2>NUL
adb shell rm /system/xbin/su >NUL 2>NUL
adb shell rm /system/app/Superuser.apk >NUL 2>NUL
adb shell rm /system/app/superuser.apk >NUL 2>NUL
adb push su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chown 0.0 /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
ECHO. --- ÊÖ?úÕýÔÚÖØÆô??µÚ2?Î????2?Î??????
ECHO. --- ÖØÆôÍê?ɺó??ROOTÍê?É
adb reboot
adb kill-server >NUL 2>NUL
ECHO.
ECHO.
ECHO. ??ÈÎÒâ?üÍË?ö?ÌÐò...
pause >NUL
EXIT
any help at all, never normally so naive but got stupid for all of 30 seconds
Click to expand...
Click to collapse
any ideas anyone?
nvm figured it out
the superboot.img messed up the radio, factory reset solved the problem
Related
I've tried just about every root method I've seen for this phone... with one click root I get this error
deleting all yo ****
error: protocol fault (no status)
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Copying files onto phone...
error: device not found
error: device not found
error: device not found
error: device not found
Setting permissions...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Installing busybox...
error: device not found
Cleaning up files...
error: device not found
error: device not found
"You should have root!"
Press any key to continue . . .
I've downloaded the drivers provided in the forums but still no luck... Has anyone else had/fixed this issue??
I had problems like this before so I modified the root batch program.
Right click on the root.bat and choose edit. Ctrl + A to select all and then backspace to delete all the text. Copy this into there and save. All I did was put multiple pauses where the phone needed to reboot so hit space bar whenever your phone successfully is at your home screen. I like to give it a little bit of time to load and what not. Let me know your outcome.
Code:
@echo off
echo based off bliss' moto exploit for the droid 3 published here http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
cls
color 0A
echo.
echo.
echo.
echo.
echo.
echo.
echo.
echo.
echo The Android Creative Syndicate
echo.
echo Presents to you
ping -n 2 127.0.0.1 > nul
cls
echo.
echo.
echo.
echo.
echo.
echo.
echo.
color 0C
echo One Click Root
echo for the Moto Photon 4G
ping -n 2 127.0.0.1 > nul
color 0A
echo.
echo.
echo Special shoutout to
echo.
echo. Bliss
echo.
echo.
echo.
pause
cls
echo.
echo.
echo.
echo.
echo.
echo.
echo.
echo You need to enable usb debugging first
echo Go to settings - applications - development
color 0A
ping -n 2 127.0.0.1 > nul
color 0C
ping -n 2 127.0.0.1 > nul
color 0C
echo.
echo.
pause
cls
echo.
echo.
echo.
echo.
echo.
echo.
echo.
cls
adb.exe kill-server
adb.exe start-server
COLOR E0
echo Getting temp root
pause
adb shell rm /data/local/12m.bak > NUL
adb shell mv /data/local/12m /data/local/12m.bak > NUL
adb shell ln -s /data /data/local/12m > NUL
echo Will Reboot phone
pause
adb reboot
echo.
echo RE-boot-en
COLOR 47
adb kill-server > NUL
adb wait-for-device > NUL
adb wait-for-device > NUL
echo.
echo Hackin Things
COLOR A0
pause
adb shell rm /data/local/12m > NUL
adb shell mv /data/local/12m.bak /data/local/12m > NUL
adb shell rm /data/local.prop.bak > NUL
adb shell mv /data/local.prop /data/local.prop.bak > NUL
adb shell echo "ro.sys.atvc_allow_netmon_usb=0" ^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_netmon_ih=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_res_core=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_res_panic=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_all_adb=1" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_all_core=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_efem=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_bp_log=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_ap_mot_log=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_gki_log=0" ^>^> /data/local.prop
adb reboot
echo.
echo deleting all yo ****
COLOR E0
pause
adb.exe wait-for-device > NUL
adb.exe wait-for-device > NUL
adb.exe remount
COLOR B0
adb.exe push rootsetup /data/local/tmp/rootsetup
adb.exe shell chmod 755 /data/local/tmp/rootsetup
adb.exe shell /data/local/tmp/rootsetup
adb.exe shell rm /data/local/tmp/rootsetup
adb.exe shell sync
echo Copying files onto phone...
adb.exe push su /system/xbin/su
adb.exe push Superuser.apk /system/app/Superuser.apk
adb.exe push busybox /system/xbin/busybox
adb.exe push remount /system/xbin/remount
echo Setting permissions...
adb.exe shell chmod 755 /system/xbin/busybox
adb.exe shell chmod 755 /system/xbin/remount
adb.exe shell chown root.shell /system/xbin/su
adb.exe shell chmod 6755 /system/xbin/su
adb.exe shell ln -s /system/xbin/su /system/bin/su
echo Installing busybox...
adb.exe shell /system/xbin/busybox --install -s /system/xbin
echo Cleaning up files...
@ping 127.0.0.1 -n 6 -w 1000 > nul
adb.exe shell rm /data/local/tmp/*
adb.exe reboot
echo "You should have root!"
COLOR D0
ping -n 1 127.0.0.1 > nul
COLOR 90
ping -n 1 127.0.0.1 > nul
COLOR B0
ping -n 1 127.0.0.1 > nul
COLOR A0
ping -n 1 127.0.0.1 > nul
COLOR E0
ping -n 1 127.0.0.1 > nul
COLOR C0
ping -n 1 127.0.0.1 > nul
COLOR D0
ping -n 1 127.0.0.1 > nul
COLOR 90
ping -n 1 127.0.0.1 > nul
COLOR B0
ping -n 1 127.0.0.1 > nul
COLOR A0
ping -n 1 127.0.0.1 > nul
COLOR E0
ping -n 1 127.0.0.1 > nul
COLOR C0
ping -n 1 127.0.0.1 > nul
COLOR D0
ping -n 1 127.0.0.1 > nul
COLOR 90
ping -n 1 127.0.0.1 > nul
COLOR B0
ping -n 1 127.0.0.1 > nul
COLOR A0
ping -n 1 127.0.0.1 > nul
COLOR E0
ping -n 1 127.0.0.1 > nul
COLOR C0
echo.
pause
adb.exe kill-server
goto:eof
Ok I'm going to try this today
Sent from my MB855 using xda premium
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
hi.. all..
I am stuck in bootloop after failed system update.. there's no stock rom and no custom recovery available..
device is coolpad dazen 1 (8297L-100)
I have dumped system.img , boot.img and recovery.img
i want to restore system.img but fastboot flash command does not work always show... waiting for device..
but this script works..
taskkill /f /im "adb.exe" >nul 2>nul
taskkill /f /im "tadb.exe" >nul 2>nul
taskkill /f /fi "imagename eq wandoujia*" >nul 2>nul
taskkill /f /im "AndroidInterface.exe" >nul 2>nul
taskkill /f /im "Android PC Suite.exe" >nul 2>nul
taskkill /f /im "360MobileMgr.exe" >nul 2>nul
taskkill /f /im "qitu_adb.exe" >nul 2>nul
echo. Tat nguon, an giu Volume+ dong thoi cam cap USB
adb An nut Volume+
adb reboot bootloader
fastboot oem unlock
fastboot boot recovery_7to.img
ping -n 12 127.0>nul
adb push recovery_7to.img /tmp/
echo.
echo.
adb shell "dd if=/tmp/recovery_7to.img of=/dev/block/mmcblk0p28"
adb shell "rm -r /tmp/recovery_7to.img"
adb kill-server >nul 2>nul
pause>nul
goto MENU
i had used this script to boot in recovery temporarily when i was stuck in bootloader..
can i use this script with some changes to flash system.img.
i don't remember which partition was system /dev/block/mmcblk0p26 or 25 or somthing.
will it require flash_image file..
thanks.. plz reply...