Related
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
EDIT: need help trying to get 3g to work again (solved kernel flashing c 3rd post)
Hi !
i am trying to flash the kernel from preshoot, i was able to flash the file in recovery however when i try to push the file using terminal i get an error... i am on a mac and heres what i am doing.
cd "/Applications/android-sdk-mac_86/tools"
./fastboot devices
i get a confirmation that a device is connected.
./adb mount
gives me a long list of what i can do
./adb push bcm4329.ko /system/lib/modules
gives me
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
what am i doing wrong here ... and also i sometimes seems to have no 3g after flashing nextheme and goodies onto cyn 5.0.6, my wifi is runnin fine.
any help would be appreciated.
thanks in advance
EDIT: SOLVED SEE THIRD POST
device needs to be booted up normally and be in debug mode for adb to work.
to verify that it works, do a "adb devices".
ok thanks ill try that ..
EDIT:
got the above to work :
did the following, if someone needs to know how to ( this is on a mac):
phone on, usb debuggin on:
cd "/Applications/android-sdk-mac_86/tools"
./adb devices to check if device is connected
./adb mount
./adb push bcm4329.ko /system/lib/modules gave error so
./adb remount
./adb push bcm4329.ko /system/lib/modules
and worked ... wifi is working with preshoot 1.13ghz kernel
Stil trying to figure out :
one other issue im having is that all of a sudden i have no 3g/H or any data services on my phone showing up(nexus one att version)... i thought maybe it was 5.0.6 so i reverted back to 5.0.5.3 but still have no data services, i know its not a provider issue as my iphone has 3g right now ... any ideas what this could be or how i can solve it ..
configuration is :
cyng 5.0.3
n1apps
nex2 theme
nex2 goodies
desre notification bar
desire camera ...
other configuration tried:
cyn 5.0.6
with and without n1apps.
tried both the new and 4.0.3.00.2.1_2 baseband ( downloaded from rom/kernel/baseband sticky)
current:
cyn 5.0.6
n1 apps
pershoot 1.13 kernel
baseband 4.0.3.00.2.1_2
EDIT: if i switch it to 2g network i get edge and it works, but once i switch it back the H shows for a while and the uplink arrow turns white but there is no downlink, and after a while the H icon just disappears and there is no edge either.
Since I applied the froyo update from Paul's site wifi was working fine for 36 hours.
After a crash caused by copying files on my sdcard I rebooted the phone several times to recover it (another story).
Then wifi stopped working, by "stopped working" I mean the driver won't even load, giving me a warning in logcat, some timeouts in dhd_module_init and "Error" in the control panel.
It has nothing to do with my router configuration because I cannot even enable the wifi to scan for some ssid so it's not a "false alarm" issue...
I tried to flash Stock rom and radio, flash superboot FRF50, the last cyanogen, wipe a few thousand times between all of this but nothing seems to give life back to my wifi chip... I tried flashing InsectRaven and cyanogen .34 kernels with no results...
I can't stop thinking it is hardware related but why ??!! There was no shock, no fall, no EMP from a nuke in the vicinity, everything was smooth when I got back from work and bam !
Is there some options to pass to the driver when I insmod to "reset" the chip in a healthy state ?
Can I somehow compile a debug build giving more informations on my hardware when it is crashing like **** ?
I don't know where to look anymore ... and I'd like some proof thats it is indeed fried...
Here are logs from various sources when I enable wifi in the settings (or insmod /system/lib/modules/bcm4239.ko)
From dmesg : http://pastebin.com/uaRM4EyK
From logcat :
Code:
E/WifiService( 83): Failed to load Wi-Fi driver.
From insmod /system/lib/modules/bcm4239.ko :
Code:
# insmod bcm4329.ko
insmod: init_module 'bcm4329.ko' failed (Invalid argument)
I2C errors in dmesg : http://pastebin.com/ehB7RtN7
Another question , has someone successfully compiled "strace" and "modinfo" to run on android ?
I guess it will be helpful to debug my issue.
Hi,
I'm having a similar issue, thought on another device. Did you find a fix for this?
Thx
Raph
Have this working well and thought this info may help others...
First, your phone needs to be rooted and busybox properly installed. If you've rooted in the past few days, you're fine as the current payload-update.zip does install busybox with all of the links, but if you rooted early please confirm this before continuing.
Next, grab the tun.ko module from the OpenVPN thread.
Then follow the instructions for the Motorola Droid at the VPN Connections site, using the tun.ko you downloaded previously. The one caveat here is that you have to copy the module in recovery on the Incredible as we don't yet have rw access to the /system partition when booted normally.
Once you've restarted your phone after installing tun.ko, just install the latest VPN Connections apk and you're ready to go!
One point that confused me (for longer than I care to admit) is that once you create a VPN profile, you have to long-press on it to bring up the menu for connect/disconnect.
Enjoy!
Dave
which vpn connections. I downloaded latest from the store it opened but did not work.
then tried the latest from the site and it forces close. I'll start over tonight and try again.
-------------------------------------
Sent via the XDA Tapatalk App
I was working on this the other day, but I cannot get the phone to connect to my company's VPN - I setup the IPSEC ID/PW correctly as well as my user IP/PW, but I get an ISAKMP_N_AUTHENTICATION_FAILED. The one thing I didn't do was copy tun.ko in recovery mode - I just did a modprove /sdcard/tun.ko...it didn't complain and it seems like VPN Connections can find the device node without a problem.
On my linux box, I can run the same config options in vpnc and connect no problem...
I got it working after a couple days playing with it. My problem was that I had not installed busybox to xbin like their instructions outlined since it was already installed to sbin. once installed to xbin and proper permissions were granted, it worked like a charm.
Please someone post a complete how to. I cannot get this working. Busybox will not "--install" to xbin
Is there a secrete to getting busybox installed? I know this is weak sauce, but I need help.
Did you try installing busybox while in recovery mode?
where do I install busybox? /system/xbin or sbin?
Kulaa said:
where do I install busybox? /system/xbin or sbin?
Click to expand...
Click to collapse
I've got it in both places. It needs to be in xbin for the vpnc-script. I tried modifying the vpnc-script but running in to too many problems.
Those to configured their ASA
I am trying to setup the ASA for this VPN. Numerous vague (to me) unresolved errors. Phase 1 completes (easy).
Phase 2 Failure: Mismatched attribute types for class Encapsulation Mode: Rcv'd: Tunnel Cfg'd" Transport
Group = <group>, Username = <username>, IP = <IP Address>, All IPSec SA proposals found unacceptable!
" " Duplicate Phase 2 packet detected. No last packet to retransmit.
I am not finding the answers to these issues. I have not been working on VPNs for long but have setup A LOT of client (Any Connect & SSL) VPNs. I tried to "match" those configurations and have failed.
Anyone know of a tut they used to set the VPN up on the Firewall side? Im sure one of these guys I work w/ can set it up in mins but learning the hard way is what "they" prefer. < a week later is enough, I concede!
Bump ~ 10 ~
Bump ~ 10 ~
Console output?
It think I followed all the necessary steps but wanted to confirm somehow. Is there any ways to see the log on what VPN Connect is trying to do and why login fails?
supagene said:
It think I followed all the necessary steps but wanted to confirm somehow. Is there any ways to see the log on what VPN Connect is trying to do and why login fails?
Click to expand...
Click to collapse
./vpnc --debug 3 --script <path to script> --gateway <gatewayip> --id <VPN Group ID> --username <username>
johnnybags said:
./vpnc --debug 3 --script <path to script> --gateway <gatewayip> --id <VPN Group ID> --username <username>
Click to expand...
Click to collapse
./vpnc --script ./vpnc-script --gateway gateway.domain.com --id "Default Initial G
roup" --username supagene
Enter IPSec secret for Default Initial [email protected]: *******
Enter password for [email protected]: *******
uname: not found
basename: not found
grep: not found
which: not found
grep: not found
which: not found
grep: not found
which: not found
[: not found
readlink: not found
[: not found
[: not found
hash comparison failed: (ISAKMP_N_AUTHENTICATION_FAILED)(24)
check group password!
I know about the comment to check the group password, but I copy and pasted it so I know it is correct. Any suggestions? Do I copy the busy box from sbin to xbin or do I need to look for another busybox, where do you recommend me getting it form? Sorry for the noob questions.
Ok So I looked and found that the Procudures I followed for Rooting didn't actually copy busybox to xbin so maybe the first post should be updated to mention to check that xbin actually has busybox. I used the same busybox that was included in the rooting guide.
Now I'm at a different error.
Error binding to source port. Try '--local-port 0'
Failed to bind to 0.0.0.0:500: Address already in use
that's fine, it means you probably have another process of vpnc running that didn't terminate. just ad --local-port 0 to the end of your command line.
So how is your ASA configured? Is it the latest software or 8.2? ???
Kulaa said:
So how is your ASA configured? Is it the latest software or 8.2? ???
Click to expand...
Click to collapse
Not sure. I just know that the Admin can connect with his Cyanogen Modded G1 and it works great for him. He has his NAND fully unlocked of coarse.
Thanks for all the help I'll post my next issue tomorrow.
Following this thread that was linked for helping to get this working on the Incredible.
I'm getting a constant "unable to connect" error... Where do I need to enable logging to find out more about where the error is happening at? On my ASA or on the Incredible?
Thanks.
I've never got it working but if you look above you'll see how I ran this thin in adb shell. That will output everything to console and tell you what is wrong.
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Just so others know, TWRP under the "Advanced" menu item has a "File Manager" which allows you to remove each of these files. That's important for those who can't get to a PC with a working adb to mount the shell. I used OTG external storage to access the OTA and Magisk zips for flashing and storage of my nandroid backup.
Personally I would need the File Manger as I have a fully functioning PC fastboot but for some reason can't see my OP5 using adb. Not a big deal but there is a user-friendly built right into TWRP which always has "root" privileges to "/data".
zdimension said:
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Click to expand...
Click to collapse
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Dchoi229 said:
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Click to expand...
Click to collapse
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
zdimension said:
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
Click to expand...
Click to collapse
Thanks for the response Z! I just tried it and my wifi isn't stable at all when trying to connect to wifi. It's my workplace wifi that I usually have to sign into to access. It'll connnect and disconnect constantly. Is there anything you'd advise me to do?
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
buzzfuzz1 said:
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
Click to expand...
Click to collapse
Nah, the command is supposed to be run when the phone is in TWRP.
First, you use adb shell to open a terminal from your PC (ignore this step if you want to use TWRP's integrated terminal directly on the phone).
Then, when you're in the shell, run the rm command.
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
buzzfuzz1 said:
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
Click to expand...
Click to collapse
The file the command deletes is basically the "Wi-Fi" settings file, which contain identification settings for the network card amongst other things. If you keep the Nougat one while you're on Oreo, you can't turn on Wi-Fi, or use anything related to the Wi-Fi antenna; Thus, we delete it. That solves the problem "Wi-Fi doesn't turn on". Here, you've got another problem: "Wi-Fi can't connect". I have no clue of what could be causing this, this issue never happened to me. I'm gonna search a bit and update here if I find anything.