After seeing so many people get hung up on complicated guides to manually update to 4.4, I thought I'd write the simple guide during my next bout of insomnia. So, no sleep tonight for me means a new guide for you. It's very simple, with only four steps: 1) download the OTA update, 2) reboot into recovery, 3) prepare to sideload, and 4) sideload.
Preamble:
I use a Mac. My Nexus 7 2013 is WiFi only (flo). This guide is written from that perspective.
It's just as easy to do this from any computer you'd like (e.g. Linux, Mac, or Windows *see end of post*). The commands are exactly the same. The only difference is the way you install the android SDK (+/- USB drivers *see end of post*) and open a terminal or command prompt on your machine of choice. Learning this is simple and necessary for developing, hacking, rooting, unbricking on ANY ANDROID DEVICE.
Three things you need to have set up before starting
Other than being stock, the other items on this list are going to come in handy if you want to fully realize the potential of your nexus device, so take a minute and set it up if you haven't already.
1. NEXUS 7 2013, build number JSS15R, with STOCK ROM. The guide is written from the perspective of STOCK RECOVERY, but it's been done from TWRP (I swear to god). Yes, you can be any combination of rooted, unrooted, locked, unlocked, but if you're rooted, you should probably revert any changes you've made to system files before starting.
2. Up to date android platform tools from the SDK installed on your Mac:
http://developer.android.com/sdk/index.html
Note: the only platform tool you need to sideload is adb.
3. USB debugging enabled on your Nexus 7:
Settings, About tablet, tap build number a bunch of times to enable developer options, back out to settings, developer options, check USB debugging
THE ACTUAL GUIDE:.
STEP 1 (DOWNLOAD):
This is the second hardest step in this guide. You have to download the OTA, not the factory image, so, on your Mac, download this file: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
STEP 2 (REBOOT INTO RECOVERY):
a. Hold the Power and Volume down buttons at the same time to enter fastboot mode.
b. Find and select "Recovery Mode" using the volume and power buttons
STEP 3 (PREPARE TO SIDELOAD):
a. Connect your N7 to your Mac with a USB cord
b. While in recovery mode, hold the power button and tap the volume up button (this is the hardest part of the guide).
c. Select "apply update from ADB"
STEP 4 (SIDELOAD):
a. Open a terminal window on your Mac and type "adb devices". Terminal will identify your nexus 7.
b. Type "adb sideload ". Don't forget the space.
c. Open a finder window and find the file you downloaded in step 1. Drag and drop it to your terminal window. Press enter.
VICTORY!
* Windows 8.1 x64 drivers, thanks to sahilcc7: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Command not found
xdhall said:
After seeing so many people get hung up on complicated guides to manually update to 4.4, I thought I'd write the simple guide during my next bout of insomnia. So, no sleep tonight for me means a new guide for you. It's very simple, with only four steps: 1) download the OTA update, 2) reboot into recovery, 3) prepare to sideload, and 4) sideload.
Preamble:
I use a Mac. My Nexus 7 2013 is WiFi only (flo). This guide is written from that perspective.
It's just as easy to do this from any computer you'd like (e.g. Linux, Mac, or Windows). The commands are exactly the same. The only difference is the way you install the android SDK (+/- USB drivers) and open a terminal or command prompt on your machine of choice. Learning this is simple and necessary for ANY developing, hacking, rooting, unbricking on ANY ANDROID DEVICE.
Three things you need to have set up before starting
Other than being stock, the other items on this list are going to come in handy if you want to fully realize the potential of your nexus device, so take a minute and set it up if you haven't already.
1. NEXUS 7 2013, build number JSS15R, with STOCK ROM. The guide is written from the perspective of STOCK RECOVERY, but it's been done from TWRP (I swear to god). Yes, you can be any combination of rooted, unrooted, locked, unlocked, but if you're rooted, you should probably revert any changes you've made to system files before starting.
2. Up to date android SDK installed on your Mac:
Follow instructions here: http://developer.android.com/sdk/index.html
3. USB debugging enabled on your Nexus 7:
Settings, About tablet, tap build number a bunch of times to enable developer options, back out to settings, developer options, check USB debugging
THE ACTUAL GUIDE:.
STEP 1 (DOWNLOAD):
This is the second hardest step in this guide. You have to download the OTA, not the factory image, so, on your Mac, download this file: http://android.clients.google.com/packages/data/ota/google_razor/3a3951e8243c82bc01a620ab858f4454c8ebd65c.signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
STEP 2 (REBOOT INTO RECOVERY):
a. Hold the Power and Volume down buttons at the same time to enter fastboot mode.
b. Find and select "Recovery Mode" using the volume and power buttons
STEP 3 (PREPARE TO SIDELOAD):
a. Connect your N7 to your Mac with a USB cord
b. While in recovery mode, hold the power button and volume up button down (this is the hardest part of the guide).
c. Select "apply update from ADB"
STEP 4 (SIDELOAD):
a. In the terminal window on your Mac, type "adb sideload "
b. Open a finder window and find the file you downloaded in step 1. Drag and drop it to your terminal window. Press enter.
VICTORY!
Click to expand...
Click to collapse
I downloaded the SDK file for Mac and set up the Eclipse app. However I get a "Command Not Found" when I try to type into Terminal? I appreciate seeing instructions for a Mac; thank you.
Make sure you're connected with a microUSB. Type "adb devices" in terminal to verify that you're hooked up.
Sent from my Nexus 7 using Tapatalk 4
Also, be sure there's a space between the word sideload and the file name that shows up after you've dropped the zip onto the terminal window.
Sent from my Nexus 7 using Tapatalk 4
That's another problem I'm having my files automatically unzip. I'm looking to find out how to stop that from happening.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
---------- Post added at 02:24 AM ---------- Previous post was at 02:21 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
You can use Mini ADB and Fastboot Installer from xda too, just 2mb. I used it.
Sent from my Nexus 7 (2013)
bobng said:
That's another problem I'm having my files automatically unzip. I'm looking to find out how to stop that from happening.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
Click to expand...
Click to collapse
In theory the first time you execute an adb command during a session in terminal you'll get the following echo:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Then it will execute your initial command.
I've added an adb devices command to the guide so if anyone reports a problem, they'll already know if they've been able to communicate across the microUSB cord.
Sent from my Nexus 7 using Tapatalk 4
I downloaded everything again and even though I deleted a program that aoto unzipped files the both unzipped. I connected the tablet and tried "adb Devices" and still returned -bash: adb: command not found
I've been at this for several hours. Google might even beat me with their installation at this rate.
bobng said:
I downloaded everything again and even though I deleted a program that aoto unzipped files the both unzipped. I connected the tablet and tried "adb Devices" and still returned -bash: adb: command not found
I've been at this for several hours. Google might even beat me with their installation at this rate.
Click to expand...
Click to collapse
I believe you're missing a step or so when installing sdk. You likely need to edit your profile. I couldn't readily find it on the Google site, but here's an independent guide: http://m.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/. I expect the part your missing begins with step 4 under "Installing on Mac OS X; Installing the Android SDK"
Sent from my Nexus 7 using Tapatalk 4
xdhall said:
I believe you're missing a step or so when installing sdk. You likely need to edit your profile. I couldn't readily find it on the Google site, but here's an independent guide: http://m.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/. I expect the part your missing begins with step 4 under "Installing on Mac OS X; Installing the Android SDK"
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks, I rarely use Terminal so will have to read up some more to get this working.
bobng said:
Thanks, I rarely use Terminal so will have to read up some more to get this working.
Click to expand...
Click to collapse
I should be able to walk you through it tomorrow.
Sent from my Nexus 7 using Tapatalk 4
Thanks, guide worked great. Just the part where you select adb sideload - maybe state that you should hold power and tap vol up to select it. I got stuck there.
And for those with Windows 8.1 x64: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked.
bobng said:
Thanks, I rarely use Terminal so will have to read up some more to get this working.
Click to expand...
Click to collapse
Basically you need to tell terminal where to find the bits of the various SDK programs by editing your bash profile. This is how terminal knows what you mean when you ask it to execute an adb or fastboot command. Let me simplify from the androidauthority guide. It takes three lines of code.
Open up a terminal window and execute the following:
Step 1: This step lets you edit the profile that tells terminal where to find executable binary files
Type and press enter:
Code:
vi ~/.bash_profile
Step 2: The step actually edits said profile
Type but don't press enter:
Code:
export PATH=$PATH:
Open a Finder window and find the folder "platform-tools" in the sdk folder (make sure you've put your sdk folder wherever you want it to live--if you move it later, terminal won't be able to find it). Drag and drop the folder on the terminal window. This time you DON'T want a space between the typed code and the file path.
Now press enter.
Step 3: This step saves your changes
Type and press enter:
Code:
source $HOME/.bash_profile
From now on, whenever you open a terminal window, you'll be able to use your sdk tools.
sahilcc7 said:
Thanks, guide worked great. Just the part where you select adb sideload - maybe state that you should hold power and tap vol up to select it. I got stuck there.
And for those with Windows 8.1 x64: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked.
Click to expand...
Click to collapse
Updated OP with the recommended tweak to the language and the link to the drivers. Thanks!
Sent from my Nexus 7 using Tapatalk 4
This worked for me without issue. I only had to install the proper drivers and after that it went smooth.
I tried your suggestion and as you can see Step 1 wasn't successful but I tried the rest the result is as follows:
Last login: Mon Nov 18 21:56:38 on ttys000
Bobs-Retina:~ bobng$ vi -/.bash_profile
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
Unknown option argument: "-/.bash_profile"
More info with: "vim -h"
Bobs-Retina:~ bobng$ vi-/.bash_profile
-bash: vi-/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$ vim -h
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
usage: vim [arguments] [file ..] edit specified file(s)
or: vim [arguments] - read text from stdin
or: vim [arguments] -t tag edit file where tag is defined
or: vim [arguments] -q [errorfile] edit file with first error
Arguments:
-- Only file names after this
-v Vi mode (like "vi")
-e Ex mode (like "ex")
-s Silent (batch) mode (only for "ex")
-d Diff mode (like "vimdiff")
-y Easy mode (like "evim", modeless)
-R Readonly mode (like "view")
-Z Restricted mode (like "rvim")
-m Modifications (writing files) not allowed
-M Modifications in text not allowed
-b Binary mode
-l Lisp mode
-C Compatible with Vi: 'compatible'
-N Not fully Vi compatible: 'nocompatible'
-V[N][fname] Be verbose [level N] [log messages to fname]
-D Debugging mode
-n No swap file, use memory only
-r List swap files and exit
-r (with file name) Recover crashed session
-L Same as -r
-T <terminal> Set terminal type to <terminal>
-u <vimrc> Use <vimrc> instead of any .vimrc
--noplugin Don't load plugin scripts
-p[N] Open N tab pages (default: one for each file)
-o[N] Open N windows (default: one for each file)
-O[N] Like -o but split vertically
+ Start at end of file
+<lnum> Start at line <lnum>
--cmd <command> Execute <command> before loading any vimrc file
-c <command> Execute <command> after loading the first file
-S <session> Source file <session> after loading the first file
-s <scriptin> Read Normal mode commands from file <scriptin>
-w <scriptout> Append all typed commands to file <scriptout>
-W <scriptout> Write all typed commands to file <scriptout>
-x Edit encrypted files
--startuptime <file> Write startup timing messages to <file>
-i <viminfo> Use <viminfo> instead of .viminfo
-h or --help Print Help (this message) and exit
--version Print version information and exit
Bobs-Retina:~ bobng$ -v -/.bash_profile
-bash: -v: command not found
Bobs-Retina:~ bobng$ export PATH=$PATH:/Users/bobng/Downloads/adt-bundle-mac-x86_64-20131030/sdk/platform-tools
Bobs-Retina:~ bobng$ source $HOME/.bash_profile
-bash: /Users/bobng/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$
I just upgraded to Mavericks, not sure if that makes a difference?
bobng said:
I tried your suggestion and as you can see Step 1 wasn't successful but I tried the rest the result is as follows:
Last login: Mon Nov 18 21:56:38 on ttys000
Bobs-Retina:~ bobng$ vi -/.bash_profile
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
Unknown option argument: "-/.bash_profile"
More info with: "vim -h"
Bobs-Retina:~ bobng$ vi-/.bash_profile
-bash: vi-/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$ vim -h
I just upgraded to Mavericks, not sure if that makes a difference?
Click to expand...
Click to collapse
You're using a hyphen where you need a tilda.
You typed: vi -/.bash_profile
It should be: vi ~/.bash_profile
vi space tilda forward slash period bash underscore profile
It might help to copy and paste the code from my post directly into terminal.
Thanks again, I see that it is a tilda now. I appreciate you sticking with me.
---------- Post added at 01:15 AM ---------- Previous post was at 01:00 AM ----------
OK, I got in trouble again. When I did Step 2 I got a message abowut not being found. I tried to copy and somehow moved it and couldn't get a prompt. So I tried to shut down and start over, not a good idea. Here is where I am now:
Bobs-Retina:~ bobng$ vi ~/.bash_profile
E325: ATTENTION
Found a swap file by the name "~/.bash_profile.swp"
owned by: bobng dated: Tue Nov 19 19:04:46 2013
file name: ~bobng/.bash_profile
modified: YES
user name: bobng host name: Bobs-Retina.local
process ID: 20981
While opening file "/Users/bobng/.bash_profile"
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /Users/bobng/.bash_profile"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/Users/bobng/.bash_profile.sw
p"
to avoid this message.
Swap file "~/.bash_profile.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:
bobng said:
Thanks again, I see that it is a tilda now. I appreciate you sticking with me.
---------- Post added at 01:15 AM ---------- Previous post was at 01:00 AM ----------
OK, I got in trouble again. When I did Step 2 I got a message abowut not being found. I tried to copy and somehow moved it and couldn't get a prompt. So I tried to shut down and start over, not a good idea. Here is where I am now:
Bobs-Retina:~ bobng$ vi ~/.bash_profile
E325: ATTENTION
Found a swap file by the name "~/.bash_profile.swp"
owned by: bobng dated: Tue Nov 19 19:04:46 2013
file name: ~bobng/.bash_profile
modified: YES
user name: bobng host name: Bobs-Retina.local
process ID: 20981
While opening file "/Users/bobng/.bash_profile"
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /Users/bobng/.bash_profile"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/Users/bobng/.bash_profile.sw
p"
to avoid this message.
Swap file "~/.bash_profile.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:
Click to expand...
Click to collapse
Delete the swap file by executing the following:
Code:
rm -r ~/.bash_profile.swp
Don't forget the ".swp" at the end
Then start again
Here's what I did, I downloaded the the full image, some 400mb to
File i found in the forums here, I then rebooted into twrp, and installed from zip.
Boom.
All my apps were ok apart from the browser. I'm on 4.4, have new kit Kat features etc. Other than that, how do I know if I did it right?
Sent from my Nexus 7 using xda app-developers app
Related
Can someone please help me, or point me in the right direction on how to setup and run simple commands through adb on a MAC? Yes, I've used the search, and yes I've searched all over the internet but I still cannot figure it out. Sorry for my stupidity lol
But any help would be greatly appreciated, thank you
Perhaps you could say a few words about what you have tried already and where you are stopped.
I'm assuming you've downloaded and installed the Mac version of the SDK, yes?
On the phone, you need to turn on Settings -> Applications -> Development -> USB debugging (and may as well check "Stay awake", too).
I don't have a OS/X box, but on Linux you need to perform the *first* adb command as root... the first time an "adb" command is run (after a reboot) it starts up an adb-server process, and that needs to be priviliged enough to write to USB. (After that, you can run adb commands as any user, since those commands "talk" to the adb-server on your Mac, which in turn talks to the phone over the USB cable.)
bftb0
Go to developer. android. com/sdk/index.html (take out the spaces - I still can't post links for some reason) and download the Android SDK for Mac. That same page also includes directions on how to get started with installation. You'll be using the Terminal within Mac OS X for ADB commands, so I would recommend getting comfortable with Terminal before jumping into the SDK. Unfortunately, you'll have to look this up because I couldn't even begin to explain everything, nor do I have the time. Hope the rest helps, though.
bftb0 said:
Perhaps you could say a few words about what you have tried already and where you are stopped.
I'm assuming you've downloaded and installed the Mac version of the SDK, yes?
On the phone, you need to turn on Settings -> Applications -> Development -> USB debugging (and may as well check "Stay awake", too).
I don't have a OS/X box, but on Linux you need to perform the *first* adb command as root... the first time an "adb" command is run (after a reboot) it starts up an adb-server process, and that needs to be priviliged enough to write to USB. (After that, you can run adb commands as any user, since those commands "talk" to the adb-server on your Mac, which in turn talks to the phone over the USB cable.)
bftb0
Click to expand...
Click to collapse
Yes I've downloaded and installed the sdk, turned debugging on and now im trying to flash the recovery image onto my phone and that is where im lost at because I don't know exactly what to do
Los-O said:
Yes I've downloaded and installed the sdk, turned debugging on and now im trying to flash the recovery image onto my phone and that is where im lost at because I don't know exactly what to do
Click to expand...
Click to collapse
Note that what you are asking (now) is completely different than what you asked about in your OP - in fact, OS X is immaterial, really, in light of what you just indicated. That suggests that you are in a hurry... if that is the case, I recommend you spend a couple days reading before you rush off and do something you might regret. It is evident from your response that you really have not been reading the threads here with much diligence.
If you are trying to flash a recovery image, that implies that your phone is already rooted; either that what you are trying it isn't going to work - you have to have a rooted phone to begin with before you flash a custom recovery image. At the moment, you can root your Eris only if it has a 1.5 (1.16.605.1 or 1.17.605.1) official Verizon/HTC release on it. This has been described if not a hundred times in the threads here, at least tens of times - you need to read some more.
Nevertheless, if you want to rush into something, here is a step by step set of instructions which was current a couple of days ago. I won't vouch for it being 100% up to date with the latest and greatest images (either ROM or recovery), but it completely describes the process involved.
Stock 1.5 --> Root (2.1) install --> Custom Recovery install -> recovery to custom ROM 0.3. That's what is working at the moment.
bftb0
bftb0 said:
Note that what you are asking (now) is completely different than what you asked about in your OP - in fact, OS X is immaterial, really, in light of what you just indicated. That suggests that you are in a hurry... if that is the case, I recommend you spend a couple days reading before you rush off and do something you might regret. It is evident from your response that you really have not been reading the threads here with much diligence.
If you are trying to flash a recovery image, that implies that your phone is already rooted; either that what you are trying it isn't going to work - you have to have a rooted phone to begin with before you flash a custom recovery image. At the moment, you can root your Eris only if it has a 1.5 (1.16.605.1 or 1.17.605.1) official Verizon/HTC release on it. This has been described if not a hundred times in the threads here, at least tens of times - you need to read some more.
Stock 1.5 --> Root (2.1) install --> Custom Recovery install -> recovery to custom ROM 0.3. That's what is working at the moment.
bftb0
Click to expand...
Click to collapse
I've already rooted my phone
Los-O said:
I've already rooted my phone
Click to expand...
Click to collapse
Well, then you should be on your way; the instructions for what you are trying to attempt are in that link I provided for you in answer to your question (which you purposely redacted when you quoted my post).
I understand that it's your first post, and I should give some leeway for that reason alone, especially since you might have gotten root without ever having used "adb" or "fastboot". (PB00IMG.ZIP method).
On the other hand, I think you can see my point. Please try to avoid wasting other people's time by providing them useful & relevant details of your situation so they can give you good answers. And reading some of the links adjacent to your own post which actually give exactly the details you are asking for might be a good idea, too.
You wanted to know "What are the directions to DisneyWorld?", but instead asked "How do I put gas in my car?" - when you already knew exactly how to do that. But don't take my word for it - reread your first post for yourself - it actually says nothing about what you are trying to do.
I don't know, maybe I got this all wrong, and you still don't have your phone talking to your OS X machine correctly with adb, and that's the source of the trouble. But then, there would be no way to know one way or another - you haven't really said.
bftb0
Download the android sdk and run this automator script.
20 Questions
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Once you have the android sdk unzipped, add the full path to the android tools directory to your path.
I just added the path to my .bash_profile.
For me it looks like this:
export ANDROID-SDK=/Users/Aaron/android-sdk/
export PATH=$ANDROID-SDK/toolsATH
Then I save and close my bash_profile and run the command, from the terminal:
source .bash_profile
This reloads the bash_profile into the shell. Then cd to your android tools directory. Once you get into the tools directory type the command adb. If everything is correct you should see a help menu spit out to the console.
If you need help with your bash_profile a simple google search will help you out.
hey bftb0,
just wanted to chime in and say thanks for that step-by-step. been wrestling with the same issues as the original poster and your walk through got it going. thanks for being patient.
taocow
bftb0,
thank you so so soo much for that last post, I think i've finally figured it out. and also thank you for your patience, i wish i could buy you a coke or something lol
taocow said:
hey bftb0,
just wanted to chime in and say thanks for that step-by-step. been wrestling with the same issues as the original poster and your walk through got it going. thanks for being patient.
taocow
Click to expand...
Click to collapse
los-O said:
bftb0,
thank you so so soo much for that last post, I think i've finally figured it out. and also thank you for your patience, i wish i could buy you a coke or something lol
Click to expand...
Click to collapse
taocow / los-O
Did you need to run the first "adb" command as root with "sudo" ? Let me know - and also mention the version of OS X that you are using; maybe it will help other Mac users if they read this thread. (I got the impression from reading a little bit that different releases of OS X might handle "sudo" a little differently - or have different device permissions for regular users.)
Also, in reviewing this thread, I have to say ... I acted like an a$$. And I should know better, I did IT for a while. If there is one thing I learned about dealing with people and computers, it's that it is extremely easy for a misunderstanding to occur, and especially if you are helping someone out over the phone or via mail/forum. Please accept my apologies.
bftb0
bftb0 said:
taocow / los-O
Did you need to run the first "adb" command as root with "sudo" ? Let me know - and also mention the version of OS X that you are using; maybe it will help other Mac users if they read this thread. (I got the impression from reading a little bit that different releases of OS X might handle "sudo" a little differently - or have different device permissions for regular users.)
Also, in reviewing this thread, I have to say ... I acted like an a$$. And I should know better, I did IT for a while. If there is one thing I learned about dealing with people and computers, it's that it is extremely easy for a misunderstanding to occur, and especially if you are helping someone out over the phone or via mail/forum. Please accept my apologies.
bftb0
Click to expand...
Click to collapse
also now im able to install the recovery (thanks to you) but when i try and push the recovery and flash images i get
"cannot stat 'recovery.img': No such file or directory" same for the flash image
but i put the files in the tools folder like the guide said to do...?
also im on OS X 10.6.2, but no i didnt have to use the "sudo" thing you were talking about, the "adb devices" command worked the first try. and dont worry about it, i understand where you were coming from. but apology accepted, though
Los-O said:
also now im able to install the recovery (thanks to you) but when i try and push the recovery and flash images i get "cannot stat 'recovery.img': No such file or directory" same for the flash image but i put the files in the tools folder like the guide said to do...?
Click to expand...
Click to collapse
That sounds like you are referring to the files by name, but they are not in the current directory where you are running the fastboot command.
The "pwd" command (Print Working Directory) tells you what your current directory is.
The "cd folder-path" command (Change Directory) allows you to change the Terminal/Shell's idea of where the "current directory" is.
The idea behind the PATH variable is that it is a searchable list (separated by ':' colon characters), so that you can be in a given directory with the files you want to manipulate, but the commands you use are in other directories. When you start a command by typing its' name, the Terminal/Shell app walks through that list of folders in PATH (from left to right in order), looking for that program by name.
That means that if you want to run a program ("proggie") that opens a file ("myfile") that is in the current directory you might type the command.
$ proggie myfile
(or $ proggie ./myfile )
... and as long as "proggie" was in one of the folders listed in your PATH, it would run, and find your file "myfile".
But, there is no requirement that you be in the same directory with your files, or the program that you are running (for instance "fastboot"). In those cases, you need to explicitly specify the complete path to your files or programs, so they can be found. For instance:
$ proggie /users/los-o/mystuff/project3/myfile
or, if "proggie" was not in a folder in your PATH, but you knew that it was located in /opt/tools, you could type the command
$ /opt/tools/proggie myfile
If your current directory contains the file "myfile", or
$ /opt/tools/proggie /users/los-o/mystuff/project/myfile.
Same deal with fastboot - you give it the name of the recovery file as the 3rd argument on the "command line"
$ fastboot flash recovery name-of-my-copy-of-the-recovery-file.img
bftb0
*Whew!* Ok thanks again bftb0 for all the help, I think im finally starting to get the hang of this adb stuff
u have a knack for teaching
bftb0 said:
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Click to expand...
Click to collapse
excellent post...very helpful
Los-O said:
Can someone please help me, or point me in the right direction on how to setup and run simple commands through adb on a MAC? Yes, I've used the search, and yes I've searched all over the internet but I still cannot figure it out. Sorry for my stupidity lol
But any help would be greatly appreciated, thank you
Click to expand...
Click to collapse
I do everything on a Mac, so I would be the guy to ask. How far did you get? Have you unzipped the sdk to a folder?
Basically the difference between mac and others is that when others do a command like adb, we have to do ./adb This is true for other commands too. It's easy once you get used to it.
bftb0,
Thanks so much! Step 6 solved my problem
Thank you!!
bftb0 said:
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Click to expand...
Click to collapse
Wow what a straightforward guide to helping me get this set up!! A million thanks! I don't even have an Eris, but what model of the phone you have is irrevelant to this guide...
Thanks again!!
One thing I've noticed is there isn't a lot of documentation for getting set up and unlocking your bootloader on a Linux OS. Setting up your machine to get adb and fastboot to recognize your device takes a tiny bit of extra work on a Linux operating system, but what exactly needs to be done may not be clear to everyone. Whether it's because you're new to the Android SDK/adb, somewhat new to Linux, or can't simply can't seem to find the Vendor Code for the Nexus S. (For those who are looking specifically for this, it's '18d1', and I assume will be the same on all Nexus devices to come; If this means nothing to you right now, read on.)
Disclaimer: I take no responsibility if something goes wrong (if it does, it should be fixable though), Unlocking your bootloader voids your warranty (but you can lock it back), Unlocking the bootloader will wipe your entire phone, including USB Storage; so make a copy of all those family photos and other files you may have put onto the USB storage if you want to keep them.
For the sake of sanity, this guide assumes you are using Ubuntu. If you're using something else (or different applications), there are terminal commands offered, and you probably have an idea on how to adapt the given instructions to your Linux OS.
Preparation: Installing the Android SDK, ADB, Fastboot & Setting Up Your Nexus S to be Recognized
1. Download the Android SDK for Linux: http://dl.google.com/android/android-sdk_r08-linux_86.tgz
2. Save it in a folder of your choice. I chose to keep it in my Downloads folder, myself. If you'd like, you can rename it to the simpler name of 'AndroidSDK.tgz'. The rest of the guide will assume that you did, because I'm lazy, and it makes things simpler; it will also assume you saved it in Downloads. If you feel that you have the intuition to rename and edit the path names based on your own choices, then fine; but if you're utterly lost here, just stick with what I'm doing; download to 'Downloads', rename to 'AndroidSDK.tgz'.
3. Now that you have it, navigate to the folder you downloaded it to, right-click, and click 'Extract' to unzip it. If for some reason you cannot do this, open up a terminal and try this command:
Code:
tar zxvf /home/<your-user-name>/Downloads/AndroidSDK.tgz
You may have to adjust the command if you didn't save it under Downloads or didn't rename the file to AndroidSDK.tgz.
4. Now, we'll install adb and some other software packages by starting up the Android SDK and AVD Manager. Start it either by:
- Navigating to your AndroidSDK folder, going to the 'tools' folder and double-clicking the file called 'android'; if a popup opens asking you what you want to do with it click 'Run'.
- Using this command:
Code:
/home/<your-user-name>/Downloads/AndroidSDK/tools/android
5. In Android SDK and AVD Manager, click on "Available packages". Check the box next to "Android SDK Tools, revision 8" and "Android SDK Platform-tools", and click on "Install Selected" then "Install". When prompted click "Yes" to restart ADB.
6.You should now have a folder in /home/<your-user-name>/Downloads/AndroidSDK/ called "platform-tools".
7. Download fastboot here: http://developer.htc.com/adp.html
- Save it to the aforementioned platform-tools folder.
- Now, navigate to the file, right click it, click 'Properties', go to the 'Permissions' Tab and check 'Allow executing file as program'. Alternatively, run this command:
Code:
chmod +x /home/<your-user-name>/Downloads/AndroidSDK/platform-tools/fastboot
8. Now to set things up so adb and fastboot recognize your Nexus.
- Type this command into a terminal:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
- Paste this into the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
- Click save and close.
- Then, type the following terminal command:
Code:
sudo restart udev
9. Almost done with preparations! Run this command:
Code:
gedit .bashrc
And add this line to the top of the file:
Code:
#AndroidDev PATH
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Then save the file and close.
10. Download this file and save it to /home/<your-user-name>/Downloads/AndroidSDK/platform-tools: http://www.mediafire.com/?4pe5y906zr67nfh
10.We're ready to go!
Unlocking the Bootloader on your Nexus S and Rooting
Once again, unlocking your bootloader wipes everything on your device, including USB storage. Make a backup of any files you want to keep.
1. On your Nexus S, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
2. Power off the phone, and then hold down the Volume Up button and the Power button simultaneously to get into Bootloader/Fastboot mode. Connect your Nexus to the computer via USB.
3. Run this command to unlock your bootloader: (Once again WIPES EVERYTHING!)
Code:
fastboot oem unlock
Hit Enter and on your phone you will be prompted to confirm the action. (Use Volume +/- buttons to choose, power button to confirm choice) Confirm. At this point you will have an unlocked bootloader.
4. Copy/paste the following into the Terminal window:
Code:
fastboot flash recovery /home/<your-user-name>/AndroidSDK/platform-tools/recovery-clockwork-herring.img
5. Use the Volume +/- buttons to choose the Recovery option, then press the power button.
6. In Recovery, go to 'mounts and storage' and choose 'mount USB storage'.
7. Go to this page: http://forum.xda-developers.com/showthread.php?t=682828
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Link As..." Save that file to your desktop and then copy it to the main directory of your mounted phone.
8. Click 'Unmount'. Go back to 'mounts and storage' and choose 'mount /system'. Then Go Back and choose 'install zip from sdcard'>'choose zip from sdcard'>su-2.3.6.1-ef-signed.zip
9. When it's finshed installing, reboot. You are now rooted.
Special Thanks
Amin Sabet; I used your Mac guide as a reference and copy/pasted some things for convenience.
Koush; For first posting the unlocking information, developing ClockworkMod Recovery, and ROM Manager. You should probably hook him up with a donation. https://www.paypal.com/us/cgi-bin/w...63663d3faee8d9384d85353843a619606282818e091d0
Michael.B.; for suggesting adding the platform-tools folder to the .bashrc file.
Linus Torvalds; Without which we'd have neither Android nor Ubuntu.
Feel free to leave your comments on the guide below.
Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ and platform-tools directories to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Click to expand...
Click to collapse
Be sure to update your username above.
Thanks a lot man, great guide. I didn't get my NS yet but this is gonna be very useful soon
ps: someone please stick this
Michael.B. said:
Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
Be sure to update your username above.
Click to expand...
Click to collapse
Thanks for the tip. I added your tip and instructions for marking fastboot as executable.
Stuck due to the thread's usefulness
I forgot to ask: will this work for 64 bit systems?
nicholasbgr said:
I forgot to ask: will this work for 64 bit systems?
Click to expand...
Click to collapse
It should work just fine.
Thanks, got me rooted nice and quickly.
BlackOtaku said:
It should work just fine.
Click to expand...
Click to collapse
Yes but don't forget to install 32 libs.
Thanks for guide
Useful !
I'm waiting for cyanogen ROM so i'll able to install
Cheers
To confirm, yes it works on 64bit. I am running that
Thanks for the confirmation, guys
Good stuff, much appreciated.
I'm working on a simple shell script that should automate some of the more menial tasks while holding the user's hand through the process. I should have it up later today.
UPDATE: It's up! Link on the first page.
Sent from my Nexus S using XDA App
question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?
confiq said:
question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?
Click to expand...
Click to collapse
Or, I don't get OTA until i change OS with zip file (ex: su app) ?
confiq said:
Or, I don't get OTA until i change OS with zip file (ex: su app) ?
Click to expand...
Click to collapse
You shouldn't flash the recovery in the boot partition, I think that will cause problems with the phone period. :S
If you flash a custom boot.img (which this guide doesn't cover, though the script will flash Superboot) or kernel like Paul's Superboot, Supercurio's Voodoo Kernel, or Koush's insecure boot.img, OTA updates will fail to install. OTA updates will also reflash your recovery back to stock. One of the devs around here will probably start modifying them so they don't check the boot.img or reflash the recovery though.
Thanks for this! Worked perfectly
Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska
matroska said:
Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska
Click to expand...
Click to collapse
To fix the problem, before selecting zip file, you have to select mount /system. Then go to apply update.zip and proceed as usual.
Thanks
ok im stock
with this part fastboot oem unlock ware i put this code in my terminal of my pc ,,i put the cell in fasboot , i intall everiting if i put that code in my terminal
bash: /home/toshiba/.bashrc: line 2: syntax error near unexpected token `('
bash: /home/toshiba/.bashrc: line 2: `export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools# ~/.bashrc: executed by bash(1) for non-login shells.'
[email protected]:~$ fastboot oem unlock
fastboot: command not found
[email protected]:~$
what can i do or im doing wrong
I am running on a Mac (OSX Lion) and have installed android-sdk-macosx.
I am trying to connect to a Kindle Fire 6.2.2
However, this is as far as I can get:
Code:
bash-3.2# ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
bash-3.2#
As you can see, no devices show up.
I have tried switching cables, USB ports, reboot the device and my machine... banging my head against the wall.
Nothing works.
I have read about 29 pages of posts through this forum, and Googled it.
No dice.
Any suggestions?
would not use the sdk at all - if you use the mac/linux version of kfu you save a lot of time and space - you don't need to use kfu if you don't like to - but all commands you'll ever need are in the tools folder of kfu - it also includes drivers and setup scripts - maybe give it a try:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
mkdir ~/.android
echo 0x1949 >> ~/.android/adb_usb.ini
ADB needs this entry to see the Kindle Fire no matter what OS you're on.
right - there is also a installation script for this included in the pack - install.sh if i remember right
took the advice above and it's still not working for me. i have the same exact problem. when i try to run install_drivers.sh i get:
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
When I run KFU i get:
/Users/donaldclark/kfu/run.sh: line 84: seq: command not found
please help
as far as i know (don't own a mac) you have to call the commands with
./ from terminal window - eg ./run.sh
I also got the same error message at line 84 running the install script in OSX 10.6.8
-E
it's from eratosthene - give him a pm - i'm shure he can help you
http://forum.xda-developers.com/member.php?u=1616763
Try remove the usb driver from your device and re-install gain.
I use Kindle_Fire_Utility_MacLinux_0.9.2 3 with adb.mac
and its located right inside my root directory (not under users) step before.
I went to the files and I opened file called
install_drivers.sh
I did deleted everything behind -p and just dragged
the adb_usb.ini (its located in drivers) into that install_drivers.sh script and I hit save.
thats how it looks like
mkdir -p /Kindle_Fire_Utility_MacLinux_0.9.2 3/drivers/adb_usb.ini/adb_usb.ini
Than I just run adb.mac and all is operational
my kindle was rooted with burittoroot2
If you need those files send me a pm I have them in my dropbox.
somboonr said:
Try remove the usb driver from your device and re-install gain.
Click to expand...
Click to collapse
there is no uninstalling drivers like in windows.
line 84 SOLUTION
Incarnate609 said:
took the advice above and it's still not working for me. i have the same exact problem. when i try to run install_drivers.sh i get:
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
When I run KFU i get:
/Users/donaldclark/kfu/run.sh: line 84: seq: command not found
please help
Click to expand...
Click to collapse
Regarding the "run.sh: line 84: seq: command not found", I found out that the "seq" command is not recognized with MAC OS... so I did a search and replace, replacing "seq" with "jot -". Now it works.
Reference: Search google for seq and mac
What worked for me.
I had the same problem after updated the sdk on my MacBook Mac OSX 10.6.8
cd to the tools directory (where android program is located)
run:
./android update usb
./android update adb
then edit the ~/.android/adb_usb.ini file and add 0x1949 as the last line (your previous adb_usb.ini file is overwritten by the above commands).
Did this the other night and cant find a guide on here which shows how to root the TF101 from linux/ubuntu/arch, so thought id share. I was on v9.2.1.27
Apologies if this is documented elsewhere somewhere. Props goes to Thing O Doom for the PERI script (which was the source for the adb commands, the recoveryblob and Superuser-3.0.7-efghi-signed.zip) and to Wolf for the orignal exploit.
First grab the android SDK (I cant embed external links yet as im such a noob here, so heres a sort-of link) - developer.android.com/sdk/index.html
Extract the SDK to the directory of your choice. On my boxen, the SDK lives in ~/adt-bundle-linux-x86_64-20130522/sdk
Then grab the wonderful PERI by Thing o Doom and from the zip file you get, extract two files - recoveryblob and superuser zip file to somewhere like /tmp/
Connect your transformer to the USB port and ensure 'enable usb debugging' is set in the developer settings on the TF101. Check that adb can see the tablet, you should see a device ID returned;
Code:
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb devices
Got a device ID back? great, lets push the recovery blob onto the device;
Code:
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb push /tmp/recoveryblob /sdcard/
That should transfer sucessfuly. If not, its time to check up why. If it worked, time to run some commands. Run them one at a time and if any fail, stop and find out why.
Code:
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb shell mv /data/local/tmp /data/local/tmp.bak
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb shell exit
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb shell exit
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb reboot
Device should now reboot and look as normal. Wait for it to fully boot up. All worked? Great. Lets run this. now do NOT unplug your computer, USB or TF101 during this process - brick warning!
Code:
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb shell exit
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb reboot
All worked OK? you should have seen the tablet reboot with a blue bar on the screen and now be back into your OS as normal. Nearly there!
Code:
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb push /tmp/Superuser-3.0.7-efghi-signed.zip /sdcard/
Once completed, reboot the tablet by holding VOL-DOWN and POWER. Keep holding it down until some white text appears on the boot screen, top left. Once you see "Checking for RCK" then let go and press VOLUME-UP. You should now be in the recovery.
From the recovery menu, touch 'wipe' then touch 'wipe cache'. After that completes, touch 'wipe dalvik-cache'. After they are both wiped, go back and touch 'install', select 'install from internal' and look for the Superuser-3.0.7-efghi-signed.zip and install it. Once done, go back and hit reboot
Thats it - you are rooted!
Disclaimer: do this soley at your own risk. I am not responsible if you break anything, kill your hamster, your fluffy cat or your guinea pig.
I'll automate this when I get linux running on my machine again, I just don't exactly know how to make .sh or bash or whatever the linux .bat equivalent scripts work.
If you could help me out I can do this with the .5 release of peri, good guide though c:
I remember attempting this a while back but I believe I couldn't get the sdk working properly..
x
Thing O Doom said:
I'll automate this when I get linux running on my machine again, I just don't exactly know how to make .sh or bash or whatever the linux .bat equivalent scripts work.
If you could help me out I can do this with the .5 release of peri, good guide though c:
I remember attempting this a while back but I believe I couldn't get the sdk working properly..
Click to expand...
Click to collapse
No problem. Have PMd v1
Thanks to both of you, I confirm this works on my tf101 .27. It would be good to have the commands also in the README of one click install.
Hi guys! Thank you for sharing this, I really appreciate it.
I was able to get to the end flawlessly but I have a problem, the touchscreen doesn't work in TWRP so I was wondering if it's really necessary to wipe the cache and if so what other recovery image can I use? I know there is CWM but I found too many in Google that it confuses me.
Thank you very much for your answers!
I have an Asus Slider SL101 with firmware 9.2.1.27, Android 4.0.3
Hi guys. I whipped up this script just for shiggles. Same commands as above, you just don't have to type them.
Unzip the script in the same directory as the recoveryblob and Superuser files, make it executable (right click -> Properties -> Permissions -> Execute), and then you can run it from a terminal with: ./TF101_1Click.sh
Code:
~$ adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb devices
List of devices attached
0428008242a0b117 device
Code:
~$ ~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb push ~/recoveryblob /sdcard/
bash: /home/xxx/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb: File not found
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
The-Undertaker said:
Code:
~$ adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb devices
List of devices attached
0428008242a0b117 device
Code:
~$ ~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb push ~/recoveryblob /sdcard/
bash: /home/xxx/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb: File not found
Click to expand...
Click to collapse
Code:
~$ adt-bundle-linux-x86_64-20140702/sdk/platform-tools/adb devices
List of devices attached
428008242a0b117 recovery
Thanks! I used this successfully today.
simonplexus said:
Code:
~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb devices
Click to expand...
Click to collapse
A very minor suggestion. If you can trim the commands to just `adb` instead of `~/adt-bundle-linux-x86_64-20130522/sdk/platform-tools/adb` it will be easier to read and copy. Right now the code box has to be scrolled to see the full command.
HOW TO ROOT YOUR LENOVO IDEATAB A1000
<DISCLAIMER>
By attempting these steps, your warranty will be void. Even worse than that, it might cause crashes, freezes, random explosions, 2nd degree burns, or even turn your beloved tab into $100+ paperweight. What works on mine might not work on yours, so don't attempt if you don't know what you're doing. Do at your own risk. Corrections are welcome. I must admit that I'm not an expert, so any info I posted might be wrong, and I can't offer you much help. I'm not responsible for anything arising from the use of this how-to. I can only wish you good luck.
<WHY ROOT?>
- Without root or OTA upgrades (at time of writing, Indonesian customers still can't get it), you'll be stuck with ~500MB internal memory. That's annoying.
- You're stuck with the default IO scheduler (cfq) and governor (hybrid, haven't heard that one..)
- You have an incredibly large amount of bloatware you can't get rid of, in that already cramped up internal storage
- Did I mention freedom?
<REQUIREMENTS>
This method is originally used to root Acer Iconia B1-A71. Somehow I noticed that the two actually has the same chipset, MTK8317 (if it really was relevant ). So I tried the method, and through sheer n00b's luck, it worked like a charm!
Lenovo IdeaPad A1000-G --> 4GB storage, 2G/EDGE. This method haven't been tested on A1000-T/F, different storage cap (16GB, etc.) or other variants, but it should work with slight modification. Screenshots of my specs are attached below. Remember, proceed at your own risk!
A Linux System. Never tried on Windows or Mac. I personally used Linux Mint 15. The source post uses Ubuntu.
working ADB (android-tools-adb). You can get this from synaptics, apt-get, etc. If your system can detect adb devices, you should be fine.
Superuser Binary
Busybox Binary (You can get these two from the links on original post. XDA says noobs can't post links :'( )
ORIGINAL THREAD
<CREDITS>
XDA Senior Member entonjackson, for writing such a noob-friendly how-to for rooting Acer Iconia B1-A71 and for allowing me to use it for this how-to.
XDA Member alba81, for discovering the method as acknowledged on the original post by entonjackson
All awesome gurus on XDA which I can't mention one by one.
<THE STEPS>
1. Extract the android sdk to your home folder, e.g. a user named Bob will use like /home/bob
2. Open a terminal
3. Now plug your A1000 into your machine and turn on Debugging Mode (Go into Settings -> Developer Tools, turn on Developer tools, then turn on USB Debugging Mode)
4. Now back at the keyboard of your Linux machine in your terminal type:
Code:
sudo adb devices
The output should be something like:
Code:
123456789ABCDEF device
If it's not, google for it. Somehow your Linux hasn't detected the A1000, although the android sdk for Linux brings all needed drivers with it.
If your device was found, congratulations. The adb connection between your linux machine and your tablet is intact.
5. Now extract the downloaded busybox archive to your home folder, in it there should be a busybox binary. So Bob does:
Code:
sudo ./adb push /home/bob/busybox /data/local/tmp
Code:
sudo ./adb shell
Code:
chmod 755 /data/local/tmp/busybox
6. You should copy the busybox binary into a directory where you can access it as a plain non-root user on the tablet. We need this binary. so we can apply unix tools like telnet, dd, cat, etc. But for now we need it to establish a telnet session between our tablet and our linux machine.
(This point is written on original post. Seems important, but as soon as I finished step 5, I can use those tools)
7. Dial *#*#3646633#*#* to enter Engineer Mode
8. Go to Connectivity -> CDS Information -> Network Utility
9. type the following command:
Code:
/data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
Advice from original poster: copy and paste it from the browser on your tablet, because dependent on which keyboard app installed, this can be freakin tricky. In the next step you will learn, why it's so important why this command should be correct.
10. Tap on Run. You won't get any feedback, so you will never know if the entered command runs properly or not. That's why you should make sure the command is ok.
Now we have started our telnet server on the tablet.
11. Back in the terminal type:
Code:
/data/local/tmp/busybox telnet 127.0.0.1 1234
If you now get an error like couldn't find busybox or something, then either adb push failed or you forgot to chmod, in step 5
12. Now enter:
Code:
cat /proc/dumchar_info
You should get a bunch of lines, try to find a line containing the partition named android
{..... partition list .....}
android 0x0000000028A00000 0x00000000020E8000 2 /dev/block/mmcblk0p3
{..... partition list .....}
13. We will create a dump of our android system. This is the point where different variants *MIGHT* have different parameters. This step is important, as wrong parameter will result in unmountable image.
Stop. Take a deep breath. If you're not familiar with dd, find a good doc of it. There's a plethora of them.
Get yourself a programmer's calculator (Linux Mint 15 has one built in).
Here's what you'll do :
Convert the hex number on the 3rd column into decimal. In my case (0x20E8000) will yield 34504704. Divide by 4096. The result (8424) goes to the skip parameter.
Convert the hex number on the 2nd column. In my case (0x28A00000) will yield 681574400. Divide by 4096. The result (166400) goes to the count parameter.
So the full dd command will look like :
Code:
dd if=/dev/block/mmcblk0 bs=4096 skip=8424 count=166400 | gzip > /cache/system.img.gz
Do a full sanity check before hitting enter! It will take about 5 minutes.
14. After it's finished we must make the image readable for adb, so we do:
Code:
chmod 777 /cache
and
Code:
chmod 777 /cache/system.img.gz
15. Leave the telnet, and then adb shell session by:
Code:
exit
Code:
exit
16. Now we pull our image by
Code:
sudo adb pull /cache/system.img.gz
wait 1-2 minutes.
It should be then located inside /home/bob. It did for me. If not, do a search . It should be a .gz, extract it right there (or /home/bob if it isn't there)
17. Now we need to modify our system image by adding the tiny but helpful su binary. Extract the SU binary to /home/bob.
18. We create a folder where we will mount our system image to. To create it do:
Code:
sudo mkdir /media/a1000
19. Now we mount it:
Code:
sudo mount -o loop /home/bob/system.img /media/a1000
if it fails, then you entered wrong parameters on step 13
20. Now we copy our SU binary to our mounted system image:
Code:
sudo cp /home/bob/su /media/a1000/bin
21. the su binary needs to have the proper rights to make it usable, so we 'suid' it with:
Code:
sudo chmod 06755 /media/a1000/bin/su
22. Let's unmount our baby by:
Code:
sudo umount /media/a1000
and because bob doesn't like a messed up system, he does:
Code:
sudo rm -rf /media/a1000
because he hopefully won't need it anymore.
23. We have to gzip it again to bring it back to where it belongs to. this we do by:
Code:
cd /home/bob
Code:
gzip /home/bob/system.img
24. So here we are now, we made it to the final Boss fight! The next steps are dangerous and should be performed with caution. We copy back our modified system image, which can brick your device, if you do a mistake! Enter adb shell again :
Code:
sudo adb shell
25. Remove the old boring image:
Code:
rm /cache/system.img.gz
26. Leave adb shell
Code:
exit
27. copy our cool new system image containing the su binary:
Code:
sudo adb push /home/bob/system.img.gz /cache
28. Enter adb shell again
Code:
sudo adb shell
29. Usually the telnet server on the tablet is still running, at least in my case it's been like that. That's why we can directly connect to the telnet server with:
Code:
/data/local/tmp/busybox telnet 127.0.0.1 1234
If this doesn't work, then obviously your telnet server isn't running anymore. So on your tablet if the telnet command is still entered (see step 9), tap on Run again and repeat step 29.
30. Now this is the most dangerous step in this how to (no it wasn't the mkdir one). You can copy following command to make sure everything is fine and paste it into your telnet session on your linux terminal.
<WARNING! SANITY CHECK! MAKE SURE *ALL* THE DD PARAMETERS MATCH THE FIRST DD (STEP 13) OR YOUR A1000 WILL TURN INTO A VERY EXPENSIVE PAPERWEIGHT!>
Code:
[B]/data/local/tmp/busybox zcat /cache/system.img.gz | dd of=/dev/block/mmcblk0 bs=4096 seek=8424 count=166400[/B]
After 1-2 minutes you're done, if your tablet or pc or yourself didn't catch fire, everything's fine.
31. Leave telnet / adb shell by doing
Code:
exit
Code:
exit
32. Reboot your A1000 via ADB, then exit
Code:
sudo adb reboot
Code:
exit
33. Unplug your tablet from PC
34. Install Superuser (No, not SuperSU, cause it won't work!). I personally use Superuser by ChainsDD, from Play Store
35. Be lucky. Your tablet and thus you are now free!
Don't forget to hit thanks, if this helps
hi, after step 13 (i double checked the command), i get this error
Code:
/system/bin/sh: can't create /cache/system.img.gz: Permission denied
/dev/block/mmcblk0: cannot open for read: Permission denied
I have the WiFi 4G version
Im too stuck in step 13.....nothing wrong with the script, can u give me a solution?
Im using A1000G also
@ts
Your guide work perfectl, in windows enviroment but mount step still need linux,
I've question are you using DirectoryBinding? Mine always close when playing Real Racing, its very annoying
You have suggeztion or alternative for DirectoryBinding?
Root with Windows ?
Hi,
I am a new member because i bought this tblet but i can't root. I don't have a linux environment, so there is a solution with W8 Pro 64 ?
Thanks a lot for you help,
ulisez said:
hi, after step 13 (i double checked the command), i get this error
Code:
/system/bin/sh: can't create /cache/system.img.gz: Permission denied
/dev/block/mmcblk0: cannot open for read: Permission denied
I have the WiFi 4G version
Click to expand...
Click to collapse
have you chmod-ed the busybox (or is the chmod successful without error)? Try chmod-ing the /cache before attempting step 13. It seems that you still don't have access to the NAND device (mmcblk0). Have you updated firmware via OTA?
artonelico said:
Im too stuck in step 13.....nothing wrong with the script, can u give me a solution?
Im using A1000G also
Click to expand...
Click to collapse
Do you encounter the same error message like ulisez had? Could you post the screenshot of the partition list (the lines after you execute dumchar_info)?
rmage said:
@ts
Your guide work perfectl, in windows enviroment but mount step still need linux,
I've question are you using DirectoryBinding? Mine always close when playing Real Racing, its very annoying
You have suggeztion or alternative for DirectoryBinding?
Click to expand...
Click to collapse
I personally use Link2SD by Bulent Akpinar to link apps to 2nd partition on my SDcard.
Letsar said:
Hi,
I am a new member because i bought this tblet but i can't root. I don't have a linux environment, so there is a solution with W8 Pro 64 ?
Thanks a lot for you help,
Click to expand...
Click to collapse
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029
sammymaddog said:
have you chmod-ed the busybox (or is the chmod successful without error)? Try chmod-ing the /cache before attempting step 13. It seems that you still don't have access to the NAND device (mmcblk0). Have you updated firmware via OTA?
Do you encounter the same error message like ulisez had? Could you post the screenshot of the partition list (the lines after you execute dumchar_info)?
I personally use Link2SD by Bulent Akpinar to link apps to 2nd partition on my SDcard.
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029
Click to expand...
Click to collapse
Link2SD doesn't link app data, do you have any option?
yes i had same message with ulyses, by the way im from indonesia too can i contact you through chat client?
oh yeah im using windows 7 and using cmd as a terminal in linux
thx before bro
sammymaddog said:
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029
Click to expand...
Click to collapse
Ok, i see his toolkit. It's very good. I'll wait
rmage said:
Link2SD doesn't link app data, do you have any option?
Click to expand...
Click to collapse
I'm not sure whether the stock kernel of our devices supports init.d, thus supports CronMod/Data2SD. Lenovo locked our bootloader, and currently there's no way around it. So I personally think, Link2SD method are the best option for now.
Let's give it several months until our dev gurus bring their miracles upon this device
The attached image shows mt6577 Hardware, can u provide the Soc details please
Hi, Can any one upload Lenovo ideatab A1000 system.img
in step 20, it appears you are writing to a /bin directory on the android system. However such a directory is not visible either through shell or the system telnet account.
Do I need to understand something else about android to make sense of this.
regards
vidya
one month gone past but the op seems to be in caves or has bricked the device
STOCK ROM
CAN ANY BODY PROVIDE ME A STOCK ROM OF THIS DEVISE
I HV ROOTED SUCCESSFULLY BY A VERY EASY METHOD
BUT SCREWED UP WHILE UPDATING IT SO PLZ PLZ HELP ME OUT
THE DEVICE BOOTS BUT ALL THE APP CRASHES :crying::crying:
VR.gtmini said:
The attached image shows mt6577 Hardware, can u provide the Soc details please
Click to expand...
Click to collapse
VR.gtmini said:
one month gone past but the op seems to be in caves or has bricked the device
Click to expand...
Click to collapse
sorry to make you wait. I'm a last grader university student, and final project stuffs have got me pinned down. Hope you understand
Actually the SoC is MT8317. For some god-knows reason Mediatek have made this SoC with signatures similar to MT6577. But somehow CPU tweaker correctly detects the SoC (MT8317). Maybe it's the CPU-Z bug?
unknown_world said:
Hi, Can any one upload Lenovo ideatab A1000 system.img
Click to expand...
Click to collapse
zod0070 said:
CAN ANY BODY PROVIDE ME A STOCK ROM OF THIS DEVISE
I HV ROOTED SUCCESSFULLY BY A VERY EASY METHOD
BUT SCREWED UP WHILE UPDATING IT SO PLZ PLZ HELP ME OUT
THE DEVICE BOOTS BUT ALL THE APP CRASHES :crying::crying:
Click to expand...
Click to collapse
I'm uploading the modified .img. Let's pray my old HSPA modem won't catch fire by the morning.
vidyadhara said:
in step 20, it appears you are writing to a /bin directory on the android system. However such a directory is not visible either through shell or the system telnet account.
Do I need to understand something else about android to make sense of this.
regards
vidya
Click to expand...
Click to collapse
I think you got it wrong. The write process does not take place on the device. It's on the loop-mounted .img in /mnt/a1000 on your computer (step 18-19). Cheers!
Here's the ALREADY BUSYBOX-ED .img for Ideapad A1000-G 4GB EDGE version. Hope it helps :
www dropbox com/s/rmpnz7c285t5sqz/system.7z
sammymaddog said:
Here's the ALREADY BUSYBOX-ED .img for Ideapad A1000-G 4GB EDGE version. Hope it helps :
www.dropbox.com/s/rmpnz7c285t5sqz/system.7z
Click to expand...
Click to collapse
Thanks for coming back, could u post the MD5 of the system.7z & system.zip.
Also could u provide simple way/steps to directly flash this .img without extracting existing stock system image
My tab A1000-G
do you have stockROM for lenovo A1000G
I need this :crying:
raffly said:
do you have stockROM for lenovo A1000G
I need this :crying:
Click to expand...
Click to collapse
Don't worry, the above link is a stock Lenovo A1000 G ROM, but with pre-root files having no superuser app. Just extract the .7z file
System.7z MD5: 658CA71AC8A230B244F267513857F9A5