Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.
Would be nice if you posted that guide on this forum too.
Thanks for the guide.
Oooohh pictures
Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.
"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!
Related
May NOT work for 2.3.3, if attempting on 2.3.3 use old part 1! - Will wipe all data though
Windows ONLY!
Hey guys, rooted my Nexus S today, and decided to write a thorough, detailed guide on how I did it, as none of the guides I had found had everything detailed. I came across a few problems, and all of this is in the guide. I successfully completed it on my Nexus S running 2.3.2, so any version below that will also work.
The original guide was made by AllGamer, and can be found here. I followed this guide, and added things when I found it was needed
The full guide with everything (including links, pictures) can be found on my site, Complete Android.
New info: Upon finding another thread over at XDA (http://forum.xda-developers.com/showthread.php?t=931865) it has been realized that you can root your Nexus S without unlocking the bootloader, and therefore not loosing your data on the SD card. Part 1 for the new method is still the same, but choose the new Part 2!
WARNING: Rooting your device will wipe all data off it, so you will loose EVERYTHING! Make sure you backup all important data first. Only applies to old Part 2 (fastboot oem unlock method), but it is still a good idea to backup important information!
Click to expand...
Click to collapse
What you will need:
Nexus S (obviously)
Android 2.3 SDK
USB Cable
PDAnet (for drivers)
Clockwork Recovery Image
Superuser
Part 1
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Once it has finished downloading, unzip it, and run the SDK manager.
Select whatever components you wish to install, but you MUST make sure you install Google USB Driver (Available packages > Third party Add-ons > Google Inc. Add-ons > Google Usb Driver package, revision 4) otherwise this guide will not work!
We must now install the Google USB Driver, or the phone will not be recognised as a device other than a mass storage device.
Connect your Nexus S to your computer, and put it in USB storage mode.
Put it in USB Debugging Mode (Settings > Applications > Development > USB Debugging)
Windows should now recognise your Nexus S when you plug it in, and ask to install drivers. It probably won’t find anything, so we need to help it manually.
(Installing drivers manually varies between Windows versions, so please refer to http://developer.android.com/sdk/win-usb.html if you are having trouble). Launch Device Manager (you can find it in Control Panel), find Other Devices, and listed under that heading, you should find Nexus S. Right click, and select Update Driver Software. Click Browse my computer for driver software, find your SDK folder, then the google-usb_driver folder inside it, click OK, then Next. This should install the USB driver successfully. Reboot your computer.
Power off your Nexus S, connect it to your computer via USB cable, and boot it into the Bootloader Interface (you can do so by holding down the Power and Volume Up buttons at the same time).
It should say LOCK STATE – LOCKED, in white just above the green Android. You are now ready to move on!
Part 2 - Fastboot oem unlock method - WIPES ALL DATA!
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use ‘fastboot oem unlock’ (the rooting command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn’t).
Now in the command prompt, type in (without the quotes) ‘fastboot oem unlock’.
Now turn your attention to the phone, and read through the new information displayed on the screen. Using the Volume keys select Yes, then press the Power button. This will WIPE EVERYTHING! I bear no responsibility for any lost data on your phone!
If everything is successful, on your phone, the LOCK STATE should now read UNLOCKED, and on your computer, the command prompt window should say something like this:
Download the Clockwork Recovery image (here if you don’t already have it) to your Android SDK tools folder (*Android SDK*\tools).
Rename the newly downloaded Clockwork Recovery image to ‘recovery.img’ (no quotes).
Now we need to flash it to our Nexus S, so enter this command into the Command Prompt (make sure it is in the Androis SDK tools folder!) ‘fastboot flash recovery recovery.img’ (without the quotes).
If all is successful, the Command Prompt window should look something like this now:
Download the superuser app to the Android SDK tools folder.
Power on your Nexus S, leaving it connected to USB.
Mount the USB storage, and drag and drop the superuser .zip file you just downloaded into the root of the internal SD card (so Computer > *Device Name*, not in any other folders!). It should look something like this:
Power off the Nexus S, and return to the Bootloader Interface (step 9, part 1).
Select Recovery using the Volume buttons, then the Power button.
The phone should reboot into Clockwork Recovery, but if not don’t panic, just repeat steps 9-12, including downloading a new copy of the file (mine only worked the second time around, don’t worry!)
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot. (You will now also have an unlocked padlock when you boot up)
Done! You now have to set up your phone again like when you first got it, but it will be rooted now.
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
Make sure Part 1 is completed.
Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot.
Done! You should still have all your data present on your phone, and have root access!
Notes
As AllGamer said in his tutorial:
It’s normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you’ll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you’ll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Keep this in mind! It's not because you did something wrong
Also, some root apps require BusyBox to be installed, as I found out with Titanium Backup, so once you set up your Nexus S again, head on into the Market, and download BusyBox. It installed fine on my Nexus S this way, and now TB works fine.
I hope this is the best, most thorough guide you will find on rooting the Nexus S. Enjoy! Feedback is appreciated, and I will help out if you need any extra help.
Your guide has been wonderful however I'm stuck on part 2, step 4. I tried writing in the path to my directory and they keep giving me whatever I wrote in the command prompt "is not recognized as an internal or external command, operable program or batch file"
"Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’."
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
STARSCR33M said:
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Click to expand...
Click to collapse
Ok so if you want to change directories in the command prompt, you need to use the command
Code:
cd
So in your case I would type in
Code:
cd c:\Users\Du\Downloads\android-sdk_r09-windows\android-sdk-windows\tools
That way is fool proof, however you could take a shortcut, because you are already in the Users/Du folder (because of how it looks when you first open it), you could just type in
Code:
cd Downloads\android-sdk_r09-windows\android-sdk-windows\tools
Hope that helps
ravidavi said:
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Click to expand...
Click to collapse
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
EDIT: New approach added, now there is choice and easyness for all
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
Click to expand...
Click to collapse
Thanks
Jonathon Grigg said:
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
Thanks
Click to expand...
Click to collapse
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step. Once you're in clockwork you pretty much own the phone. I'll be interested to see if someone can use clockwork to flash a new boot image once rooted without the unlock; if so I can't see any reason to unlock the bootloader. That said, mine is unlocked, and I like it that way, but many won't root for fear of losing data on the phone.
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it. I guess that's there own fault for not doing enough searching on their own...
Anyways, nice and thorough effort. I'm sure many will benefit from your additions to AllGamer's tutorial.
distortedloop said:
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step.
Click to expand...
Click to collapse
I have been wondering that myself. My guess is that for the average user you don't need to, but maybe it's for real power users who build their own ROM which has been fully modded or something, I'm not sure.
but many won't root for fear of losing data on the phone.
Click to expand...
Click to collapse
I definitely agree with that, and your guide is probably the best way for those people!
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
Click to expand...
Click to collapse
Exactly, this is one of the better uses for both methods. I already had to wipe my phone twice due to Samsung CS so I'm used to it Although it does give you a chance to clear out the apps you don't need. Doing that I noticed better battery life on my phone.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it.
Click to expand...
Click to collapse
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Thanks distortedloop
This is awesome cause i relocked my bootloader i really just needed root. Thanks!
Edit oops lost track of tabs open.
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Jonathon Grigg said:
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Click to expand...
Click to collapse
Nicely done. Thanks.
sam4free said:
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Click to expand...
Click to collapse
That's what I suggesting a couple of posts above (root without unlock to at least make a backup of user data).
Restoring a titanium backup would not re-lock the phone. A nandroid restore might, depends on what all it imaged and restores, but it's so easy to re-root, that doesn't seem like a big deal.
Jonathon Grigg said:
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Click to expand...
Click to collapse
Looks like you forgot to add the link in your copy pasta.
AtomicPC said:
Looks like you forgot to add the link in your copy pasta.
Click to expand...
Click to collapse
I've been working on it I just wanted to get it up here as soon as I could That's why I mentioned that the full guide is available on my website. I'm going back to school today, so I don't really have too much time for changing links now. Besides, most people on XDA should know how to look at the 'What's needed' part
Sent from my Nexus S using XDA App
Jonathon,
Thank you for posting this detailed guide to rooting without losing your data! I do have a question. As you've probably heard, there are a few updates coming soon and if they are like they were on the N1, they always broke root. So getting root back was tricky unless I "unrooted" before applying the update. Using your method, is it easy to "unroot"? Thanks!
No problems
As for your problem, I never actually had a N1 so I don't exactly know why that would happen. So far from the 2 updates available to NS owners it seems like the OTA update does break root but it appears to be the same to get it back again. Can someone confirm this? I haven't been through an update with my root yet.
As for unrooting, if you haven't unlocked the bootloader (so you have followed the new part 2) I think it is just a case of finding a stock image (I think there's a GRH78 one around here somewhere) and booting into Clockwork Recovery and flashing it. That should remove root and then also give you a notice to install the GRH78C OTA update so you get the latest version.
I think that is what you meant? If you did unlock the bootloader (using the original part 2) then I think you just have to follow the same steps as I mentioned just then but afterwards go back into the bootloader interface and run 'fastboot oem lock' and it should be right.
Sent from my Nexus S using XDA App
Question on Part 2- step 1.
Code:
# We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
hmanxx said:
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
Click to expand...
Click to collapse
When I tried to use the fastboot command with my Nexus S connected, it would hang and not do anything, despite leaving it for about 5 minutes. I searched online, and found the PDAnet solution, so I don't know what the difference is exactly. All I found the Google SDK USB drivers to do is enable you to see your device in Device Manager, however you could try it without the PDAnet drivers, and let me know what happens!
Thanks
Thanks for the prompt reply.. I tried out the google driver..it doesnt work under fastboot. I eventually get the fastboot enabled driver..that could explain why the pdanet driver required.
After i installed the fastboot enabled driver, i could test the connectivity under fastboot with "fastboot devices"
thanks going to try out rooting..i just want simple root access..without wiping data is a ++ ..
I managed to run fastboot boot recovery.img...going into clockwork menu..apply the superuser.zip.(for froyo version)..till completion..no word of failure..
However after rebooting, su and SuperUser.apk are not installed.( I used adb to check the system/app and system/bin folder.
Edit- manage to root properly after system mounting .
Just a note..to properly complete the rooting, one need to apply mounting then mount system before applying the Superuser.zip install from sdcard.
Prior to step 11, you may want to add the following steps for folks having problem to get the superuser.zip to install properly.
Originally Posted by droidmage
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
Thanks for the extra bit of info, I will attempt to add that in when I get a bit more time on my hands. when I did it it seemed to work fine so thanks for discovering that!
Enjoy your rooted phone
Sent from my Nexus S using XDA App
Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?
Disclamer: I take absolutely NO credit for this, I was searching through the forums and found a posting by ragingMonkey that worked for rooting the 10.3.1.E.0.191 build number for the Sony Xperia Z (C6606).
Well, here it is:
you should have your phone in developer mode and have usb debugging on
- i used a flash tool from d-h.st/Kb8
- switched my kernel to d-h.st/1Vz
- rooted with download.cnet.com/Kingo-Android-Root/3000-2094_4-75996768.html
1. you do this by opening flash tool. letting it install. then selecting you device and flashmode drivers.
2. then connect your phone to computer via usb
3. then click the lighting bolt in the top right in the menu bar.
4. a window will pop up. press the flashmode radio button then ok
5. another window will pop up.
6. on the right side of the window it will ask if you wanna wipe types of info like cache, data, applogs. if you want you can click those if not leave them blank.
7. then at the top you will see a browse button to browse files (i think its a ... button)
8. use it to find the kernel
9. after you do that click the flash button and follow the instructions.
10. the instructions are "1 unplug the phone. 2 turn off phone. 3 enter flash mode by pressing and holding the down volume button (while off). 4 connect device (still off)"
11. once you plug the phone back in the flash tool will exit the window you were in and be doing its process in the terminal like window in the original window.
12. after you do that. unplug the device and reboot it. then exit flashtool (important) and then
use the kingo android root.
13. it should do some installing then ask you to connect device
then just follow those instructions in which i dont have up so i cant tell you hope i helped
NOTE: It will say "Root Failed", although it actually did NOT fail and was successful!
BIG thanks to ragingMonkey!
Bye!
There is a much easier way, no different kernals needed. I have also heard alot of negative about kingo root.
Use the tools mentioned here.
http://forum.xda-developers.com/showthread.php?t=2547714
Download both the tools. Make sure you have USB debugging is on and install from unknown sources is on. One of the folders downloaded will have ABD files while the other will not. Copy the ADB files to the one that does not. Run the ADB.exe then run the tool, the install batch file.
I did this with a C6606 on 10.3.1.E.0.191.
Tried going through your suggestion, it didnt help help on my Tmobile C6606. Attached is a screenshot. any suggestions??
Here's my info though:
Android 4.2.2
Build: 10.3.1.E.0.191
Thank you.
deerhurst said:
There is a much easier way, no different kernals needed. I have also heard alot of negative about kingo root.
Use the tools mentioned here.
http://forum.xda-developers.com/showthread.php?t=2547714
Download both the tools. Make sure you have USB debugging is on and install from unknown sources is on. One of the folders downloaded will have ABD files while the other will not. Copy the ADB files to the one that does not. Run the ADB.exe then run the tool, the install batch file.
I did this with a C6606 on 10.3.1.E.0.191.
Click to expand...
Click to collapse
for anyone looking for a solution, this post helped me root my tmo C6606
http://forum.xda-developers.com/showpost.php?p=48861859&postcount=26
Thanks everyone.
This is my NOOB friendly version for rooting and installing Dual Recovery on a Sony Xperia Z1S (C6916).
First things first, I have written this entire this myself and have only used links from other posts here on XDA.
The thank you's will be at the end of this post.
Ok, Now onto the real reason your here...
Follow these steps to pre-pair your Z1S for the road ahead...
1) Go to "Settings-About Phone".
Be sure your "Model Number" is "C6916".
Your "Build Number" is "14.4.B.0.37".
If your "Build Number" is different then see 2nd post for "How to Downgrade/Upgrade Build Number"
2) Click "Build Number" about 7 times (I think) to unlock "Developer Mode".
3) Go back to "Settings" screen.
Second option from the bottom should now be "Developer Options".
5) Enter this new screen and enable "USB Debugging".
6) Go back to "Settings" and enter "Security".
Enable "Unknown Sources" and disable "Verify Apps".
7) Go to "support.sonymobile.com/us/tools/pc-companion/"
Download, Install, plug device in, and it should detect and install drivers for your Z1S.
8) Download & Extract "forum.xda-developers.com/showthread.php?t=2784900" to a folder on the desktop (Name folder something easy like Z1S).
9) Download & Extract "Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip" from "nut.xperia-files.com/" by clicking the "XZDualRecovery" to the same folder from step #8 (keeping separate folders inside to avoid confusion).
Well that seemed like allot now didn't it? Well the worst is over (hopefully).
Follow the below steps to root your phone...
1) On computer go to the folder where you extracted "Easy Root Tool v12.4"
Run file called "install.bat"
Wait for it to load and follow the on-screen instructions to gain root.
Notes!!!
a) If at any time it seems like the tool has frozen, it probably has.
Wait for at least 1 minute and then click the red X in the top right of the window to close.
Press "Ctrl+Alt+Delete" and select "Start Task Manager" (depending upon windows version).
Choose the "Processes" tab and look for "abd.exe".
Choose it and then click "End Process" and confirm in the new window.
If you do not find "adb.exe" or you have killed it already then repeat step 1.
2) Once Easy Root Tool v12.4 has completed and shows a successes message you will be rooted! But we cant just use it as it is now, its "SuperSU Binary" is outdated.
3) Unplug usb and reboot your phone.
4) Once rebooted, go to the "Play Store" and search for and download "supersu" by "Chainfire" (support him if you can )
5) Once installed run supersu and a window should come up saying to update binaries...well...update them
6) When finished you will now have root, super user control, but outdated "BusyBox".
******* NOTE!!!I have found out that some users were having problems after updating "BusyBox".
Update at your own risk!!!
BTW it worked for me with and without updating so I'm just giving feedback from other users.
7) Use "Play Store" again to download, install, and run "BusyBox" by "Stephen (Stericson)".
a) Let it run until "Smart Install" is finished.
b) Choose "Replace All (Symlinks all)" (not supposed to be able to but it worked for me )
b1) if it doesn't check then don't worry about it. its an extra step
8) Choose "Install" and wait for process to finish.
9) Congratulations! You now have Root, SuperSU, and BusyBox needed to use your phone to its (almost) full potential.
Now onto the Custom Recovery...1) Go to the folder we created (in a land far far away...lol...couldn't help it ) and go into the dual recovery folder.
a) Run "install.bat" and (if we installed SuperSU) choose option #1 (if we installed SuperUser) choose option #2.
b) Follow instructions until you get success message. (see above for freeze or errors fixes at 1-a)
2) Congrats again! this time you now have a dual recovery!
a) I recommend installing "NDRUtils [root]" by "CamberCreek", it makes things much easier with your new found recoveries.
Here is my who's who and thank you's for this post. (this is in order of use in guide not relevance or importance)1) XDA for such a great site!
2) Sony Mobile for a great phone and PC Companion.
3) zxz0O0 for his Easy Root Tool v12.4 without which I would have been lost.
4) [NUT]'s Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip recoveries woot!
5) Chainfire for SuperSU the force in this rooted world.
6) Stephen (Stericson) for BusyBox the gears that keep us going.
7) CamberCreek for NDRUtils [root] making Xperia recoveries easier since....
8) Bin4ry & Androxyde for Flashtool making time travel possible?
9) And anyone else i might have missed.
Hope this helps those that were stuck like myself trying to get my phones true power unlocked!
***** NOTE!!!I'm not sure if its just me/my phone/everyone's phone but i have noticed while working to get adb to recognize my device my usb debugging would seem to not be working (adb devices). If anyone has some feed back about this problem i would love to hear. BTW my device is less then 2 months old.
Ok, so you updated and now want to root? Well great news! We can get you downgraded to "14.4.B.0.37" so you can rock like the rest of them!
1) Download, install "flashtool.net/downloads.php".
2) Download "storagecow.eu/Xda/Sony/Xperia%20Z1s/C6916_14.4.B.0.37_T-Mobile.ftf".
3) Move "C6916_14.4.B.0.37_T-Mobile.ftf" to folder "C:\Users\(your name)\.flashTool\firmwares".
4) Run "Flashtool" and wait for loading to finish.
a) Connect your device and Flashtool should recognize it and show that it is connected and has debugging turned on.
1a) If debugging is off then go to "Developer Settings" again and turn off then back on the "USB Debugging" option.
b) Click the lightning bolt in the top left area.
c) Choose "Flashmode" and click "Ok".
d) On the left should be the files you moved, choose "", uncheck the "DATA" box on the right side, and lastly choose "Flash".
e) When it says to turn "Off" your device and enter "Flash mode", turn off and wait for the charging screen (if connected still) or it to fully turn off.
f) Disconnect device and hold down "Vol. Down" and plug device back in. When you see your charging lights show/flash a few times you should have a blank screen and no lights.
g) Flashtool should have automatically started flashing now.
h) When finished exit flashmode by removing usb and holding the power button down to turn on. If it dont vibrate after a few seconds just release power and try again.
5) Felicitations! You should not be running "14.4.B.0.37" and are now able to follow above guide!
Forgot to mention that once finished rooting with above method you can upgrade to latest (as of this post) and still keep root. happy rooting
theshadower10 said:
This is my NOOB friendly version for rooting and installing Dual Recovery on a Sony Xperia Z1S (C6916).
First things first, I have written this entire this myself and have only used links from other posts here on XDA.
The thank you's will be at the end of this post.
Ok, Now onto the real reason your here...
Follow these steps to pre-pair your Z1S for the road ahead...
1) Go to "Settings-About Phone".
Be sure your "Model Number" is "C6916".
Your "Build Number" is "14.4.B.0.37".
If your "Build Number" is different then see 2nd post for "How to Downgrade/Upgrade Build Number"
2) Click "Build Number" about 7 times (I think) to unlock "Developer Mode".
3) Go back to "Settings" screen.
Second option from the bottom should now be "Developer Options".
5) Enter this new screen and enable "USB Debugging".
6) Go back to "Settings" and enter "Security".
Enable "Unknown Sources" and disable "Verify Apps".
7) Go to "support.sonymobile.com/us/tools/pc-companion/"
Download, Install, plug device in, and it should detect and install drivers for your Z1S.
8) Download & Extract "forum.xda-developers.com/showthread.php?t=2784900" to a folder on the desktop (Name folder something easy like Z1S).
9) Download & Extract "Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip" from "nut.xperia-files.com/" by clicking the "XZDualRecovery" to the same folder from step #8 (keeping separate folders inside to avoid confusion).
Well that seemed like allot now didn't it? Well the worst is over (hopefully).
Follow the below steps to root your phone...
1) On computer go to the folder where you extracted "Easy Root Tool v12.4"
Run file called "install.bat"
Wait for it to load and follow the on-screen instructions to gain root.
Notes!!!
a) If at any time it seems like the tool has frozen, it probably has.
Wait for at least 1 minute and then click the red X in the top right of the window to close.
Press "Ctrl+Alt+Delete" and select "Start Task Manager" (depending upon windows version).
Choose the "Processes" tab and look for "abd.exe".
Choose it and then click "End Process" and confirm in the new window.
If you do not find "adb.exe" or you have killed it already then repeat step 1.
2) Once Easy Root Tool v12.4 has completed and shows a successes message you will be rooted! But we cant just use it as it is now, its "SuperSU Binary" is outdated.
3) Unplug usb and reboot your phone.
4) Once rebooted, go to the "Play Store" and search for and download "supersu" by "Chainfire" (support him if you can )
5) Once installed run supersu and a window should come up saying to update binaries...well...update them
6) When finished you will now have root, super user control, but outdated "BusyBox".
******* NOTE!!!I have found out that some users were having problems after updating "BusyBox".
Update at your own risk!!!
BTW it worked for me with and without updating so I'm just giving feedback from other users.
7) Use "Play Store" again to download, install, and run "BusyBox" by "Stephen (Stericson)".
a) Let it run until "Smart Install" is finished.
b) Choose "Replace All (Symlinks all)" (not supposed to be able to but it worked for me )
b1) if it doesn't check then don't worry about it. its an extra step
8) Choose "Install" and wait for process to finish.
9) Congratulations! You now have Root, SuperSU, and BusyBox needed to use your phone to its (almost) full potential.
Now onto the Custom Recovery...1) Go to the folder we created (in a land far far away...lol...couldn't help it ) and go into the dual recovery folder.
a) Run "install.bat" and (if we installed SuperSU) choose option #1 (if we installed SuperUser) choose option #2.
b) Follow instructions until you get success message. (see above for freeze or errors fixes at 1-a)
2) Congrats again! this time you now have a dual recovery!
a) I recommend installing "NDRUtils [root]" by "CamberCreek", it makes things much easier with your new found recoveries.
Here is my who's who and thank you's for this post. (this is in order of use in guide not relevance or importance)1) XDA for such a great site!
2) Sony Mobile for a great phone and PC Companion.
3) zxz0O0 for his Easy Root Tool v12.4 without which I would have been lost.
4) [NUT]'s Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip recoveries woot!
5) Chainfire for SuperSU the force in this rooted world.
6) Stephen (Stericson) for BusyBox the gears that keep us going.
7) CamberCreek for NDRUtils [root] making Xperia recoveries easier since....
8) Bin4ry & Androxyde for Flashtool making time travel possible?
9) And anyone else i might have missed.
Hope this helps those that were stuck like myself trying to get my phones true power unlocked!
***** NOTE!!!I'm not sure if its just me/my phone/everyone's phone but i have noticed while working to get adb to recognize my device my usb debugging would seem to not be working (adb devices). If anyone has some feed back about this problem i would love to hear. BTW my device is less then 2 months old.
Click to expand...
Click to collapse
Ugh, where were you when I was stuck on 4.4? :laugh: I ended up downgrading my c6916 to 4.3 when I rooted it, it was the only way I could seem to achieve root. Hopefully this article will help someone out!
I myself haven't experienced any issues with adb/debugging, but maybe it's because I'm on a different os build.
So grateful for the EasyRoot tool!
Glad this could help you and thanks for the feedback
Thank you for this! I just got the lollipop update notification but wanted to double check to see if I could root before updating. Glad I did!
Two questions...
This file.... Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip I cannot find. I can only find the 2.8.15 version. Will that do?
Also... Since I just got the lollipop update. Can I OTA to that and keep root?
silentsnow31802 said:
Thank you for this! I just got the lollipop update notification but wanted to double check to see if I could root before updating. Glad I did!
Two questions...
This file.... Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip I cannot find. I can only find the 2.8.15 version. Will that do?
Also... Since I just got the lollipop update. Can I OTA to that and keep root?
Click to expand...
Click to collapse
Yes, that version is fine and will work. Also, I will update this soon. Just been busy with work so haven't had time as of yet. Also if you update you will loose root and have to start over again. Hope this helped.
So I am stuck..
Hey. So I was on 4.5 Lolipop and decided to follow the guide, the 2nd one first of course. And now I am in a Boot loop. and stuck.
Any suggestions or help ?
BTW i really do not want to wipe everything using the companion software. ...Did not fully back it up :/
me too
dweller02 said:
Hey. So I was on 4.5 Lolipop and decided to follow the guide, the 2nd one first of course. And now I am in a Boot loop. and stuck.
Any suggestions or help ?
BTW i really do not want to wipe everything using the companion software. ...Did not fully back it up :/
Click to expand...
Click to collapse
did you get any solution to stop dat ?
---------- Post added at 01:16 PM ---------- Previous post was at 01:11 PM ----------
theshadower10 said:
Ok, so you updated and now want to root? Well great news! We can get you downgraded to "14.4.B.0.37" so you can rock like the rest of them!
1) Download, install "flashtool.net/downloads.php".
2) Download "storagecow.eu/Xda/Sony/Xperia%20Z1s/C6916_14.4.B.0.37_T-Mobile.ftf".
3) Move "C6916_14.4.B.0.37_T-Mobile.ftf" to folder "C:\Users\(your name)\.flashTool\firmwares".
4) Run "Flashtool" and wait for loading to finish.
a) Connect your device and Flashtool should recognize it and show that it is connected and has debugging turned on.
1a) If debugging is off then go to "Developer Settings" again and turn off then back on the "USB Debugging" option.
b) Click the lightning bolt in the top left area.
c) Choose "Flashmode" and click "Ok".
d) On the left should be the files you moved, choose "", uncheck the "DATA" box on the right side, and lastly choose "Flash".
e) When it says to turn "Off" your device and enter "Flash mode", turn off and wait for the charging screen (if connected still) or it to fully turn off.
f) Disconnect device and hold down "Vol. Down" and plug device back in. When you see your charging lights show/flash a few times you should have a blank screen and no lights.
g) Flashtool should have automatically started flashing now.
h) When finished exit flashmode by removing usb and holding the power button down to turn on. If it dont vibrate after a few seconds just release power and try again.
5) Felicitations! You should not be running "14.4.B.0.37" and are now able to follow above guide!
Click to expand...
Click to collapse
Hey i was running at lollipop 5.0.2.while i was using the second method first my mobile is looping after flashing...kindly tell me a solution
sorry for not a faster response...haven't had internet for awhile
anyways, for above 2 posts...i had updated to 5.0.2 and had to downgrade myself.
i had followed the same thing as above just updated the programs and apps from their respective owners.
i had no issues and have even upgraded back up to 5.0.2 using a different guide found on xda.
cant remember for the life of me what post it was though...
since i still have no internet and am typing this on friends laptop, i would suggest searching for other guides here to find one.
My apologies beforehand: I have Xperia Z1S (C6916, Android 5.0.2, Build #: 14.5.B.0.247), unlocked bootloader, Android Lollipop & would like to root my phone after first downgrading it. Viewing this post, I would like to know where I can get access to the files mentioned in this post. Or am I a year too late?
he has mentioned the links to the files
1)"forum.xda-developers.com/showthread.php?t=2784900" for Easy root tool
(you can even try kingroot "https://kingroot.net/" if you want,i used kingroot to root my Z1)
2) "nut.xperia-files.com/" for XZdualrecovery
3)use playstore for downloading Superuser by chainfire
4)"support.sonymobile.com/us/tools/pc-companion/" for pc companion
Hi
(Sorry for my little english, feel free to speak french if you can)
I have try to root my 4X HD for using a better recovery app (recover pictures deleted in sd card, now you know my skill). I have use this page: (as newbie i cant post outside links)
n fact, I never had an Android device where this was that easy to achive! Our friends at XDA-Developers offer a guide and the necessary tools in this thread. Having a "Microsoft free zone" and "only" running Linux machines (yeah, even the Android ones run a Linux kernel), I was able to follow up those steps with a little adaption here and there -- and so I will sum up the results for Windows and Linux users as well:
Preparation
First you need to download the required tools, all of them available at the linked XDA-Developers thread:
o4xr.zip is the rooting toolkit
IS11LG_SystemBackupTest.signed.apk to prepare your device
Windows users only: LGUnitedMobileDriver_Ver_3.7.2_LG-P880_LGO4XHD.zip -- the Windows drivers for the device
Having everything downloaded, some additional steps are necessary at your computer:
Windows users only: Unzip and install the drivers
Linux users: Make sure adb is able to detect the device (check with adb devices). If it's not, see at the end of this answer for some hints.
Everybody: Copy IS11LG_SystemBackupTest.signed.apk to your Optimus (e.g. after connecting it via USB in MTP mode, copy the file to the internal SDCard)
Everybody: Create a new directory, unzip o4xr.zip there, and change into this directory.
The rooting process
On your Optimus, go to Settings→Security and make sure "Unknown Sources" is TICKED (i.e. contains a checkmark)
Go to Settings→Developer Options and enable "USB Debugging"
Now install IS11LG_SystemBackupTest.signed.apk (e.g. use a file explorer to find and "launch" it)
Open the "SystemBackupTest" app you just installed. Nothing spectacular will happen, so don't be disappointed here.
Hold the power button and choose "Power off and restart".
When you can see the lock screen, you may notice that the phone is running very slowly, this is normal.
Once the device is fully started up again, connect it to your computer with an USB cable. Make sure the phone is in "Charging Only" mode.
On your PC, open a terminal (Linux) resp. command (cmd.exe, Windows) window and change into the directory you've extractedo4xr.zip` into.
(on Windows, you may need admin privileges: right click, run as administrator. On Linux it did fine for me without superuser/root permissions)
Now run the rooting script:
Windows users: type root followed by the enter key
Linux users: type ./root-linux.sh, also followed by the enter key
Any Mac users? Type ./root-mac.sh, also followed by the enter key. Don't worry, it won't root your Mac/Linux machine (Windows users: it is unlikely to root your box, either
DO NOT DISCONNECT YOUR PHONE WHILE THE SCRIPT RUNS! Wait while it does its job. During that process, the phone will reboot automatically a couple of times. The script will inform you about this in your command/terminal window. Once the command/shell prompt returns, the misdeed is accomplished
Now uninstall SystemBackupTest from your Optimus. Do not launch it again at this state, or you might have to start over from step 5
On your phone, open up Google Play Store and search for "SuperSU". Update the app when prompted, then open it. Press OK to update the SU binary.
You now have root and can safely restore the "Unknown Sources" and "USB debugging" settings back to how you had them! Congratulations! Next steps are to install Titanium Backup, LBE Privacy Guard, and all the other things you might need and which require root!
At step 8. i got "command not found" in Terminal (Linux Mint), assuming script don't work i have reboot my device.
Since my phone boot but is very very slow and screen is friezed, even if i can unlock my SIM card by memory pattern (without sim card and always by memory i can see Settings of android but not down the list).
In recovery boot (Sound up + Power), my device show me a picture that would say "dont unplug charge and usb".
I guess my phone is not rooted, adb can list it but not fastbood. LG software (on windows 7) cant communicate with it because usb driver not work. I guess i've try and read more since 8 hours but my brain is off right now. Any help will be very welcome.
Cheers