***Xoom Rooting Guide for N00bs***
Hello Xoom Dev community! Sorry. I know you're thinking, "Man! Not another Xoom root guide?!". Lol. But I wanted to make this, so, here ya go...
***WARNING***
-This will erase everything on your xoom. Its like flashing flashing back to stock because of the unlocking process. So BACK everything up before continuing via USB, or your preferred backup app-
**Also, this Tutorial is for the 3G version ONLY. The Wifi model is different and uses an incompatible boot.img. Once again, ONLY FOR 3G MODEL**
Ok. So, rooting the Xoom isn’t really that “hard” of a task. I’m a n00b as well, so I did have a little difficulty doing it. Only because this method requires you to use adb, the command prompt, etc…
Well, I wanted to make a guide that should be ‘n00b-proof’. LOL. It’s really super simple.
**Bofore you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development --> USB Debugging**
Alright, you’re going to need some tools to get it done. First of all, download the Xoom USB drivers. Either get them from motodevs.com --> http://developer.motorola.com, which requires a free membership; or get them from the Motorola/Support site --> http://www.motorola.com/Support/US-EN/Consumer-Support/TABLETS/MOTOROLA_XOOM, and download the ‘motohelper’ program. I prefer the drivers from the dev site because they’re just stand-alone drivers. Motohelper is an actual app that “keeps your drivers up-to-date”. Both will have the same version of drivers, i.e. 4.9.0.
Now that we have the drivers installed plug in your Xoom to make sure all drivers/services were detected/installed properly. If you’re good, next we will need the Android SDK, if not already installed. To properly install it though, you must download the Java JDK from --> http://www.oracle.com/technetwork/java/javase/downloads/index.html, and click the “Download JDK” button. Choose your OS, and install.
**NOTE** If you’re running Vista/7 x64, Android SDK will not detect the REQUIRED Java kit installation. Yes, JDK has been properly installed, but the Registry doesn’t read the installation right. So, to get around this issue, either go here --> http://codearetoy.wordpress.com/2010/12/23/jdk-not-found-on-installing-android-sdk/, for a tutorial that gets it detected by modifying the Registry. Or, do what I did, and just download the .zip installer of Android SDK. I’m writing this guide based on the ‘zip type’ of installation, but I’m sure the directories are identical besides having SDK installed in your Program Files folder.
Whew! Now, either extract the SDK to a directory of choice, or point your mouse to the Program Files\Android SDK\ directory. There will be some folders like platforms, platform-tools, tools, etc…
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
**NOTE** When I first installed SDK, I ran the emulator.exe from within the ‘tools’ directory. This updated everything, but I’m not sure if it matters for this tutorial?
Ok. The “hard” part is over. We should be all setup, and ready to type some commands! What you’ll need to do now is, open up a command prompt i.e. cmd. And do a cd --> to whatever path the ‘tools’ folder is in. For example, mine is in a Xoom folder from my documents. So the command would be “cd C:\Users\%name%\Documents\Xoom\android-sdk_r10-windows\android-sdk-windows\tools”. Without quotes of course.
You should now be pointed at the ‘tools’ folder from cmd, and next we can start the commands!
CHECKPOINT
- Xoom drivers installed, xoom is plugged in, & detected properly. To make sure, open Device Manager to see if the “ADB Interface” is there. **Sorry, I’m not sure ADB is in Device Manager before, or after rooting** Can’t remember! As long as you don’t have any ‘device is not properly installed’ pop-ups, you should be good!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Android SDK is configured right, and cmd is pointed at the correct location.
-USB Debugging option is checked. Check above for instructions
***This is obviously, from Koush’s site, so give him some kudos please ***
***I will bold all commands, and try to put in ‘n00b’ terms***
Type the following commands in CMD… after you have moved the “XOOM root” files.
1. Download the XOOM root zip.
2. Unzip the package, and
3. put the 3 files inside the same ‘tools’ folder we’re running cmd from!
4. adb reboot bootloader (skip the next 3 steps if you have already unlocked your Xoom via fastboot, which is another guide on XDA that just lets you unlock the Xoom. It’s not rooting.)
5. fastboot oem unlock
-You have to accept the terms by pressing the vol - down key, and then select 'accept' by pressing the vol + up key.
6. -wait for the Xoom to reboot completely.
**You may have to re-enable USB Debugging mode again for the next command**
7. adb reboot bootloader
8. fastboot flash boot rootboot.img
9. fastboot reboot
10. -wait for the Xoom to reboot completely.
11. adb remount
12. adb push su /system/bin/
13. adb shell --> You will now be mounted within adb shell…
14. ln –s /system/bin/su /system/xbin/su
15. chmod 4755 /system/bin/su
16. exit --> This gets you out of adb shell…
17. adb push Superuser.apk /system/app/
That is all! Now, unplug the Xoom and reboot it.
To verify your root is working properly, download an app such as, Cachemate, or any other that requires Superuser access. Open up Superuser to see if that apps’ rights were saved successfully.
Yay! Root access! But honestly, this tutorial will be outdated and inefficient, once the source code is out and then we’ll have a oneclickroot method. Which is way better! Until then, I hope anybody who is a little confused about the process benefits from this guide.
Happy moddin’!
good guide.
Thanks, I like this guide and made rooting my xoom super easy.
One other important initial step is to make sure USB debugging is enabled:
Settings>>Applications>>Development>>USB debugging
Hey, thank you guys for your kudos. I appreciate the feedback.
@jtseidner, Man you are a genius! That is a very important step that I left out! You couldn't root the Xoom without that option. I'll add it to the tutorial.
Thanks!
14. ln –s /system/bin/su /system/xbin/su
Its saying In: not found.. help
Hey. The command is all lower case so it would be "LN" not "IN". Just type it in all lower case. The rest of your command is ok. Simple syntax error, that's all. Let me know if it works and if you have any other concerns.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
ok i got to step fastboot oem unlock #5 and the screen shows choices. i accidentally chose device unlock operation aborted, the down arrow. now it wont go off this text screen. how can i reboot this xoom?
disregard, i pressed the volume UP and power, tablet is rebooting now.
Hey worked great for me only problem is that it wiped my xoom...probably said that somewhere in the instructions and i just missed it. Anyway Thanks.
Yeah sorry. I should put that on the tutorial. But im pretty sure any method of rooting the xoom will wipe it. Only because you have to unlock the device. Until we receive clockwork, this is the only way. Im glad you were successful with my guide though!
Thanks.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Screen Stuck At Starting FastBoot Protocol Dont Know How Long This Screen Stays Up Or Have I Done Something Wrong I Downloded FastBoot Already And Put It In My Sdk Folder Can Someone Pleas Help Me
You shouldn't be stuck at fastboot. It probably means that your xoom wasn't fully rebooted into the bootloader. Fastboot is a program located in the tools folder and ran from your command prompt. So have your xoom loaded up and connect the usb. Make sure usb debugging is on. Open your cmd and point to that tools folder. Type the first command from step 4, adb reboot bootloader. This will restart your xoom and I believe you'll see the 'dual core technology' logo. Just wait a minute after step 4. Now try the remaining commands, but be sure to wait for reboots before typing the next commands. I have a note after each step that says wait for reboot. Please let me know if you have any further issues.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
This is utterly confusing.. can you explain in-depth please. Don't copy, but leave it as is; copy but replace the file, or replace it completely. Only three options.
for example... it will show adb.exe and adb.exe(2) - is that what you wanted?
misdirection said:
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
This is utterly confusing.. can you explain in-depth please. Don't copy, but leave it as is; copy but replace the file, or replace it completely. Only three options.
for example... it will show adb.exe and adb.exe(2) - is that what you wanted?
Click to expand...
Click to collapse
Nevermind.. I was able to root my Xoom!!
Great! Sorry if it was misleading. Im not the best writer at times. All I meant was just to copy everything from the platform folder over to the tools folder without replacing, or writing duplicate files. Hope that makes sense?
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Is this the stock .img or is it the tiamat one? I used other root guide but I'm interested in flashing this .img if it contains the stock kernel.
Sent from my Xoom using Tapatalk
This is the stock .img and this guide will work for the original stock firmware, along with the new 3.01. But this guide is ONLY for the 3g version of the Xoom. If you have any further questions please ask away.
EDIT: Sorry. I didn't fully understand your post. This guide doesn't include any kernels. It assumes you are coming from a stock system. If you are already rooted, and want to return to stock, you would probably have to do a complete restore, and re-lock your device. Then, if you just want the stock kernel; root with this guide, or similar. You can't flash the tiamat kernel unless you're already rooted. This tutorial just gives you root access. Im sure there is a way to go back to the original kernel, without having to restore, but I don't know where those instructions are? Poke around and you may find it. But you'll probably have to start over. Hope this helps!
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Thanks. I have a WiFi only version and used another root method which included tiamats kernel. Currently having some reboot issues with the kernel so I was hoping to find a stock kernel that I can use.
Ok. Well, you can use this method to root, but the xoomroot files are different. This tutorial was based off the 3g only, and maybe ill add the wifi option as well.
Here's are great guide from xaositek for the wifi version...
http://forum.xda-developers.com/showthread.php?t=1010568
And I'm pretty sure it doesn't include the overclocked kernel.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
http://mirror1.kanged.net/motorola/stingray/xoomroot.zip
seems link are broken
Related
First of all, unforgiven512 deserves most of the credit for coming up with the initial tutorial for perm root and s=off for the new HTC devices. Also, thanks to adwinp for the instructions on hexeditting the kernel module to make it work with the MT4G.
This was a collaborative #g2root effort, primarily involving scotty2, tmzt, IntuitiveNipple but also many others!
Ok, so the usual disclaimers go here:
I am not responsible for your bricked phone or the ignorance that may or may not have caused it based on the fact that you CHOSE to follow these steps. Read through the forums and LEARN before you attempt to flash any device. You have been warned.
This method only works for those devices who have already received their OTA update!!!
Now that that is out of the way here we go:
First make sure you have visionary installed!
Root.rar (all files plus a script to make things a little easier. )
http://www.mediafire.com/?flit79p2y069bb3
md5sum: 46361b0cc8652d88688c0ab66d44950b
1. Download the root.rar file and unzip it to /sdcard on your device.
2. Run VISIONary to gain temp root.
Now I am going to run two different sets of instructions (you'll understand why in a minute):
Terminal Emulator Method
3a. Start terminal emulator up on your device.(I prefer this method b/c you can see the output.)
a. type "su" + enter to gain root privileges.
b. Type "cd /sdcard/root" + enter.
c. Type "sh root.sh" + enter.
d. Follow the on screen prompts.
File Explorer Method
3b. Start up root explorer, sufbs, or some other type of file browser with root privileges.
a. Navigate to /sdcard/root on your device.
b. Click on root.sh and allow it to run. Some file browsers ask you if you want to or not.
c. Now wait about 18 to 20 seconds and restart your device into the bootloader to check if S=off is displayed.
4. Start the device back up.
5. Run visionary again and reboot again. This will make root stick.
You can now uninstall visionary and enjoy permaroot.
Alternative Root Process
First, uninstall visionary and superuser and restart your device to wipe out temp root.
Second, download MT4G Modperm.zip and unzip its contents to your sdk tools directory.
MT4G Modperm.zip: http://www.mediafire.com/?eaw0q0zjc7rrrwh
MD5Sum: 3ea4a7a6ddee711d12f7350ce60fae33
Then:
Windows Users:
1a. Using Explorer navigate to the root of your sdk. Hold shift and right mouse click on the tools folder. Select "Open command window here".
2a. Type "adbbat" + enter. Wait till the batch file finishes.
Linux Users:
1b. Using file browser of your choice (or terminal) navigate to the tools folder of your sdk and double click on adbbat.sh (type sh adbbat.sh if you are using terminal). Credit for adbbat.sh goes to slhpss.
2. Disconnect your phone from the PC.
3. Open terminal emulator on the phone and type "/data/local/rage" + enter. Wait for "Forked XXXXXXXX children" to appear and then close the terminal.
4. Start terminal back up. It should force close.
5. Start terminal back up, again. This time it should stay open and you should have a "#" prompt instead of a "$" prompt. Then type "/data/local/temp.sh.
6. When the script finishes run /data/local/rage again and sit tight. The phone should start acting weird and do a soft reboot. Then right after everything loads it should do a hard reboot. After the hard reboot reboot and check S.(If it doesn't do the two reboots just reboot into hboot yourself after rage finishes with the "forked xxxxxxxx children" message.
7. Enjoy root!
If you still have problems getting su to work after this uninstall visionary, shutdown, pull battery, and restart. Should work after that. Props to PolishDude for figuring that one out.
If you have tried EVERYTHING and still cannot get it to work for through the process and wait 30 minutes to an hour. The driver might have a cache delay write and you may need to give it some time to allow the sync command to work. This has worked for one other person (mfouco). BTW, this was figured out by coachmai. Props man!
If su doesn't stick, flash again! You can't overroot it!
Process for turning S back on
Download this file and unzip it to /sdcard on your device.
unroot.rar
http://www.mediafire.com/?12oi5elu7v2y8og
md5sum: aad4e64126cf8d92d7e8b5abb48fdadd
Terminal Emulator Method
1. Open up terminal editor on your device.(I prefer this method b/c you can see the output.)
a. Type "su" + enter to gain root privileges.
b. Type "cd /sdcard/unroot" + enter.
c. Type "sh unroot.sh" + enter.
d. Follow the onscreen prompts.
File Explorer Method
2. Open root explorer, sufbs, or some other file browser with root access.
a. Navigate to /sdcard/unroot.
b. Click on unroot.sh and allow it to run. Some file browsers ask permission before they execute scripts.
c. Wait 18 to 20 seconds and reboot your phone into the bootloader to check if S=on.
You now have S=ON again.
Since we opened up the nand to writes you should still retain persistent root privileges.
Hope this makes it all easier for you.
Cheers --grankin01
For everyone that is have trouble writing to the protected areas of the system after following the rooting procedures.
Reboot into Clockwork recovery and choose the mounts and storage option. From there choose mount system (or whichever protected directory you want access to) and click the trackpad. When unmount system shows you have rw access to the /system directory and all of its subs.
Great I just saw this on PaulObrians twitter so this is great news.
Mackster248 Macky Evangelista
@PaulOBrien will your visionary app tomorrow be able to root the mytouch 4g as well? Since it roots the desire hd.
Pual's answer:
PaulOBrien Paul O'Brien
@
@Mackster248 Possibly...
Question, Did you recompile the kernel for the MT4G yourself? A big thanks to everyone. We all need to dig in out pockets to these developers and not forget them.
No, I really didn't do much of anything but legwork on this, lol.
I had to hexedit the wpx.ko module to add our kernel version (instructions and hboot file in the desire hd permaroot thread thanks to adwinp). I then uploaded both and pasted the links here.
Good job man, can you post an image of the bootloader with s-off?
Testing now. I don't have my USB cable with me at the moment so I couldn't execute the ADB commands, however I moved the files to their relevant positions via Root Explorer app.
EDIT: I has a ROOT. Glacier PVT ENG S-OFF ftw!
EDIT2:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the bad quality, but there ya go!
EDIT3: For those who were wondering, I did everything I could through Terminal Emulator with Fast Boot off and not through ADB. Once the hboot_dhd.nb0 file had completed, I believe I sync'd, then I attempted to run VISIONary which said the phone was already rooted. Went ahead and hit "Restart," then ran VISIONary one more time when it was done and restarted again to get it to stick.
unremarked said:
Testing now. I don't have my USB cable with me at the moment so I couldn't execute the ADB commands, however I moved the files to their relevant positions via Root Explorer app.
Click to expand...
Click to collapse
Please Let us know how it goes. And also does this require the OTA update to 2.2.1?
grankin01 said:
No, I really didn't do much of anything but legwork on this, lol.
I had to hexedit the wpx.ko module to add our kernel version (instructions and hboot file in the desire hd permaroot thread thanks to adwinp). I then uploaded both and pasted the links here.
Click to expand...
Click to collapse
There were actually three files on the G2 thread. Two were slightly different versions - pre-OTA and post OTA update. Which is the one here - pre or post OTA?
I have the OTA update, and am hoping I don't have to roll back to do this.
In any case - great job for getting it up for the MT4G. Just want to be sure what i am working with.
Getting my MyTouch in a couple of hours. Can't wait for the new challenge.
-kmobs
Bump for great success! I'll try to post a picture of my S-OFF.
Mmarzex said:
Please Let us know how it goes. And also does this require the OTA update to 2.2.1?
Click to expand...
Click to collapse
I'm going to assume so since I was on 2.2.1 and it worked.
Double post, all the way! What does this meeeeaaan?
Guys might be a stupid question but how do you get into the hboot on mytouch 4g. I thought it was the power button and camera but that doesn't seem to work.
Mmarzex said:
Guys might be a stupid question but how do you get into the hboot on mytouch 4g. I thought it was the power button and camera but that doesn't seem to work.
Click to expand...
Click to collapse
Turn off "Fast Boot" under Applications then power on holding Power + Vol Down
unremarked said:
Bump for great success! I'll try to post a picture of my S-OFF.
Click to expand...
Click to collapse
This is for after the OTA. I figured everyone had already gotten it and didn't worry with the two versions. If that becomes a problem I will edit the file again and post a pre-OTA file on here.
I am also trying to post a pic. I wasn't ignoring everyone its just that my phone is my camera and I was trying to track an old phone or something down. LOL
persiansown said:
Getting my MyTouch in a couple of hours. Can't wait for the new challenge.
-kmobs
Click to expand...
Click to collapse
I'm loving it bro. Coming from n1 too
grankin01 said:
This is for after the OTA. I figured everyone had already gotten it and didn't worry with the two versions. If that becomes a problem I will edit the file again and post a pre-OTA file on here.
I am also trying to post a pic. I wasn't ignoring everyone its just that my phone is my camera and I was trying to track an old phone or something down. LOL
Click to expand...
Click to collapse
Likewise! LOL Trying to find a program to turn my netbook's camera on real quick.
wow guys that was fast!
OP has been updated with a pic of s=off.
Cheers guys.
Link Down
hboot_dhd.nb0 link not working
edit: i guess its back online
any word on clockwork now that we have perm root?
Dead Link
the link for hboot_dhd.nb0 is dead. anyone want to post a mirror? it would be appreciated.
Thanks in advance.
EDIT: Nevermind...guess it working. Megaupload was having a glitch.
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
I bought the Motorola Bravo which is similar to the Flipside and an app on the market called Z4ROOT was able to root the phone. It works on many phones not just the Bravo. Give that try and see if it works.
z4root does work for permanent root i have tried and can confirm
jediskywalker said:
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
Click to expand...
Click to collapse
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Got my Flipside rooted and non market apps allowed
I followed the instructions given at modmymobile dot com forum. Look up "fully unlock 3rd party apps backflip" It allowed me to root my phone and install non market apps. I tried and tried to follow the instructions given here, but i guess they weren't idiot proof. It is for the backflip, but it worked perfectly for my Flipside. I couldn't post the link here.
Someone found some typos in my scripts. I have updated them so they are accurate. Should make things run better.
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
ishiiisbooyah said:
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
Click to expand...
Click to collapse
Lets say you installed your SDK in the default folder, you would need to type
Code:
cd c:\"Program Files"
cd Android
cd appinventor-extras
Now, I put mine in c:\SDK, so all I type is
Code:
cd c:\SDK
you either must add the SDK to your PATH, or find the directory that you installed it to, and then try running adb from there. If adb.exe isn't in the folder, you aren't in the right folder.
jonsjava said:
Rooting a Motorola Flipside
[/url]
Click to expand...
Click to collapse
hi
i m new in unlocking field
can i unlock this handset "flipside" by motorola came from usa at&T
if yes then plz explain
thanks in advance
RZ4root does not appear on the marketplace and when I click the link above it starts to download, then says the content is not supported on my phone.
Model num MB508 Motorola Flipside running Android 2.1 update 1.
You need to push it to the phone from a computer using adb to install z4root, now that it has been removed from the market.
Sent from my Liberty using Tapatalk
adb.exe not in the zip file
jonsjava said:
Rooting a Motorola Flipside
grab the ADB SDK files
android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
(...snipped...)
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Click to expand...
Click to collapse
adb.exe is not present in the SDK that you linked. Are you sure that is the SDK we need to root the Flipside?
You have to install it manually. It comes with the platform-tools.
how do i install adb.exe from platform-tools
lol, i may ask stupid questions but this one wasnt me, i shouldnt leave my laptop lying around haha
jonsjava said:
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Click to expand...
Click to collapse
Notice:
For anyone having trouble rooting the Motorola Flipside with these instructions, after much trial and error I managed to get my girlfriend's rooted. I'll provide the method I took.
Note: The easiest way to do this is to have downloaded and extracted "android-sdk_r08-windows" directly to your (C: ) drive. Not under programs or another system folder.
Once you have it extracted to (C: ), copy and paste z4root.1.3.0.apk into the "android-sdk_r08-windows" folder. ADB.exe will most likely not be in here. What you have to do now is click on SDK Manager within the SDK folder. A Black Command window will pop-up, ignore it. A secondary window will pop-up prompting you to install the packages I went ahead and installed all of them (better if you don't know which to install).
Now that they've all been installed, a command line will state that ADB has to be restarted. Let it restart and it should say completed.
Now -- here's where everything was messing up. When you click open the SDK-R08 folder, you should have the z4root.apk file right there amongst a list of folders. Go to the "platform-tools" folder and in there you should see the ADB.exe file. Ignore that for now. While in platform-tools press Ctrl+A so that everything is highlighted. Right click and select Cut, back out to the main directory of the SDK R08 folder and select Paste so that the ADB.exe, .dll, and all the other files from within platform-tools is out and listed alongside the z4root.apk.
Next - Follow all of the instructions up to "Plug in your phone, and have it set to "Charge only" Like JonsJava said, open up command prompt (type in CMD in the "search programs and files bar"). If you extracted the "android-sdk-r08-windows" file directly to the (C: ) drive, all you have to type in is...
(Note: Before I go into that, it'll be easiest to rename the file "SDK" instead of the whole "android-sdk, etc, name... I'll complete the instructions assuming you renamed it to SDK. Continued below... all you have to type in is...
cd C:\SDK
(The next line below will look like this)
c:\SDK>
Here, type in... adb install z4root.1.3.0.apk
Total should look like... c:\SDK>adb install z4root.1.3.0.apk
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Last note:
Uploaded with ImageShack.us
This is what the main directory of the SDK folder should look like before you enter anything in the command line.
I don't seem to be able to get this...
I'm using x64 windows 7, I have a Flipside MB508 on 2.1, and I can't get this to work.
I followed all the instructions, updated all the platform-tools stuff, and now my problem lies with the driver, I believe.
I installed those Motorola drivers that were linked, with my phone unplugged, successfully..
copied the apk to C:\SDK...
found adb.exe in the platform-tools folder..
...and this happened..
C:\SDK\tools>cd C:\SDK
C:\SDK>cd platform-tools
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
error: device not found
C:\SDK\platform-tools>_
"error: device not found" every time i try this
USB debugging is on, phone is plugged in set to charge only..
Windows even sees it, the taskbar eject icon says 'Eject MB508"
please please help me get adb to see my phone.. I really want to be able to root this thing!!
EDIT: I noticed the Motorola drivers are 32bit.. I'm going to try 32 bit windows 7 instead of 64 bit and see if I get more successful results
EDIT 2: Bazinga!! Installed Win7 32 bit on my other HDD, booted up, followed the steps again, worked flawlessly! Thanks a lot for the easy instructions, got z4root installed, and my phone worked with permanent root
ErebusRaze said:
Notice:
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Click to expand...
Click to collapse
You wrote in here that once rooted, thebphone would no longer have low memory issues...i rooted my wife's phone, was able to sideload applications (but for some strange reason I am now unable to, as adb command prompt states 'device not found')- but she still gets low memory issues at least 2-3 times a week...
I should just hold up a sign...
LINK2SD
Its in the market
Sent from my MB508 using XDA App
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
thehotrod11 said:
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
Click to expand...
Click to collapse
Link2sd makes installing to sd card possible on 2.1...
Sent from my MB508 using XDA App
Mod Edit: Incomplete instructions. Follow at own risk.
Hello all! I am making this thread, and i know there are plenty out there, because there are still people who cant seem to root their phone no matter what they try. I was one of these people, I couldn't root my phone for the life of me until i tried the method im about to explain to you. Im going to try to make it as easy as possible. Here we go.....
Before we get started:
I am not responsible for what happens to your phone. It will void your warranty and if not followed correctly, can brick your device. So read the directions and follow it to a "T" if you wish to root your phone.
FIRST
Set up ADB/USB Drivers
1. Download the Android SDK from Google.
http://developer.android.com/sdk/index.html
2. Extract the Android SDK .Zip file to C:\AndroidSDK
3. From your phone click SETTINGS, APPLICATIONS, and make sure USB DEBUGGING is on.
4. Plug your phone in via USB to your computer. If you are using windows, it should say installing drivers.
5. After the drivers finish installing, go to the Start menu on your computer and type in CMD in the search bar. You can also click run and type in CMD and it will open the command prompt.
6. Type as follows (hit enter after every line)
cd\
cd AndroidSDK\tools\
adb devices
7. After you have typed all of that, You should see a serial number and the word "device" to the right of it. If you see that, then you are set and can continue reading.
(If it says adb not found or something along those lines, then you need to download these files and extract them into the Tools folder of the SDK)
(If that still doesnt work, then try re-installing the drivers)
SECONDLY
1. Make sure you have visionary installed. (It can be the new r14 version)
2. Download this file [URL="http://www.mediafire.com/?gzaozcurazidh98"]http://www.mediafire.com/?gzaozcurazidh98
3. Unzip the file you just downloaded into the Tools folder in the SDK
4. Plug your phone into the computer.
5. Head over to the Tools folder thats located in the SDK and hold down shift and right click on your mouse over that folder. Select open command window here.
6. Type "adb push gfree /data/local" and press enter. (exclude the quotations)
7. Unplug the device from your computer.
8. Run Visionary to gain temporary root (temp root)
9. Open terminal emulator on your phone (if you dont have it, its a free app in the market) and type "su" (exclude parenthesis) to get root permissions.
10. Type in "cd /data/local" (exclude parenthesis) and press enter.
11. Then type "chmod 777 gfree" (exclude parenthesis) and press enter to make the program executable.
12. Then type in "./gfree" (exclude parenthesis) and press enter.
13. Wait for it to finish then reboot into HBoot by powering down and then powering your device back up by holding volume down and power to see if you have S=OFF. If you have S=OFF with the 0.86.0000 bootloader version, it worked!!
Not to be an ass.... but how is this different from the other threads we have on this?
If people can't figure it out using the guides.... they probably have absolutely no business rooting and should be using a moto razor.
Sent from my HTC Glacier using XDA App
Yeah, this is getting ridiculous...
And by the way, your method there will leave you with a half-rooted device. What I mean is, yes, it is S=OFF, however, you still don't have the su binary and Superuser.apk in the proper places until you "permaroot" with Visionary or another tool by setting the system R/W and putting those binaries in place. That is unless you are already half-assed-rooted with the binaries in place but still S=ON before you even do this. This guide is incomplete, and why so many are having trouble rooting completely.
There are three distinct things that must be done to completely root the MT4G.
1. Temp-root - so you can do the next step.
2. Turn S=OFF - so you can do the next step.
3. Permanently root - to copy the proper binaries and complete the process.
If you can't follow the instructions here: http://forum.xda-developers.com/showthread.php?t=858996 then you shouldn't root your device. No, seriously, we mean it.
Should just delete this thread... incomplete guide with incomplete instructions..... just going to lead to people having problems.
Sent from my HTC Glacier using XDA App
You mean .85.2007?
Sent from my HTC Glacier using XDA App
.........(blank stare)
Made a small change to the OP for the safety of readers.
For the safety of the readers . Lol that sounds so professional
option94 said:
Made a small change to the OP for the safety of readers.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Its simple if u have a backup. I have not heard of anyway of getting to build.prop thru recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
You need to restore from backup (nandroid) or start over if you don't have a backup..
Did you copy the original file to ur sd card then back over?
Chances are you did.. I did the same thing lol.. And when u do that it doesn't save original permissions of the file.
The reason the wallet post says to use root explorer is because it saves the file in the same folder permissions and all and you can just rename it back.
Sorry dude u are sol.. Restore from back up or flash a new rom and start over.
Sent from my SAMSUNG-SGH-I747 using xda premium
Get into recovery, do a factory reset.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
Any resolution. I have the same problem.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
I don't think that would work, as far as I know a factory reset only wipes data and cache. The build.prop is part of the system, so it will not change.
Sent from my SPH-D710 using xda premium
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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.
Side note--> twrp recovery has a built in terminal and the ability to copy/paste files from internal and external SD cards. Not so sure about changing permissions easily....but through the built in terminal....might be able to load what you need (plus twrp flashable found in android dev forum) on external SD card with an adapter on a computer. Flash twrp and transfer files or use built in terminal to change perms. Good luck....
I know editing build props with es file explorer will cause That.
Sent from my SAMSUNG-SGH-I747 using xda premium
Fixed it!
Thanks everyone for your help, i feel like an idiot for not replying to anyone i didnt have it set up to notify me of replies, i figured out it was the build prop that was messed up, im not sure how this worked but i figured i would try to root again and flash the root files using the simple root steps using odin and it actually fixed the file and booted up fine! i appreciate everyones help and hope this thread helps other people because i know many people screw this up the same way i did. (i will never do anything like this without doing a nandroid backup again). THANKS AGAIN!
thanks but..
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
prior to running that command, type su then hit enter
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
stratatak7 said:
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
Click to expand...
Click to collapse
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
lyrictenor1 said:
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
Click to expand...
Click to collapse
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
crammer04 said:
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Click to expand...
Click to collapse
_________________________________________________________________________________________________________________
If you got no back up give us your phone information one of us can send you one I have aTT D2att you
?
Its all in my sig get mobile odin bellow, get the tar for which ever recovery you got. I got all three. CWM, CWM Touch and TWRP for d2att (only) if different phone then use other ones.
Thats my build prop im D2att SG3 ok so just make sure. But you can grab mobile odin bellow and fix it.
_________________________________________
Just get mobile odin HERE
and flash your reocvery there CWM, TWRP, CWM TOUCH... all of them latest all in my sig bro
Here is all drop box to get any of the recoverys --------------------> Recoverys Drop Box
Get mobile odin Here along with the s3 kernal extension its all in here -----------------------> Mobile Odin
If you get hardware id missing error install these old samsung dricers this is a bonus, don't update it ----------------> Hardware ID samsung driver fix
__________________________________________________________
S3 build prop here --------------> here
Mobile odin is simple if download zip in my drop box just install it (or get it form market) download the driver you need (in my drop box) or go mobile odin thread and find it if your on a different phone. Rest is simple just load what your going to flash click the OPEN FILE option in mobile odin click tar and run it.
_________________________________________________________
Get android comander. You can mod build prop easy with it its nice GUI for installing programs or uninstalling or backups or moving files around. awesome try out here --------------------------------> ANDROID COMANDER
need anything else?
---------- Post added at 09:42 PM ---------- Previous post was at 09:20 PM ----------
lyrictenor1 said:
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
Click to expand...
Click to collapse
Tiy need to remount system Read Write i don't think its a SU problem it could be but normaly you already got su i forget comand in adv its mount system -r i beleive. I dunno I run a script that mounts it for me let me check it out real fast
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
crammer04 said:
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
Click to expand...
Click to collapse
Just so you no a common problem when doing commands you forget to do it just trying help didn't know fixed
#!/system/bin/sh
busybox mount -o remount,rw /system
My build.prop got messed up while trying to install Google Wallet on my rooted sg3 and my phone became soft bricked. I had to reinstall the stock jellybean ROM with root that I had been running before this happened, through Odin. Solved my problem. Never got wallet to work though.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Would this work on S3 T-Mobile T-999?
stratatak7 said:
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
Click to expand...
Click to collapse
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Boosoth1st said:
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1746682
Try downloading the toolkit from there. It should contain the necessary T-Mobile files. If you are having an issue, please PM me. Make sure you flash the right one! Be careful and read the whole thread.
I've noticed an increase of users "bricking" their handsets. I use the term "bricking" in the slightest sense, as to them, it is bricked.
The main cause is simply a lack of background knowledge & experience with ADB & Fastboot, I've also noticed that the very helpful guides to recover handsets from this "bricked" state, have an assumption that the users know basic things such as using ADB/Fastboot & cmd. The very things that caused the "brick" in the first place.
Here I'm going to throw together a crash course in the very basics of ADB/Fastboot and how to implement them into your system so that they work all the time and from anywhere on your system. Then an example on how to flash a ROM.
Ensure that USB debugging is enabled on your handset. On HTC Sense it can be found under Settings > Developer Options > Check USB Debugging.
Step One - Download ADB & Fastboot - HERE
Step Two - Extract this to a folder on your C:\ - e.g. "C:\ADB"
Step Three - Add this location to your System PATH - This is important as it makes things a lot easier later
Control Panel > System > Advanced System Settings > Environment Variables...
At the bottom "System Variables" scroll down and find "Path", Click it then "Edit..."
Add to the end of the line named "Variable Value:" ";C:\ADB\" - Try not to delete anything previously in there, the ; is needed, just omit the quotes "".
Hit Ok on the menus and go back to your desktop.
Step Four - Reboot your system or just log out and back in.
Here is a image guide to follow.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-
-
Adding ADB & Fastboot to your System PATH allows you to run the commands adb & fastboot from anywhere in your system. Normally the guide you'd follow would say,
cd into fastboot folder
Click to expand...
Click to collapse
Now you don't need to.
Example usage.
You download a new ROM (CM10) plus GApps & the boot.img from the relevant thread. You copy the ROM & GApps from your computers download folder to your handset. Unmount USB storage and you do the following, making sure that your handset is still plugged in.
Open your computers default download folder.
Shift + Right Click > Open command window here
Type the following
adb devices > Serial Number should be printed
adb reboot bootloader > Device reboots into HBOOT, Fastboot is automatically selected.
fastboot devices > Serial Number should be printed again
fastboot flash boot boot.img > boot.img is sent and flashed, easy. Sometimes the boot.img maybe named different, just start typing and hit TAB, should autocomplete.
fastboot erase cache > not always needed, better being safe
Press the power button on your handset to enter HBOOT, then navigate to RECOVERY and press power.
In Recovery, make your backups as per, and wipe & flash the ROM + GApps, then reboot normally.
Profit
If you still do not understand what you are doing, don't do it. You would not attempt to change a head gasket in your cars engine, unless you knew and understood what you were doing. If you are unsure, search, read & ask until you know what your doing. Sometimes what I write looks too clinical so here's a :cyclops: smiley to lighten the post.
Andy said:
I've noticed an increase of users "bricking" their handsets. I use the term "bricking" in the slightest sense, as to them, it is bricked.
The main cause is simply a lack of background knowledge & experience with ADB & Fastboot, I've also noticed that the very helpful guides to recover handsets from this "bricked" state, have an assumption that the users know basic things such as using ADB/Fastboot & cmd. The very things that caused the "brick" in the first place.
Here I'm going to throw together a crash course in the very basics of ADB/Fastboot and how to implement them into your system so that they work all the time and from anywhere on your system. Then an example on how to flash a ROM.
Ensure that USB debugging is enabled on your handset. On HTC Sense it can be found under Settings > Developer Options > Check USB Debugging.
Step One - Download ADB & Fastboot - HERE
Step Two - Extract this to a folder on your C:\ - e.g. "C:\ADB"
Step Three - Add this location to your System PATH - This is important as it makes things a lot easier later
Control Panel > System > Advanced System Settings > Environment Variables...
At the bottom "System Variables" scroll down and find "Path", Click it then "Edit..."
Add to the end of the line named "Variable Value:" ";C:\ADB\" - Try not to delete anything previously in there, the ; is needed, just omit the quotes "".
Hit Ok on the menus and go back to your desktop.
Step Four - Reboot your system or just log out and back in.
Here is a image guide to follow.
-
-
Adding ADB & Fastboot to your System PATH allows you to run the commands adb & fastboot from anywhere in your system. Normally the guide you'd follow would say,
Now you don't need to.
Example usage.
You download a new ROM (CM10) plus GApps & the boot.img from the relevant thread. You copy the ROM & GApps from your computers download folder to your handset. Unmount USB storage and you do the following, making sure that your handset is still plugged in.
Open your computers default download folder.
Shift + Right Click > Open command window here
Type the following
adb devices > Serial Number should be printed
adb reboot bootloader > Device reboots into HBOOT, Fastboot is automatically selected.
fastboot devices > Serial Number should be printed again
fastboot flash boot boot.img > boot.img is sent and flashed, easy. Sometimes the boot.img maybe named different, just start typing and hit TAB, should autocomplete.
fastboot erase cache > not always needed, better being safe
Press the power button on your handset to enter HBOOT, then navigate to RECOVERY and press power.
In Recovery, make your backups as per, and wipe & flash the ROM + GApps, then reboot normally.
Profit
Click to expand...
Click to collapse
This is what i was looking for. I am just about to flash a ROM in a HTC vivid S-ON and i need it to flash the kernel manually.
Thank you. :cyclops:
Can you boot into recovery with a fast boot command?
Sent from my HTC One X using xda app-developers app
Tw1tchy said:
Can you boot into recovery with a fast boot command?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Fastboot works in the bootloader
ADB works in the running OS and the recovery
So fastboot reboot recovery will work in the bootloader, adb reboot recovery works in the running OS and inside the recovery (if you want to reboot it for some reason when you are already in)
Unfortunately there is no fastboot command (AFAIK) to reboot into recovery from fastboot directly. Your only fastboot reboot options are
fastboot <command>
Code:
reboot
reboot-bootloader
Andy said:
Unfortunately there is no fastboot command (AFAIK) to reboot into recovery from fastboot directly. Your only fastboot reboot options are
fastboot <command>
Code:
reboot
reboot-bootloader
Click to expand...
Click to collapse
Ah my mistake , sorry mate. So it only apply to adb .
Thanks
Mr Hofs said:
Ah my mistake , sorry mate. So it only apply to adb .
Thanks
Click to expand...
Click to collapse
if you are in ADB
"
adb reboot bootleader
adb reboot recovery.
"
but if you are in fastboot you need to navigate to recovery option using the vol up and vol down keys and power on recovery.
:facepalm:
and i was wondering why fastboot write: waiting for device, of course if i use fastboot instead adb to try to reboot my phone in OS
i had forgotten...
Hi Im desperatte trying to root my ATT HTC ONE X with 1.5 using this method http://forum.xda-developers.com/showthread.php?t=1709296
I found this tutorial and I dont know if could work.
I have one big question: After i extracted the file in step one I get a folder named fastboot, instead en adb folder U mentioned in step 2
Im feeling stupid asking so basic things but I prefer to ask and not cry later
Thanks
ErnestoD said:
Hi Im desperatte trying to root my ATT HTC ONE X with 1.5 using this method http://forum.xda-developers.com/showthread.php?t=1709296
I found this tutorial and I dont know if could work.
I have one big question: After i extracted the file in step one I get a folder named fastboot, instead en adb folder U mentioned in step 2
Im feeling stupid asking so basic things but I prefer to ask and not cry later
Thanks
Click to expand...
Click to collapse
No worries, mate. Fastboot folder contains both fastboot and adb commands, so all you have to do is open command prompt in it (something like C:/fastboot/) and then type commands.
Beforehand, you must have htc drivers installed, and the phone connected, of course.
Also, beware that this forum is for International One X with Tegra 3, so be careful with instructions found here.
Thanks man.
I undestood what u said.
My problem is with the fisrt command I should write in the root proccess: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
I copied SU as stated, then typed adb shell and then rm /data/data/com.redbend.vdmc/lib/libvd* . here I get notification about missin file or folder.
The thread Im in is: http://forum.xda-developers.com/showthread.php?t=1709296
Do U understant what should I do or. If Im missing something
Thanks
[email protected]|-|oR said:
No worries, mate. Fastboot folder contains both fastboot and adb commands, so all you have to do is open command prompt in it (something like C:/fastboot/) and then type commands.
Beforehand, you must have htc drivers installed, and the phone connected, of course.
Also, beware that this forum is for International One X with Tegra 3, so be careful with instructions found here.
Click to expand...
Click to collapse
Where did you extract your fasboot/adb commands? Is SU in the same folder? Where do you open your command prompt?
Again, I'm no expert in AT&T One X, but fastboot/adb should be the same.
I suggest you open Windows Explorer, go to your fastboot/adb folder, press SHIFT, and right click your mouse.
Select "Open command window here".
Then type "adb devices" (make sure your phone is connected with USB cable, and USB debugging is turned on).
If adb sees your phone that's good.
Type dir and see if SU inside the folder.
Then follow the steps you should.
I hope this helps.
yes It has worked . Thanks man.
So now I know Im at least oriented. Lets see If I receive more help in the root thread Im talking about.
Thanks one more time
[email protected]|-|oR;40510609]Where did you extract your fasboot/adb commands? Is SU in the same folder? Where do you open your command prompt?
Again, I'm no expert in AT&T One X, but fastboot/adb should be the same.
I suggest you open Windows Explorer, go to your fastboot/adb folder, press SHIFT, and right click your mouse.
Select "Open command window here".
Then type "adb devices" (make sure your phone is connected with USB cable, and USB debugging is turned on).
If adb sees your phone that's good.
Type dir and see if SU inside the folder.
Then follow the steps you should.
I hope this helps.[/QUOTE]
It's alright, mate. That's the whole spirit of XDA.
Take care of you and of your One X, mate! :good:
Thanks
Woot Saved me
Thanks