Related
I have been helping out with rooting HTC Aria's over in IRC in the #liberatedAria channel for a while now. A lot of people have problems with drivers on Windows. The easiest solution for them to do this has been to download an Ubuntu LiveCD and use it to root their phone, however many people know nothing about Linux at all and feel daunted by this.
I have created a customized Ubuntu LiveCD that has a script that downloads the Unrevoked Teams reflash, untars it, and runs it as root to root HTC's phones that are supported by the tool (HTC Evo, Hero, Aria, Desire, and Incredible). It also has the Android SDK included and added to the path so it is accessible from a terminal. Everything can be done without a single change to the computer you are doing it on.
Download the iso image here:
MD5: 9a34c343e8f610e66674af9384334bf6
ubuntu-10.04-desktop-i386-HTCROOT.iso Primary
ubuntu-10.04-desktop-i386-HTCROOT.iso FileFactory.com
Burn the iso to a cd (This can be done with any cd burning software, imgburn found here is free)
[Optional]
If you do not have a CD drive, you can create a bootable flash drive by using the tool found here:Pendrive Linux
Put the CD into your computer cd/dvd drive and reboot your computer.
You must make your computer boot from CD, there are many different ways to do this depending on what computer you have, most recent computers have this enabled by default. Here is a guide that may help if you can't get this to work:Enable Boot from CD
Once it boots from the cd it will show a small picture of a keyboard and a person, do not press anything here and it will come to a window that will allow you to select your language.
Select your language and click "Try Ubuntu 10.04 LTS". This will boot up to a standard Ubuntu livecd desktop.
On your phone click menu, settings, applications, development, usb debugging
On the computer click "Places" on the top menubar and click "Home Folder". This will open a file explorer window, in that window is a script called "reflash.sh".
Double click reflash.sh. A window will pop up asking you what to do with this file, click "Run in Terminal". This will go get from the internet the current version of Unrevoked recovery installer from unrevoked.com/recovery, unzip/tar it, and run it as root.
Once it is complete you will be looking at the unrevoked3 screen and you should follow the prompts on screen.
You will then follow the prompts on the screen to plug in your phone, from the notification pane in android select charge only.
unrevoked3 will reboot your phone twice and leave you in ClockworkMod Recovery. On the computer at the bottom of the window it will say "Done".
Close the window, if you do not need to do anything further you can shut down the machine and be back in windows with nothing changed on your windows system.
Congratulations, your phone is now rooted and has ClockworkMod recovery installed.
There are other guides to setup of sideloading for the aria as well as how to load roms. You can do these using this live cd as well, this is a full ubuntu 10.04 livecd with only games and open office removed, and the unrevoked3 installer and the android sdk installed, it is already in the path and you can use adb commands from the terminal without having to switch directories(however it can be found in /opt/android-sdk-linux_86).
I would like to thank The Unrevoked team for making such a nice tool, and website that made this possible. I would like to that the guys in IRC on Freenode.net channels #liberatedAria and #koush for everything I've learned recently as well as all the great work they have done. Thanks also to Attn1 for making some nice roms for the HTC Aria and gave me the idea to create this. Thanks to Downer3d for the torrent mirror. Thanks to Neolobster for the new faster mirror.
Allowing Non-Market Apps using this cd on the stock ARIA rom:
Click Applications in the upper left corner.
Go to Accessories, click Terminal. This will put in you a terminal in the default users home folder. Because ADB(and android sdk) are in the path you do not need to change any directories. Start the phone in CLockworkmod with data mounted from the partitions menu and plug the phone into the computer.
Code:
sudo su
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
What this does:
Switch user to root.
ADB pulls the file that contains the setting to allow non market apps down to the machine from the phone.
The next line runs a sql update of the field install_non_market_apps in table 'secure' and sets the value to 1 (on).
ADB then pushes the file back to the phone in its original location.
You then use ADB to reboot the phone to enable it.
Thats awesome!! If I didnt already go through all the trouble of doing it on my Windows box I would definitely try your live CD. I already have 10.04 installed on my laptop and I never really thought of trying it on there. I wonder if it would have been easier....oh well. Thanks again. Im sure there are plenty of people out there that will find this very useful.
Much easier. And yes, this IS awesome. Great job, Shad0wf0x. This kicks ass.
This is a fantastic idea, I had a ton of trouble rooting my Aria on Win7 x64 and downloading and using Ubuntu 10.04 eventually proved to be much easier. If your iso works as advertised I can see this possibly being the most pain-free solution for annoyed Windows rooters.
Sent from my HTC Liberty using XDA App
This works wonderfully for rooting and sideloading apps (the only issue there was figuring out I needed the root account and permissions). As painless as a dentist trip.
If I was to install Ubuntu from that LiveCD, would it still have the Android SDK on it or would I need to reinstall it? I like not having to cd to it.
the android sdk is installed on the livecd and in the path, you'll have it every time you boot up, the part the script downloads will be gone on a second boot(unrevoked.com's recovery installer)
Great job!
Do u think that u could add some other HTC devices, in the future?
Awesome, thanks!
matteios said:
Great job!
Do u think that u could add some other HTC devices, in the future?
Click to expand...
Click to collapse
The devices supported are the devices supported by the unrevoked3 tool, I am not part of their team, just trying to help out some windows users who have driver problems.
Virtual image?
Has anyone created a virtual image of s full Android dev system? That would sure be handy!
jmdearras said:
Has anyone created a virtual image of s full Android dev system? That would sure be handy!
Click to expand...
Click to collapse
not sure if this is what you're looking for, but it'll help.
http://forum.xda-developers.com/showthread.php?t=701816
Problem with reflash.sh tool
I followed all the steps, till the final step, and it said failed to flash recovery image and my phone only booted up once. Am I doing something wrong?
I am currently running.
Version 2.2 updated OTA last week Aug 3rd
Kernel version - 2.6.32.15
build #: 3.26.651.6
software: 3.26.651.6
PRI version: 1.40_003
jbwfg said:
I followed all the steps, till the final step, and it said failed to flash recovery image and my phone only booted up once. Am I doing something wrong?
I am currently running.
Version 2.2 updated OTA last week Aug 3rd
Kernel version - 2.6.32.15
build #: 3.26.651.6
software: 3.26.651.6
PRI version: 1.40_003
Click to expand...
Click to collapse
it says in your signature you have 2.2 updated OTA, that must mean you have an evo, and those aren't supported by the unrevoked tool when running 2.2.
awesome shortcut for rooting phones, however I followed the steps and it is saying that the hero is not supported at this time? Did i do something wrong, I'm running 2.27.651.5
I've burned the the iso file to a cd but I'm not able to get the boot-up to work correctly..or to come up at all, when re-booting windows.
@lcw
When you boot, you will need to hit your bios and select your CD drive as a boot device. Then enjoy the ride - easy as falling off a bike.
I cannot get my dell d600 or d630 to boot. The CD spins but I get the message "No bootable device".
I verified that the ubunto_*HTCROOT.iso file 641,942 kb is the only file on the CD.
Can someone please help.
pinkpanther2000 said:
I cannot get my dell d600 or d630 to boot. The CD spins but I get the message "No bootable device".
I verified that the ubunto_*HTCROOT.iso file 641,942 kb is the only file on the CD.
Can someone please help.
Click to expand...
Click to collapse
You're not supposed to burn the ISO file onto a disc as a file. You're supposed to burn the contents of the ISO to a disc.
Sent from my HTC Liberty using XDA App
I attempted to boot from the CD, I get the person/keyboard screen then i get the Ubuntu screen, then my computer goes black, any solutions?
This is the BEST way to root your Aria. Big props to everyone that helped create it. You guys are the best.
Hey guys I an having the darnest time root this guy should be easy with these one clickers programs.
Pretty sure its a driver thing, note I can see the device when in cmd and doing the adb devices that shows up. just gets hung up at the end there.
attached a pic of what the cmd line looks like
anybody have the current drivers, googling for them just yields me to forum posts asking where the drivers are
thirty views and nothing
ok its not a driver issue if your loading root.sh (the big block of text) the issue is that the adb server isnt starting back up in time in order for your device to be recognized. solution? open up the bat file and copy and paste the commands one at a time; or if you have a linux/osx computer try doing it there with my scripts in my sig
couple ideas..
1.open up the run.bat file in notepad or similar and go through all the commands manually, that way you have control on speed of commands and allow enough time for adb to startup again.
2. open up the run.bat file and increase the wait time in the script.. -w 3000 or something like that..
i would suggest you do commands manually. The one-click root did not work for me but doing things manually worked right away.
How to do it
Hey man this is how I got it to work. I was having all the problems device not found etc etc. Have been trying since Sunday. What I finally did after installing the drivers was restart the computer and Phone. After that i tried to run the program it failed with device not found again so i unplugged the usb cable from the phone and closed the cmd window. And also brought up Task manager and killed the adb.exe process. then i reran the run.bat file and this time when it gets to the adb restart relogin apart i killed the SMALLEST ADB.EXE IN THE PROCESS TAB OF TASK MANAGER and that is when it finally got it to work. Had to do the same when I tested it with the uninstaller. So that seems to work. If anyone has any questions feel free to pm me.
But thank god it finally worked.
David
other people have done this and it worked for them also.
I tried all kinds of stuff ultimately I ended up using an xp machine. I later remembered the whole xp mode in windows 7 but didn't actually try it ... win7 just gave me a hard time although the post about changing the amount of time to restart adb makes sense
Sent from my SPH-D700 using XDA App
will try all of that thankyou gents
Ok,
So Ive been scouring the net to find out if there is anyway I can get my device to be recognized. So far I've tried:
Windows 7 Ultimate 64bit, phone goes into storage mode and loads the drivers. although the drivers are not signed so windows refuses to load them, nice microsoft.
Ubuntu 10.04 64bit, ok i've installed usb_modeswitch and setup a bunch of udev rules (attached) and I can get the device to be detected but not recognized ie if I execute
Code:
adb devices
I get
Code:
List of devices attached
???????????? device
if I try
Code:
adb shell
I get dropped right into the user shell on the device. *Nice* score one for linux, but this doesn't do me much good because if I try to bring up the dalvik monitor it refuses to recognize the device grrr bad linux
I've attached my udev rules and a listing from when I tried to start the dalvik monitor, if anybody has some idea how I can get either windows to load the provided drivers or ubuntu to recognize the device I would be eternally greatfull
Thanks
Tired and wear from trudging around the net all day
Ben
I am trying to get a development environment setup and running into all sorts of problems with ADB when I have an actual device attached to the system. I am using eclipse and can use the emulators with no problems, until I attach an actual device to the system. At that point, even when trying to debug on the emulator, ADB keeps crashing. I can start a debug session on the actual device, but if I try to switch to the DDMS view, ADB crashes.
I am running on windows 7 and have even go so far as to do a complete reinstall of the system and only install the development tools only to have this problem show up again. I can't believe that this is normal, how could anything get developed with this type of issue?
I have been searching for answers and not been able to find anything helpful. I restart ADB only for it to immediately crash again. All the software is updated to the most recent versions. This problems occurs on both my desktop and laptop so don't think it is a hardware issue with my systems. Only thing really in common is the device, my EVO.
Any help would be appreciated. This is driving me nuts. I need to get this working for some projects but I feel like I am pounding my head on a brick wall trying to get it to work.
If this isn't the best place for this thread, could you please point me in the right direction? Thanks.
First navigate to where adb is located within cmd prompt.. [depends on what tutorial you followed if any at all] Either C:\android-sdk-tools\tools or if you used the .exe installer then itll be in your Program Files\android\android-sdk-tools\platform-tools\.. when you are in the directory of the adb location in cmd prompt runt the following code.. "adb devices" to see if adb is working at all.. it sounds like it might be a ROM issue unless adb is missing files it needs which i ran into that problem.
jr10000 said:
First navigate to where adb is located within cmd prompt.. [depends on what tutorial you followed if any at all] Either C:\android-sdk-tools\tools or if you used the .exe installer then itll be in your Program Files\android\android-sdk-tools\platform-tools\.. when you are in the directory of the adb location in cmd prompt runt the following code.. "adb devices" to see if adb is working at all.. it sounds like it might be a ROM issue unless adb is missing files it needs which i ran into that problem.
Click to expand...
Click to collapse
ADB is working fine like this. My phone shows up in the devices command. I can shell to it. Push/Pull files. All with no problems. It's not until I try running a debug session from eclipse (either in the emulator or on the device) that it crashes.
No one here that can help?
To the best of my knowledge, you either use the Emulator OR the phone.
At least that's what I do. Before I plug in my phone, I shut down any Emulator(s) that I might be running.
Also make sure to eject phone (Mac) or stop the device (Windows).
Never had a problem.
Rootstonian said:
To the best of my knowledge, you either use the Emulator OR the phone.
At least that's what I do. Before I plug in my phone, I shut down any Emulator(s) that I might be running.
Also make sure to eject phone (Mac) or stop the device (Windows).
Never had a problem.
Click to expand...
Click to collapse
The problem is I can't use EITHER when the phone is connected. So even if I wanted to debug on the phone, I can't.
i have the same problem, and it drives me crazy, i can't get a specific reasong, once i uninstalled google upadter and the adb works fine, second time i uninstalled Google chrome and it work fine until yesterday, today it is back to crashing, i dont know what else to do
Edit: my problem started after upgrading to android 2.3
NoEnd said:
i have the same problem, and it drives me crazy, i can't get a specific reasong, once i uninstalled google upadter and the adb works fine, second time i uninstalled Google chrome and it work fine until yesterday, today it is back to crashing, i dont know what else to do
Edit: my problem started after upgrading to android 2.3
Click to expand...
Click to collapse
I have pretty much given up on getting it to work right. I have a linux box that I set up the development environment on and it is working fine there. I'm thinking it could be something with 2.3 also. Going to see if I can find the 2.2 and do the setup with that.
edboston said:
I have pretty much given up on getting it to work right. I have a linux box that I set up the development environment on and it is working fine there. I'm thinking it could be something with 2.3 also. Going to see if I can find the 2.2 and do the setup with that.
Click to expand...
Click to collapse
Try going into your sdk/tools folder and setting adb to run as administrator, expecially for win 7 (leave it open then go back to eclipse). I had the same problem and I also closed the emulator when debuging on the device.......don't know, but maybe it will work for you also. Good luck!
awrnsmn said:
Try going into your sdk/tools folder and setting adb to run as administrator, expecially for win 7 (leave it open then go back to eclipse). I had the same problem and I also closed the emulator when debuging on the device.......don't know, but maybe it will work for you also. Good luck!
Click to expand...
Click to collapse
No luck. Eclipse reported it couldn't run adb because it needed elevated. Thanks for the suggestion.
yeah tell me when ever found a soultion for the problem, it seems that it's a small problem
is your windowsOS 64??
NoEnd said:
yeah tell me when ever found a soultion for the problem, it seems that it's a small problem
is your windowsOS 64??
Click to expand...
Click to collapse
Yes it is. But I do have the 32bit version of all the development system. I have an extra drive on my system that I can try installing the 32bit version of Windows 7 on and see if I have any better luck with that.
edboston said:
Yes it is. But I do have the 32bit version of all the development system. I have an extra drive on my system that I can try installing the 32bit version of Windows 7 on and see if I have any better luck with that.
Click to expand...
Click to collapse
please do and reply back
NoEnd said:
please do and reply back
Click to expand...
Click to collapse
Just tried running it on 32bit windows. Same problems. ADB crashing.
edboston said:
Just tried running it on 32bit windows. Same problems. ADB crashing.
Click to expand...
Click to collapse
there must be a problem with the phones???
mine is Desire HD
Rom Revolution HD
NoEnd said:
there must be a problem with the phones???
mine is Desire HD
Rom Revolution HD
Click to expand...
Click to collapse
I had someone suggest it could be a custom rom or kernel issue. I am running an evo with a custom rom and kernel. I'm not sure where the adb part is implemented but I might be able to try stock later this week. Strange that it works fine on my linux box with the custom. Probably the linux version of adb is more robust and can handle the errors better.
I'm having similar issues on Windows 7 32 and 64 bit. I'm using the 2.3 tools.
The interesting thing is that ADB only crashes when I try to run (not debug) one particular application (one I wrote) inside Eclipse. I have 3 other projects that work just fine, no crashing.
Even with the one app, it starts out working ok, then it'll start crashing when I try to run it, and then it'll crash anytime eclipse is up and that program is running on the phone!
Completely wiping the data partition fixes it for a while, but that's obviously a crappy solution.
Wiping the Cache/Dalvik Cache doesn't do anything.
Wiping the data for the com.android.debugtool (is this even related to ADB? seems too coincidental) doesn't do anything.
Uninstalling, or just killing my app on the phone, stops the crashing, until the program is installed, or starts, again.
Turning off and on USB Debugging a few times seems to sometimes help, but only for a while.
Rebooting also can help stop the crashing for a while, but not every time.
I turned the logging in eclipse up to verbose, but I don't see anything in the console window that seems to offer any clues.
Is the problem with ADB, or with DDMS? (DDMS is what eclipse runs to do everything on your device, DDMS then calls ADB). Because without eclipse open, adb works fine. Or is it a specific command send to ADB through DDMS? Is there any way to find out exactly what DDMS is doing with ADB?
Does anyone know if there's another "debugging" cache on the phone somewhere that, if cleared, may fix the crashing?
Scott
edboston said:
I had someone suggest it could be a custom rom or kernel issue. I am running an evo with a custom rom and kernel. I'm not sure where the adb part is implemented but I might be able to try stock later this week. Strange that it works fine on my linux box with the custom. Probably the linux version of adb is more robust and can handle the errors better.
Click to expand...
Click to collapse
Okay. Tried it with the stock ROM/Kernel with the same results. ADB crashing.
Delvorak said:
I'm having similar issues on Windows 7 32 and 64 bit. I'm using the 2.3 tools.
The interesting thing is that ADB only crashes when I try to run (not debug) one particular application (one I wrote) inside Eclipse. I have 3 other projects that work just fine, no crashing.
Even with the one app, it starts out working ok, then it'll start crashing when I try to run it, and then it'll crash anytime eclipse is up and that program is running on the phone!
Completely wiping the data partition fixes it for a while, but that's obviously a crappy solution.
Wiping the Cache/Dalvik Cache doesn't do anything.
Wiping the data for the com.android.debugtool (is this even related to ADB? seems too coincidental) doesn't do anything.
Uninstalling, or just killing my app on the phone, stops the crashing, until the program is installed, or starts, again.
Turning off and on USB Debugging a few times seems to sometimes help, but only for a while.
Rebooting also can help stop the crashing for a while, but not every time.
I turned the logging in eclipse up to verbose, but I don't see anything in the console window that seems to offer any clues.
Is the problem with ADB, or with DDMS? (DDMS is what eclipse runs to do everything on your device, DDMS then calls ADB). Because without eclipse open, adb works fine. Or is it a specific command send to ADB through DDMS? Is there any way to find out exactly what DDMS is doing with ADB?
Does anyone know if there's another "debugging" cache on the phone somewhere that, if cleared, may fix the crashing?
Scott
Click to expand...
Click to collapse
your reply can be summarize in few points:
1- its a library or code you used in that app that crashes ADB.exe (as u said only this app)
2- it maybe an app in the phone, the apps i suspect is SU(for rooted phones) or Whatsapp(because it's runs a service that stops as soon as the USB mode activated)
i hope this Thread doesn't die, because it's the only one on the WEB.
One thing I checked between the v7 and v8 of the SDK is adb.exe is the same version in each of these. So the thought about the DDMB being a possible culprit is a good possibility. Because outside of eclipse debugging, I have no problems with ADB at all.
Ok I've researched this to death and tried in on both Windows 7 and osx 10.6.6 to attach using adb and install a couple of .apk's and the same thing happens on both platforms - NOTHING :-(.
You would think this would be pretty basic, but I am missing something somewhere.
Summary:
1. Am running the stock rooted b&n rom.
2. Can access both the internal and SD cards on the nook on both windoze and
osx. Eliminates cables, drivers etc...
3. Debug is selected in the nookstools settings
On both OSX and Win 7 installed the latest version of the Android SDK - both installs provided me with the platform-tools directory from which I will initiate all adb commands. So far so good...
on mac: ./adb devices returns:
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
$
As you can see I never get any device information returned, does not matter if Im on Windows or mac - same response.
Just for grins I downloaded the wireless app and tried to connect adb that way...no luck...
I could go into everything that i have tried over the last 24 hours...but that would also be pointless.
Bottom line...assuming this is something simpleI am just missing. Assuming since the symptoms are the same on both platforms that the issue lies on the nook but for the life of me I cannot find it.
Assuming if I cannot figure this out I will slowly go insane..my next step is to flash either froyo or honeycomb rom and see if this helps with the problems. Of course I MUST have the market available to me or I will not b able to load any .apk's.
Hpe Im in the right place. Any guidance is GREATLY appreciated.
Love this little Nook....BG
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
YMMV, but it solved that issue fo me.
Who Swami - It Worked
Swami,
I fall to my knees and bask in your knowledge: It WORKED!
I knew it was something simple, there is not a post on the entire Internet in any forum I have ever found (and I may have searched them all!) that mentions superuser needs to be running for adb to be able to communicate with the device. I wonder if this is a nook issue only. Will test on my wife's Epic this evening and post the results tonight.
My sanity now restored I bid you all a hearty SEE-Ya!
-BG
Omg I actually helped someone!
Glad it worked for ya I'm sure you felt the same relief I did when I finally stumbled across that fix.. I was pulling my hair out for hours LOL
Thanks Once More
As was I such a simple fix you would think I would have thought about permissions on the client side , such is life and tech thats why we all hang together.
Must say I was going to purchase the iPad 2 when it came out (NEVER buy 1st gen Apple) but now I'm not so sure...LOVING my Nook.
themirthfulswami said:
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
Click to expand...
Click to collapse
I'm not sure if this is related but I *think* that what made it work for me was to freshly enable the Debugging USB mode immediately before connecting the USB cable. Maybe that also triggered the Superuser app??? It's always the small things in life that make us smile
my problem is a little different.... I have sd cards with honeycomb (no market) and froyo (market and other apps). I can see the NC in adb with both, but honeycomb shows the device offline... and adb cannot talk to it. froyo show the device online and I can use adb. Both honeycomb and froyo show up in windows too.
I can't find anything that talks about getting the NC to show online to adb.
Same Problem
I have the same problem of trying to get my nook recognized. The only thing I can see different between my setup and the instructions on NookDevs was that they said I should see Android ADB Composite Interface on my Device Manager. Mine reads Android ADB Interface.
Tried the Superuser and the USB Debugging with no luck. Just really trying to get this set up so in case I need to factory reset. Because the 8x method manually is way too hard.
Have you guys read though this thread?
http://forum.xda-developers.com/showthread.php?t=910008&highlight=ADB
it worked for me like a charm.
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
I had intermittent ADB success with my Mac. After installing the ADB Wireless app there have been no problems.
Seaweedbrain said:
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
Click to expand...
Click to collapse
nvm
i connected my nook to the back of the cpu.
for some reason, it seemed to work fine.
it read the device as online.
got the g-apps