Database Develop

Cyanogenmod 5.0.5.3 - Wireless_tether 2.0_pre8 (and older)

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

[FIXES] Milestone Latest WIFI Module for 02_36 kernel

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?

Rogers Dream Slow Mobile Data Need Your help

Hello i have a Rogers dream rooted. I used speedtest.net application here are my last 10 test result in kbps...
I have a clue can it be that is lsow my connection because it always roaming?
D/U
202/1553
5/1531
2/1605
24/1697
235/533
3/7
8/-0
561/1664
19/1806
Note:those numbers are not backward!
you get the picture the download speed is very very bad upload is good.
i tryed many differents roms and kernel mix.
here is my setup for those test above
radio: 3.22.26.17
spl: dangerspl
recovery: RA-dream-v1.7.0R
rom: MT3G-test2_S + MT3G-test2-market-fix_S
kernel: ez-BiffTest2Kern_ebi1_S
i dont know how can i fix my trouble i use this phone on telus network ans tested my sim in a telus htc desire and speed is fantastic!
if you have any idea to fix my trouble it would be very very appreciated since i need some internet for my work and if i cant fic it i need a new phone and its not a good option for me now!
thank for your help.

Look up ro.rill settings, the ota being a T-Mobile stock Tom is not optimized to other networks.
But you can from recovery modify your ro.ril settings to speed things up..
(Or copy the out of the desires build.prop)

thx for the info i will try the file from my firend desire he is on telus. i edited mine but im not sure if it worked yet!

pr0cess0r said:
thx for the info i will try the file from my firend desire he is on telus. i edited mine but im not sure if it worked yet!
Click to expand...
Click to collapse
You just want the ril settings, since the rest will impact the operation of the rom. Also not all settings will work so keep a backup.
Also in other threads it's noted it may take a few restarts for it to work.

Im not able to write to system i tryed some guide in terminal and one apllication from the marking but im notable to copy prop.buil to system.

Boot into recovery, atatch your USB wire and run the following adb comands from your computer:
To pull build.prop to your computer:
Code:
adb shell mount /system
adb pull /system/build.prop build.prop
Edit the file
Then to push back:
Code:
adb push build.prop /tmp/build.prop
adb shell dos2unix /tmp/build.prop
adb shell cat /tmp/build.prop /system/build.prop
adb shell sync
adb shell um
adb shell reboot

I finally managed to change the setting from 10 to 12 and its faster but not like the desire. i get 1000 kbps somes times and upload is still faster. Thx for the help whit this !! im still wondering if roaming can make the connection slower.

pr0cess0r said:
I finally managed to change the setting from 10 to 12 and its faster but not like the desire. i get 1000 kbps somes times and upload is still faster. Thx for the help whit this !! im still wondering if roaming can make the connection slower.
Click to expand...
Click to collapse
You have a telus sim on the telus network correct? [That combo is not roaming]
There are many factors in network speed. Personally for most things I use phone data for latency is more of a problem than speed.
One other note: if you are no longer with rogers you might try changing 3.22.26.17 -> 3.22.20.17 by fastboot. (not sure it will help speed but is know to solve some other gotchas without impacting the current rom)

do i need to flash a new recovery at the same time?

pr0cess0r said:
do i need to flash a new recovery at the same time?
Click to expand...
Click to collapse
No .. if you are just going between 3.22.* radios using fastboot to flash:
The current system (including recovery, boot, system, and userdata) ought to work without any modification..
In case of problems however: so long as you flash the radio via fastboot [AND NOT recovery] you can use fastboot to restore a -R recovery and wipe the rest of the system if something goes wrong.

ezterry said:
No .. if you are just going between 3.22.* radios using fastboot to flash:
The current system (including recovery, boot, system, and userdata) ought to work without any modification..
In case of problems however: so long as you flash the radio via fastboot [AND NOT recovery] you can use fastboot to restore a -R recovery and wipe the rest of the system if something goes wrong.
Click to expand...
Click to collapse
ok i flashed this older radio but i think froyo rom wont work whit it im not 100% sure about this.

i got good spped then checked 2g only by mistake and whas not able to change it back i wiped and now im not able to get good speed again

Finally i got some speed one of my trouble is that i cant test iut at home the signal is bad just here.I listened to internet radio for 100 KM today whit no trouble.Little cut when i whas changing tower i think!

N1 rebooting

I'm on CM 7.1.0-N1 now , I was having randomly reboots, sometime like 2 or 3 in a hour , sometime 1 per day.
Today I just update to 7.1.0 , but same issue was happening on 7.0.2
I did tried the following to narrow the issue:
-Change to a new SIM
-reformat SD card
-wipe and factory reset (twice)
-upgrade from 7.0.2 to 7.1.0
-After the wipe and reset factory , I keep using the phone without any app installed, and after 12 hrs it did reboot
Issue is still happening most of the time when phone is idle
For now My only hope is that SD card could be provoking the reboot but Im not sure about that
I have a 2 old days logcat (that I got after a reboot) , so I don't know if anyone can help me looking into the logcat file, I cannot find anything useful on the log file
Please let me know if I can attach the file , right now Im monitoring my phone , if I get another reboot I will try to obtain a newest logcat
Any idea or suggestion will be appreciated
thanks in advance!

I just saw a similar post, sorry for creating a new one (I did a search before creating it but found nothing).
I will try with this suggestion posted by Jack_R1
Immediately after the phone rebooted, connect it to ADB and execute:
adb bugreport > bugreport.txt
Check the file, see the last_kmsg log and the last logcat (bugreport has several sections).
If you see "ARM9 has crashed" - your phone's HW is faulty and needs repair.

[Q] Android keeps rebooting before even starts

Hi, I have SGS I9000 for over 2 years now, and today, I unlocked it and it just started to reboot, by itself. As far as the start goes is moment when it needs to switch between "starting aplicatios" and home screen. Then he goes again into starting android mode (it doesn't turn off completly, just android reeboting). It worked fine before seconds before.
I have MIUI android V4 and I've tried everything, wiping, restoring, but main problem is that I have some unsynced contacts and sms that I need but I can't access them. Can you help me please? (only way I can access internal storage is boot/mount/mount USB, because of the restarting thing)

something must be segfaulting everytime it comes to load the UI, what does adb logcat say?

Could you please tell me how to check adb logcat? I don't know much about phones but I'm willing to learn

unzip the adb package below, open a command prompt in that directory and type adb.exe logcat
you need Android Debug Bridge drivers installed, windows should do the job for you, unless you're on crappy vista
if it gets stuck on - waiting for device - you don't have those drivers

Tank you SuicideFlasher on your replies but I managed everything by my self :victory: I flashed my phone with Odin and got semaphore kernel, but it got stuck in a boor loop again. I then copied restore folder from my computer to internal storage (that i previously saved there), reinstalled CWM with Odin and restored the system that worked (I backup ed all data) and now I completely formated my phone to start over. Congrats if any of this makes any sence but it worked for me :good:

it's good to see beginners trying to fix stuff by themselves :good: you have good probabilites of becoming a dev one day imo
anyway, by using logcat you would just have watched the phone freak out in that bootloop while seeing in detail whatever the log could tell you, but i think that log would have frightened the hell out of you if your knowledge is really that minimal atm