Please Help - G1 Q&A, Help & Troubleshooting

Ok i have an g1 thats unregistered and i kow how to activate it through wifi but i cant because i dont have an router i was wonder if someone could explain to me how to bypass this without activating my g1 it said or how i send these commands with adb
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
- If you don't want to register the phone at all, you can set the app.setupwizard.disable property to 0 to prevent registration. Once you have an adb shell session open, type the following:
setprop app.setupwizard.disable 1
and then reboot. once it loads back up, it should bypass the registration screen all-together
but i am so confused thanks for the help

Do you have root? Most custom ROMs give you an option to skip.

i was in the process of rooting my g1 when i had downgraded it but i couldnt finish it because i had to activate it when i got it it was already activated

charles20212 said:
i was in the process of rooting my g1 when i had downgraded it but i couldnt finish it because i had to activate it when i got it it was already activated
Click to expand...
Click to collapse
It's been so long since I rooted that I can't remember if there are any other options. I think when first I got mine, there was no way to root with wifi. I couldn't even register while roaming, and had to drive 40 miles (nearest T-Mo tower) just to use my G1 for the first time. That sucked!

is there a way to bypass it without using wifi or can i install a new rom or something

If you are rooted, then try a new rom. Most of them will have the option to skip.

how i know if im rooted

Related

ABSOLUTELY cannot root this G1!

The G1 is a loan from a friend, they want me to help fix it.
I get to the final part here in the list of rooting the G1:
10. The Final step is to type
"am start -a android.intent.action.MAIN -n com.android.settings/.Settings"
After I do that, in ADB all I get is this sign >. I get no settings menu popup in the phone at all. It stays at the no sim card / emergency calls only screen.
Fixing the phone for a friend - absolutely no way I can obtain a sim to get past this - no sim card at all. Its a fresh downgrade to RC29 to begin the root.
The reboot command works on the phone perfectly. ADB recognizes the device. Permission Denied in ADB when trying to SU.
I need to be able to bypass the activation AND the No Sim / Emergency calls only screen, thats my goal, to root, and install recovery and finally cyanogen.
Do have experience with ADB. Is definitely installed properly. Driveres are definitely in right.
havocxrush said:
The G1 is a loan from a friend, they want me to help fix it.
I get to the final part here in the list of rooting the G1:
10. The Final step is to type
"am start -a android.intent.action.MAIN -n com.android.settings/.Settings"
After I do that, in ADB all I get is this sign >. I get no settings menu popup in the phone at all. It stays at the no sim card / emergency calls only screen.
Fixing the phone for a friend - absolutely no way I can obtain a sim to get past this - no sim card at all. Its a fresh downgrade to RC29 to begin the root.
The reboot command works on the phone perfectly. ADB recognizes the device. Permission Denied in ADB when trying to SU.
I need to be able to bypass the activation AND the No Sim / Emergency calls only screen, thats my goal, to root, and install recovery and finally cyanogen.
Do have experience with ADB. Is definitely installed properly. Driveres are definitely in right.
Click to expand...
Click to collapse
I think there's a newer dreaimg.nbh file available that allows you to skip activation. Do that and install the 1-click-root app and be happy.
Nah I cant find it after tons of looking around. I just need to get that settings screen to pop up. But nothing........
havocxrush said:
The G1 is a loan from a friend, they want me to help fix it.
I get to the final part here in the list of rooting the G1:
10. The Final step is to type
"am start -a android.intent.action.MAIN -n com.android.settings/.Settings"
After I do that, in ADB all I get is this sign >. I get no settings menu popup in the phone at all. It stays at the no sim card / emergency calls only screen.
Fixing the phone for a friend - absolutely no way I can obtain a sim to get past this - no sim card at all. Its a fresh downgrade to RC29 to begin the root.
The reboot command works on the phone perfectly. ADB recognizes the device. Permission Denied in ADB when trying to SU.
I need to be able to bypass the activation AND the No Sim / Emergency calls only screen, thats my goal, to root, and install recovery and finally cyanogen.
Do have experience with ADB. Is definitely installed properly. Driveres are definitely in right.
Click to expand...
Click to collapse
go here it is the best place to root your g1 I use it for everything, it is da bomb
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
That requires adb to be enabled, which I believe it is NOT enabled on a tmobile firmware.
There was another sort of bug in the tmobile firmware... stuff you type might just be run in a console as root. I don't recall if it applies to where you're stuck, but it might... I think it is... try this:
Flip open the keyboard and type this: (don't worry that it doesn't show up on the screen)
<enter>sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"<enter>reboot<enter>
Where "<enter>" is actually pressing the enter button.
It should reboot at this point and hopefully it will come up to the REGISTRATION screen instead of the NOSIM screen.
Then type:
<enter>am start -a android.intent.action.MAIN -n com.android.settings/.Settings<enter>
(again, won't see anything, so just type very carefully...)
If all works as planned, this should pop up the settings program, you can go into network and activate WiFi, press the <back> button a few times to return to the REGISTRATION screen, then you should be able to register (if you want). Or, when you activate the wifi, you could just type in <enter>telnetd<enter> and log in through telnet, root, and be happy.
Note: I believe that you can enable adb using this command:
<enter>setprop persist.service.adb.enable 1<enter>
** if you do this, then you can do the other two commands I showed you over adb rather than blind.
chris6551 said:
go here it is the best place to root your g1 I use it for everything, it is da bomb
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
Click to expand...
Click to collapse
That isn't going to work for him since he doesn't have a simcard.
oh ok I didnt realize he did not have a sim card, my bad.
Without a SIM card, you're pretty SOL. It has to be in RC29 or RC7 firmware to be able to access the WiFi via that vulnerability, so you'd have to start there. I don't know how far you can get with SIM message, though.
Well, just search the development on this forum you can do anything even if you don't know how, and my last g1 i had to pass everything like you then root then unlock and done alll of that and now runing flawlesly. Don't be afraid of searching. And p.s. you don't need a sim card for anything after passing the login screen.
Ninjineer said:
Without a SIM card, you're pretty SOL. It has to be in RC29 or RC7 firmware to be able to access the WiFi via that vulnerability, so you'd have to start there. I don't know how far you can get with SIM message, though.
Click to expand...
Click to collapse
It is a really good idea to read through the entire thread before responding and making yourself look *really* foolish.

Need Root help

Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Have you installed a rooted rom? or just trying to see if you have root access on the stock rom?
Jeremy.Bentham said:
Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Click to expand...
Click to collapse
Try using the nexus-addon-0.1-signed.zip
http://forum.xda-developers.com/showthread.php?t=636795

Registering G1 Without Data

So I've been trying to register my G1 without the data plan, but it's not working. I have RC9 on it, but when I try to enable adb and get root access, it doesn't seem to work. I tried rebooting it with the command and it worked. I don't know what I'm doing wrong at this point. :l
its a 3 step process
1. downgrade to RC29 or below (i used DREAIMG.nbh)
2. enable ADB (even though you are seeing the GUI and CLI is still going on in the background
to reboot the phone you typed in <enter>reboot<enter> try typing this next one in (if u dont already have the android sdk u should download it)
<enter>setprop persist.service.adb.enable 1<enter> )
3. use adb to force open wifi setting menu
(adb shell)
(am start -a android.intent.action.MAIN -n com.android.settings/.Settings)
try this thread for more help, and next time pls use search button
theres countless threads on this
I got it to work now, thanks.

How do you change the root password after rooting?

After you root the Nook Color, how do you set or change the root password? Is it similar to how it is done in linux with the passwd command? What is the default root login and password?
thanks
I think you're confused on what rooting is. There is no root password.
tunwear said:
I think you're confused on what rooting is. There is no root password.
Click to expand...
Click to collapse
Actually, there is on Linux but I believe android lacks the feature. Just type su in terminal to get root access if you are rooted.
Sent from my SPH-D700 using XDA App
phfaty said:
After you root the Nook Color, how do you set or change the root password? Is it similar to how it is done in linux with the passwd command? What is the default root login and password?
thanks
Click to expand...
Click to collapse
This sounds like something you had to do after jailbreaking an iDevice maybe you're mixing them up
I think he's comming from the apple world where you have to change the ssh password from alpine to something else.
There is no password to change because there is no ssh or telnet service running in the background. Hense no one can access the device remotely. If you install a remote access server and run it as a service (deamon, running all the time) then yes you need a password for that service. Most of these services in android are apps and only run when you turn them on. The one I use asks you to create a password before it even runs. Wireless adb doesn't ask for a password but then you are only using it for a short time and I seriously doubt hackers would be scanning for open adb ports since it is such a small number of devices using it.
But...
Hello, I have a question about this: what about other apps can access system files by accessing with root priveleges to install software that collect our information ?
Thanks
MikiBroki said:
Hello, I have a question about this: what about other apps can access system files by accessing with root priveleges to install software that collect our information ?
Thanks
Click to expand...
Click to collapse
Only if you click 'allow' for that app.
I am looking for a SU binary that has password protection. Does it exist? Can someone compile that into the SU binary?
Just a simple text file like /data/system/passwd ?
If not set it will not ask (like now)
I you want to set it use /system/xbin/su --setpwd ***** where ***** is the password stored in /data/system/passwd (rw-rw---- root.root)
Only factory reset will clear it.
Then if password is set then /system/xbin/su will ask for a password in the shell.
Just my 2 cents.
Thx.
tweakradje said:
I am looking for a SU binary that has password protection. Does it exist? Can someone compile that into the SU binary?
Click to expand...
Click to collapse
I personally have one, actually, but I'm not about to publish it (I'm not confident enough in my setuid-program-writing skills to promise anyone else security, and the code I have actually requires compiling the password hash into the binary). That said, you don't actually want my personal su, because it breaks pretty much every root-using Android app out there by prompting for a password via standard input.
It's certainly possible to do this "correctly" -- you'd need to move the password prompt into the Android UI (the Superuser app or equivalent). That would further complicate code that's already far too busy for comfort, though (seriously, who links SQLite into a setuid root binary??!?).
Thanks for your feedback. Nice to know there is a need for this. I only want security when adb is on.
You can detect if su request is from the shell? Then only ask for password if request is from the shell.
Else SuperUser.apk is not compatible? Or devs like Chainfire needs to change that too.
Cheers
gedster314 said:
I think he's comming from the apple world where you have to change the ssh password from alpine to something else.
There is no password to change because there is no ssh or telnet service running in the background. Hense no one can access the device remotely. If you install a remote access server and run it as a service (deamon, running all the time) then yes you need a password for that service. Most of these services in android are apps and only run when you turn them on. The one I use asks you to create a password before it even runs. Wireless adb doesn't ask for a password but then you are only using it for a short time and I seriously doubt hackers would be scanning for open adb ports since it is such a small number of devices using it.
Click to expand...
Click to collapse
I just installed cm10.1 and saw their is built in ssh.... I configured it without authentication and allowed root login and its asking me for my android root password -.-
Using any ssh of the market works. But this thing comes with ssh.. Whats the password its asking for lol
leathan said:
I just installed cm10.1 and saw their is built in ssh.... I configured it without authentication and allowed root login and its asking me for my android root password -.-
Using any ssh of the market works. But this thing comes with ssh.. Whats the password its asking for lol
Click to expand...
Click to collapse
Type "su" and then after it asks for root type "passwd" in terminal emulator without the quotes. It will ask you to enter a new password as one has not yet been set up.
Changing root passwd android 2.3.3
tunwear said:
I think you're confused on what rooting is. There is no root password.
Click to expand...
Click to collapse
I beg to differ there is a way to do it however i found this on someone elese thread and figured id share.....i got as far as making a new user however i still can but cant change the root passwd.
mount -o remount,rw /dev/block/mtdblock3 /system
now type:
cd /system/bin
ls
Do you see su or your username listed?
If so type:
chmod 4755 (type su or your username here, without parantheses)
now open terminal emulator on your phone and try your superuser command again.
If you did not see su or your username in the output of ls type the following to get a setuid shell:
cat sh > (username or su whichever you want)
chmod 4755 (username or su whichever you want)
now open terminal emulator on your phone and try your superuser command again.
That should get you going.

"No Sim card."

The flex cable inside my g1 broke and so i replaced it. prior to this it worked perfectly. However, now it is not picking up any sim card whatsoever - i have factory reset it and it is locked ot t-mobile. I have tried a friends T-mobile sim and this did not work, i also tried a "giffgaff" sim, checking to see if it would detect it, still nothing.
I've been following this guide:
http://forum.xda-developers.com/showthread.php?t=452316
And cannot figure out how to get past:
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
How do i give busybox permissions :S?
Nevermind, got it. Used http://blog.vgod.tw/tutorial-activate-g1-via-wifi-without-a-sim-card/ as well to figure it out, this was posted deeper down in the thread posted before.

Categories

Resources