Related
I was trying to root my defy with my macbook. I tried superoneclick, but it doesn't work on mac.
I tried z4root on this website [http://forum.xda-developers.com/showthread.php?t=833953]. But it didn't work for me as well it was stuck with "acquiring root shell". But on the website, it said it's compatible with defy.
Does anyone know how to root defy on a mac
Thanks a lot
Even if you could root your defy using a Mac, you'd still need Windows to run RDS lite.
Sucks, I know... but there it is.
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Being under Linux, I use sbf_flash for flashing and root the phone manually via adb.
Though I don't know about any macos alternatives.
sbf_flash has been updated; there's now a mac os x port, in addition, support has been added for the Defy, Charm and possibly the Atrix.
Click to expand...
Click to collapse
So it's also working for Macos, great.
MisterWB said:
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Click to expand...
Click to collapse
oh really? thanks a lot
Can u please put down the steps when ur free
MisterWB said:
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
Wow! I didn't know about sbf-flash.
Thanks for the heads-up.
My process to obtain root access:
1) connect phone to your mac via usb cable
2) In Finder extract "Getroot.zip" on Desktop for exemple
you should have a Getroot directory now with files inside (su, busybox...)
3) Copy/Paste this "Getroot" directory on root of your sdcard
4) Eject sdcard in Finder
5) push down notification bar on Defy and click "USB..." item
6) Select "none"
7) Check in Defy Settings that "Applications->Developpement->USB debugging" is on
8) On Mac launch Terminal
9) type "adb shell", you should have a "$" prompt
10) type "cd /sdcard/Getroot/"
11) type "sh getroot.sh"
You'll be eject from adb shell, it's normal
12) type again "adb shell", prompt should be "#" now, that mean root privilege !
13) type "cd /sdcard/Getroot/"
14) type "sh copy_rootfile.sh", this copy root file, recovery application and remount script*
15) type "reboot" to reboot phone
16) after reboot don't forget to push down notification bar on Defy and click "USB..." item of your choice
17) Done
Take care that "Settings->Applications->Developpement->USB debugging" mustbe off to boot in recovery mode. In other way you'll get a black screen
Hope I don't make mistake during zipping and writing process !
-----------------------------------------------------
* remount script to use from adb shell or any terminal:
- type "remount rw" to mount /system read-write
- type "remount ro" to mount /system read-only
- type "remount sdcard" to mount /sdcard when usb cable is plug to PC
MisterWB said:
My process to obtain root access:
1) connect phone to your mac via usb cable
2) In Finder extract "Getroot.zip" on Desktop for exemple
you should have a Getroot directory now with files inside (su, busybox...)
3) Copy/Paste this "Getroot" directory on root of your sdcard
4) Eject sdcard in Finder
5) push down notification bar on Defy and click "USB..." item
6) Select "none"
7) Check in Defy Settings that "Applications->Developpement->USB debugging" is on
8) On Mac launch Terminal
9) type "adb shell", you should have a "$" prompt
10) type "cd /sdcard/Getroot/"
11) type "sh getroot.sh"
You'll be eject from adb shell, it's normal
12) type again "adb shell", prompt should be "#" now, that mean root privilege !
13) type "cd /sdcard/Getroot/"
14) type "sh copy_rootfile.sh", this copy root file, recovery application and remount script*
15) type "reboot" to reboot phone
16) after reboot don't forget to push down notification bar on Defy and click "USB..." item of your choice
17) Done
Take care that "Settings->Applications->Developpement->USB debugging" mustbe off to boot in recovery mode. In other way you'll get a black screen
Hope I don't make mistake during zipping and writing process !
-----------------------------------------------------
* remount script to use from adb shell or any terminal:
- type "remount rw" to mount /system read-write
- type "remount ro" to mount /system read-only
- type "remount sdcard" to mount /sdcard when usb cable is plug to PC
Click to expand...
Click to collapse
I am kind of stuck, What do u mean by "USB..." for step 5? Is it usb connection? and for step 6 is it "charge only" for "none"?
I typed "adb shell" in terminal and it was like "command not found".
What should I do now? Btw, thanks for helping
Right, step 5 is "USB Connexion"
and step 6 "Charge only", text may change with language and rom version.
Regarding "adb" it's part of Android SDK: http://developer.android.com/sdk/index.html
So you have to download full SDK kit and install it....
...or use adb executable for mac attached below
On my mac I putted it into /usr/bin
1) In Finder put adb.zip into Download directory
2) In Finder Download directory, extract adb.zip, you'll get an "adb" file
3) Open Terminal
4) Go into Download directory
cd ~/Download
5) Copy adb file into /usr/bin with executable permissions
sudo cp adb /usr/bin/ -> and type your session's password
sudo chmod 755 /usr/bin/adb -> and type your session's password
next you can use "adb shell" like any unix command
Keep me inform
I found the link to download sbf_flash for mac
http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html
[A] How to Root Defy Android OS 2.1 on mac
I tried rooting the defy with z4root and SuperOneClick (using Mono to run it on a mac).
It appears that the z4root no longer works on later firmware updates for the defy, which others confirmed on another forum. For me it got stuck trying to run exploits. Similarly, SuperOneClick hung up during the "waiting for device" phase.
This other thread on xda did work and was super easy to do and I recommend it:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
I checked it with "Root Checker Basic" from app store and it is indeed rooted.
beefinit said:
I tried rooting the defy with z4root and SuperOneClick (using Mono to run it on a mac).
It appears that the z4root no longer works on later firmware updates for the defy, which others confirmed on another forum. For me it got stuck trying to run exploits. Similarly, SuperOneClick hung up during the "waiting for device" phase.
This other thread on xda did work and was super easy to do and I recommend it:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
I checked it with "Root Checker Basic" from app store and it is indeed rooted.
Click to expand...
Click to collapse
I followed the simple directions in the thread recommended by beefinit. The root.command script that comes with the G2xRootMacLinux_v0.5.zip package appears to have successfully rooted my Defy. The script is designed for a Tmobile LG G2x, but is based on SuperOneClick 1.8, so the fact that is seems to work for the Defy is not that surprising.
Here is the terminal log from when I ran the script:
Last login: Thu May 17 10:41:29 on console
/Downloads/G2xRootMacLinux_v0.5/root.command ; exit;
/Downloads/G2xRootMacLinux_v0.5/root.command ; exit;
Checking for connected device...
Pushing temporary root exploint (psneuter) to device...
2604 KB/s (585731 bytes in 0.219s)
Running psneuter on device...
property service neutered.
killing adbd. (should restart in a second or two)
Waiting for device...
Remounting /system read/write...
remount succeeded
Pushing su to /system/bin/su...
100 KB/s (26324 bytes in 0.255s)
Pushing busybox to /system/bin/busybox...
3162 KB/s (1062992 bytes in 0.328s)
Installing Superuser.apk android application...
775 KB/s (196521 bytes in 0.247s)
Removing psneuter from device...
Rebooting device...
Once device has rebooted you should be rooted.
Press Enter when you're ready to quit:
I'm very new at rooting phones but Superuser app is now installed and I've also installed ROM Toolbox Pro and confirmed that I can get a # prompt via it's Terminal Emulator.
My Defy is an unlocked MB525, Android 2.2.1, System version 34.4.9.MB525.T-Mobile.en.US, Kernel 2.6.32.9-g8431013, Build number 3.4.2-107_JDN-9
Thanks go to goroh_kun, ayati and DoomLord. All the usual warnings about attempting to root a phone apply. This works on a phone with build number V16R24C, which is current as of this writing. I can't speak for any later updates.
You will need the following:
Java SDK (required for android dev kit – get the JDK): http://www.oracle.com/technetwork/java/javase/downloads/index.html
ADK: http://developer.android.com/sdk/index.html
ADB driver: http://spf.fmworld.net/oss/usb_driver/f-05d/index.html
F-05D rooting files: http://ayati.cocolog-nifty.com/blog/files/F05Droot.zip
zergRush files (tested with v4): http://forum.xda-developers.com/showthread.php?t=1319653
Optional:
- a terminal application of your choice
- busybox installer from the market
- English versions of the .bat files (remove the .txt extension): http://pastebin.com/RBCWvzES and http://pastebin.com/EQfjpDAM
Part 1, installing the ADB driver:
1. Install the JDK
2. Install the ADK
3. Go to C:\Users\YourUsername\.android and edit the adb_usb.ini file.
4. Add 0x04C5 on a separate line at the bottom. Save and close the file.
5. Reboot the computer or restart adb
6. On the phone, press home, settings, applications – toggle Unknown sources to On.
7. Same place, press development and toggle USB debugging to On.
8. Connect the phone to the PC, and when prompted, navigate to the location where you extracted the ADB driver.
Part 2, rooting the phone:
1. Extract the zergRush and rooting files to the same folder. (put the English versions in the same spot if want to use them instead).
2. With the phone connected and in debug mode, run the f05dsu.bat file (DO NOT RIGHT CLICK AND SELECT RUN AS ADMIN).
3. You first will get asked to go to Settings, Setting my body, Step/activity counter app, Pedometer use, is turned On. Press space after doing that.
4. You will then get asked to toggle the same setting OFF once, then back to ON. After doing that, press space and the phone will reboot
5. Wait for the phone to reboot and connect over USB properly. Press space when ready.
6. Files will be transferred over and the phone rooted. If you don't get any errors, press space and wait for the phone to reboot again.
7. The phone should now be rebooted, and you can install Busybox and Superuser from the market.
I had trouble getting the Busybox installers to work properly at first – the stericson one would wipe su and require re-running the f05dsu.bat, and the jrummy one would simply not start properly. I suggest trying the jrummy16 installer first just to see if it runs. In the end I had to do things manually to get it installed, but once that was done both installers worked fine.
Part 3, optional, installing Busybox manually:
1. If superuser has been lost, re-root the phone.
2. Open up your favorite terminal application and enter the following manually:
Code:
su
soff
mount -o rw,remount /system /system
dd if=/data/local/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
dd if=/data/local/su of=/system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
echo insmod /data/local/lsm_disabler.ko > /system/xbin/soff
chmod 755 /system/xbin/soff
At this point you should be able to do a "which su" and get /system/xbin/su as a response. If you don't get any response, Busybox is not properly installed (start over). Doing a "ls -ls /system/xbin/su" should also NOT return a symbolic link to Busybox – if it does, you'll need to copy over su from /data/local again. The same goes for soff. Once this is done, start up jrummy's Busybox installer to confirm the installed version of Busybox, and upgrade it if you want.
Thanks very much, worked well but sadly I managed to boot loop my phone after rooting it.
Now I need to SIM unlock the phone as the factory unlock code is gone.
F05D rooting
Hi there i have successfully rooted my Fujitsu F05D have root access but I can't seem to loads busy box, I have permission through superuser and it goes through the motions but at the end it says " install unsuccessful".
The files are in the system/bin folder but something is wrong. if I use busy box installer jrimmy16 it just say installing and keeps going and never stops if I got to to scripts and click fix file permissions
" run script" it too just spins round and round..
hmm any hints guys.
Don't do a forced install or whatever it's called, that's how I bootlooped and later SIM locked mine, still yet to send it back haha.
Hello, is this working?? I want to root my Docomo Fujitsu Arrows X F-10.. And also my phone keeps on rebooting Please help.. Any ideas why?
does it work on Fujitsu T-02D?
These instructions are not solely my own and are adapted from miloj’s Windows based instructions found here:
http://developer.android.com/sdk/installing.html
Thank you miloj for the instructions!
This guide is intended to help noobs with rooting their TF300T device with a Mac. I am probably a half step above noob, so please don’t expect perfection.
Read this these instructions straight through, maybe even a couple of times before you begin to make sure you fully understand what you are doing.
I am not responsible for any bricked devices, malfunctions, etc. and most likely will not be able to problem solve much for you. Hopefully, the real geniuses here on XDA will jump in should you need extra help.
First off, make sure you have Android SDK and ADB installed. Follow these instructions skipping the Eclipse installation step (unless you plan on developing apps and such):
http://developer.android.com/sdk/installing.html
Save these files wherever makes sense to you and once done open up the folder containing adb in file explorer and leave open. This should be in the SDK>platform-tools folder.
Now for miloj’s instructions with some Mac specific extras and for sake of ease:
Download the debugfs and su binary files provided by miloj first from here:
http://db.tt/FBUNeVmo
Again, save these files where it makes sense to you and then open up the containing folder in file explorer and leave open.
Make sure “usb debugging” is turned on on your Asus TF300T by going to Settings>Developer options and check the USB debugging options.
Make sure you device is plugged into your Mac via usb cable. Now find out if our Mac recognizes your device.
Open up terminal from your utilities.
Organize your Terminal and folder containing adb on your workspace so you can easily access both. Click, hold, and drag the adp icon and drop it into the Terminal window. This will allow you to you immediately move into the adb command without having to type in the complete destination. Your line should end with “…/adb” now type in the command devices and hit return/enter.
NOTE – from here on out assume after every command you hit “return” or “enter”
It will look something like this:
Code:
…adb devices
the response should read:
List of devices attached
{serial number} devices
If nothing is listed, then you either didn’t activate USB debugging or your adb isn’t up to date, start again from the top.
If it showed your device, then lets move forward.
Now we have to push over the debugfs file and the su file (superuser). Make sure you can see Terminal and both open file explorer windows listed above all visible on your workspace.
Again, click, hold, drag the adb into Terminal and then complete the following commands by typing the command (in this case “push”) in between adb and the proper file and then typing in the location you want it pushed to on the device: (*note: dragging and dropping the “debugfs”file where it says “debugfs” – your file destination path name will be shown, not just debugfs)
Code:
adb push debugfs /data/local/
In the command above you would drag into Terminal the adb file then type push, drag in the debugfs file then type in “/data/local/” all with spaces in between. Every time you read in a “Code” section “adb” you are going to follow this procedure with the adb icon/file. Now, rinse and repeat moving forward.
Then this command (dragging and dropping the “su”file where it says “su” – your file destination path name will be shown, not just su)
Code:
adb push su /data/local/
now you have debugfs and su on your device.
You now have to have Terminal take control and run commands in your device by using this command:
Code:
adb shell
once in you will have a line starting with a “$” and you type in the following commands to gain root access: (type them exactly as written)
Code:
cd /data/local/
mv tmp tmp.back
ln -s /dev/block/mmcblk0p1 tmp
exit
The “exit” takes you back into your Mac, now reboot your device through adb:
Code:
adb reboot
WAIT UNTIL THE TF300T HAS BOOTED UP AGAIN!
Now get back into the device:
Code:
adb shell
Continue with the following commands after the “$” symbol:
Code:
cd /data/local
toolbox chmod 755 /data/local/debugfs
/data/local/debugfs -w /data/local/tmp
Now you’re going to run the debugfs files. Make sure you are writing these all in EXACTLY as written. All lines preceeded by “debugfs:” you will type in the following:
Code:
cd xbin
rm su
write /data/local/su su
set_inode_field su mode 0106755
set_inode_field su uid 0
set_inode_field su gid 0
quit
Now, back in to lines starting with “$” and run these:
Code:
rm /data/local/tmp
mv /data/local/tmp.back /data/local/tmp
exit
Now reboot:
Code:
adb reboot
WAIT UNTIL THE TF300T HAS BOOTED UP AGAIN
You are rooted! Congratulations!
Let’s double check and do some clean up:
Code:
adb shell
From the line “$” type these commands for double check:
Code:
/system/xbin/su
Now the line is a hash tag “#” and type
Code:
id
The Terminal response should read something like this:
id=0 (root) gid=0 (root) … and so forth
Clean up:
Code:
rm /data/local/su
rm /data/local/debugfs
Done with Terminal.
Now, open up the Play store and download the Superuser app immediately. Once it is installed, open the app and go into the settings. Under the heading “GENERAL” Tap the “Su binary v…” to check for updates and update the app.
You are now rooted, you have Superuser control.
Let me know how this works for you!!!
Credits: wolf849 for exploit, and miloj for commands.
Good stuf, just wait firsts feedbacks about this process :good:
Inserted in the Index for TF 300t
Guess i'm the only person who either owns a Mac here or has tried this but...
First time Terminal user and first time ASUS owner. Was a bit iffy doing it. Read through the TF300 board for weeks and was scared as sh#t to mess with this but...
it works!! Thank you so much. :good:
ngocdao said:
Guess i'm the only person who either owns a Mac here or has tried this but...
First time Terminal user and first time ASUS owner. Was a bit iffy doing it. Read through the TF300 board for weeks and was scared as sh#t to mess with this but...
it works!! Thank you so much. :good:
Click to expand...
Click to collapse
I'm glad it was easy for you! I am not a pro Terminal user by any stretch of the imagination! I am a first time ASUS owner as well, and have only rooted 2 phones and worked on rooting another (the phone ended up being software updated via Verizon to the point of unrootable that I could find or figure out). I am a Mac user and do not have easy access to a Windows PC and figured there were plenty of other Mac users noob to rooting. Apparently, that lists is you and me!!!
Thanks for the feedback, though! Congrats on your root!!
...too dificult for me,
Thanks.
Enviado desde mi ASUS Transformer Pad TF300T usando Tapatalk 2
dirator said:
...too dificult for me,
Thanks.
Enviado desde mi ASUS Transformer Pad TF300T usando Tapatalk 2
Click to expand...
Click to collapse
It sounds intimidating, I know, trust me when I say this is rather easy! The first time I rooted my phone I was quite worried! I read the instructions a few times and took my time though and it was really quite easy! Read the instructions a few times and you'll be alright. If you start to have trouble come back here or to this thread http://forum.xda-developers.com/showthread.php?t=1704209 and ask for answers.
not working as expected
Sorry to bother you with noob's problems.
I think I unlocked my TF300T ww Jelly Bean 4.2.1 allright.
I moved debugfs and su and other files to /data/local/ through bluetooth 'cause I wasn't able to do it in any other way.
The process worked fine up to here:
mv tmp tmp.back
Then I got this message:
[email protected]:/data/local $ mv tmp tmp.back
failed on 'tmp' - Permission denied
also, when pressing Power + Vol Down and then Vol Up to choose RCK it just dies (lying android with red triangle)
I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.
maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:
THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.
error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?
i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help
ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help
dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]
THIS GUIDE NO LONGER WORKS BECAUSE ANDROID ISN'T WHAT IT USED TO BE BACK IN 2013-14.
PLEASE STOP WASTING TIME TO FOLLOW THIS OBSOLETE METHOD 1. PLEASE REFER ONLY TO METHOD 3
The Ultimate Guide to Rooting any Android Device Manually !!!!
Wanting to ROOT Your Phone but can't do Because Of No rooting Guides or want to learn to root any device ? Then , This Guide Is For YOU
OK So lets start....
**What You Need**
1.Your Unrooted Android Device.
2.ADB Drivers Installed On Your PC. If you Don't Have Download From Here :
Code:
adbdriver.com/
3. The Most Inportant Root Kit Made By Me (N'ayam Amarsh'e) - Download From The Attachment.
4.Strength And Courage 'Coz Rooting Voids Your Warranty... If You have a samsung device then Don't Worry Your warranty is gone forever... But if you own any other, maybe you can void it or maybe......
I've Written Android Device as ADV to make it more easy....
**Steps**
So you have the adb drivers installed let's go....
1. Open The root kit by Extracting The Rootkit with WinRAR....
2.Turn 'USB DEBUGGING' 'ON' in your ADV...
3. Connect your ADV to Your PC...
4.In the root kit Open Cmd.exe File ... [ IF YOU CAN'T OPEN CMD, GOTO C:/WINDOWS/SYSTEM32/ COPY CMD .EXE TO YOUR ROOTKIT FOLDER]
5. In CMD window Type the following command...
Code:
->adb devices *Your device will get listed in the window if it doesn't check your adb drivers or if you have followed the steps properly...
->adb push busybox /data/local/tmp
->adb push su /data/local/tmp
->adb push Superuser.apk /data/local/tmp
If you Succeed Move On ...
6.Then You need Root Shell Type :
Code:
adb shell
Note that you see a "$" sign in the command prompt. That means you are not in 'su' shell.
7.Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
Code:
->chmod 6755 /data/local/tmp/su
->chmod 755 /data/local/tmp/busybox
->chmod 644 /data/local/tmp/Superuser.apk
{Note}The names of the files are case sensitive!
8.Done ? Now You need to open a copy of linux which has nautilus... So enter your linux (I recommend using ubuntu 11.4) and type in the terminal (ctrl+alt+T)
Code:
->sudo nautilus
this will open nautilus with root privileges...
You can just boot it from USB so no hassle of installing it... http://www.cyberciti.biz/tips/download-ubuntu-linux-11-04-iso-cd-dvd-images-natty-narwhal.html
Having your ADV connected with USB to PC switch it off and put it in download/recovery mode...
superlouro said:
DEVICE OFFLINE?
! SOLUTION ! (click me)
Click to expand...
Click to collapse
9.In The Exploring Window navigate to
Code:
/data/local/tmp
and move/cut 'su' and 'busybox' to
Code:
/system/bin
...
10.From the tmp Folder you went earlier Move/cut 'Superuser.apk' to
Code:
/system/app
11.Now Reboot You ADV ... Congrats ! You're now ROOTED !
Many Users Are Having Problem with This Method, If you can't do the method 1. Try Method 2.
METHOD 2
PLEASE DON'T ASK ME ABOUT THIS METHOD, THIS IS JUST FOR A TRY, MY BROTHER FOUND THIS METHOD TO BE WORKING, I HAVEN'T TRIED IT YET!
This is linux based method, It's quite easy if you follow every step correctly...
You need to download psneuter, https://github.com/tmzt/g2root-kmod/tree/master/scotty2/psneuter
When you have it execute the following...
Code:
adb devices
Code:
adb push psneuter /data/local/tmp
This will copy the file to your device and now we'll execute it..
Code:
adb shell
cd /data/local/tmp
chmod 777 psneuter
./psneuter
Now You'll see
Code:
adb kill-server
adb devices
adb shell
now # will appear in place of $, or after typing $su.
Code:
# mount -o remount,rw -t rfs /dev/block/st19/system
# exit
$ adb push busybox /system/bin
$ adb push su /system/bin
$ adb install Superuser.apk
$ adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19/system
# exit
$ adb reboot
Now your device will reboot and you can see SuperUser App in your app drawer...
----------------------------------------------------------------------
METHOD 3
There is no chance of the phone not getting rooted with my method but If you don't want to do the above methods, Try these, I'm pretty sure they will root your device with ease...
1. Framroot App [Not On Google Play]-http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2.KingoRoot App - www.kingoapp.com
3.One Click Root Free/Pro (My Favorite app, roots many devices with No-Brick Guarantee) - www.oneclickroot.com
4.Root Master App - forum.xda-developers.com/showthread.php?t=2672150
5.z4root App - http://forum.xda-developers.com/showthread.php?t=833953
6.Easy rooting toolkit App-http://forum.xda-developers.com/showthread.php?t=1321582
7.Vroot Software - http://vrootdownload.info/ or http://www.mgyun.com/en/getvroot
8.SRSRoot Software - http://www.srsroot.com
9.Unlock Root Software - http://www.unlockroot.com/download.html
10.Universal Androot App - forum.xda-developers.com/attachment.php?attachmentid=391774
ONLY FOR MTK DEVICES- MTK DROID TOOLS- http://forum.gsmhosting.com/vbb/f60...3-2014-imei-repair-rooting-tool-more-1780568/
HOPE THESE WILL DO....
Press Thanks To appreciate me to Work On Other Guides And Roms....
Your Appreciation Is Needed...
And This GUIDE IS Originally By N'ayam Amarsh'e
I have any error. Device is offline.
---------- Post added at 09:13 AM ---------- Previous post was at 09:02 AM ----------
uukasz92 said:
I have any error. Device is offline.
Click to expand...
Click to collapse
Problem solved i download another adb drivers and work fine
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
uukasz92 said:
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
Click to expand...
Click to collapse
that means you have not properly pushed the files into the directory.... Try installing adb drivers again and do the same steps...Good luck
When you open cmd just type ' adb devices' if your device gets listed then you can start if it doesn't check your drivers...
After uinstall all adb drivers and phone drivers comand prompt shows me a device code and status ofline. At the begining i install atached to therad package of adb drivers. But lately some where in Internet I find some update package of adb drivers. And there was the same sort of files like in your package. I put them there and replace and after that adb shows the device is working and status is online but your guide still does not work. Question is where is real problem ? I checked and Debug Mod is on, drivers are installed.
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
N'ayam Amarsh'e said:
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
Sent from my Mi-492 using xda app-developers app
Click to expand...
Click to collapse
I used the same files in android commander because program can't finde my device to.
Which phone you have.... Try to download its original drivers this might help...
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
uukasz92 said:
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
Click to expand...
Click to collapse
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
N'ayam Amarsh'e said:
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
Click to expand...
Click to collapse
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Droid Explorer cant change folders premission too. Command prompt says : Read-only drirectory. I don't know what to do now.
uukasz92 said:
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Click to expand...
Click to collapse
thanks.... Guide is updated now
Good 1 helped alot
harmeet singh said:
Good 1 helped alot
Click to expand...
Click to collapse
I am happy that I helped....
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
thankyou for information i think is hard for me
Very nice, ty
Humbel said:
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
Click to expand...
Click to collapse
For Your First Answer You Need not to worry /tmp and /tmp/ are the same...
2.Have you tried typing 'adb shell' then ' su ' if yes there's your solution.... If not then you have problem with su binary or busybox....
3.You have an Ubuntu 11.4 .iso file so burn it to a blank disk and boot your live disk .... It should be all right then...
4.Answer in 3....
5.Answer in 3....
6.Press Thanks if I helped...
bro im confused wt to do exactly in that sudo ... step pls give a brief explaination