Related
Every time I run the root update utility, it gets to a point where it says something along the lines of Customer ID error. I don't know what the problem is!? Can anyone help me out please?
Hmmm... might be related to the GoldCard. Did you mange to create one successfully? (It shouldn't have given any 'do you want to format the drive?' messages when connecting the phone in Windows, in USB Disk Drive mode.
That's what I thought might've happened, but I'm pretty sure that it didn't, and unlike in the past the HXD Editor successfully wrote the goldcard.
Tiny Linux
Hi guys, trying to load the Tiny Linux ISO referred to on Paul's page, however my pc boots up, recognises the disk, starts to load Linux then black screen......anyone else had this? Not sure what to do next, desperately want to root my phone......help.............
ummm... silly question, I know, but... you did press enter at the first prompt, didn't you? (it will hang a bit, then start the actual boot process)
alternatively, you might want to try the 'rooting from windows' method posted here in another thread, instead:
http://forum.xda-developers.com/showthread.php?t=673277
cezarL said:
ummm... silly question, I know, but... you did press enter at the first prompt, didn't you? (it will hang a bit, then start the actual boot process)
alternatively, you might want to try the 'rooting from windows' method posted here in another thread, instead.
Click to expand...
Click to collapse
LOL......yeah did that.........i get some text appear about installing ADB etc, but then immediately after the screen goes black. How long does it take before you get the desktop on normally? Cheers Andy
I've even tried reformatting the SD card and reconverting it into a Goldcard, and the update utility still gives me error 131, Customer ID error, use correct utility.
about 20-30secs after pressing enter. are you booting it in a vm, or did you burn it to a cd and use it on the computer? (vm's might be buggy)
ipodtouch, what bootloader version do you have? if it's 0.80, then you can't root the device. not yet, at least.
No I'm using the guide for Windows.
cezarL said:
ipodtouch, what bootloader version do you have? if it's 0.80, then you can't root the device. not yet, at least.
Click to expand...
Click to collapse
It's definitely at 0.75 when In check it after booting with back held down.
cezarL said:
about 20-30secs after pressing enter. are you booting it in a vm, or did you burn it to a cd and use it on the computer? (vm's might be buggy)
Click to expand...
Click to collapse
Hi, thanks for your replies. Burnt to a CD, booted via the cd. I get past the press enter bit, I have about 10 lines of text, it says "DONE" then the screen goes black....I dont suppose it matters that I am running a digital connector from my graphics card does it??????? Attached a photo of where it gets to, immediately after the last line of text appears as "DONE", the screen goes blank and stays like it....
murdoch1 said:
Hi, thanks for your replies. Burnt to a CD, booted via the cd. I get past the press enter bit, I have about 10 lines of text, it says "DONE" then the screen goes black....I dont suppose it matters that I am running a digital connector from my graphics card does it??????? Attached a photo of where it gets to, immediately after the last line of text appears as "DONE", the screen goes blank and stays like it....
Click to expand...
Click to collapse
Ok.......I think I may be getting somewhere......I tried pressing F2 when asked to press Enter. I get a load of options. I have tried TINYCORE and then used the setting to switch on text mode only. This resulted in the following command prompt being dsiplayed:-
[email protected]: ~$
Is this what would appear within the terminal window? Would I then be able to use the following commands?
SUDO MKDIR /NMT/cdrom
etc etc etc???????
Yes, that should be a good text prompt.
The Professor said:
Yes, that should be a good text prompt.
Click to expand...
Click to collapse
Thanks.....so.....just want to re-cap the process. I have made the goldcard..On it I have the rootedupdate.zip file.. do i just follow the steps below? Is there anything missing from the steps below as initially Paul had supplied a testRUU.exe file?
# Turn off your HTC desire, then turn it back on with the 'back' button held down. You'll see 'FASTBOOT' written on the screen in a red box. Connect the phone to the computer.
# In the terminal window, enter the following commands:
CODE
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
sudo ./step1.sh
# When this step has completed, using the optical trackball, navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select. Then, again in the terminal window, enter the following commands:
CODE
sudo ./step2.sh
# When this has completed, your device should be at the 'recovery' screen. Select the 'wipe' option, then select the option to apply an update zip from sdcard, and select 'rootedupdate.zip'. This will take a little while, so go make a nice cup of tea. When the flash has finished, reboot, and you are DONE!
That's all correct if you've burned it to CD-ROM and you only have the one drive in the system. If it's on USB (as I did it) or you have multiple drives, you may have to hunt for the right one. If you do need to hunt, try using the fdisk command to show all drives; then you should be able to use mount /dev/whatever (cdrom1,flash,sdc1, etc).
Try the cdrom option first, then come back if that doesn't work.
To clarify, step1 pushes the new RUU, flashes what it needs to, then step2 puts you in recovery so you can flash the new ROM.
The Professor said:
That's all correct if you've burned it to CD-ROM and you only have the one drive in the system. If it's on USB (as I did it) or you have multiple drives, you may have to hunt for the right one. If you do need to hunt, try using the fdisk command to show all drives; then you should be able to use mount /dev/whatever (cdrom1,flash,sdc1, etc).
Try the cdrom option first, then come back if that doesn't work.
To clarify, step1 pushes the new RUU, flashes what it needs to, then step2 puts you in recovery so you can flash the new ROM.
Click to expand...
Click to collapse
Sorry Professor. I am confused now. Do I need to have the testRUU anywhere or do I not need this?
What are you referring to when you said "if you've burnt it to cd-rom?"......are you referring to tinylinux or the testRUU? As you can tell I am a little nervous and want to be sure I have everything needed to root the phone....
If you took Paul's tinylinux iso, it contains the Testruu file in one of the directories already on there. In other words, if you took the iso he linked and burned it to CD, you should be able to follow the directions word for word once you get to the TL command prompt, which you have. His step1 and step2 scripts will take care of everything, there's nothing extra besides the rootedupdate.zip that you need to worry about.
You don't need testruu with the .iso, it's included in the 'step1' phase (downgrades your rom to an unrooted 504.3 versio). 'step2' will push the required files for entering recovery mode, and also the rooted version of the current stock rom (504.4 - which is what you'll end up with after flashing).
Has anyone got any ideas about my problem please?
This post will no longer be updated and is pretty much for the archives at this point. It detailed the rooting process for Linux users right after the Slide was first rooted. Since then, newer, more foolproof methods have been devised. For those rooting their phones today (or any point since T-Mobile's OTA update), please see this link: http://forum.xda-developers.com/showthread.php?t=780213. It says it's Ubuntu-specific, but the instructions there should apply to any GNOME desktop and any other desktop with slight modification. Thanks for the comments on this thread. I hope it helped.
Most of this is not new information, but it's all in one post for the first time. I post it in case Linux (and probably MacOS) users need clarification on the process. It should keep people from having to dig in deep threads to find all the info needed. I only added the loop.sh for Linux and the partitioning information.
For all the following, I assume that the reader knows how his computer works, but not necessarily Android rooting.
Preliminary Information
1. As always, make backups and take notes. You might want to make a list of installed apps you want to reinstall later, for example.
2. Install adb. Download it here: http://developer.android.com/sdk/index.html. adb is a little program distributed as part of the Android software development kit (SDK). Its job is to communicate with the phone from a shell (terminal). To install adb, I strongly suggest you copy the adb file from the tools directory into your system's /usr/local/bin directory. This way, it will always be in your path. If you don't intend to do development work on Android applications, feel free to delete the rest of the SDK after installing adb.
3. Start adb as root. In more traditional Linux distros, this can be done by typing "adb devices" in a root terminal ("su" then "adb devices"). In Ubuntu-based distros, "sudo adb devices" followed by your password should do the trick. You'll get a message about the adb daemon being started. If not, sometimes typing "adb root" or "adb start-server" as root will do the trick.
4. Make sure your phone has "USB Debugging" checked off in Settings > Application > Development
5. It may not make any difference, but I turn off the "disk drive" option, so that my SD card doesn't mount when the phone is plugged in via USB (unless I need it to).
Partitioning the SD Card (Optional)
This is an optional step, as ROMs are coming out now that allow swapsace (virtual memory) and apps2sd (installing applications to the SD-card rather than on the phone's internal memory). Right now, most Slide ROMs support apps2fat32, so the whole card can be left as is (one, big, fat32 partition). If your desired ROM supports apps2sd using an ext2 or ext3 partition, you can save some headache later by doing this step first. If you don't want it, just skip to the next section.
1. Using the package manager for your Linux distro, install parted. GNOME users have a great, graphical frontend to this utility called gparted. KDE users have the KDE Partition Manager available to them. I only have gparted, but the instructions should be similar for all variants. The graphical frontends take a lot of the pain away from using parted (automatically formatting for ext4, for example). For the braver souls, there is a much more detailed tutorial for using vanilla parted from the command line here: http://forum.xda-developers.com/showpost.php?p=4098568&postcount=1.
2. Mount your sd-card, either using the "disk drive" function of the phone, or in an external card reader.
3. Make a backup of your sd-card by simply copying and pasting to a new folder.
4. Start up the partition manager of your choice with root permissions (using gksu or kdesu).
5. Make sure your desktop environment (KDE or GNOME) or a terminal doesn't have a file manager window open to the sd-card partition. You can't unmount a partition that's being accessed.
6. Find out which device node is assigned to the partition by typing "dmesg" in a terminal. The last few lines should tell you how it's assigned. Mine was /dev/sdg1, for example.
7. Using the dropdown menu, select your sd-card partition in parted.
8. Right-click on the partition in the bottom pane of the window and select "unmount".
9. Delete the partition using the same, right-click menu.
10. Now you're left with free space to configure as you see fit. You use the same right-click menu to create partitions.
11. When done, click "apply" and the partition manager will create and format the partitions you've selected.
12. When done, the computer should mount two partitions from the card, one for apps, the other for user data. Copy your backed-up files to the larger partition.
NB: Android phones can work with a smallish ext* partition at the beginning of the card for apps (around 512MB should be more than enough for almost anyone), a super-small swapspace in the middle (no more than 32MB, if any at all--it's up for debate whether the Slide benefits from swapspace at all), and the rest of the card formatted as FAT32 for the "normal" partiton. I'll leave those decisions to those who have the need and desire. Also, whether to use ext2,3, or 4 for the apps partition is a matter for debate, and some kernels for other phones didn't support the newer versions at all. All that is beyond the scope of this howto, mainly because I won't be trying it out.
NB2: Eugene has released Koushik Dutta's recovery scripts that can help automate the partitioning process. It can be done directly from recovery, rather than on the computer. I much prefer the old way, as it gives more flexibility. For reference, the post with instructions is found here: http://forum.xda-developers.com/showpost.php?p=6993132&postcount=1.
Getting root (original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1)
The following instructions are "the old way" to gain root. There is a new method found at: http://forum.xda-developers.com/showpost.php?p=7658764&postcount=1 that seems to be a saner process, but I have not tested it as of yet.
1. Download the Slide Root package: http://outboundlink.us/anxo/dr_ta_1...ttp://www.4shared.com/file/IfrPbWG7/Root.html
2. Extract it somewhere convenient (I'm using the Desktop folder here. I'm also renaming the folder "slideroot" to keep things simple).
3. Open a terminal and cd to the slideroot folder you just created.
4. The "loop.bat" file here is of no use to you. Use a text editor to make your own loop.sh file, or edit loop.bat and rename it when you're done. It should contain the following:
Code:
#!/bin/sh
watch -n .50 adb devices;
done
5. Power on the slide while holding down the Volume-down button. This will bring you to the bootloader screen (three droids on skateboards). Plug the Slide in via USB.
6. Just to make sure everything is working correctly, type "adb devices" in the terminal to make sure the system is seeing your phone properly. If so, run your loop.sh by typing "sh loop.sh".
7. Use the Volume-down button on the phone to select "recovery" and press the power button to enter. The terminal will flash a few messages like "offline" and "recovery". When the phone's screen shows an icon of a phone with a red triangle, you know it worked.
8. Press Volume-up and Power together to enter the recovery menu on the phone.
9. Now, back in your terminal, hit "ctrl-C" to cancel the loop.sh script.
10. Type "adb push ota.zip /sdcard/update.zip" and hit enter.
11. Type "adb push update.zip /sdcard" but DO NOT hit enter yet.
12. This step requires some coordination and timing. On the phone, select "run update.zip" and press the power button. When you see a little greenish progress bar at the bottom in the background, hit enter in your terminal.
13. If it worked as planned, the phone will see the keys from the first file you pushed, and then use the file you're pushing now to run clockwork recovery. If not, don't worry. Just repeat. I haven't had to do it more than once yet.
14. Once this is done, reboot the phone from the menu system and wait. You can use "adb devices" in the terminal to see if the phone is detected.
15. Type "adb shell" and look for the "$" prompt. If you type "su" you should get a "#" (root) prompt. Give yourself a pat on the back.
Installing the Engineering ROM (original HOWTO at http://forum.xda-developers.com/showpost.php?p=6821968&postcount=1)
A. Now that your phone is rooted, you can "downgrade" it to the Engineering ROM. This gives a better recovery environment that allows other ROMs to be installed (custom ROMs are signed with the test keys; the original recovery will not install them since it looks for your carrier's keys.)
B. Download two files: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/OsmF_ZD7/ESPRIMG.html and http://www.4shared.com/file/sz0VO2TL/SlideEng-package.html.
C. I extracted the SlideEng-package.zip, copied the contents inside loose to the Desktop, and copied the ESPRIMG file to my sd card.
1. cd to the Desktop and type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
3. Start an adb root shell as above ("adb shell" then "su")
4. Type "cd /data/local"
5. Type "chmod 04755 mtd0.img" and "chmod 04755 flash_image". I didn't change any permissions on the other files in that folder, just in case.
6. Type "./flash_image misc ./mtd0.img" and hit enter.
7. Power off the phone.
8. Holding Volume-down, power the phone back up. The recovery will scan the sd card and automatically detect the update file (from step "C" above) and prompt to install it. Hit Volume-up to install.
9. You're done. Just reboot the phone after the update and you're good to go. The boot process will be a little longer this time around.
Updating the Radio (May be optional) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6856313&postcount=1)
I leave this section here for archive purposes. Since switching the ROM to ChiefzReloaded's OTA in the "Installing a custom ROM" section below, this step is no longer necessary, as it contains the newest radio. Unless you're installing a custom ROM released before the last T-Mobile over-the-air update, feel free to skip this section.
When we downgraded the system to the Engineering ROM, we downgraded our radio as well. The following instructions will bring us back to the stock radio version.
1. Download the following file: http://files.androidspin.com/downloads.php?dir=chiefzreloaded/ROM/&file=Newest_Slide_Radio.zip and copy it to your sd-card.
2. Remember that update.zip way back in the rooting section? The one found in the slideroot package? Copy it to your sd-card as well, if it's not already there. I deleted the one on my sd-card and re-copied it, just in case. It contains the clockwork recovery and can be left on your sd-card for future upgrades.
3. Reboot the phone into recovery (should be easy now.)
4. Select "apply update.zip from sd card" to start clockwork recovery. No looping necessary anymore!
5. From the clockwork menu system, apply the Newest_Slide_Radio.zip file you just copied over.
6. Once that's done, just reboot. The boot process will take longer and you'll see a few crazy icons before the system finally loads up. When all is finished and you're back to the home screen, the phone will pop up a dialog telling you the update was successful.
Installing a Custom ROM (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6827968&postcount=1)
For this install, I'm using the new OTA update rooted by ChiefzReloaded. Complete information on this ROM is here: http://forum.xda-developers.com/showpost.php?p=7534163&postcount=1. Like the older SLIDEMEROOT2 I had here before, I picked it because it's mainly the same, stock ROM the phone shipped with, but with root. I had way too many "fast, stable, feature-packed" custom ROMs on other phones that really weren't that fast or stable. I don't want to lose the use of my camera/camcorder to have live wallpapers, for example. These instructions will work for any custom ROM (adjusting for the new ROM in step 1 and 4.)
1. Download the following file: http://db.androidspin.com/androidspin_filedownload.asp?release=330&type=1 and copy it to your sd card.
2. Boot the phone into recovery mode.
3. From the recovery menu, select "apply update.zip from sd card". As stated earlier, this update.zip file contains the clockwork recovery. Applying it like an update will always load clockwork from now on.
4. In the clockwork menu, select "apply any zip from sd card" and select CR_Mod_1.35.531_OTA.zip.
5. Let the update take its course, reboot, wait, and enjoy.
Going Back to Stock (Just in case) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6994424&postcount=1)
There may come a time when you might need your phone just the way it came from the store. It could be that you're tired of custom ROMs, a feature you find you can't live without is broken, or you need to return the phone for warranty purposes. If it gets to that point, here's how:
1. Download the following file: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/x7HRRsbM/ESPRIMG_2_.html and copy it to your sd-card.
2. Reboot the phone into recovery (just the regular one, not clockwork). The file will be automatically detected.
3. After checking the file, you'll have to hit Volume-Up to confirm the flash.
4. Once done, reboot and the Slide will be good as new.
Very nice!
I kind of wish I would have seen this before I rooted this morning!
I just rooted mine this afternoon. Figured I'd put it up while I still had it in my head.
Excellent summary!
I also wish I'd seen this before muddling through the other guides myself. Thanks for posting it!
Quick question. I plan on rooting my MyTouch Slide within the next couple days. I was just reading over your list and thought I'd try to move the adb file first. After I moved it to /usr/local/bin, and then opened a root terminal. I typed "adb", but nothing came up about a dameon being started. It looked like I had asked for the man page. Any idea why? Or if it started it anyway?
The first time you run adb, do so as root "sudo adb devices", "sudo adb root" or the equivalent. It will start the daemon. A normal user (ie, not superuser) will not have the permissions to start a daemon.
When you run just "adb" without any options, it shows you the command-line options you can use with adb. Most Linux command-line apps work the same way when run without options.
beartard,
huge props to you. this is, by far, the best guide for rooting anything that i have ever used, and certainly for the slide.
as mac osx is a *nix system, this worked great. none of the steps were missing, everything was a normal sized font, and left justified, and took me from the stock to a custom rom flawlessly.
thanks a bunch.
really.
I'm very glad it worked for you. Thanks! Did you have to do anything differently under MacOS? I used to use it before OS X came out. I know the newer versions are based on *nix, but I didn't know how similar they were underneath.
I didn't do very much differently.
I started with "How to get Root" section, as I didn't want to partition my sdcard and already had the SDK installed (obviously, though I really need to look into working with it more, as right now it scares the bejesus out of me).
I used a "do while [1]" style (I love accidentally rhyming) loop.sh file though, mostly because my terminal couldn't understand "watch" for some silly reason.
Your guide was just the one that felt the least like a tween myspace page (no offense to the other guides).
Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.
sultan.of.swing said:
Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.
Click to expand...
Click to collapse
I'm not sure what the problem is, man. I've never had to try more than once using the process above. You're using a new install of ubuntu. Do you have adb from the latest sdk?
Just added the link to a new method for rooting and updated a few minor points.
Updated partitioning info to reflect what's actually going on in the MT3GS world.
Changed custom ROM to ChiefzReloaded's OTA, eliminating the need for the "updating the radio" section.
Beartard, I want to say thank you for taking the time for typing this all out. It worked like a charm with not one problem. I have spread your link to others so they can get the same satisfaction I got from this thread. Thanks again
hello
when i want to install a new rom
can i remove without any risk from the system directory all the apps and widgets i never use (such as facebook, flickr, etc...) before installing the rom ?
thank you
I would like to know this too... apparently there are some "adb commands" you can use??
Thanks
youll have to resign zip file after, otherwise installation will be interupted due to missing files.
2nd way to get rid from these apps is to remove them using adb, after installation
shoonari said:
2nd way to get rid from these apps is to remove them using adb, after installation
Click to expand...
Click to collapse
Can you please post instructions how to do this one?
Thanks
1.boot to modified recovery
2.connect to pc
3.adb shell
4.mount /system
5.cd /system/app
6.ls -this will list all your apps installed, chack it and:
7.rm Facebook.apk (for example) case sensitive!
or
rm *Facebook* -this will remove everything connected to Facebookdex files,widgets, etc...
Yes you can remove files from a .zip before flashing. Just delete them. Then just before you flash, disable verification in the custom recovery. It will flash and ignore any errors about missing files!
i guess this option exists only in clockworkmod recovery?
im using amonra, so do not know about that
there is in amonra recovery too.......
I like to freeze apps with Titanium Backup. Works like a charm.
but you have to have donation version for that
verification in amonra recovery - how is it looks like there? I've just checked again - found nothing...
@Vice83 and anyone else whose interested
How I removed stock apps using SDK
I've had my HTC Desire for 2 weeks (T-Mobile UK, Eclair 2.1)). I'm a newbie to all of this. I spent untold hours on forums and other Android sites, and managed to do Nandroid backup of my phone, and then successfully rooted it (using Unrevoked and a SLAX (Linux) bootable cd). It was really straight forward.
I then installed the AdamG/OpenDesire Sense Froyo v1.0c custom ROM
I then wanted to remove apps that I know I don't need and will never use. There are many online guides on how to do this but, maybe it was me being very dumb, but none of them seemed to work for me. After many more hours reading forums etc I found that all the guides I had read missed out KEY actions\information.
So I've put this together from all the things I've learned from the forums etc. I'd like to give credit \ thanks to all of those who contributed to Android sites, forums etc which provided me with all the info I needed.
!!!!THE FOLLOWING IS WHAT I DID TO REMOVE APPS FROM MY (rooted) T-MOBILE HTC DESIRE - IT WORKED FOR ME - BUT MAY NOT WORK FOR YOU CREATE A NANDROID BACKUP FIRST!!! AND USE AT YOUR OWN RISK!!!!!
I installed Java and the Android SDK on an old laptop as I don’t want Java on my main desktop \ laptop.
I then created an Android folder on my pc (C:\Android)
I then copied the following folders from the "android-sdk-windows" folder into it
· Tools
· USB_DRIVER***
· Market-Licensing
*** The default drivers didn't work on my pc\laptop (Win 7 Ultimate, 64bit) so I extracted the drivers contained in a adb_driver_htc.zip file was posted on the My HTC Desire site to the USB folder and successfully installed the driver(s).
With my phone switched on, and in Disk Drive mode, I connected it to my pc with the usb cable. If the phone drivers are not installed / found
· Go to Device Manager.
· Right click on the device that represents your phone.
· Select "update driver software".
· Select "browse my computer for driver software".
· Browse to the C:\Android\usb_driver folder (or to wherever our usb_drivers folder is located, and make sure the "include subfolders" box is ticked).
· Click Next etc to install driver(s).
To test that the drivers were installed and the phone recognised by my pc I
· Opened a command prompt window (Start-run-cmd) and typed the following (don’t include the text in the brackets).
· CD\ (enter\return).
· CD\Android\tools (enter\return).
· adb devices (this listed my phone as HT******SS Recovery).
To exit from adb type EXIT at the “#” prompt. This takes you back to C:\Android\tools directory. Type EXIT to close the command prompt window
Safely remove \ eject the phone from the pc and disconnect the usb
Switch off the phone, and re-start it in Recovery mode by
Holding down the "volume-down" button and pressing power button.
Use " volume-down " button to highlight Recovery.
Press POWER to reboot. Phone will start in Recovery mode i.e. green text on black background.
Still in Recovery mode, connect phone to Computer via the usb cable.
On the pc, open a command prompt window
Type CD\ and press enter\return
Type CD\Android\tools and press enter/return
Type adb shell and press enter/return
On the phone, use the trackball to highlight Partition Menu and press trackball to select.
Use the trackball to highlight Mount /system and press trackball to select. This bypasses the need for the following adb command: mount –o rw,remount /dev/block/mtdblock3 /system - a command which caused me no end of grief!!!
In the windows command prompt window, type cd /system/app
Type ls –a to get a listing of all the *.apk files in the /system/app directory.
To remove an app type rm appname.apk (where appname is the name of the app to be removed – this command is case sensitive so you must type the app name exactly as it appears in the /system/app directory)
I’ve removed the following apps with the above method without any ill effects, and they no longer appear in my Applications list, or in the system/app directory.
Plurk, FaceBook, Stocks (and com.htc.StockWidget.apk), Twitter, Quick Office and YouTube
From what I’ve read, its not advisable to remove any of the Google apk files due to dependencies etc. People have also reported problems after deleting News, PicoTts and Weather apk’s / widgets – so I’ve left these alone. I’ve not been able to find a definitive list of stock apps that are safe to remove
Anyhoo, I hope this proves useful.
Vybz
Hey guys, I checked my apps2sd and it seems to be working fine, here are the symlinks:
dalvik-cache -> /system/sd/dalvik-cache
app-private -> /system/sd/app-private
app -> /system/sd/app
However when checking the Settings page, "Internal phone memory" is still showing 115mb free, and it was 129mb free when I flashed the rom 2 hours ago. Why aren't the apps installing to the SD card as they should? Can someone plz help?
EDIT: Now it's 108mb after I installed another 2 apps. Whats going on?
Accidentally broke my G2's screen [blank & unresponsive].
I'm getting a replacement from T-Mo ...but need to extract a some data from the phone's memory.
I've tried connecting it to my computer but I can't access anything unless I put in the Unlock Pattern on my phone (which I obviously can't)
Any suggestion on what I can do?
****Update*****
Screen went out but touch screen functionality remains [Screen Defect?].
I've been able to use ScreenCast to see my screen on my pc & use it to some degree.
Temp. rooted my 'broken' phone with Visionary, ran Titanium Backup ... now trying to do Clockworks Recovery.
...need some help with operating Clockworks w/ a Broken Screen..
More info on second page
If you install adb via the Android SDK, you should be able to extract everything you want.
http://developer.android.com/sdk/index.html
EDIT:
install adb
use adb pull to get what ever data you are looking for, probably something in /data/data/ ??
you can use adb shell to poke around on your phone
I think you might have to be rooted. I don't have an unrooted phone to test this on.
gee one said:
If you install adb via the Android SDK, you should be able to extract everything you want.
http://developer.android.com/sdk/index.html
EDIT:
install adb
use adb pull to get what ever data you are looking for, probably something in /data/data/ ??
you can use adb shell to poke around on your phone
I think you might have to be rooted. I don't have an unrooted phone to test this on.
Click to expand...
Click to collapse
I've had the SDK but I can't access my phone files because they are inaccessible from my PC + my phone doesn't have USB Debugging / ADB enabled by default...
I tried running ScreenCast to try and emulate my screen on my PC (something I've done before) but it wouldn't work because, as before, the phone to be detected as an ADB device
Other suggestions?
If nothing else what's a quick way to wipe all data to factory defaults (without relying on a screen )
SmartHat said:
I've had the SDK but I can't access my phone files because they are inaccessible from my PC + my phone doesn't have USB Debugging / ADB enabled by default...
I tried running ScreenCast to try and emulate my screen on my PC (something I've done before) but it wouldn't work because, as before, the phone to be detected as an ADB device
Other suggestions?
If nothing else what's a quick way to wipe all data to factory defaults (without relying on a screen )
Click to expand...
Click to collapse
If you have Clockwork recovery, you can boot into recovery mode and use adb.
shutdown
unplug the USB and shutdown- press and hold the power button for 2 seconds, scroll down on the trackpad several times and then press the trackpad button twice. it should shut down, or else pull the battery.
reboot into recovery
hold volume "down" and press the power button for a second and release. Wait 5 seconds and then press volume "down" once and press the power button. If all goes well, the phone should vibrate briefly. Wait a few seconds and then try adb.
Get a Ubuntu livedisk, boot from it and plug the phone in. You can see the phone's contents as well as sdcard. That would be the easiest. But if you can't do that and you have the latest clockwork mod, you will still need to mount stuff from recovery before you can access it. These instructions are relevant to the latest version (2.5+).
Once in recovery per gee one's instructions the menu is as follows:
Main Menu
- reboot system now <<- cursor
- apply sdcard:update.zip
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
By default "reboot system now" is select where it says cursor. Volume up/down to go up/down and trackpad to confirm. Power is to go back. The trackpad will also navigate for you, but it's hard to control so avoid using it for movement at all costs. It is also very sensitive to double clicks, try and make your click as quick and clean as possible.
Press Volume down 6 times and you will land on mounts and storage, then press trackpad (very quickly so as not to make it register a double click).
That menu is as follows:
Mounts and Storage
- mount /system <<-cursor
- mount /data
- unmount /cache
- mount /sdcard
- mount /sd-ext
- format boot
- format system
- format data
- format cache
- format sdcard
- format sd-ext
- mount USB storage
Your cursor starts on mount /system. Press trackpad once will mount system, pressing it again will unmount. Volume down will take you to data, and so forth. Then you can access those directories from adb, and do adb pull as others have suggested. Pressing it again will unmount it, and should be done. Keep in mind it will only unmount if you close all windows that point to that directory and leave the directory in adb shell (you can leave the directory by typing "cd /" to do that). If you stay in the directory or something is pointing to it, it will cause an error.
If you're unsuccessful, you can try doing a backup from clockwork.
From the main menu, press volume down 5 times and press trackpad.
The menu that appears is as follows:
- Backup <<-cursor
- Restore
- Advanced Restore
Simply click the trackpad again and it will perform a backup.
It will save the backup of the phone to the sdcard at /clockworkmod/backup/2010-12-8.x.x.x/
After that I'm not entirely sure how to extract it, hopefully someone else can help.
But simply put, get a live CD of linux and you go to Mounts and Storage and then to mount USB storage, you should have access.
Pic Please
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
gee one said:
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
Click to expand...
Click to collapse
*facepalm*
or that. if you go into adb shell, you can mount whatever directory and cp it to the sdcard. you can use 'umount' to unmount.
adb push/pull will not work when in adb shell, but you can easily copy it over to your sdcard with the cp command.
funkeee said:
*facepalm*
or that. if you go into adb shell, you can mount whatever directory and cp it to the sdcard. you can use 'umount' to unmount.
adb push/pull will not work when in adb shell, but you can easily copy it over to your sdcard with the cp command.
Click to expand...
Click to collapse
I just tried finding my G2 using an ubuntu 10.10 installation- it wouldn't find my phone unless I enabled USB mode, and then it would only find the sdcard. I'm still pretty new to ubuntu, so I might be missing something. It's like a brown version of my Mac!
adb push/pull will work from the terminal command line on your computer, not the shell.
Had some obligations I had to take care of but ... thank you for all the suggestions, I'll be trying them all to see which one I can get going!
I just got my replacement today & the first thing I noticed was the Z-Hinge issue.
Its looser than my original 'broken' phone right out of the box, even though the original has been thoroughly used for about 2 months...
so I gotta go thru Another replacement process ...
I suppose I'm going to keep getting replacements that people sent back for the Z-Hinge issue
gee one said:
If you have Clockwork recovery, you can boot into recovery mode and use adb.
Click to expand...
Click to collapse
^ I don't have any recovery programs on my device (unfortunately).
--
@ funkeee: I'll def. try this, seems promising.
ddgarcia05 said:
Pic Please
Click to expand...
Click to collapse
^ of?
gee one said:
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
Click to expand...
Click to collapse
^ how would I go about and do that?
and as I mentioned before my device is simply set up for mass storage mode & I'm certain I need to get past the Unlock screen to access anything (but I obviously cant)
What kind of data are you trying to extract? It might seem obvious, but I think I should ask for the sake of completeness- is the data actually in the phone or on the memory card?
gee one said:
What kind of data are you trying to extract? It might seem obvious, but I think I should ask for the sake of completeness- is the data actually in the phone or on the memory card?
Click to expand...
Click to collapse
Well I can get the data from the memory card via my replacement G2 or an Sd adapter...but its mainly messages and some miscellaneous content / apps I had saved on the phone itself & the settings; its not a Big deal, but its something I'd like to port over.
If I didn't have a lock on it I could've managed my way through the menus using hard keys w/ my replacement as a guide but I have no way of doing it.
I wish there was an easy way to make a backup... still haven't got time to try the methods mentioned before, but I'm going to try and give it a go tonite.
Do you have a stock, unrooted phone? If you installed hboot-eng.img then there might be a chance.
gee one said:
Do you have a stock, unrooted phone? If you installed hboot-eng.img then there might be a chance.
Click to expand...
Click to collapse
yup, stock & unrooted... any hope?
SmartHat said:
yup, stock & unrooted... any hope?
Click to expand...
Click to collapse
I'm out of ideas, for whatever that is worth.
Thank you very much for the input, everyone.
I managed to get my phone into USB Debug mode & I've been able to open up a lot of options... (since I can finally use ADB).
So, Now I'm using my previously installed Android ScreenCast to see my previously Dead Phones Screen! -- Gotta love Android!
-- Now, can anyone suggest the best method for me to a image of my device, so I can flash it onto my replacement?
A Nandroid backup would be perfect, but you don't have root.
adb pull /data/app /somewhere/on/your/pc/app
will back up non-system apps, but not the settings or data
adb pull /data/data /somewhere/different/data
will grab your settings and data, but there is mix of other stuff in there as well that doesn't restore so well because it also contains other data. I think someone who is well versed in sqlite might be able to put it all back together.
Are there any data that you are looking for specifically? SMS? Browser bookmarks? etc?
gee one said:
A Nandroid backup would be perfect, but you don't have root.
adb pull /data/app /somewhere/on/your/pc/app
will back up non-system apps, but not the settings or data
adb pull /data/data /somewhere/different/data
will grab your settings and data, but there is mix of other stuff in there as well that doesn't restore so well because it also contains other data. I think someone who is well versed in sqlite might be able to put it all back together.
Are there any data that you are looking for specifically? SMS? Browser bookmarks? etc?
Click to expand...
Click to collapse
well I just temp rooted my 'broken' g2 ... ran titanium backup; Flashed clockworks recovery & now am backing up again(just to have all my bases covered)
When I went in to 'backup current ROM' in the Clockworks app, phone turned off and my Screen Cast disconnected... So I have no means of checking if I need to do anything else before my Rom's backed up
*ed-*
...but then again, since I have Visionary Temp root, wouldn't Clockworks loose its super user privileges when it restarted?
Answered my own question.
So it looks like nothing else will be possible unless I permaroot, which would void my warranty, meaning I won't be able to send it back in to T-mo
You can check the clockworkmod folder on your sd card to see if the backup completed. There should be 4 or 5 .img files if it ran.
Sent from my CyanogenMod Vision
Root Galaxy Nexus (Either GSM or LTE) in Linux (Personally in Ubuntu)
Disclaimer: I am not at fault for anything you have done to your phone (ie. Brick, break, etc.). You are doing this at your own discression. I am merely stating what I did to unlock/root my phone.
Tutorial Broken Down Into Three Sections
I. Unlocking the bootloader
II. Installing Clockwork Mod Recovery
III. Installing SuperUser
Resources
1. Super User (used by flashing in Clockwork): http://download.clockworkmod.com/test/su.zip
You can get the latest version here: SuperUser by ChainsDD
2. Clockwork – based by carrier
1. Verizon (CDMA) version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.4-toro.img
MD5:*b2d31c29b7ef785f9c0802a12264d322
File size:*5,263,360*(bytes)
2. GSM version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.2-maguro.img
MD5:*445887336a863573997ccbaeedddc984
File size:*5,427,200*(bytes)
Unlocking Bootloader
Part 1: Unlock
1. First off, you need to download the adb drivers. There have been mentions of just getting the drivers, but I actually have the entire SDK. You can download it here. http://developer.android.com/sdk/index.html
2. Plug in your device, then open up Terminal (Ctrl + Alt + T) and type in: “lsusb” (without quotes). This will pull up all the devices plugged into your usb slots. Look for the one that says samsung (others have found google, but please make note).
3. Find the device, then find where it says ID. After where it says ID, it should have a number/letter mix such as “04e8” or such. Make note of that for later.
4. Go to http://developer.android.com/guide/developing/device.html . This will give the instructions on how to Install the device drivers (specific to each manufacturer). Start from where it says “4. Set up your system to detect your device.”
5. Go to your internal and cd to platform-tools. (This should include both adb and fastboot.) Put your phone into fast boot. (Do this by holding the power, volume up, and volume down buttons while phone is off).
6. Once in fastboot, go back to your computer and type in “sudo fastboot oem unlock”. This will bring up the option to unlock your phone's bootloader on your device's screen. It will give you a disclaimer, and it will say that if you unlock, it will wipe all of your phone's data. Scroll to Yes using the vol up or vol down buttons, and select it with the power button.
7. If you boot straight from there, you will go through a series of boot loops (it was 2 for me) then will be prompted to go through the process of setting up your Google account again. again.
Congratulations, your phone is now unlocked. However, this doesn't mean that you have rooted your phone.
Rooting
Part 2: Putting Clockwork Mod Recovery On Your Phone
(do step one for preparation of Part 3)
1. First, we will want to push su.zip to your phone's Internal storage or “sdcard” partition. Open up Terminal and type the command “adb push 'directory_of_su.zip'/su.zip /sdcard/”. Hit enter/return and it should transfer over. (Based on the quality of usb cord, times of transfer may vary.)
To make this easier, put su.zip into the directory of adb. Then all you have to use for the command is “adb push su.zip /sdcard/”.EDIT:
After you root, you have to delete /system/recovery-from-boot.p and reflash or else every time you reboot, the recovery partition will be written over by android. This can either be done in terminal (phone or comp) or by a file manager with root access (such as Root Explorer).
Reference: http://forum.xda-developers.com/showthread.php?t=1392336
Thanks vihil
2. Put your phone in fastboot mode again (vol up + vol down + power)
3. Go back to Terminal and type in “fastboot flash recovery 'whatever the file name is'”. This will flash CWM (Clockwork Mod) onto your phone, deleting your phone's stock recovery image.
EDIT: If it doesn't work, i.e. due to permissions, run with sudo
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.
Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Special Thanks to scary alien on androidforums.com and jcarrz1 on XDA
Reserved
Reserved......
Thanks a lot I was looking for exactly this. Appreciated. Will try in a few hours when I get my phone.
Downloaded the sdk file but have no idea what to do. My windows computer died and it would be a lot easier on that to do all this but all I have is a computer with linux currently so if anyone would be kind enough to tell me how to install sdk I'd appreciate it. I seen the read me and seen it says execute "android" first but I don't know how to do that. I realize this is incredibly annoying to the xda hive mind trust me I hate needing help like this I'm nothing close to a noob as far as rooting flashing and all that good stuff I'm just unfortunately stuck with only Linux. I'd really really appreciate it.
under the tools folder there is a script called android, u can either run it in a terminal or hopefully if u were to click it, it was ask if u want to run it!
If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.
Seems like my fastboot is stuck on `waiting for device`. I have the fastboot screen on my GN.
Before rebooting into fastboot `adb devices` successfully showed a device (i.e., usb debugging is enabled, dunno whether it is needed for the unlocking):
$ fastboot oem unlock
< waiting for device >
Any idea?
EDIT: Found the solution. After doing a `fastboot devices` it told me "no permissions fastboot" so I needed to be root on my computer for it to work.
FadedLite said:
If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.
Click to expand...
Click to collapse
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.
C-4Nati said:
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.
Click to expand...
Click to collapse
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
For simplicity, you can shorten that to: mount -o rw,remount /system
You can also delete it from a terminal on the phone or any file manager that allows root access. I think the free ES file explorer has root options.
vihil said:
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
Click to expand...
Click to collapse
for needing to type in lsusb, i found that as somewhat of a precaution. I had seen on other threads that others had their device show up as either google or samsung. So i just figured rather check first instead of installing both or something.
for the preparation, basically you do that since your phone is already on. after flashing cwm, you would have to boot back into your phone, push the file to your sdcard, then boot back into recovery. All it does is that it saves just a bit of time.
As for the sudo fastboot, I didn't actually have to do that, but i'll add it, Thanks.
As for the cwm terminal commands, i'll add that as well. Thanks again.
FadedLite said:
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Click to expand...
Click to collapse
not yet. after flashing su-bin-3.0.3.2-efghi-signed.zip (which is just the binary), the user still needs to flash Superuser-3.0.7-efghi-signed.zip, to have Superuser.apk placed in /system/app, otherwise GUI apps won't have access to su. (unless, of course, the zip you are linking here has them both)
It's preferable to have users linked to ChainsDD website, there people will find latest binaries and Superuser.apk. I also don't see any mention to him in the OP. Even if this is a tutorial, don't forget to give credit where needed.
Some help for an Ubuntu Noob/Not a Noob to Windows
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar
jmartino5920 said:
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar
Click to expand...
Click to collapse
Are you getting a "waiting on device" message or something similar when you run adb or fastboot?
Forget about the udev nonsense (not important really until you start developing full time) and just drop a sudo before your commands.
You can shoot me a PM or a gtalk (same username as my xda) if you want and I'd be more than happy to help you get your system going.
Thanks, still a bit more annoying that Windows but this tutorial makes it easy.
Sorry if this is ignorant, but can I use these instructions with Unix & terminal on Mac OS X? I'm thinking yes???
I rooted mine in linux as well... No problems. For some reason I was able to do it much easier though...
I did the fastboot oem unlock step above (Part 1). Rebooted then installed superuser from the android market. Then I installed Clockworkmod from the android market.
Done.
Not sure if I'm missing out on something by doing it this way but so far I've had no issues....