1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.
Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.
You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium
smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.
Related
HTC Hero Root access
By fakker1
1. Download:
1. http://developer.android.com/sdk/download.html?v=android- sdk-windows-1.5_r3.zip
2. http://rapidshare.de/files/47972320/orange-htc-hero-uk-boot.img-28-july-2009.zip.html
2. Install HTC Sync from your HTC device
1. Connect device to computer using USB cable.
2. Mount the SD card from the HTC Alerts Menu (Drag from the top of the screen).
3. Install the sync application from the newly discovered drive in Windows.
3. Extract the two zip files into some folder (separate folders for each zip).
4. Go to the Android SDK folder and open the tools folder.
5. Copy the two files from the boot image zip (1.b) into the tools folder:
1. boot.img.insecure
2. boot.img
6. Shutdown the phone.
7. Press and hold the back key and power on the phone.
This is get you into the fastboot screen (the white screen with three androids at the bottom).
8. Connect the phone to the USB cable if it’s unplugged.
9. On Windows, open cmd.exe (Start -> Run -> cmd.exe -> Enter):
1. Change the directory to the tools directory you’ve created earlier.
2.Run fastboot.exe boot boot.img.insecure from within the tools directory.
Output: downloading 'boot.img'... OKAY
booting... OKAY
3. Now your device will start from the given image with root access.
10. Gain root access:
1. In the phone’s alerts menu, click HTC Sync. This will popup the HTC Sync tool in Windows. Ignore it!
2.In cmd type: adb.exe shell
Output:
#
3. From the prompt you got (#) run the following command to mount the phone’s file system in RW mode:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
11. Add su command to your Phone
1. Run the the following commands in the shell (#) – Run each command separately (don’t just copy-paste all the lines!):
1.cat /system/bin/sh > /system/bin/su
2. chmod 4755 /system/bin/su
12.Reboot the phone by typing reboot in the shell (#).
13. The phone will restart and load the original Android ROM.
14. Enjoy the your Rooted Device
From Android Forum
Perhaps better titled "Alternative method to Root" since I personally had a nightmare just installing HTC Sync and on reading, this method certainly seems more complex than the one here http://forum.xda-developers.com/showthread.php?t=543571
Dayz xx
hummm
sorry but that would lose many n00bs....just like me...
i am going to change the title and let the pubic go for what they think is best.
liamhere said:
sorry but that would lose many n00bs....just like me...
i am going to change the title and let the pubic go for what they think is best.
Click to expand...
Click to collapse
You Noob!
Lol. Just kidding, Yeah i think this title is much better! I've been Rooting Android Devices since the g1 came out so im familiar to all this.
Im still waiting for my HTC Hero to arrive, it should be here any second. Once my dog starts barking, it will probably mean fedex guy is here.
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
**THIS IS FOR US WIFI & 3G XOOM**
This guide in no way implies or expresses any warranties.
What you choose to do with your equipment is your sole responsibilty.
________________________________________________________________________________________
SUMMARY
You must already be running Honeycomb 3.2 on your Xoom **DO NOT USE WITH HC 3.2.1. IT HAS BEEN REPORTED TO CAUSE WIFI FAILURES** USE THIS TO ROOT HC 3.2 AND THEN UPDATE TO 3.2.1 USING THIS METHOD.
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be performing steps in ADB. If you are not familiar with this, read HERE first.
You will need Xoom USB drivers and Fastboot
You will need the WIFI boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)
OR You will need the 3G Verizon boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)
You will need Superuser.apk and su binary to enable functioning root
**Before you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development -->USB Debugging**
PROCEDURE
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot rootboot.img (for WiFi)
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)
Type; fastboot reboot
Allow the xoom to boot completely - your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)
Type; chmod 4755 /system/bin/su
Type; exit
Type; adb push Superuser.apk /system/app
Thats it...your done!! Unplug the xoom and reboot. Your xoom is now stock rooted. You can now flash ClockworkMod, other kernels and roms. To verify root, download a root user app from the market and run it. You should be prompted to allow superuser permissions.
Mac Only Procedure
You will need fastboot for mac - download HERE
Open a terminal (located in the utilities folder)
Navigate to your sdk/platform-tools folder
Type; ./adb devices - (look for the xoom serial number to show its connected.)
Type; ./adb reboot bootloader
Type; chmod 755 fastboot
Type; ./fastboot oem unlock
Type; adb reboot bootloader
Type; ./fastboot flash boot rootboot.img
Type; ./fastboot reboot
Type; ./adb remount
Type; ./adb push su /system/bin
Type; ./adb shell
Type; chmod 4755 /system/bin/su
Type; exit
Type; ./adb push Superuser.apk /system/app
Disconnect and reboot xoom. Download a root app and test.
If you found this helpfull press the THANKS button.
Excellent write-up, I'll try this when I get a chance.
Been trying to downgrade and then get to the rooted, stock 3.2 using a couple routes shown here. They seem to create an issue with CWM not sticking...
Works great!
I just flashed back to 3.01, re-locked the WiFi Xoom (USA), OTA'd to 3.1 and followed that with the OTA to 3.2. I then unlocked and went thru your rooting procedure and it worked great. All tests indicate a successful root. Thanks for the practical guide!
thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
_delice_doluca_ said:
thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
Click to expand...
Click to collapse
It is only a boot partition with rooted stock 3.2 kernel.
Sent from my HD2
[*]In the command window on your PC type; adb remount[*]Type; adb push su /system/bin[*]Type; adb shell[*]Type; ln -s /system/bin/su /system/xbin/su [*]Type; chmod 4755 /system/bin/su [*]Type; exit[*]Type; adb push Superuser.apk /system/app
Click to expand...
Click to collapse
when I type adb remount after completely boot, I've got error device not found !!! any idea??
Hussain Isa said:
when I type adb remount after completely boot, I've got error device not found !!! any idea??
Click to expand...
Click to collapse
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
Wow that was easy... Why cant all android devices be this open and straightforward? Im sooo pissed at HTC with the EVO 3D. Cant wait for the Galaxy S2 to come out
Mad respect to Motorola for getting this one right
And last but not least, Thanks so much to the OP for the great writeup!
jase33 said:
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
Click to expand...
Click to collapse
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App
Hussain Isa said:
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Are you certain you have unlocked the bootloader?
Sent from my HD2
jase33 said:
Are you certain you have unlocked the bootloader?
Click to expand...
Click to collapse
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App
Hussain Isa said:
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App
Click to expand...
Click to collapse
If you get an error please post exactly what it says.
Sent from my Xoom
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
droidx1978z4 said:
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
Click to expand...
Click to collapse
Glad to here it! And thanks for pointing that out....I will clarify that in the op for others.
Sent from my HD2
thanks jase33 my problem was with the driver, I re-install it & now rooted
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
WOW! Thanks jase33 that was painless.
Everything worked great, just as you said it would.
fwempa said:
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like you worked it out.
Sent from my HD2
Where did you get fastboot for Linux. I just get my self a xoom today, I'm planning to root it but my laptop is running ubuntu
Sent from my Nexus One using XDA App
fwempa said:
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Reinstall the driver, that will solve your problem
Sent from my Xoom using XDA Premium App
I've noticed several users having trouble with their phone when editing the build.prop. They will edit the file, reboot, anxious to use Google Wallet, and be greeted with a black screen of death. Their heart will jump in their throat and they think... "Oh no... I didn't nandroid backup... What's a nandroid backup anyway?" No worries! I have the solution for all of you. Hopefully this short guide will get you going again.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
You also need the naked ADB drivers if you're a Windows user... Here http://forum.xda-developers.com/showthread.php?t=1379875
Once you reboot your phone into recovery: Open start menu, right click on Computer, click properties. This will open the system panel. Top left, click device manager. Somewhere along there, see if you see your device name (something like "Samsung-SGH_I747") with an exclamation point or question mark. Double click it if it does. Click update driver in the window that opened. Click "Browse My Computer...." "Let me pick..." "All devices / next"... "Browse". Now go find where you downloaded and extracted the naked driver zip. Open the folder and double click on one of the available .ini files. You'll get some compatibility warnings, just continue.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Thanks, worked like a charm on my SII. And I finally have ADB set up for any future hiccups!
ibanezbass said:
I've noticed several users having trouble with their phone when editing the build.prop. They will edit the file, reboot, anxious to use Google Wallet, and be greeted with a black screen of death. Their heart will jump in their throat and they think... "Oh no... I didn't nandroid backup... What's a nandroid backup anyway?" No worries! I have the solution for all of you. Hopefully this short guide will get you going again.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
You also need the naked ADB drivers if you're a Windows user... Here http://forum.xda-developers.com/showthread.php?t=1379875
Once you reboot your phone into recovery: Open start menu, right click on Computer, click properties. This will open the system panel. Top left, click device manager. Somewhere along there, see if you see your device name (something like "Samsung-SGH_I747") with an exclamation point or question mark. Double click it if it does. Click update driver in the window that opened. Click "Browse My Computer...." "Let me pick..." "All devices / next"... "Browse". Now go find where you downloaded and extracted the naked driver zip. Open the folder and double click on one of the available .ini files. You'll get some compatibility warnings, just continue.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
I'm having the same issue; I did the above procedures (using a Mac) but every time I type "adb shell", I get this:
"-bash: adb: command not found"
Help, please....
Thanks!
Nevermind, I figured it out.
good write up, thank you
Seems to be only when you use a gnex as build prop.
HTC jewel works great
I had two softbricks worked great
Sent from my SAMSUNG-SGH-I747 using xda premium
very helpful. Thanks!
This doesn't do anything for me. It still shows rw-rw-rw after running that command in adb. Any other ideas?
It also seems like it doesn't modify any of the files at all. I even tried renaming because i have a build.prop.bak file that i want to use and it doesn't seem to rename it.
[update] I am using the Odin method just to reflash it to the stock rom. I have moved on from this useless method.
Hi i just edited the /system/build.prop
for able to play gameloft games
now my tablet cant boot
i use this room : http://forum.xda-developers.com/show....php?t=1816795
i tried your method
i got this error
>adb shell
error: device not found
what can i do i don't want lose data
i tried to recovery mode and normal booted mode no lucks
please help. ican't find my device in device manager
Thank You !!!!!!!
Thank You, Thank You, Thank You, Thank You, Thank You, Thank You - I was hours away from taking my phone back ... I found my build.prop file with 0 bytes but fortunately I already had a build.prop.bak in there. I'm fairly certain I softbricked my phone by not following the instructions closely on rahpyqui utube Google Wallet process. Thanks SO MUCH!
isn't just easier to re-install the ROM you are running? You don't loose any settings.
unable to chmod build.prop
Help me!!
Error: unable to chmod build.prop: Operation not permitted
lyrictenor1 said:
Nevermind, I figured it out.
Click to expand...
Click to collapse
I'm having the same problem, how did you solve it?
IMEI unknown - invalid
I have problem with IMEI ,no sim cards work in lenovo A660.I have done some factory resets and tried all possible solutions referred in xda forums but none worked.DOu think that build.prop could cuz problem to the IMEI somehow? i had to overwrite a build.prop file from a friendly site because i couldnt use 160 characters in sms and they said that this would help.BUt now , no IMEI.Can anyone help?
Thank you for the info:highfive::highfive:
Help!!!
How do I boot my Xperia S into Recovery Mode? Do I have to press the power button + VOL UP Button so that the LED gets blue?
Anyways I did it that way, expecting it to be in Recovery Mode, but when I run the adb shell it says "Device not found." Can somebody help?:crying::crying::crying:
I guess its because I didnt install the naked drivers but I cant do it because I wont find my device in the device manager... Why not?
Very nice guide, thanks!!!:victory:
THANK YOU!
permission denied
I am getting this when starting adb shell
- exec '/system/bin/sh' failed: Permission denied (13)
is this just a driver issue as I installed the naked driver and rebooted after.
so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/showthread.php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted.
To Root HTC One VX
LordXombie said:
so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/showthread.php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted.
Click to expand...
Click to collapse
First Unlock Bootloader And Then Root. :silly:
i have unlocked the phone. but it will not allow me to access the bootloader unless threw other means. while in the bootloader it says tampered followed by unlocked. i cannot seem to figure out what is going on.
How to root htc one vx
HTC One VX comes from the
HTC One series of
smartphones consisting of
high-end specifications, such
as Dual-Core processors and
the latest version of Android
on-board. While we already
have a root guide for the
One VX, another root
method has popped-up on
XDA and to help users root
their devices with this new
method, here we’re
presenting a tutorial
explaining everything you
need to root your device.
So, let’s see how you can
root your HTC One VX
smartphone.
I. Before You Begin:
1. This will void the warranty
of the device. However, you
can reinstate it by unrooting
the device if there’s any
unrooting procedure
available.
2. The following procedure
works on Windows based
PCs only.
II. Downloading
Required Files:
download file. http://forum.xda-developers.com/showthread.php?t=2123359
III. Rooting the HTC
One VX:
1. Place the Root Package
archive on the Desktop of
your PC.
2. Extract files from the
archive to your Desktop.
Don’t launch any files just
yet.
3. Turn ON the USB
debugging option on your
device by heading to
Menu>>Settings>>Developer
options>>USB debugging .
4. Turn OFF the device.
5. Reboot the device into
Fastboot mode. To do so,
simply hold down the
Volume DOWN+Power
buttons together.
6. Once inside the Fastboot
mode, connect the device to
your PC using the USB cable.
7. Open a Command Prompt
Window on your Desktop. To
do that, hold down the Shift
button on your keyboard
and right-click on any empty
area on the screen, then
select Open command
window here .
8. Type in following
command into the Command
Prompt Window:
fastboot flash boot boot.img
9. Once it’s done, issue the
following command:
fastboot reboot
10. Your device will reboot.
Once it boots up, enter the
following command:
adb remount
11. Next, enter following
commands into the
Command Prompt Window
one-by-one. Press ENTER
after each line you type:
adb push Superuser.apk /system/app/
adb push su /system/xbin/
adb shell mkdir /system/bin/.ext
adb push .su /system/bin/.ext/
adb shell chmod 6755 /system/xbin/su
adb shell chmod 6755 /system/bin/.ext/.su
adb shell chmod 777 /system/bin/.ext
adb shell ln -s /system/xbin/su /system/bin/su
adb reboot
12. Your device will reboot
in normal mode.
13. Once it boots up, simply
open the Superuser app
from your App Drawer.
14. Tap the Update binaries
button in the app and let it
do the rest of the work.
15. And you’re all done!
Brilliant! Your device has
been successfully rooted and
the SU binaries have also
been updated. Now load-up
some root-only apps on
your device to realize the
power of root-access!