Stuck on rooting - G1 Q&A, Help & Troubleshooting

I was following this guide:
http://wiki.cyanogenmod.com/index.p...eam_Firmware_to_CyanogenMod#Rooting_the_phone
Everything worked out okay until I got to the section about rooting. Because I live in Hawaii, I have no 3G network and must sign in to my Google account through WiFi. That's when I got linked to this guide:
http://modmygphone.com/forums/showpost.php?p=51891&postcount=12|
...and everything went downwards from there. I could not understand what this guide was talking about. There were downloads sending me to links. There were links sending me to downloads. I wound up visiting dozens of external links and downloading dozens of .zip files with no clue whatsoever as to where to put them. I still have no idea what this guid is talking about.
Can anybody help me get past the Google sign in screen so I can continue with the CyanogenMod guide?

You don't need 3G to sign in, Edge or even GPRS is just fine. Do you really need to activate by Wi-Fi?
Did you set-up ADB? This is crucial, you 100% need it.
The guide you linked to is one the most comprehensive that've seen up-to date. To use that guide, you do NOT need to download anything, everything is done by typing in few commands on your phone and then on your computer.
To me, it sounds like you have problems setting up your ADB and there are good guides for that as well, even the one in the linked thread is pretty good.
Basically, to set up your ADB you need to
Download ADB first.
Install Drivers
Point your computer to ADB (Path variable)
Connect your phone and hack away.
Follow only one guide.. do not wander off and download all kinds of zip files.

I think I got to that step somewhere in that second guide I linked to. I clicked on "Windows USB driver" assuming it was just one file, but instead it sent me to this page:
http://developer.android.com/sdk/win-usb.html
I decided to read that page and download the SDK file here:
http://developer.android.com/sdk/index.html
I think this is exactly where I left off because this was where I started getting confused. I did not know how to install the program or where to install it in (Windows 7 64-bit). I'm also having a hard time getting my computer to recognize my SD card/phone (it charges, but it won't recognize it as an external drive anymore).

Related

ADB HELP

I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.

[HELP]cmd adb error msg...

I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
SG_Shadow said:
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
plug your phone in
get working drivers
install linux, it works better
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problem
Click to expand...
Click to collapse
[*]plug your phone in
[*]get working drivers
[*]install linux, it works better
Click to expand...
Click to collapse
u forgot a step.
[*]post in the correct forum
Firerat said:
plug your phone in
get working drivers
install linux, it works better
Click to expand...
Click to collapse
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Daneshm90 said:
u forgot a step.
[*]post in the correct forum
Click to expand...
Click to collapse
Fail!
SG_Shadow said:
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Fail!
Click to expand...
Click to collapse
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
This IS in the wrong forum.
Moved.
Firerat said:
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
Click to expand...
Click to collapse
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
SG_Shadow said:
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
Click to expand...
Click to collapse
you posted a couple of hours ago, duplicating posts might be considered spam
you didn't really give any useful information in your post(s)
and if I were to assume your were, then this is just some boring role play thing at a job interview or something, as you wouldn't really need anyones help on this.
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
ivanmmj said:
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
Click to expand...
Click to collapse
Thank you for trying to "actually" assist me. I am using the exact same usb cable on purpose to rule that out as a reason. I've also recently update both computers to the latest norton antivirus. Like I stated the drivers install on the laptop and I'm able to connect the G1 for file transfers, so I assume the driver is working but when I type in adb device or adb shell in cmd, I get the no device msg. I'm really stumped with this one...
*Update* My norton did remove adb.exe from windows\system32 on both computers, but I was able to restore that file on both. Like I said, my pc works just fine, laptop no good...
And point 3
Install linux ( ubuntu 10.4 )
Just give it 10gb
It will eliminate hardware faults as being the problem
The android developer has a tutorial for 10.4, so it should be easy
( no need for drivers, aparently 10.4 ships with the android udev rule )
the driver for file transfer isnt the same as the driver for adb....so your logic is flawed
seriously tho, use linux...wubi is pretty good now and u only need 4-10gb if u are only using it for android stuff
in my experience, windows, especially where norton is used, randomly breaks adb
The file transfer is done using the standard windows mass storage driver, not an android specific driver. Even if it's the same norton, try disabling it and see what happens. Also, trying removing the driver completely and reinstalling it again. I've had the issue happen also only when in windows and it's always something random.
virtualbox _should_ ( I think ) let you 'see' the Android Phone regardless of the drivers being installed on the Windows host
But, I have not tested that
Did you ever get this to work, I have the same issue?
I'm having the same issue, I'm trying to use ADB with my TF300T from a Windows 7 64 bit system. Always get the error adb error.
I have a couple of questions will this work correctly with a 64bit O.S?
Also the part of the instructions that reference SDCARD are they talking about the directory on my ASUS /sdcard/ or are they talking about the physical card?
Just need to know does it require you to have a sdcard in the ASUS to use adb?
May sound like fundamental questions to a lot of you, however I have combed through these forums as well as others all over the web, and the majority of instructions seem to be lacking the basics.
Thank you,
I have Ubuntu at work should I run ADB through this?
I have Ubuntu at work
It's a bit of a process according to the instructions that I have on the
screen right now to setup ADB through this, is there any gotchas that I should
know about before attempting this?
This is running on a VM on one of my servers. What I'm looking for is any known compatibility issues with versions of ADB and the Asus TF300T running .26
Thanks in advance.
Nordis

Cannot open ddms.bat in order to take screenshots on Nexus One

I wanted to take screenshots of my Nexus One (2.2 FRF91/T-Mobile/Stock) but I'm just a newbie so I followed the guide on andriodcentral Anrdroid 101 tips. (Sorry I can't link to it since I'm a new user on these forums
That guide led me to another guide on how to install the sdk
When I tried to pull my 3rd party apps, cmd didnt do anything it simply said "0 pulled, 0 skipped", however I was able to pull my standard apps. I'm confident the sdk was installed correctly though.
I'm using a laptop with Windows 7 64bit and an AMD processor, I'm not sure if that information is helpful or not
I've already downloaded and installed the android 2.2 sdk, java runtime environment, java development kit. I've also properly installed the ADB drivers for the Nexus One. I also downloaded Eclispe but when I tried to run it, the application won't open. I have a feeling its because I didn't install it properly.
My problem now is that the ddms.bat (Dalvik Debug Monitor) won't open when I double click on it. I tried to right click and run as administrator but that didn't work either. In both cases when I try to open it, a cmd windows opens for a fraction of a second and then closes before I can read it. So I googled it and found a website that seemed to be able to solve the problem but its geared towards linux users.
I specifically followed these directions "To fix this a replace of the bundled swt is needed. The file is located under android-sdk-linux_x86-1.5_r3/tools/lib/. Rename swt.jar to swt_32b.jar. Next download swt for your platform. I have used swt-3.4.2-gtk-linux-x86_64.zip. Unpack the file swt.jar in the zipfile to android-sdk-linux_x86-1.5_r3/tools/lib/ and finally start ddms" but that didnt work either. So now my android-sdk-windows/tools/lib/x86_64 is full of other files rather than just having that swt.jar file.
Can anyone please help on getting ddms.bat to open or on how to get eclipse to open?, I'm so close to being able to take screenshots.
Some notes:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
2. USB debugging was ON when I tried it
TaeKwonDonkey said:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
Click to expand...
Click to collapse
Do you have the right drivers installed?
When your phone is on, plugged in, SD not mounted, and USB turned on, you should see "Android Phone" and "Android Composite ADB Interface" underneath that.
If you don't want to root (it's so easy and painless if you can follow instructions) then I don't know what to tell you other than:
1. Install "USB Deview" and remove all HTC/Google/Android related drivers.
2. Completely uninstall and wipe out the SDK stuff.
3. Rebooted, and reinstall Android SDK, and make sure that Windows7 installs the right drivers.
Installing the SDK is no more difficult than installing any other piece of software. If you've got Java installed, and you've plugged your phone in, and debugging is turned on, what *should* happen when you double-click ddms.bat is, the command prompt window opens, but then the Debug utility should open.
I had the screenshots stuff working before I ever rooted.
I followed the steps here: http://www.knowyourcell.com/google/...take_screenshots_on_the_google_nexus_one.html
Rooting is easy and painless. If you root, you don't have to flash a custom ROM or anything, but then you can install an app that you simply open, enable, then whenever you're doing something that you want to take a screenshot of, you shake the phone, and there it is.

[Q] Problems with ADB / Drivers after froyo internal installation

Ok. I got my nc rooted, and used ROM Manager to install NF internally. Now I want to put gApps on it. So far everything is working wonderfully.
I download the Easy Driver Pack (http://forum.xda-developers.com/archive/index.php/t-910008.html) and follow the instructions. My NC isnt recognized. I went through all the troubleshooting tips there that I could find and my NC still isnt recognized.
Next I download http://legacyschool.us.to/nookdev/nook-usb-installer.rar and follow those instructions thinking that I might be able to fix said problem above. Still a failure. Now I've reached the point that I'm becoming slightly frustrated. Before I rooted my NC was recognized. Before I used ROM Manager to install NF my NC was recognized, and now I cant figure out wtf I'm doing wrong. Can someone help me out please?
UPDATE:
I got ADB to recognize my nook and it says that it's one of the adb devices plugged into my computer. When I go to enter the command prompts to install google apps, the cmd window freezes up after I input the first line (and I'm hoping I read the directions correctly and have my cmd window pointed in the right direction, at the sdk tools folder with the correct google application system file inside it)
So I'm not sure where to go after this because I'm not seeing anywhere that I could go back and fix an error. Maybe someone else will.

Installing fastbook

I'm trying to install the latest ROM - I have followed the instructions, but when I try and run setup to install the drivers, Windows tells me that it has found fastbook, I get the windows driver install prompt - I select next, it obviously looks for the driver - and then I get the message - Cannot Install this Hardware. This therefore means that the drivers do not install and I get the message "Please Plug-in your Device!!" I hit OK - it tells me the same again and again - and the rollsback the driver install. Any ideas on how I can overcome? Thanks.
leighv said:
I'm trying to install the latest ROM - I have followed the instructions, but when I try and run setup to install the drivers, Windows tells me that it has found fastbook, I get the windows driver install prompt - I select next, it obviously looks for the driver - and then I get the message - Cannot Install this Hardware. This therefore means that the drivers do not install and I get the message "Please Plug-in your Device!!" I hit OK - it tells me the same again and again - and the rollsback the driver install. Any ideas on how I can overcome? Thanks.
Click to expand...
Click to collapse
I really hope your on a mobile device that is auto correcting "fastboot" as "fast book":thumbdown:
You have to manually point windows to the folder you have the drivers unpacked onto your computer
Search the forums...... even read the stickies section. This has been described in full detail several times.
This took me a minute to search, copy, paste:
http://forum.xda-developers.com/showthread.php?t=1395964
There is a link there to install drivers, do some reading, the streak is not as common a development as other more popular devices.
The drivers should be located in the nvflash package you say you are trying to install. Again, point windows to the folder the drivers are in.
I will not provide step by step instructions as I myself and many before me have already done so. Give yourself a half hour of reading through the posts and you will more then likely find exactly what you are looking for.
Sent from my Galaxy Nexus using xda premium
ElfinJNoty said:
Give yourself a half hour of reading through the posts and you will more then likely find exactly what you are looking for.
Click to expand...
Click to collapse
you're being way too lenient with the n00bs, half an hour of reading through forums? seriously, this is the same guy who apparently put a 128gb sdcard in a streak 7 and made it apparently work, I deem this thread closed as the amount of others that contain information to the questions asked
Question answered above. Please search thoroughly in future before creating threads.
Thread closed.

Categories

Resources