Ok so this all started 7 hours ago.
I did a factory reset and I couldn't get passed the gmail account login. I tried multiple times, and tried resetting. Didn't work.
So I looked online to see if I can use wifi, and I could.
http://modmygphone.com/forums/showth...1891#post51891
I updated my drivers, downloaded Android SDK.
I got up to the part where I type " adb shell "
It says no devices found. Please help. Thanks in advance :]
Currently I am in stock ROM RC29.
I am trying to do this on the site above:
"6. Now type this on your G1 keyboard..
<enter>setprop persist.service.adb.enable 1<enter>
7. Now.. Open the command prompt on your PC ( Start > Programs > Accessories > Command Prompt )
8. Type "adb shell" without the quotes.
(Just in case typing that doesn't do anything.. Navigate to the folder you've unzipped the ADB Files and type there instead)
9. Then when the '$' comes out .. type this:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
9. Take a look at your G1 and now it'll be in the WiFi settings section. Configure it.. Connect to your network.. And done!"
I find this guide:http://forum.xda-developers.com/showthread.php?t=532719 much easier to follow
the code
cd C:\android-sdk-windows\tools needs to be typed in the cmd before typing in adb shell.
thanks for the guide, but I followed what you said/the guide said, still the same result =/
TmobileDash12 said:
thanks for the guide, but I followed what you said/the guide said, still the same result =/
Click to expand...
Click to collapse
Do you have the android-sdk-windows file on the root of your C drive?
Debugging
Did you make sure to add a path for adb in the environmental variables tab on the pc, and also make sure that usb debugging is checked off in the settings>applications>development tab.
It is in my C drive or root folder.
I can't access settings because my phone's stuck on the login screen.
I have a Nexus One rooted running the latest Cyanogenmods (5.0.8), I installed QuickSSHd and started the SSH deamon. I am able to ssh into the Nexus One over WiFi using Putty from my PC (Windows 7) using "root" as the user and the password set in QuickSSHd.
When logged into the phone, I can do a "su" command and "id" returns "uid=0 (root) gid=0(root)".
But... when I try to do "ls" nothing happens, just nothing is returned, not even a "not found" message (which I get if I type a random command string).
vi works tho
Any hint what I am doing wrong?
Do you have busybox installed?
Please read the rules on posting in the development section.
If you type "ls" and hit return and nothing but a blank line appears, chances are it's dropped you into an empty directory.
Where does "pwd" say you are? What happens if you type "ls -al"?
If you type "ls" and hit return and nothing but a blank line appears, chances are it's dropped you into an empty directory.
Where does "pwd" say you are? What happens if you type "ls -al"?
Click to expand...
Click to collapse
Exactly what i thought:
Pwd
-------------------------------------
Sent via the XDA Tapatalk App
I have updated my nexus one to Ginger bread image GRI40 from http: //android.clients.google.com/pa...8.656099b1.zip
following this thread http: //forum.xda-developers.com/showthread.php?t=966939&page=4
And I have rooted my phone and I can get 'adb shell' and able to execute 'su' command.
But when I execute 'hierarchy viewer' at my desktop, I get this error in console:
[2011-04-05 15:35:33 - hierarchyviewer]Unable to debug device HT9BSP800010
Can you please tell me how can I run 'hierarchy viewer' on Nexus One?
Thank you.
Did you ever find an answer to this question?
Actually, a quick Google later and it seems that you can't run the hierarchyviewer on stock phones. You may need to unlock the bootloader and root the phone, perhaps even install a non-stock ROM.
http://stackoverflow.com/questions/3711348/how-can-i-run-hierarchy-view-with-nexus-one
http://androidgroup.blogspot.com/2011/05/android-developers-hierarchyviewer-on.html
http://stackoverflow.com/questions/4328151/trouble-with-nested-layouts
not sure if anyone has seen this but i found it posted in another forum dated june 8 (retail launch date) and no one has commented. i dont know enough to try this out my self but looks promising.
Galaxy Tab Rooting Instructions - ADB Method
These instructions provided me with a permanent root workaround when SuperOneClick, run within Windows 7, repeatedly hung "waiting for device". SuperOneClick elegantly automates the ADB method, but for some reason the ADB command "adb devices" fails to recognize an attached Galaxy Tab when run from within Windows 7. The larger problem seems to be that in some situations like mine, ADB simply does not run correctly from within Windows 7, even when one right-clicks on SuperOneClick.exe and runs it as Administrator. Perhaps SuperOneClick would work OK on Windows XP, but I have no idea.
The procedure below uses components from SuperOneClick but runs the ADB server and commands from within Linux. In this environment the ADB command "adb devices" correctly reports the attached Galaxy Tab, and other ADB commands work correctly as well. To obtain the needed SuperOneClick components, download SuperOneClickv1.9.1.zip to Linux and unzip it there. The SuperOneClick.exe (which is a Windows executable) will be ignored, but other files (see below) will be pushed to the Galaxy Tab during the rooting process.
I'm indebted to authors at http://pastebin.com/i234U96k and http://rootingdroid.com/ for the hack below. Note that there is a modification to require no dependence on a "cp" command at the ADB shell prompt. For some reason "cp" is missing in /system/bin on my Galaxy Tab.
As always, attempt using this procedure at your own risk. Be specifically aware that you may not be able to "unroot" your Galaxy Tab after using this procedure--ever! This procedure doesn't back anything up from the unrooted device, so if "unrooting" it requires restoring something from such a backup, I'm (and you're) stuck with a permanently rooted device. This condition may interfere with your receiving certain updates or downloading DRM content in the future.
1) Download and install TitaniumBackup and SuperUser onto your Galaxy Tab from the Android Market. Note that SuperUser may not be necessary since there are sources for this app below. I'm including it at this step because I had previously installed it prior to the steps below.
2) Download and unzip SuperOneClickv1.9.1 into some Linux folder of your choice. You can get it at http://shortfuse.org/?page_id=2 near the bottom of the page.
3) Install Android SDK for Linux x86 into your home directory on your Linux box. You can get it at http://developer.and.../sdk/index.html The ADB server will be located in ~/android-sdk-linux_x86/platform-tools.
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
Note that there is an alternative source for Superuser.apk and su at http://www.rootingdroid.com at the "Download" link in Step 2.
5) Enter the Linux directory containing the ADB server with the command
cd ~/android-sdk-linux_x86/platform-tools
6) Plug in the Galaxy Tab to the computer, with USB debugging turned on.
7) Test ADB recognition of the Galaxy Tab with the command
./adb devices
You should see messages indicating the ADB server is starting, and then a message similar to
List of devices attached
100020497aab device
If no device is listed, begin investigating by ensuring that USB debugging is turned on. In my experience, when the "adb devices" command is entered from within Windows 7, no device is listed. Again, I think this is related to the "waiting for device" hang when SuperOneClick is run in Windows 7.
8) Push psneuter to the Galaxy Tab with the command
./adb push psneuter /data/local/tmp
9) Make psneuter executable with the command
./adb shell chmod 777 /data/local/tmp/psneuter
10) Run the psneuter exploit with the command
./adb shell /data/local/tmp/psneuter
The message "property service neutered." should appear indicating success.
11) Test for successful rooting with the command
./adb shell
The # prompt should result.
12) Remount the /system volume rw (by default it's ro), so that files can be pushed to /system, with the command
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
13) Return to the Linux computer command line with the command
exit
14) Push Superuser.apk, su and busybox to the /system volume with the commands
./adb push Superuser.apk /system/app/Superuser.apk
./adb push su /system/bin/su
./adb push busybox /system/bin/busybox
15) Make su executable with the command
chmod 4755 /system/bin/su
16) Remount the /system volume as ro with the command
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
17) Verify that su works with the command
su
You should see the # prompt; type the command
exit
and you should see the # prompt again.
18) Power the Tab down and then power it back up. Run TitaniumBackup, which will ask for root privileges that (hopefully) will be granted. It's a good idea to backup your Galaxy Tab before using your new root privileges!
i take no credit for this. all credit to feral urchin for which ever device this works for retail or I/0 but something tells me its for retail because I/o has had an easier way to root for a while..
I am running windows vista ultimate. Should I try this and see if I have the same bug that has been reported for Windows 7?
I have a new Tab 10.1 Retail picked up today.
give it a try let us know the results please
dsh897 said:
but for some reason the ADB command "adb devices" fails to recognize an attached Galaxy Tab when run from within Windows 7. The larger problem seems to be that in some situations like mine, ADB simply does not run correctly from within Windows 7, even when one right-clicks on SuperOneClick.exe and runs it as Administrator. Perhaps SuperOneClick would work OK on Windows XP, but I have no idea.
Click to expand...
Click to collapse
This might work. I am running Vista Ultimate x64 and my adb does recognize my retail Tab 10.1. See image below.
Now when I execute the command on step 10 I receive this error. . .
"Failed to set prot mask <Inappropriate ioctl for device>"
Suggestions?
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
did you put everything in the right directory?
where are you a firefighter? im a medic finishing up fire academy in 2 weeks in sofla
im attempting another angle right now..
i got odin working with my galaxy very quickly i backing up now. but i have a funny idea that i can flash the i/o unlocked bootloader with odin 3 unlock it then gain root and then update everything and then flash clock work.
dsh897 said:
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
did you put everything in the right directory?
where are you a firefighter? im a medic finishing up fire academy in 2 weeks in sofla
Click to expand...
Click to collapse
Yes I copied all those files to the correct directory. Only on my windows machine the it is /android-sdk/platform-tools/
I am a firefighter in the Charlotte, NC area. Just got off tour this morning.
Google searching that error as I type. I'll let you know the progress.
dsh897 said:
im attempting another angle right now..
i got odin working with my galaxy very quickly i backing up now. but i have a funny idea that i can flash the i/o unlocked bootloader with odin 3 unlock it then gain root and then update everything and then flash clock work.
Click to expand...
Click to collapse
I would like a backup image to odin if needed as well. How do I do this. I have a slight idea but i don't know the directories to pull?
i just disconnected my odin during dump im screwed at the mobile phone and computer! dunno how to get out
trying both volume rockers now. days downloading and flashing android box
just hold the power button for 10 seconds or just goto recovery mode and select reboot
that should get you back to honeycomb.
yea i got it with the power up then the recovery mode thx
How did you get adb to dump. i am running all sorts of commands and nothing works. some help would be greatly appreciated.
i was using odin3 to dump but it doesnt seem to be working correctly i think because its still locked. my next step is to flash the I/0 bootloader / system but im nervous now after it not correctly dumping (failure to write) it just creates a dummy file.
I am at work i will have to play with at home more. and have more resources
I am at an standstill as well. I don't know much more then what I have done thus far. I admittedly know nothing about Linux user privileges so I was never a help to begin with. The image below speaks for itself.
have you been able to flash anything with odin? i think if we can flash the stock i/o bootloader were set
Nope. Dont you think thats a little balzy without a retail dump to fall back on? Although, i could just exchange the device with best buy if something happens...
Sent from my GT-P7510 using XDA Premium App
haha why i havent done it yet. i cant see to get adb to recognize my tablet anymore i was making progress until now
is this method working ok to root a new retail SGT 10.1? thanks
i tried it and this what i got
"Failed to set prot mask (Inappropriate ioctl for device)"
any suggestions, thanks
neonflx said:
is this method working ok to root a new retail SGT 10.1? thanks
Click to expand...
Click to collapse
Nope. I am stuck. He is stuck. We are stuck.
any other methods to root a retail SGT, i took my XOOM back to Cotsco already
I cant seem to find anything about the sgs 1 and changing its mac adress (permanently/temporarily) ?
Can someone help pleaseeee!!!
Thanks in advance
I dont think we can change the mac address.
can't you spoof it?
I havent heard of this in android yet.
Sent from my GT-I9000 using Tapatalk 2
Mac address is a permanent address hard coded into the phone's hardware, or any wireless device's hardware for that matter.. Each wireless device in the world has its own unique mac address, just as each computer's bios has its own unique code..
You cannot change your device's mac address..
Hi
REQUIREMENTS
1) ROOTED PHONE
2) BUSYBOX INSTALLED
3) Terminal App
OPEN UP TERMINAL AND WRITE
:su
:busybox iplink show eth0
(THIS WILL SHOW YOUR CURRENT MAC ADDRESS)
NOW TYPE IN
:busybox ifconfig eth0 hw ether 00:11:22:33:44:55
(INSTEAD OF 00:11:22:33:44:55, YOU CAN WRITE YOUR WANTED ADDRESS)
Code:
http://forum.xda-developers.com/showthread.php?t=1385577
hardrockk said:
Hi
REQUIREMENTS
1) ROOTED PHONE
2) BUSYBOX INSTALLED
3) Terminal App
OPEN UP TERMINAL AND WRITE
:su
:busybox iplink show eth0
(THIS WILL SHOW YOUR CURRENT MAC ADDRESS)
NOW TYPE IN
:busybox ifconfig eth0 hw ether 00:11:22:33:44:55
(INSTEAD OF 00:11:22:33:44:55, YOU CAN WRITE YOUR WANTED ADDRESS)
Code:
http://forum.xda-developers.com/showthread.php?t=1385577
Click to expand...
Click to collapse
I started to grant SuperUser rights to my terminal app . After this, i started with the command "busybox iplink show eth0" and received the following error message:
iplink: can't find device "eth0"
Additionally tried the other command (with eth0) and there is the following error message:
ifconfig: SIOCSIFHWADD: No such device
Im using a Samsung I9000 with root access and all root-related apps already have root access all in all.
Even when Im typing ":su" or ":busybox ~", the device means:
sh: :busybox: not found
I don't get it, the terminal can work without these colons but the "eth0" could not be found, too
Any hints/tipps? Would be great, thank you
Wlan0 not eth0 no Ethernet on galaxy s
Sent from my GT-I9000 using xda premium
At first, thanks for the fast reply and I think your right..
..but at least, I already tried "Wlan0"
It seems, that the command (including wlan0) could be executed and I'm also able to display the wlan0 settings by typing: busybox iplink show
All related content is displayed including the "wlan0". The recently added mac-adress is successfully taken at this point (xx:xx:xx~ instead of the original one) and could be displayed there but even when im checking for the MAC adress in my android wlan settings, there is still the old one and my smartphone still connects with the old MAC to my gateway
I'm not sure then sorry will have to see if anyone else knows how
Sent from my GT-I9000 using xda premium
error eth0
eth0 not found in terminal what i should to do ? how to fix this error and ip link not found i know xda devloper in work fine but they have not solution for this...........
flexoduss said:
I cant seem to find anything about the sgs 1 and changing its mac adress (permanently/temporarily) ?
Can someone help pleaseeee!!!
Thanks in advance
Click to expand...
Click to collapse
1. A rooted device
2. Busybox installed </system/xbin>
3. Terminal Emulator
open terminal
type 'su' press Enter
grant super user access
then type 'busybox iplink show wlan0' press Enter
this shows ur current mac address of ur android phone
then type 'busybox ifconfig wlan0 hw ether XX:XX:XX:XX:XX:XX' press Enter
type the desired mac in XX:XX:XX:XX:XX:XX
voila Done!!!