Related
I just loaded my AT&T version with cyanogen 5.0.5.3, and the wireless tether app does not work.
No matter the security settings I use, it always shows unsecure network on my laptop (OSX, Ubuntu and Vista).. If I set it to unsecure in the app, it still does not connect.
I have never used it before, but I am assuming the cyanogenmod kernel has the required bits for the app to work properly.
Am I missing something stupid?
Thanks
-G
ghost_o said:
I just loaded my AT&T version with cyanogen 5.0.5.3, and the wireless tether app does not work.
No matter the security settings I use, it always shows unsecure network on my laptop (OSX, Ubuntu and Vista).. If I set it to unsecure in the app, it still does not connect.
I have never used it before, but I am assuming the cyanogenmod kernel has the required bits for the app to work properly.
Am I missing something stupid?
Thanks
-G
Click to expand...
Click to collapse
Did you turn off USB tethering?
hotweiss said:
Did you turn off USB tethering?
Click to expand...
Click to collapse
Never turned it on, and verified it is off...
how did you load the apk?
lpasq said:
how did you load the apk?
Click to expand...
Click to collapse
Downloaded to SD, and installed from browser download screen...
ghost_o said:
Downloaded to SD, and installed from browser download screen...
Click to expand...
Click to collapse
you may want to adb push method or adb install -r method instead. reboot after install. or try my rom linked in signature.
if you don't know how to use sdk's adb, do a search here on xda for one of the many basic tutorials or ask for details.
lpasq said:
you may want to adb push method or adb install -r method instead. reboot after install. or try my rom linked in signature.
if you don't know how to use sdk's adb, do a search here on xda for one of the many basic tutorials or ask for details.
Click to expand...
Click to collapse
Will do adb.. I have the linux sdk..
Thanks, will post back with results..
OK, installing with adb has the same effect.
There are posts from the google code pages where this has happened in the past (last year though), so I doubt related..
Out of ideas...!
eth0 IEEE 802.11-DS ESSID:"AndroidTether" Nickname:""
Mode:Ad-Hoc Frequency:2.437 GHz Cell: 3A:4E:3D:88:EC:41
Bit Rate=72 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementmode:All packets received
Link Quality=5/5 Signal level=-57 dBm Noise level=-57 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with WEP set.. It must have something to do with wpa_supplicant somewhere.. I'll keep digging...
maybe it might have something to do with atnt not able to do it throught there network. like us tmobile users can use data while on the phone? dont know alot but that could be a possibility
Nah, wpa_supplicant is not negotiating wep for some reason. I just replace the wpa_supplicant.conf file with a very generic open key WEP config and it still does not work..
I need to dig through my broadcom nda's and find this chip, and see if I can use the firmware.. I'll just load it up in AP mode and run hostapd and be done with it....
Ad-Hoc just plain sucks, almost as much as wep...
Cant find find wireless apk anywhere can someone please give me link
ttieder said:
Cant find find wireless apk anywhere can someone please give me link
Click to expand...
Click to collapse
http://lmgtfy.com/?q=android-wifi-tether&l=1
deprecate said:
http://lmgtfy.com/?q=android-wifi-tether&l=1
Click to expand...
Click to collapse
lmgtfy.com - that was awesome - my family members are gonna feel like idiots asking me questions now!
I had not heard of that site before.
Regarding wep-encryption & CM 5.0.5.x:
http://code.google.com/p/android-wifi-tether/issues/detail?id=292
So, wep-encryption is broken (no idea why) on the latest cyanogenmod-build. Please use CM 5.0.4.1 - it works flawlessly there.
I will take a closer look the next days ... but it's hard to tell what is causing this - I don't know which changes were made on CM.
By the way ... why was this topic moved to Q&A
This is definitely an issue which needs to be solved and should stay in development!
Thanks - I googled for quite a while, and never came across that info. Tethering is not that critical (unless I am travelling), so I will just wait for a fix sometime.
I would have figured other in this forum would have hit it though?!?!?
-G
I've installed 5.0.5.3 and downgraded the kernel which came with 5.0.4.1 - and it start working again! So, I would say that this issue is related to the latest kernel (2.6.33.1)!
I've created an issue on cyanogemod:
http://code.google.com/p/cyanogenmod/issues/detail?id=1217
i have wifi tether pre 8 on latest CM mod and its working great, wep works, and no errors in log.
I am having the same problem. I have both a nexus one and motor milestone. Tethering on milestone doesn't have problems but my nexus can't seem to connect as well no Sep security. I can see the my SSID, anyone can help?
There are obviously factors that differ between devices somehow. I too can change kernels and the issue goes away. Something is "missing" somewhere. A git pulled vanilla 2.6.33 kernel works just fine when booting the zimage from fastboot..
I have not looked at the cyanogen .config or wireless module source yet to see any modifications that would effect it...
I'm more interested in the module working in AP mode now that the driver supports it, and have been working on that...
-G
Latest and stable Wifi Driver for Android 2.1, Build SHOLS_U2_02.36.0
Build for the kernel "2.6.29-omap1"
** Stable and without any Wifi drop problem, which is compiled from the latest source from Google Android Repository. **
I recently found out that the Wifi driver of the latest Froyo 2.2.1 of Milestone that released by G.O.T. team is a new build and very stable. Therefore, I tried to pull the latest TIWLAN Wifi driver source code from the Google Android Source Repository (http://android.git.kernel.org/?p=platform/hardware/ti/wlan.git;a=summary), and compile it for the ROM build "SHOLS_U2_02.36.0", kernel "2.6.29-omap1".
I succeeded to compile as "tiwlan_drv.ko", and use it with the latest firmware "fw_wlan1271.bin" from the Froyo 2.2.1 build, and finally uses on the "SHOLS_U2_02.36.0", and the result is very stable wifi connection with the proprietary power saving feature .
I am using the ROM South Asia SHOLS_U2_02.36.0, I am not sure if it can be used with any other ROM, but normally should work on any kernel which have the version "2.6.29-omap1".
I did it because that the latest Froyo 2.2.1 beta ROM is not stable enough and the battery drain fast, but it have the stable wifi connection, so I compiled it for 2.1.
Enhancement:
Much more stable WIFI connection, no more connection drop within good signal environment.
No more WIFI freeze occur, will auto re-connect to AP if back to the signaled environment.
Much much much more battery saving (IT IS THE MOST IMPORTANT), can also feel that impressively in using "android-wireless-tether".
!!! Use it at YOUR OWN RISK !!!
Make a backup of "/system/lib/modules/tiwlan_drv.ko" and "/system/etc/wifi/fw_wl1271.bin".
Copy the file "tiwlan_drv.ko" to "/system/lib/modules/", and copy the file "fw_wl1271.bin" to "/system/etc/wifi/".
** WARNING **
Normally should work on any ROM which have the kernel version "2.6.29-omap1", BUT I didn't test it for any ROM other than SHOLS_U2.02.36.0, so USE IT AT YOUR OWN RISK!!!
It may result in bootloop in case if you did something wrong or not compatible with your ROM (need to revert back to the old driver with OpenRecovery + adb).
Therefore, it is only for advanced users, and ALWAYS MAKE FULL BACKUP of your milestone.
Download link:
http://www.sendspace.com/file/ln3xm7
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[EDIT]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
[EDIT2]Woo! Works!
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[Edit]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
Click to expand...
Click to collapse
"fw_tiwlan_ap.bin" is the firmware required for the Froyo 2.2.1 to use Wifi Hotspot, it did nothing on Android 2.1, so just simply ignore it.
and Thanks for pointing out the location of placing the "fw_wlan1271.bin" file, I will modify it.
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb
[EDIT2]Woo! Works!
Click to expand...
Click to collapse
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
How can I copy and paste to the system?
Thanks!
royshum said:
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
Click to expand...
Click to collapse
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
How can I copy and paste to the system?
Thanks!
Click to expand...
Click to collapse
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Lollipop_Lawlipop said:
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Click to expand...
Click to collapse
failed to copy - read only!
chungtau said:
failed to copy - read only!
Click to expand...
Click to collapse
You must have a rooted milestone in order to process.
Before you using adb push, try to remount your /system partition first.
Or you can try the following commands.
Ensure your wifi is turned off first.
*** Remember to make FULL BACKUP for your milestone before proceeding the following commands. ***
Code:
C:\android-sdk-windows\tools>adb push tiwlan_drv.ko /sdcard/tiwlan_drv.ko
C:\android-sdk-windows\tools>adb push fw_wl1271.bin /sdcard/fw_wl1271.bin
C:\android-sdk-windows\tools>adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
# cd /system/lib/modules
# mv tiwlan_drv.ko tiwlan_drv.ko.bak
# cp /sdcard/tiwlan_drv.ko ./tiwlan_drv.ko
# chmod 644 tiwlan_drv.ko
# cd /system/etc/wifi
# mv fw_wl1271.bin fw_wl1271.bin.bak
# cp /sdcard/fw_wl1271.bin ./fw_wl1271.bin
# chmod 644 fw_wl1271.bin
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
And now, you can try turning on your wifi.
In case if there is any problem occurred, you may reboot into OpenRecovery, revert the drivers from "tiwlan_drv.ko.bak" and "fw_wl1271.bin.bak".
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Lollipop_Lawlipop said:
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
Click to expand...
Click to collapse
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network .
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
You haven't read the instructions carefully. It is the latest wifi driver for "2.1", not "2.2.1", as it is supposed to compile the driver from "2.2.1" down to "2.1".
So for 2.2.1, by default, you are already have the latest wifi driver (at least a stable wifi driver), it is no clue for using it.
royshum said:
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network :
Click to expand...
Click to collapse
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Btw, CM6 uses the file name fw_wlan1271.bin. I'm guessing stock Android from Moto looks for fw_wl1271.bin (just guessing... can't exactly prove it since I'm not running stock Android), which was why I was trying to correct you (although it seems to me both of us are right).
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
If you're running 2.2.1-CM6 you can extract the files from the update zip and adb push them into the phone. That is, if you're on CM6. If not, well... you can either upgrade to CM6 or go into fastboot and restore the sbf again.
Lollipop_Lawlipop said:
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Click to expand...
Click to collapse
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
MenoDev said:
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Click to expand...
Click to collapse
Yes, I have the same suspicion as well.
MenoDev said:
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
Click to expand...
Click to collapse
Can you go into a bit of detail on that? I'm interested
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
works flawless, extreme improvement, thank you very much!
Lollipop_Lawlipop said:
Yes, I have the same suspicion as well.
Can you go into a bit of detail on that? I'm interested
Well, I use to code similar stuff but I am complete new to android so i have to read the dev guide, if I had no guide I'd probably create a dump, see according the file descriptor where the tables and storage are are located, then set a "write" flag on the file system and flush it to avoid a manual battery pull. but i'm sure there's more elegant ways.
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
Click to expand...
Click to collapse
I made a little research and found a working solution, tested it myself.
Apparently it can happen that the resolved DNS can not be stored under certain circumstances, (in order to trace those, i try to avoid the "out of the box" mods, even though the guys make a tremendous job, but i feel more secure and have a higher learning curve by doing stuff myself).
In order to avoid random disconnects from network or wifi, or worst case both, add the following lines of code to /system/default.prop
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
These are the google dns, most probably the best choice. You can find this out if you fire up the "getprop" command.
I've seen that most Recovery tools such as the G.O.T one, have implemented the DNS fix, but personally I prefer to just fire up a terminal from the phone and add these lines manually with some comment, so i know what and why I'm doing stuff.
Hope this helps, let me know.
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it didn'tsolve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
b787 said:
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it solve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
Click to expand...
Click to collapse
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
MenoDev said:
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
Click to expand...
Click to collapse
I did turn off wifi before copying any files. However, I didn't rebooted before I tried to start wifi, only after I noticed it doesn't work.
Fix for 2.2.1 Possible?
I have the same issue with my home WIFI network on 2.1 and 2.2.1: namely the connection drops during large transfers (such as a Market app download) and I have to turn WIFI off and on again to have connectivity again.
I wonder if 2.2.1 really has the latest firmware baked in...how would I compile the TI firmware for 2.2.1?
***MOD EDIT***
THIS ROM ONLY WORKS ON 4.1.26. Please consider another ROM unless you know what you are doing.
History & IntroThe first version was done with 3 different batch files, it ended up being very hacky and even ended up bricking one phone because the cleanup script didn't properly work.
I have rebuilt it from the ground up as a shell script. The initial temp root and file push is done with a batch file, it then fires off the install script on the phone which reports back to the batch with helpful info about what it is doing and what to expect from the phone as it goes. You no longer have to accept any superuser requests either.
The new script has been used on tons of phones now, everything executed exactly as I expected it to. I really didn't want to post this until we had a stock firmware to restore to, after the first release I have been worried about you guys bricking your devices, but what the hell, here it is anyways.
Come chat with us!FeaturesWorks for rooted and non-rooted devices
Deodexed
Reboot Option
Reboot to Recovery option
Ad Blocking
Removed power options headerChangelogAdeo v0.2: (3/9/2011)
Added Unknown Sources checkbox
Added Preferred install location (internal, sdcard, let system decide)Adeo v0.1: (2/28/2011)
Reboot to Recovery option
Ad Blocking
Only remove app/framework Dalvik-Cache (fixes /data app issues)
Removed power options headerFour simple rulesDo NOT do a factory reset if something goes wrong(soft brick), you will lose adb access and have a pretty brick
Do NOT do this if you are not familiar with ADB, if you softbrick you need to use adb to fix it
DO NOT PULL THE BATTERY, EVER WHILE INSTALLING
BE PATIENTHow to Install
Read the four rules above
Read the four rules above, again
Read the four rules above, again, one more time to make sure you've got it
Download the installer (AdeoInstallerv0.1.7z, AdeoUpdaterv0.2.7z)
Hook up your phone via usb with ADB enabled
run INSTALL.bat from the unzipped files
sit back, relax, wait until it reboots (can take upto 5min, be patient!!)
Read the disclaimer below
Enjoy!
DisclaimerIf you brick your device, I cannot be held responsible. Simply restore with the stock SBF to get you phone working again.Video Walkthru
Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks
A custom ROM?
I'm going to have to buy an Atrix!
EDIT: Bought it!
EDIT2: And Adeo'd it. All UI lag is gone! This is awesome!
I am running this in my Atrix now - I believe my phone was the 4th phone to have this install perfectly on with no issues. Designgears, you are the man, once again! Thank you for this!
PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...
Installed on mine, worked flawlessly. Thanks!
connexion2005 said:
PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...
Click to expand...
Click to collapse
Haha, I understand your PM now... you got my file before I posted this.
psufan5 said:
Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks
Click to expand...
Click to collapse
the factory reset is only if you brick.
There is no easy way to get back to stock, I will make a thing just like this installer to do that, actually its done, testing it
designgears said:
Haha, I understand your PM now... you got my file before I posted this.
the factory reset is only if you brick.
Click to expand...
Click to collapse
So if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because Im still debating if I want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but I also need to test out custom mods before my decision.
Thanks man.
I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!
psufan5 said:
so if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because im still debating if i want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but i also need to test out custom mods before my decision.
Thanks man.
Click to expand...
Click to collapse
no no no, do not factory reset if it bricks!!! Read the op!!!!
shawnbuck said:
I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!
Click to expand...
Click to collapse
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk
I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.
psufan5 said:
I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.
Click to expand...
Click to collapse
I designed this script to handle payloads, just need to package up one with a new payload with stock files and upload it.
Installed... Removed Laggyness i was getting with blur UI.
as to refering to the blur UI....
this is my second Atrix.. had to bring my first one back because when i was on tier 3 support the other night they fried the sim card reader with an update which was killing data signal to my phone... that phone had no laggyness whats so ever at all. I got this one today out of the box was having laggyness and slow response to key presses.. this fixed that as of so far.
designgears said:
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk
Click to expand...
Click to collapse
Nice, I will give this shot. Although I am already running DeOdexed already but I figured may be you got it running better than mine
I am also going to start editing small things like animations. No sense oh having all this power without some eye candy
Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
uskr said:
Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!
Click to expand...
Click to collapse
Not sure, I didn't get an errors like that.
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Try a usb port on the back of your PC
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Download ADB Wireless from the Market. It'll help solve that one for you.
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Install the Android SDK
install the MOTO drivers it will also install the moto adb drivers with it.
Install the ADB function drivers into the SDK/tools folder
run...cd to the sdk/tools folder... run... adb devices
should show the device is up which means ADB is enabled
Hi guys
Well, I had an Atrix for a few days, but had some issues with AT&T and had to return it and deal with some customer service issues before I can re-purchase the device. I didn't let that slow me down though
While I had it, I made a few dumps of the NAND, and have been working on disassembling things. Thanks to the help from a number of great people on IRC (#xda-devs irc.freenode.net) I have been able to successfully change the Bluetooth and Wi-Fi MAC addresses, and discovered a way to write to the flash, bypassing the bootloader security.
The full writeup can be found at pocketnow.com
I will be posting more info about the bootloader bypass as soon as I get it 100% working, right now we are able to write data directly to the NAND, bypassing bootloader security, and also provide a false signature, allowing the device to boot. However there are some remaining issues (a custom kernel that was flashed to the device failed to boot properly) - stay tuned
You the man, thanks for the efforts !
Sweeeet!
Wonderful work!
Excellent, can't wait to see the end result. Hopefully custom kernels and ROMs will be coming soon.
Devs you guys are amazing! Thank you for the hard work that is put into all this! I know the challange is fun for you all, but it really helps us non dev ppl out a lot!
Sent from my MB860 using XDA App
nicely done Da-G.... great work as always glad to see you again and i hope to continue using your work as i did back in old winmo cooking !!!
quick question, is there really a reason why to change the bluetooth/wifi MAC drivers??? are there any benefits or basically just the same exact reasons when you do it on pc's
Main reason to change MAC address is to be able to join Wi-Fi networks that have whitelisting.
You could also use it to simplify device administration on your network.
Beyond that I can also imagine a few black-hat reasons to do it
Atrix is one of the few smartphones that can pull it off easily though, others I am aware of are the LG Optimus One and the SGS series (although it's not so easy on SGS)
There are plenty of other interesting datas in /pds, it is the device provisioning partition (NVRAM) and is equivalent to /efs on the i9000/Captivate (which is the last device I used, so easy for me to compare with)
Careful messing with it though, on the Captivate changing the wrong bit would kill your cellular radio until you restored an EFS backup, I suspect the same danger is here with the Atrix too! And we don't have a quick way to restore a PDS backup yet like with odin on SGS (although I am hot on the heels of a method to do so)
Omfg I'm excited! If this device gets real ROMs an even custom kernels, its going to be an even more amazing device
Sent from my MB860 using XDA Premium App
i'm exited about the bootloader bypass, i thought the firmware would do a complete checksum of it, so if it's partial then we should be able to find out exactly what gets checked.
i'm curious to see if you have been able to find something regarding sim unlock, just like the sgs was holding the lock very easily changeable with a simple hex editor. i bought the code already but maybe other people will get lucky
I've asked for a backup of /pds prior to and after locking over in the general forum, hopefully a few people can send those my way. I suspect a good hard look at that will reveal the location and provide an easy unlock method (I think I located it already, but as /pds is not restored via flashing the leaked SBF, i'm loathe to have someone else try it in fear of brickage)
I'll hammer it out once I get my device back in hand, whenever AT&T decides to allow me to purcahse
Da_G said:
I've asked for a backup of /pds prior and after locking over in the general forum, hopefully a few people can send those my way. I suspect a good hard look at that will reveal the location and provide an easy unlock method (I think I located it already, but as /pds is not restored via flashing the leaked SBF, i'm loathe to have someone else try it in fear of brickage)
I'll hammer it out once I get my device back in hand, whenever AT&T decides to allow me to purcahse
Click to expand...
Click to collapse
i will do it, but i am getting a permission denied.
Code:
C:\Users\fjleon\Desktop\android-sdk-windows\platform-tools>adb shell tar zcvpf /
sdcard-ext/pds-backup.tar.gz /pds/
tar: can't open '/sdcard-ext/pds-backup.tar.gz': Permission denied
i tried adb shell su and accepted super user on the phone, but i still cannot do it
wow bypass= custom roms...... this would be ingenious hope u get it working....
how does rsd lite 5 flashing work??? it seems to create an image and then re sign it.... would backtracking and try to use the same method work?
@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
@ahjdmarchi:
I didn't study the program too much yet. I'll look to that if the current method i'm working on proves to be a failure
Da_G said:
@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
@ahjdmarchi:
I didn't study the program too much yet. I'll look to that if the current method i'm working on proves to be a failure
Click to expand...
Click to collapse
heres a tattoo that i have on my chest
"failure is not an option" good luck brudda hope all turns well
Da_G said:
@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
Click to expand...
Click to collapse
i unmounted it and tried again and still get the same error. i killed root explorer first since i had it open and no dice
@franciscojavierleon:
Try this instead.
Code:
adb shell tar zcvpf /data/local/tmp/pds-backup.tar.gz /pds/
adb pull /data/local/tmp/pds-backup.tar.gz
adb shell rm /data/local/tmp/pds-backup.tar.gz
RadioComm
You really need to take a look at RadioComm if you haven't yet.
The BT MAC address can be edited directly in the NVM on all Motorola devices.
On CDMA chipset devices it is located in seem 01bf record 0001 bytes 0006 and there is also a module and special set of TCI commands for managing this called HOB restore.
There are also flags set in the firmware for whether the HOB is verified during the flash cycle or not.
just an FYI!
@cellzealot:
Checked out RadioComm already, but none of the commands work for Atrix. Have you tried it? Perhaps you have a more updated version?
Edited. Nevermind just saw you needed it before unlock as well. I've got my PDS folder from my unlocked phone if you need it (not sure)
i should get my unlock between today and tomorrow, so with my locked pds backup i will do a diff to see if anything gets changed at all.
Does anybody succeded in booting a functional chroot ubuntu or debian on this beautifull smartphone?
.. i'm kinda stuck at top of it, can't load at all the image
Please post here your discoverings/progress/scripts
hi , i try to install debian from the linux installer app but the installation stop at fetching distro. I really need it because need hamachi to work.
if you can post a prepared image for mounting in a loop??
i search it....
imayoda81 said:
Does anybody succeded in booting a functional chroot ubuntu or debian on this beautifull smartphone?
.. i'm kinda stuck at top of it, can't load at all the image
Please post here your discoverings/progress/scripts
Click to expand...
Click to collapse
chroot does work but sadly i could only get it working through adb shell and even that by manually typing every command.Tried to create a script for it but sadly that does not work.could not understand why that is as manually typing those commands in adb worked.
Anyway been a long time since i tried that.Will re-try in a day or two once i fix my computer
I guess that's something wrong with kernels.. does anybody compiled one with loop ? mine seems not containing it..
plus scripts act very strange, confirmed..
any more people trying this?
imayoda81 said:
I guess that's something wrong with kernels.. does anybody compiled one with loop ? mine seems not containing it..
plus scripts act very strange, confirmed..
any more people trying this?
Click to expand...
Click to collapse
Nothing wrong with the kernel.Which one do you use?I use the Stock Rom.It has support for looping.I can give u a screen shot of the adb running ubuntu(on the command line ofcourse).Will start with the scripts again in a day or two.Interested?
mickeul said:
why don't you try to install archlinux, because you can install it with the chroot installation on the desktop ?
Click to expand...
Click to collapse
I doubt it will work on the Optimus.Will try your suggestion also soon.
edit:got debian to boot from terminal emulator.The only thing remaining are the scripts.
manasgirdhar said:
I doubt it will work on the Optimus.Will try your suggestion also soon.
edit:got debian to boot from terminal emulator.The only thing remaining are the scripts.
Click to expand...
Click to collapse
Can you please upload some material? also we may try Gscript for booting.. what's wrong with scripts ? I can't immagine where's the probelm.. sh problem? maybe better bash?
imayoda81 said:
Can you please upload some material? also we may try Gscript for booting.. what's wrong with scripts ? I can't immagine where's the probelm.. sh problem? maybe better bash?
Click to expand...
Click to collapse
Yaa Sure.i will upload the stuff in a day or two.See the Problem is creating loop using scripts.When i give the following indiviual command:-
mknod /dev/loop99 b 7 0
then it works but when i give the same command using a script(.sh) it gives an error 'knod:invalid number'.Till the loop is created we wont be able to mount the device.at the moment i am trying a few alternate commands.If it can work i will post the complete work.If not then i will post the image file and the temp scripts.
Its damn hard getting it to work.If it works then i will also work on debain and BackTrack 5 and other arm linux's.Lets hope for the best.
manasgirdhar said:
Yaa Sure.i will upload the stuff in a day or two.See the Problem is creating loop using scripts.When i give the following indiviual command:-
mknod /dev/loop99 b 7 0
then it works but when i give the same command using a script(.sh) it gives an error 'knod:invalid number'.Till the loop is created we wont be able to mount the device.at the moment i am trying a few alternate commands.If it can work i will post the complete work.If not then i will post the image file and the temp scripts.
Its damn hard getting it to work.If it works then i will also work on debain and BackTrack 5 and other arm linux's.Lets hope for the best.
Click to expand...
Click to collapse
we should contact some kernel developer just to understand if loop is compiled in actual kernels.. I use B17 modaco but thing act crazy when i issue a mount command.. best wishes for ur work
imayoda81 said:
we should contact some kernel developer just to understand if loop is compiled in actual kernels.. I use B17 modaco but thing act crazy when i issue a mount command.. best wishes for ur work
Click to expand...
Click to collapse
No need to bug the dev's for such a small thing.Loops are supported in the original LG Kernel.Like i said i can mount it by typing all the commands manually but the problem occours when i use a script to do the process automatically.
If loops were not compiled i doubt i could get it to mount even by manual commands.
What craziness happens with you when you issue a mount command?
Maybe i could advise you on that?
EDIT:I think i finally found the problem with the script.Not Sure.will do some further testing and get back to you.
Hello !
If that can help, got Ubuntu running on mine, using this : http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-android/
I'm using the CM7-RC1. The files should be placed in /sdcard/ubuntu/ <-- check your /sdcard symlink ! With CM7, it's fine. But stock got a weird behaviour.
anyvie said:
Hello !
If that can help, got Ubuntu running on mine, using this : http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-android/
I'm using the CM7-RC1. The files should be placed in /sdcard/ubuntu/ <-- check your /sdcard symlink ! With CM7, it's fine. But stock got a weird behaviour.
Click to expand...
Click to collapse
even i just moved to cm7 RC-1.Gonna check my scripts now.
i got my hands on Maemo in a chroot envoirnment.atleast thats what was said on the file.i still have not tested it.Anyone interested in the img?
Edit:Got the Boot script to work for debian Finally.Now creating the prep script.once done will check on the official kernel and then post Debian atleast.Right now checking on cm7.
manasgirdhar said:
i got my hands on Maemo in a chroot envoirnment.atleast thats what was said on the file.i still have not tested it.Anyone interested in the img?
Edit:Got the Boot script to work for debian Finally.Now creating the prep script.once done will check on the official kernel and then post Debian atleast.Right now checking on cm7.
Click to expand...
Click to collapse
CM7 RC1 is a good base to start from.. even too good
however I get variable results launching mount commands in FR17 even from adb... sometimes it crashes the shell after a ioctl error..
i'm giving up on stock based roms.. there something wrong with busybox commands in them..
are u working chroot on top of CM7 RC1 ?
This thread should be moved to dev, am i wrong or maemo is on works here?
Sent from my Optimus 2X using XDA App
imayoda81 said:
CM7 RC1 is a good base to start from.. even too good
however I get variable results launching mount commands in FR17 even from adb... sometimes it crashes the shell after a ioctl error..
i'm giving up on stock based roms.. there something wrong with busybox commands in them..
are u working chroot on top of CM7 RC1 ?
Click to expand...
Click to collapse
No Mate.Nothing wrong.I got it to work on FR17 as well as cm7.the only problem is that i have been unable to download tightvnc and lxde on the Debian chroot envoirnment.Some prob with my net connection.Keeps disconnecting.anyway.I have to make the read me file with instructions and then i will zip it and upload it.any special request for the file host?
svceon said:
This thread should be moved to dev, am i wrong or maemo is on works here?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
no point in moving to dev.i am trying to chroot into Maemo.Not Native booting.altough i will give the native boot a go in August because my exams begin soon.
imayoda81 said:
i'm giving up on stock based roms.. there something wrong with busybox commands in them..
are u working chroot on top of CM7 RC1 ?
Click to expand...
Click to collapse
You mean, use debian as a primary OS, like launching it when the phone start ?
In case of yes, debian would be started when Android start, or you want to avoid Android ?
manasgirdhar said:
No Mate.Nothing wrong.I got it to work on FR17 as well as cm7.the only problem is that i have been unable to download tightvnc and lxde on the Debian chroot envoirnment.Some prob with my net connection.Keeps disconnecting.anyway.I have to make the read me file with instructions and then i will zip it and upload it.any special request for the file host?
Click to expand...
Click to collapse
Did you try to change your DNS Servers ? You can use Google's on 8.8.4.4/8.8.8.8
Did you try to connect by other means ? 3G, WiFi ?
Finally, for personal use, which debian img did you use ? Your own-made ? I ask because I just DLed an ubuntu image that someone else did, based on the ARM-one. But I don't see any ARM specific image on debian's website (or I don't know the other name, which could be shown).