1. Go to build description
2. Press 4 times to unlock Developer menu
3.Enable Debugging and OEM unlock
4. Plug USB cable to PC with ADB installed
5. Do ADB Devices and verify that your unit has a serial number
6. at the ADB prompt, go ADB shell
7. Make sure you have a Arm7 "su" inside your ADB folder.
8. At the adb shell prompt, type "[email protected]"
9. Type "su" , you should see "alps5000#"..that means you have superuser privileges now
10. type "remount"
11. type "exit"
12. type "adb push su /system/bin"
type "adb push su /system/xbin"
type "adb push su /vendor/bin"
13. type "adb chmod 0677 su /system/bin"
14. type " adb shell setenforce 0"
15. type " adb reboot system"
Now check if you have permanent root when the unit reboots..
codecxbox said:
7. Make sure you have a Arm7 "su" inside your ADB folder.
8. At the adb shell prompt, type "[email protected]"
9. Type "su" , you should see "alps5000#"..that means you have superuser privileges now
10. type "remount"
11. type "exit"
12. type "adb push su /system/bin"
type "adb push su /system/xbin"
type "adb push su /vendor/bin"
13. type "adb chmod 0677 su /system/bin"
14. type " adb shell setenforce 0"
15. type " adb reboot system"
Now check if you have permanent root when the unit reboots..
Click to expand...
Click to collapse
Or you can just install TWRP and root it in one go from there
problem with the FF-5000 is that system and vendor partitions are read only..you can upload twrp but youll get cannot modify errors..you need to unlock and remount these partitions first with the passworded su and then you can modify with twrp..the 9213ja is another type of software, its already userdebugged from stock, its partitions are already R/W from factory
Why complicate things so much OP? A much simpler way is to install TWRP recovery and then root, ViperFx and anything else u might want.
Related
I didn't find any mentions of this in the other threads or a thread dedicated to this, but just wanted to point out that it is very easy to do this on a Mac.
You will need to follow the same instructions in the other guides, but you can do it all from the Mac OS Terminal easily and no need to install drivers, just like you would with Linux.
In case someone wants step by step instructions, here they are modified for Mac OS:
Original instructions by chuckhriczko http://forum.xda-developers.com/showthread.php?t=581577
Step 1:
First you need to download the Android SDK. You can get it from http://developer.android.com/sdk/index.html. Download the Mac OS version and remember where the android-sdk-mac folder is (most likely in your Downloads folder)
The next thing we download is asroot2. This is a script that was developed that runs an exploit in Android's linux that allows us to run root. The link for that is here: http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154. Unzip that file and place it in a directory of your choice (I used android-sdk-mac/tools). Also download http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.2.3.img and place that into the same directory you extracted asroot2.
Step 2:
Connect the phone to the USB port.
Open a terminal and cd into the directory that you extracted the sdk into. Then cd into the tools directory. Then run the following commands:
sudo ./adb push /directory_you_placed_asroot2/asroot2 /data/local/
sudo ./adb shell chmod 0755 /data/local/asroot2
sudo ./adb shell /data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
type exit until you are back to your Mac's prompt.
Now your phone is officially rooted! We arent done yet though. Now you need to flash the recovery image. If you are still in adb shell type in exit until you are out. You should be in the directory where you extracted the recovery image. If not go there. Type in the following:
sudo /.adb push recovery-RA-heroc-v1.2.3.img /sdcard/
Once that is done, type in sudo ./adb shell. If your command prompt is a dollar sign then type in su and press enter. If it is a pound sign you are good. Then type in the following:
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
Once that is finished you are done. To reboot into recovery type in
sudo ./adb shell reboot recovery
If you are already in the shell, just type
reboot recovery
You should reboot into recovery mode and you can go from here. You can do a nandroid backup and then follow the other guides to install a different ROM or any other things you want to do.
If there are no instructions for Mac, just follow the Linux/Ubuntu instructions as they will be very similar if not the same.
Actually...
http://forum.xda-developers.com/showthread.php?t=581686
This is the thread I used to root my Hero CDMA from my Macbook, worked just fine...Thanks anyways for giving some love to macusers, guides are usually windows only.
I thought it was weird that there wasn't a Mac dedicated thread. I guess the search doesn't like 3 letter words.
Device must be fully loaded with USB debugging enabled.
Code:
cd\
code:
cd androidsdk\tools\
code:
adb devices (if you do not see your sn # then something's wrong)
Code :
adb shell
code :
su
Code:
cd /sdcard/
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img(OR WHAT EVER YOU NAMED THE RECOVERY IMG FILE)
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
Code:
reboot recovery
Let me know anything.
just wanted too comment on your sn
smasung???
finnese said:
Device must be fully loaded with USB debugging enabled.
Code:
cd\
code:
cd androidsdk\tools\
code:
adb devices (if you do not see your sn # then something's wrong)
Code :
adb shell
code :
su
Code:
cd /sdcard/
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img(OR WHAT EVER YOU NAMED THE RECOVERY IMG FILE)
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
Code:
reboot recovery
Let me know anything.
Click to expand...
Click to collapse
Run or Search: cmd.exe thru windows
than you type your commands.
Hi,
I am trying to push
Code:
$ adb push androidvncserver /data/androidvncserver
failed to copy 'androidvncserver' to '/data/androidvncserver': Permission denied
When I do 'su' in 'adb shell', i get a root prompt , that means I have rooted my device, right?
Code:
$ adb shell
$ su
#
If so, how can I push to /data?
Thank you.
Your default shell is secured - means, when you're executing ADB command without executing something through SU, you're going through the regular permissions.
To enable insecure boot, set ro.secure to 0 in your build.prop. I'm not sure if it's enough, though, or if you need a kernel compiled with security off to take full advantage of insecure adb commands.
You can push the file to sdcard, enter shell, enter su, and in root shell copy the file where you want it to be.
And you're posting in the wrong section. There is Q&A for questions, please move there.
I made a batch shell script for using wireless ADB in windows. It is simpler to use than opening CMD.exe, then CDing to the platform-tools directory and changing the ADB port, so I figured I'd post it. Just paste it into notepad, change the IP address to the correct one for your phone, and save as a .BAT file.
Code:
@ECHO OFF
cd "C:\Program Files (x86)\Android\android-sdk\platform-tools"
adb.exe connect [xxx.xxx.xxx.xxx:xxxx]
CLS
CHOICE /N /C:1234 /M "Press 1 for a realtime Android log, Press 2 for a shell prompt, press 3 for a bug report, or Press 4 for a command prompt."
IF ERRORLEVEL ==4 GOTO FOUR
IF ERRORLEVEL ==3 GOTO THREE
IF ERRORLEVEL ==2 GOTO TWO
IF ERRORLEVEL ==1 GOTO ONE
GOTO END
:FOUR
ECHO At the command prompt, type ADB for a list of possible commands.
GOTO END
:THREE
ECHO Enjoy your android bugs:
adb bugreport
GOTO END
:TWO
ECHO Welcome to the Android shell. Type "exit" and hit Enter to exit to command prompt.
adb shell
GOTO END
:ONE
adb logcat
GOTO END
:END
ECHO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cmd
Also, please let me know if you have any suggestions for my script.
Have you used UKE? It has wireless ADB built in to the phone. Never used wireless ADB personally, I'm a wired guy.
Don't you mean it's a Cyanogenmod feature and not a U.K.E feature?
link: opdecirkel.wordpress.com/2012/03/21/root-samsung-phones-running-android-2-3-x-without-flashing-kernels-or-executing-binaries/
1. adb shell rm /data/log/recovery_log.txt (even if fails it is ok)
2. adb shell "ln -s /data/local.prop /data/log/recovery_log.txt"
3. reboot your phone in recovery (do not do anything here)
4. reboot in normal mode
5. adb shell “echo ro.kernel.qemu=1 > /data/local.prop”
6. reboot again
7. adb shell … heeey you are root.
8. Install your favorite root tools: Superuser.apk, su, etc.
Hi there... I was trying this with an I9100 with XILA3 stock rom...
got stuck at point 5: permission denied
any advice?