Related
Too many threads... too many sites and PC options.
Here's my situation:
Droid X
Used the leak update... running 2.2 now.
Use a MAC. And have Terminal app on DX.
Have SBF file for 2.1 stock, have ZIP files of rooted 2.2's
Dont have custom recovery.
Dont care much about warranty or OTA... just want to be able to apply ZIPs.
I need to somehow either root my DX with Mac or Terminal app. Or flash the SBF to bring things back to 2.1.
Not sure what to do??? Please please help.
I am not familiar with terminal commands...so if you leave instructions that would be great.
-Roman
You follow the same ADB commands, more or less. Why not try something like Universal AndRoot though? Then you could just skip over it.
But, if you need to sbf, I would *think* you follow the Linux instructions.
1) download sbf_flash & sbf file
Code:
cd directory/where/these/are/located
./sbf_flash SBFfileLOCATION
The only way to SBF is to run windows through bootcamp or this http://www.droidforums.net/forum/droid-hacks/38671-flashing-sbf-mac.html . I am in the same boat as you luckily my girlfriend has a dell running Windows. You should also be able to root 2.2 using the Droid 2 method posted in this section http://forum.xda-developers.com/showthread.php?t=766767. I assume you have the SDK downloaded already? The Linux directions does not work for Mac.
x.v_ said:
You follow the same ADB commands, more or less. Why not try something like Universal AndRoot though? Then you could just skip over it.
I TRIED THAT, BUT THERE IS SOME ERROR THAT POPS UP... CAN'T DO IT. 2.2 ISN'T SUPPORTED... I THINK IT'S JUST FOR 2.1..
But, if you need to sbf, I would *think* you follow the Linux instructions.
1) download sbf_flash & sbf file
Code:
cd directory/where/these/are/located
./sbf_flash SBFfileLOCATION
Click to expand...
Click to collapse
SO THAT EASY? JUST TWO COMMAND LINES?
So, if I put the SBF on my desktop it would be:
cd desktop (enter)
./sbf_flash fullSBFfilename.sbf (enter)
???????
romanvail said:
SO THAT EASY? JUST TWO COMMAND LINES?
So, if I put the SBF on my desktop it would be:
cd desktop (enter)
./sbf_flash fullSBFfilename.sbf (enter)
???????
Click to expand...
Click to collapse
Running ADB with Mac OSX and therefore rooting with the mac is EASY. Just make sure you have the Android SDK installed on your Mac. Make sure in your .bash_profile you have the path set to the tools directory of your SDK folder.
Since I can't tell if you have all this down, I'll give you the instructions on setting up adb on the mac (using terminal), then give you the directions I followed on rooting my Droid X from OSX (I am running 2.2 leaked).
Essentially follow these instructions (taken from tjrocks91 on droidforum... I'd link, but I am not yet allowed to post outside links on this forum):
1. Download the Android SDK for Mac OSX. (google it)
2. Extract the zip file to any destination on your Mac. *Remember its path!*
In the AndroidSDK folder, there will be a folder named “tools”. We will be adding this folder to the path on Mac OSX. For this example, extract to your home folder (the folder that contains the desktop, documents, etc. folders)
3. To do this click on Finder > Go > Utilities > Terminal.
4. Type in without quotations “cd ~/”
5. Next, type "touch .bash_profile" to create your new bash or otherwise known path file.
6. Next, type "open -e .bash_profile" to open it in TextEdit. A TextEdit window will open, copy and past this into that window, substituting <username> for your username on OSX:
export PATH=${PATH}:/Users/<username>/AndroidSDK/tools
7. Save the file and close the window.
8. Repeat steps 5 through 7, but replace .bash_profile with ".bashrc" (without the quotes)
9. ADB should be ready to go. Make sure that your Droid X is set to "charge only" when connected via USB, and that you have debug mode set to on in your Android settings (settings>applications>development> USB Debugging)
10. In terminal, type (without the quotes): "adb devices". You should see a return that gives a list of devices attached. If the daemon wasn't started yet, this will do it. After that, type "adb shell" to enter adb.
11. After that, the adb commands are ALL the same on any platform, just make adjustments for different file systems when moving things TO your phone when using the command prompt (and not in the adb shell itself, but using adb commands). OSX follows unix/linux file structure, but not always the linux/unix file arrangement (but pretty darn close, since it is a Unix BSD GUI).
Now onto rooting your DX running 2.2. I've attached the file I used. It is a .rar files, so you will need a .rar extractor. I found a nice free one on the net called UnrarX. Google it, get it. Its free, it works. I will give instructions assuming you have them. These instructions come from karnovaran here on XDA. THey are for the droid 2, but work for the Droid X as well. i will translate them into instructions that can be followed verbatim on Mac (as the instructions he gave are meant for those doing this through the command prompt in windows).
1. Extract the contents of the attached file to your sdk tools folder
2. Open a terminal window and navigate to your sdk tools folder. if you put the sdk folder in your home folder, then the command and path you should enter from the terminal should be something like this:
cd AndroidSDK/tools
3. Now the process is as follows (follow EXACTLY, making sure you are faithful to YOUR file paths). I'm copying almost verbatim from karnovaran:
- adb devices (to verify the connection)
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (this WILL take a while, so don't TOUCH ANYTHING on your phone. Just go grab a beer and relax until the proces kicks you back out to the tools folder in terminal)
- adb kill-server
- cd <wherever-your-sdk-tools-folder-is>
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
This got me root on my DX and I did this on OSX no problem. The only PC I have that is functional is my laptop for work and because of the content on it and security procedures, though I could do android hacking with it, I will not, so I'm stuck with using my Mac. Thing is that it really is NOT hard. Commands are almost exactly as in Linux/Unix, and OSX terminal runs bash, which is quite versatile (more commands than busybox, iirc) in and of itself. And getting mac root access is bloody easy using sudo if you need it (otherwise, don't use it).
I hope this helps. Have fun.
many steps.... but will go slowly.
Thank you!!!!
Many steps, but they work!
SirBrass said:
Running ADB with Mac OSX and therefore rooting with the mac is EASY. Just make sure you have the Android SDK installed on your Mac. Make sure in your .bash_profile you have the path set to the tools directory of your SDK folder.
Since I can't tell if you have all this down, I'll give you the instructions on setting up adb on the mac (using terminal), then give you the directions I followed on rooting my Droid X from OSX (I am running 2.2 leaked).
Essentially follow these instructions (taken from tjrocks91 on droidforum... I'd link, but I am not yet allowed to post outside links on this forum):
1. Download the Android SDK for Mac OSX. (google it)
2. Extract the zip file to any destination on your Mac. *Remember its path!*
In the AndroidSDK folder, there will be a folder named “tools”. We will be adding this folder to the path on Mac OSX. For this example, extract to your home folder (the folder that contains the desktop, documents, etc. folders)
3. To do this click on Finder > Go > Utilities > Terminal.
4. Type in without quotations “cd ~/”
5. Next, type "touch .bash_profile" to create your new bash or otherwise known path file.
6. Next, type "open -e .bash_profile" to open it in TextEdit. A TextEdit window will open, copy and past this into that window, substituting <username> for your username on OSX:
export PATH=${PATH}:/Users/<username>/AndroidSDK/tools
7. Save the file and close the window.
8. Repeat steps 5 through 7, but replace .bash_profile with ".bashrc" (without the quotes)
9. ADB should be ready to go. Make sure that your Droid X is set to "charge only" when connected via USB, and that you have debug mode set to on in your Android settings (settings>applications>development> USB Debugging)
10. In terminal, type (without the quotes): "adb devices". You should see a return that gives a list of devices attached. If the daemon wasn't started yet, this will do it. After that, type "adb shell" to enter adb.
Last login: Tue Sep 14 09:12:34 on console
Roman-Vails-Computer:~ romanvail$ cd ~/
Roman-Vails-Computer:~ romanvail$ touch .bash_profile
Roman-Vails-Computer:~ romanvail$ open -e .bash_profile
Roman-Vails-Computer:~ romanvail$ touch .bashrc
Roman-Vails-Computer:~ romanvail$ open -e .bashrc
Roman-Vails-Computer:~ romanvail$ adb devices
-bash: adb: command not found
Roman-Vails-Computer:~ romanvail$
*****DOESNT WORK FOR ME*****
Click to expand...
Click to collapse
Do you have the path to adb set properly?
Sent from my DROIDX using XDA App
SirBrass said:
Do you have the path to adb set properly?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yeah this would be your problem.
@OP,
yes, it would be just that easy IF AND ONLY IF the linux commands apply to macs as well. Which I have NO IDEA on. so proceed at your own risk :z
i finally figured it out... saw another post....
here's what worked:
./
Here's my log in case anyone else needs is:
Roman-Vails-Computer:~ romanvail$ adb
-bash: adb: command not found
Roman-Vails-Computer:~ romanvail$ cd/Users/romanvail/android-sdk-mac_x86/tools -bash: cd/Users/romanvail/android-sdk-mac_x86/tools: No such file or directory
Roman-Vails-Computer:~ romanvail$ cd /Users/romanvail/android-sdk-mac_x86/tools Roman-Vails-Computer:tools romanvail$ ./adb
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Roman-Vails-Computer:tools romanvail$ adb devices
-bash: adb: command not found
Roman-Vails-Computer:tools romanvail$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015D61C60A003017 device
Roman-Vails-Computer:tools romanvail$ ./adb push Superuser.apk /sdcard/Superuser.apk
1059 KB/s (27688 bytes in 0.025s)
Roman-Vails-Computer:tools romanvail$ ./adb push su /sdcard/su
1802 KB/s (26248 bytes in 0.014s)
Roman-Vails-Computer:tools romanvail$ ./adb push busybox /sdcard/busybox
1918 KB/s (1926944 bytes in 0.980s)
Roman-Vails-Computer:tools romanvail$ ./adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
726 KB/s (5392 bytes in 0.007s)
Roman-Vails-Computer:tools romanvail$ ./adb shell
$ cd data/local/tmp
$ chmod 0755 rageagainstthecage-arm5.bin
$ ./rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3815, 3815}
[*] Searching for adb ...
[+] Found adb as PID 2846
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$ Roman-Vails-Computer:tools romanvail$ ./adb kill-server
Roman-Vails-Computer:tools romanvail$ ./adb kill-server
* server not running *
Roman-Vails-Computer:tools romanvail$ cd /Users/romanvail/android-sdk-mac_x86/tools
Roman-Vails-Computer:tools romanvail$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXXXXXX device
Roman-Vails-Computer:tools romanvail$ ./adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# cp /sdcard/busybox /system/bin/busybox
# chmod 4755 /system/bin/su
# chmod 4755 /system/bin/busybox
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
Roman-Vails-Computer:tools romanvail$ exit
logout
[Process completed]
Now that's odd. I only get problems when I try and use ./ just regular "adb" works on my machine.
SirBrass said:
Now that's odd. I only get problems when I try and use ./ just regular "adb" works on my machine.
Click to expand...
Click to collapse
Yea pretty weird... I use OSX 10.5.8
Intel machine... so, it's weird, but IT DID WORK.
romanvail said:
Yea pretty weird... I use OSX 10.5.8
Intel machine... so, it's weird, but IT DID WORK.
Click to expand...
Click to collapse
There's your problem.... you're using leopard . I'm using 10.6.3. Love it. They did well with this new OS version (for those who don't know... the difference to users between Leopard and Snow Leopard for OSX folks is like the diff between Eclair and FroYo... the former is good, but the later far exceeds it under the hood though still remaining almost the same on the front end).
And obviously that means I'm running an intel machine as well. 2008 iMac 20".... 2.66 Ghz Core 2 Duo. Just your regular, nothing-special iMac.
I thought Macs were supposed to be user friendly?
*snicker*
Sent from my DROIDX using XDA App
Will this method work for a Droid X on Android 2.3.4 Gingerbread and with build # 4.5.1_57_DX8-51 Also is there a new one click type solution by now on a Mac?
Hi all,
I want to root my U8800 under a Linux-OS. Is there a recommended and safe way to do that? Currently my phone ist flashed with V100R001C00B528G001.
I know these threads, but I am unsure if the described methods in these threads are act up on my Linux-System.
http://forum.xda-developers.com/showthread.php?t=1420728
http://forum.xda-developers.com/showthread.php?t=1423422
Many thanks in advance,
Ponder
So, after some days of reading helpfull threads in this forum I found a way to root my u8800 under my favorite OS archlinux To get access to the smartphone it's important to install some packages previously:
Install some packages from the ArchLinux reposities:
pacman -S abs
pacman -S base-devel
pacman -S jdk7-openjdk
pacman -S openal
pacman -S swt
pacman -S libstdc++5
pacman -S libmtp
Download some files from the AUR "ArchLinux User-Community Repository":
(Don't do this as root, do this as normal user and save the packages in ~/android)
android-sdk
android-sdk-platform-tools
android-udev
Create packages (via makepkg) from the three files above and install them via pacman.
https://wiki.archlinux.org/index.php/AUR
After installing the three packages put your user to the group adbusers
Code:
gpasswd -a <your user> adbusers
Figure out the device IDs from u8800:
lsusb
Code:
Bus 001 Device 002: ID 12d1:1037 Huawei Technologies Co., Ltd. Ideos
Adding udev rules for the u8800 device:
There is a template file called "51-android.rules" in the folder "android-udev". Search for the String "Huawei" and replace [VENDOR ID] and [PRODUCT ID] with yours. Copy these rules into /etc/udev/rules.d/51-android.rules:
Code:
# Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666", GROUP="adbusers"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", ATTR{idProduct}=="1037", SYMLINK+="android_adb"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", ATTR{idProduct}=="1037", SYMLINK+="android_fastboot"
Then, to reload your new udev rules, execute:
Code:
# udevadm control --reload-rules
Does It Work? After you have setup the udev rules, unplug your device and replug it. After running:
Code:
$ adb devices
you should see something like:
Code:
List of devices attached
404D8E65F146 device
Download B528_ROOT.rar. I found it in this thread (#7):
http://forum.xda-developers.com/showthread.php?t=1533922
Prepare your phone for rooting:
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) Download B528_ROOT.rar (not SuperOneClick v2.3.3).
6) Plug your U8800 into your computer but DO NOT mount SD Card.
http://forum.xda-developers.com/showthread.php?t=1420728
7) Extract B528_ROOT.rar and open the file "B528_root.bat" with an editor.
8) Open a terminal as normal user and change into the directory with the file "B528_root.bat".
9) Copy the following commands step by step into the terminal.
Code:
adb wait-for-device
adb reboot-bootloader
fastboot boot boot.img
fastboot reboot
adb wait-for-device
at this point it seems the procedure get stuck. Try the next commands... :-)
adb remount -t yaffs2 /dev/block/mtdblock3 /system
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 push makespace /data/local/tmp/.
adb shell "chmod 777 /data/local/tmp/makespace"
adb shell "./data/local/tmp/makespace"
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"
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 "cd /data/local/tmp/; rm *"
adb reboot
Now, your smartphone should be rooted.
Some helpfull threads:
http://forum.xda-developers.com/showthread.php?t=1321582
http://forum.xda-developers.com/showthread.php?p=20869699
http://forum.xda-developers.com/showthread.php?p=18615502
http://forum.xda-developers.com/showthread.php?t=1423422
https://wiki.archlinux.org/index.php/Android
Out of the 4 or so times I've successfully rooted the damn thing, I still am not 100% what I am doing right. Since each time I end up with a headache I've written myself a guide which seems to be almost always wrong along somewhere. I'm curious how wrong my latest discovery is. It seems when I use the 2.2.2 Android sbf I can't follow the usual directions listed on the wiki page. I need to run psneuter from another phone's root hack to give me "busybox, psneuter and su. Then I go back to install the bootmenu. Am I missing anything? Cheers:
II.C. Rooting
[EDIT:: It seems for Froyo 2.2.2 ("CEE sbf") you will probably need to follow the psneuter instructions:
http://wiki.cyanogenmod.org/wiki/LG_G2x:_Full_Update_Guide
Then go back and install bootmenu:
http://wiki.cyanogenmod.org/wiki/Motorola_Defy:_Full_Update_Guide ]
Is there anything else?
II.C.1. Connect Defy via USB and set it to "None." Open up terminal and begin pushing the files over:
Code:
$ adb push $PATH/TO/busybox /data/local/
i.e.
Code:
$ adb push /Users/kg/Android/android-sdk-macosx/platform-tools/busybox /data/local/
Push psneuter:
Code:
$ adb push $PATH/TO/psneuter /data/local/
… and su:
Code:
$ dab push $PATH/TO/su /data/local/
Now to change some permissions
Code:
$ adb shell chmod 777 /data/local/busybox
Code:
$ adb shell chmod 777 /data/local/psneuter
Enter into Defy and run psneuter by typing:
Code:
$ adb shell
Code:
$ /data/local/psneuter
Once the command finishes enter:
Code:
$ adb shell
"$" should now be "#."
Code:
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Code:
# mkdir /system/xbin
Should the last command say, "mkdir failed for /system/xbin, File exists" let it be. It tried to create a directory but one with that name already exists. Just move along:
Code:
# /data/local/busybox cp /data/local/su /system/xbin/su
Code:
# chown 0:0 /system/xbin/su
Code:
# chmod 6755 /system/xbin/su
Code:
# ln -s /system/xbin/su /system/bin/su
Code:
# exit
One last push:
Code:
$ adb push $PATH/TO/Superuser.apk /system/app/Superuser.apk
Code:
$ adb reboot
Fin.
II.C.2.To Install the Bootmenu by connecting the Defy via USB, allow memory card access.
Drag and drop the bootmenu folder into the SD card
Rename it "bootmenu"
Eject the SD card and on the Defy set the USB mode to "None."
In Terminal start up adb:
Code:
$ adb shell
Now give it SuperUser permissions, enter the following then unlock the screen on the defy and select "allow":
Code:
$ su
The prompt "$" should now be "#."
Code:
# cp -R /sdcard/bootmenu /data/bootmenu
Code:
# cd /data/bootmenu
Code:
# chmod 755 *
Just let this command run the script to the end (when the user prompt, # is given)
Code:
# ./install.sh
Once finished, don't reboot yet:
Code:
# rm -R /data/bootmenu
Now do so:
Code:
# reboot
If you want to see if it worked, upon the first boot animation/logo watch for the LED to flash blue after a good few seconds. Press Volume-Down upon seeing the light. You should be in the bootmenu!
Hello everyone...
I have a Motorola RAZR 201M(XT902) in Japan and use Motofail2go to root it.But it doesn't work.
(follow http://forum.xda-developers.com/showthread.php?p=32889627)
I installed Sudoku.apk and push the motofail2go to the device(also su,Superuser.apk,busybox).
when
$ run-as com.motorola.bug2go /data/local/tmp/motofail2go prep2
Here is the error message:
"run-as: exec failed for /data/local/tmp/motofail2go Error: Operation not permitted"
and i try $ run-as com.motorola.bug2go
but error message : "run-as: exec failed"
Anyone help? Thanks...
Sorry buddy. Nothing works. We 201m users are SOL.
Have you tried this?
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Thanks Paul!
No luck with that either. Appreciate the feedback, however.
I hope somebody will study the XT902 root.
goodayoo said:
I hope somebody will study the XT902 root.
Click to expand...
Click to collapse
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Almalieque said:
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Click to expand...
Click to collapse
There some Japanese guys doing some things to try and get root. They are active. The site has a lot of rather unpleasant (read offensive) advertisements. PM if you are interested (its in Japanese)
root
help!!!
Root and Unlocked bootloaders!
Proceed at yor own risk
hungln03 said:
help!!!
Click to expand...
Click to collapse
1)Prep
Android SDKと各種ドライバを導入する。
以下の必要ファイルをC:\***（何でも良い）に配置する。
・XT902_SBMの中身(http://www1.axfc.net/uploader/so/2991543 >>125氏)
・su（http://www1.axfc.net/uploader/so/2918729 password：f10d）
・Superuser.apk（in the above downloaded）
・busybox（in the above downnloaded）
201M Plug the phone into the comp
any port will do
2)adb pushで必要ファイルを/data/local/tmp転送
コマンドプロンプトを開く
C:\Users\（ユーザー名） >cd C:\***
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
adb push unlock_security_module /data/local/tmp
adb push break_setresuid /data/local/tmp/
adb push mole-plough-ccsecurity.so /data/local/tmp/
adb push mole-plough-lsm.so /data/local/tmp/
3)unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ chmod 777 *
[email protected]:/data/local/tmp $ ./unlock_security_module
[email protected]:/data/local/tmp $ ./break_setresuid
（unlock_security_moduleが動いてMIYABIとNANDロック解除）
（色々表示されるので↓が出る間で待つ）
Unlocked LSM.
Do setresuid...
OK.
[email protected]:/data/local/tmp #
（#if done correctly temp root should be achieved）
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
4)system putting together su，Superuser.apk，busybox
[email protected]:/data/local/tmp # mount -o rw,remount /system /system
[email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
[email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
[email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
[email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
[email protected]:/data/local/tmp # cd /system/xbin
[email protected]:/system/xbin # chown root.root su
[email protected]:/system/xbin # chown root.root busybox
[email protected]:/system/xbin # chmod 6755 su
[email protected]:/system/xbin # chmod 755 busybox
[email protected]:/system/xbin # mount -o ro,remount /system /system
After the opperation is done it is ok to remove the cable from the pc。
check and see if「SuperSU」was installed if it wasn't download chainfire (su) from the play store
⇒SU --> update
Fro the play store download busybox。
⇒busybox -->update
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
I don't own the 902, but it's good to see this. I know quite a few people have been looking for this. You should start your own thread with the procedures, so it will get more publicity.
Thank u!
thank u so much.!1
sbeaber4 said:
Proceed at yor own risk
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Can you tell me more about this step
Confirm?
Can confirm if the latest instructions have worked for your 201m?
That your rooted and bootloader unlock.
Thanks a bunch!
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
sbeaber4 said:
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
Click to expand...
Click to collapse
Thanks for the feedback.
Still awaiting more confirmation with others. It's a step forward though.
I've had my phone for almost a year now. If I cancel my softbank service or run the contract to the end I want an option to root and unlock the bootloader in the future.
could u provide more friendly filehost?
i can't find the download button there
Root! (temp root that is...)
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Quick Tip
zenstarlight said:
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Click to expand...
Click to collapse
Found that if I a did restart my phone root was lost but I found a quick fix without going through the whole process again.
Just do these steps
unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ ./unlock_security_module
Just enter those three steps then you're back to temp root
Also you can just to a quick reboot with link2sd or any other app that just reboots the android ui. You don't have to enter commands every time you reboot unless it's a full reboot.
Help for Gaigin rooting 201M
sbeaber4 said:
Proceed at yor own risk
...
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
kprower said:
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
Click to expand...
Click to collapse
Once CWM is online you might be able to flash a VZW or Aussie stock ROM. Actually, you could probably flash CM... That'll fix the Japanese popups. Of course, it also could very possibly brick it. Proper precautions must be made... On my tablet at the moment, does anyone know if sbf.droid-developers has 902 images?
Sent from my Nexus 7 using Tapatalk 4
THIS IS THE START THREAD FOR ANY XDA ENTHUSIAST!!keep in mind, that you do all these steps on your own and i am not responsible for any damaged or bricked phone.
So if you dont know what are you doing or are afraid of bricking your device, please dont do this!!!
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!
UNLOCK BOOTLOADER:
-Get/install Alcatel USB driver if Windows. (no need for Mac). FROM HERE, or just connect your idol3 to the computer and from the phone select "cd rom" drive..it will install the drivers automatically
-download the root zip from my GOOGLE DRIVE and unzip it.
-Set USB debugging on in Developer settings (if these are not exposed, go to Settings/About Phone/Build number, and tap 7 times.)
-Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode.
-After that a window on your phone should appear and ask you to allows usb debbuging connection to your attached computer (please also check the box that say something like "always from this computer")
-Open command prompt in direcotry where you have the unzipped files (when using windows in the direcotry hold shift and press the right button on the mouse, it will pop-up a window where you have to select "open command promt here"
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing "alcatel onetouch...powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-To reboot normally: "fastboot -i 0x1bbb reboot"
ROOT USING CUSTOM RECOVERY:
as we have now the custom recovery (TWRP)
-So download supersu.zip from HERE
-Put it on your SD card (or internal memory)
-Flash (or just boot) the custom recovery (you can see the procedure in the thread i linked above) and in recovery install the superSU.zip
-Reboot
ROOT:
-Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode.
-Run the unziped "root.bat" file and select option 1.
-The device will reboot to bootloader,then boot the boot.img which will install the SU and then the device will twice reboot
-check if you have superSU installed, if yes, then You are done.
BACKUP under windows:
-so now you have root rights and you can what ever you want, but first do not forget to backup your device
-for that occasion i made a simple BACKUP_all.bat file
-download the file and place it to the directory, where you extracted the root.zip
-run the bat file it will create a backup folder on external sd card in the phone! extract the system partitions and in the end it copies it to the subdirectory "blocks" in the dir where you ran the bat file.
BE AWARE to share the modemst and persist files because they are device specific!!!
here is the code:
PHP:
@echo BACKUP IDOL3 6045 partitions by DallasCZ
adb shell mkdir /storage/sdcard1/mybckup
echo Press any key to begin
pause >nul
adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/mybckup/modem"
adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/mybckup/tunning"
adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/storage/sdcard1/mybckup/traceability"
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/storage/sdcard1/mybckup/fsc"
adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard1/mybckup/ssd"
adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/storage/sdcard1/mybckup/sbl1"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/storage/sdcard1/mybckup/rpm"
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/storage/sdcard1/mybckup/tz"
adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/storage/sdcard1/mybckup/hyp"
adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/storage/sdcard1/mybckup/modemst1"
adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/storage/sdcard1/mybckup/modemst2"
adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/storage/sdcard1/mybckup/simlock"
adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/storage/sdcard1/mybckup/persistent"
adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/storage/sdcard1/mybckup/splash"
adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/storage/sdcard1/mybckup/tctpersist"
adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/storage/sdcard1/mybckup/hdcp"
adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/mybckup/DDR"
adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/storage/sdcard1/mybckup/fsg"
adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/storage/sdcard1/mybckup/sec"
adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/storage/sdcard1/mybckup/aboot"
adb shell su -c "dd if=/dev/block/mmcblk0p26 of=/storage/sdcard1/mybckup/boot"
adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/storage/sdcard1/mybckup/recovery"
adb shell su -c "dd if=/dev/block/mmcblk0p28 of=/storage/sdcard1/mybckup/system"
adb shell su -c "dd if=/dev/block/mmcblk0p29 of=/storage/sdcard1/mybckup/persist"
adb shell su -c "dd if=/dev/block/mmcblk0p30 of=/storage/sdcard1/mybckup/fota"
adb shell su -c "dd if=/dev/block/mmcblk0p32 of=/storage/sdcard1/mybckup/misc"
adb shell su -c "dd if=/dev/block/mmcblk0p33 of=/storage/sdcard1/mybckup/keystore"
adb shell su -c "dd if=/dev/block/mmcblk0p34 of=/storage/sdcard1/mybckup/config"
@echo BACKUP copied partitions to hard drive
@mkdir blocks
adb pull /storage/sdcard1/mybckup %CD%/blocks/
@echo BACKUP Done!
@echo Press any key to exit
@ECHO OFF
@pause >nul
FOR LINUX USERS:
for unlocking the bootloader see THIS POST by Fankee207
for backup on linux please see THIS POST by Frankee207
and dont forget to thank him. :good:
If someone send me a linux/mac guide i will post it to this post so we have all the info in one thread.
reservation 1
reservation 2
To unlock bootloader on linux, just make sure adb and fastboot are installed
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
on ubuntu based linux for example. No need to install full SDK.
just add sudo before each command
Ex:
Code:
sudo fastboot -i 0x1bbb oem unlock
Should work, but I'have not tried myself since I have not received my idol yet
No need specific drivers. Before beginning, you can run
Code:
adb devices
to make sure your device is correctly detected
Don't forget if problem with adb on linux, run
Code:
sudo adb kill-server
sudo adb start-server
Thnaks you for the backup script. May I share it on french android forum forum.frandroid.com ?
frankee207 said:
Thnaks you for the backup script. May I share it on french android forum forum.frandroid.com ?
Click to expand...
Click to collapse
Of course you can..no wait ...you must!
Awesome it works on dual sim? 6045k? I need to send my ohone to repair the microphone so i will lost the warranty right? I need to wait few months:/
DallasCZ said:
Of course you can..no wait ...you must!
Click to expand...
Click to collapse
thansk you ,I will !
Running both Linux and Windows, I converted your script for Linux usage. Please find it here.
PHP:
echo -e "#### Backup all your idol 3's partitions - DallasCZ & frankee207 @XDA ####\n\n"
echo -e "Please make sure your device is connected\n"
read -p "Press ENTER to continue"
cd ~/
echo -e "/!\ root access must be granted for using adb on linux /!\ \n"
sudo adb kill-server
sudo adb start-server
sudo adb shell mkdir /storage/sdcard1/mybckup/
sudo adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/mybckup/modem"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/mybckup/tunning"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/storage/sdcard1/mybckup/traceability"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/storage/sdcard1/mybckup/fsc"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard1/mybckup/ssd"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/storage/sdcard1/mybckup/sbl1"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/storage/sdcard1/mybckup/rpm"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/storage/sdcard1/mybckup/tz"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/storage/sdcard1/mybckup/hyp"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/storage/sdcard1/mybckup/modemst1"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/storage/sdcard1/mybckup/modemst2"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/storage/sdcard1/mybckup/simlock"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/storage/sdcard1/mybckup/persistent"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/storage/sdcard1/mybckup/splash"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/storage/sdcard1/mybckup/tctpersist"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/storage/sdcard1/mybckup/hdcp"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/mybckup/DDR"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/storage/sdcard1/mybckup/fsg"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/storage/sdcard1/mybckup/sec"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/storage/sdcard1/mybckup/aboot"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p26 of=/storage/sdcard1/mybckup/boot"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/storage/sdcard1/mybckup/recovery"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p28 of=/storage/sdcard1/mybckup/system"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p29 of=/storage/sdcard1/mybckup/persist"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p30 of=/storage/sdcard1/mybckup/fota"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p32 of=/storage/sdcard1/mybckup/misc"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p33 of=/storage/sdcard1/mybckup/keystore"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p34 of=/storage/sdcard1/mybckup/config"
sudo mkdir blocks/
sudo adb pull /storage/sdcard1/mybckup/ ~/blocks/
echo -e "Backup done ! You can find it in ~/blocks/"
read -p "Press ENTER to exit"
exit
You can download the script here: https://mega.nz/#!QtEG3TSb!DJ8N1dVRUYNPOLk8kQj2ggZfx8o5M9whiag5WFfANtc
If you use the script for linux, don't forget to make it executable by running
Code:
sudo chmod +x backup_all_AOTI3.sh
It work on 6045k or not? Thank you for the tutorial
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
Another question we will have problems with a next update?
during the root process, does it really "flash" a boot.img?
from the batch file, it appears we are booting a boot.img, from which we [presumably] push supersu to the system. thanks.
deepasadish said:
during the root process, does it really "flash" a boot.img?
from the batch file, it appears we are booting a boot.img, from which we [presumably] push supersu to the system. thanks.
Click to expand...
Click to collapse
my mistake, of course it only boot to the boot.img
I get device not found on adb and the drivers url isn't working i used the phone usb cd... Drivers
RodrigoIsaac said:
I get device not found on adb and the drivers url isn't working i used the phone usb cd... Drivers
Click to expand...
Click to collapse
you have to install the drivers from the phone mounted as Cd and then enable the usb debugging...
I clicked sevenntimes in debugging mode, I installed thebphone as drivers cd (on pc clicked onbsetup, install) then disconnected and connect again, open prompt in idol3_6045_root folder (shift right click...) wrote adb reboot bootloader. Then appeared not running daemon. Starting it now on pprt 5037 daemon started successfully error:device not found
But the dispositive is connected and can access the files etc... I tried in two diffdifferent pc's. Tank you for your help
you have enable usb debbuging in developer settings, then you have to switch the connect mode feom cd to PTP
Error: device not found
I think the drivers are not installed because when e conect in mtp or ptp it install the drivers again so i unistall the drivers and connect on cd again and install the drivers then i change to mtp and the pc install the drivers automatically if i change to ptp the same thing happens
reboot computer
Iagain the same error :'( i don't know what is going on.
for me worked to download pdanet software, or try to google adb drivers... will make research when i am at home, now i am drinking beer...
Ok, tank you so much, i will really happy when it's possible to use root apps, sorry my bad english ehehe
---------- Post added at 04:14 PM ---------- Previous post was at 04:02 PM ----------
Unlock worked, i activate debugging but not check ☑ on usb settings on notification bar
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
Rooted successfully omg tank you, tank you!!!!!!
frankee207 said:
thansk you ,I will !
Running both Linux and Windows, I converted your script for Linux usage. Please find it here.
PHP:
echo -e "#### Backup all your idol 3's partitions - DallasCZ & frankee207 @XDA####\n\n"
echo -e "Please make sure your device is connected\n"
read -p "Press any key to continue"
cd ~/
echo -e "/!\ root must be granted for using adb on linux\n"
sudo adb kill-server
sudo adb start-server
sudo adb shell mkdir /storage/sdcard1/mybackup/
sudo adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/mybckup/modem"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/mybckup/tunning"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/storage/sdcard1/mybckup/traceability"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/storage/sdcard1/mybckup/fsc"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard1/mybckup/ssd"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/storage/sdcard1/mybckup/sbl1"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/storage/sdcard1/mybckup/rpm"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/storage/sdcard1/mybckup/tz"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/storage/sdcard1/mybckup/hyp"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/storage/sdcard1/mybckup/modemst1"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/storage/sdcard1/mybckup/modemst2"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/storage/sdcard1/mybckup/simlock"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/storage/sdcard1/mybckup/persistent"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/storage/sdcard1/mybckup/splash"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/storage/sdcard1/mybckup/tctpersist"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/storage/sdcard1/mybckup/hdcp"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/mybckup/DDR"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/storage/sdcard1/mybckup/fsg"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/storage/sdcard1/mybckup/sec"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/storage/sdcard1/mybckup/aboot"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p26 of=/storage/sdcard1/mybckup/boot"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/storage/sdcard1/mybckup/recovery"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p28 of=/storage/sdcard1/mybckup/system"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p29 of=/storage/sdcard1/mybckup/persist"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p30 of=/storage/sdcard1/mybckup/fota"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p32 of=/storage/sdcard1/mybckup/misc"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p33 of=/storage/sdcard1/mybckup/keystore"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p34 of=/storage/sdcard1/mybckup/config"
sudo mkdir blocks/
sudo adb pull /storage/sdcard1/mybackup/ ~/blocks/
echo -e "Backup done ! You can find it in ~/blocks/"
read -p "Press any key to exit"
exit
You can download the script here: https://mega.nz/#!E9MnGSjR!XHreY39vw7YIxFqOncDZNcBfn5LSgdhYsbcO4DGlubM
If you use the script for linux, don't forget to make it executable by running
Code:
sudo chmod +x backup_all_AOTI3.sh
Click to expand...
Click to collapse
%frankee207, there is at least one error in your backup script: you create a directory "mybackup" but then you try to write to a directory "mybckup". You will need to change one name or the other.
I will try a corrected version later today on my Mac (in general most stuff for linux should also work on Mac, though you don't need to run as root on the mac to run adb, so "sudo adb" can be replaced by "adb".)