Database Develop

if your in a bootloop from a hero rom...

YOU NEED TO WIPE YOUR EXT2/3!
heres how to do this from console! i am kinda sick of people posting "help!!!! in bootloop after flashing this that and the other thing!"
ready to become un-noobified?
turn phone off (do i really need to tell you how?)
: Boot into recovery: home+power
: Go to console (ALT+X)
In Phone Console type this
(press enter)
# mount -o rw /dev/block/mmcblk0p2 (space) /system/sd ((DONT TYPE SPACE it to show you that you hit the spacebar! also that is a ZERO not an uppercase "o")
# rm -rf /system/sd/* (yes you need that. idk why)
# reboot recovery
there you go! are your brains on the wall yet? cause i just blew mine out from being so awesome

i am still going to make a "i got booty loops from flashing a hero rom" thread.

oshizzle1991 said:
YOU NEED TO WIPE YOUR EXT2/3!
heres how to do this from console! i am kinda sick of people posting "help!!!! in bootloop after flashing this that and the other thing!"
ready to become un-noobified?
turn phone off (do i really need to tell you how?)
: Boot into recovery: home+power
: Go to console (ALT+X)
In Phone Console type this
(press enter)
# mount -o rw /dev/block/mmcblk0p2 (space) /system/sd ((DONT TYPE SPACE it to show you that you hit the spacebar! also that is a ZERO not an uppercase "o")
# rm -rf /system/sd/* (yes you need that. idk why)
# reboot recovery
there you go! are your brains on the wall yet? cause i just blew mine out from being so awesome
Click to expand...
Click to collapse
I understand what you are saying but trust me when i say before i used JACs Hero 1.8 none of the Hero versions rom 1.6r2a worked. I would even to a full partition on the SD card and format the card then repartition it back to the 3 different partitions and still a no go. So i understand what you are saying about wiping your ext3 and that should work but it doesnt always work. Trust i know 1st hand.

hahah i wont respond then haha. just bang my head against a wall.

but seriously i see like 5 threads a day on this freaking subject and its like...freaking search man

if that doesnt work then you reformat your entire sd card and remake the partitions. it only takes like 13 minutes cause the reformatting part takes about 10

oshizzle1991 said:
but seriously i see like 5 threads a day on this freaking subject and its like...freaking search man
Click to expand...
Click to collapse
Oh i would agree with you there are alot of dumbass questions out there and all you need to do is use the search. I rooted my G1 which doing nothing but using the search. I even did all my hero flashing up until the latest versions were out with not even one post in any thread because all i did was search. Sometimes there are other things in the works that can cause problems as well, but yes you should do a search 1st. Most likely the answer people are looking for has already been posted and there is no reason to make a thread on it again.

yeah. and honestly the reformatting and recreating of the partitions is like you fallback. if that doesnt work then you should try another hero rom. there are like what...10 out there? OR install a cyanogen mod and get a hero theme.

Pretty much thats what i do is use cyanogen with a hero theme because you know that will always work. I am happy now with JACs 1.8 working like a cham no problems at all. I was kinda pissed to see Drizzy just put one out which was who i was waiting for one to get put out the whole time.

yeah i just booted up using jacs newest one. i came off akirahs. so it should work but i swear to god if one more kid posts about this...lol.

I swear to god if i see one more post in a thread that says OMFG downloading now will report back later. i am going to blow one.

hah. this threads getting off topic, we should stop before the mods...well get all moddy on our asses. well it was good to vent some steam lol.

Apps2SD greyed out....

Yeah, first thing the 'uber coders' will think is 'google it' or 'rtfm'. Well been all over and still can't get it to work. But I'll jump though the hoops and hopefully someone will point out where the missing information is. As much documentation that is out there for Android, there is much left to be desired and checked for clarity. So here it goes:
After having many issues with Clockwork Mod recovery, I finally got AmonRA installed and was able to install CM5.0.7 (8 would not install properly at all...too many broken thing like FCs on settings and such).
Things I have done to try to get Apps2SD working:
1/ Manually partitioned SD card
2/ Use Recovery option to partition the card (converted to EXT4 as per Cyanogen's suggestion)
3/ Tried following advice here: http://code.google.com/p/android-roms/wiki/A2SD
4/ Tried following advice here: http://forum.xda-developers.com/showthread.php?t=520582
- which leads to here: http://forum.xda-developers.com/showpost.php?p=3879988&postcount=41 (which seriously need to be re-written.you can't type adb push while already in adb shell....not recognized)
5/ Ubuntu's Disk Utility tells me the EXT4 partition is clean.
So where to go from here? Nothing seems to make any sort of impact on this phone.

...to the QnA section.....
have you enabled apps2sd?
Settings>Applications and tick the Apps2SD box

Moved as not development.

garok89 said:
...to the QnA section.....
Click to expand...
Click to collapse
Nope, looking now....so far I've got 3 tabs opened because of that....this process is seriously sad. Why are there so many ways (some more poorly written than others) to do the same damn thing that the ROM is supposed to do itself? Don't worry, I'll try yet again another set of instructions to get this to work. Geeze....wasn't this hard the last time I enabled it. Seriously, I do't know why I torture myself with this....
garok89 said:
have you enabled apps2sd?
Settings>Applications and tick the Apps2SD box
Click to expand...
Click to collapse
See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.

So, following the directions outline here: http://forum.xda-developers.com/showthread.php?t=534714
NO freaking change. This is on a fresh ROM install of 5.0.7. Seriously, My card size in 8GB, like his, so I used almost his numbers, just a few bytes different, and nada.
Talk about a sad state.
Yes I repartitioned the card, yes I wiped the partitions (after reinstalling the first time and getting nothing but FCs, wiped each section available in the Amon RA recovery menu....three times each.)
So, let's try yet another method.....
I downloaded Apps2SD.apk. Installed it and ran it....guess what...it aid my card wasn't paritioned?!?! Umm....wft? Why the hell was CM NOT seeing the paritions? This card has been partitioned at least 20 times in the last month, in various methods. Yeah, this i good for it's lifespan....
So I went through it's partitioning process...guess what...still greyed out.
Opened the app again... "It looks like your SD cars isn't partitioned..."...are you kidding me?? (yes the app was granted Super User permissions when it ran....)
So....where do I find the part in CM that is broken and not allowing Apps2SD to work?

How is it that after wiping each item THREE TIMES in th recovery list, and a FRESH INSTALL that my background is still the same????
What is not being wiped?

with 2.1 theres an option for all your settings to be backed up to google. if your background is stored in the same folder on the fat32 partition of your sd card, when you load the new rom, your phone will set your background to what it was.
i know because i went from 5.07 with one background to jubeh's 2.2 with another background, needed gps, wiped EVERYTHING(data, system, ext partition etc.) in RAmon's recovery, flashed 5.08 and had my old background from 5.07 set, along with all my old apps downloading automatically...half hour later and my phone was done syncing and set up exactly how i like it, w/o me doing anythin.
that's how your background is still the same. =P
edit: looking at your signature..is your ext fs first on your sd card? i might be wrong but i think the fat32 needs to be first???

JadedTech said:
Nope, looking now....so far I've got 3 tabs opened because of that....this process is seriously sad. Why are there so many ways (some more poorly written than others) to do the same damn thing that the ROM is supposed to do itself? Don't worry, I'll try yet again another set of instructions to get this to work. Geeze....wasn't this hard the last time I enabled it. Seriously, I do't know why I torture myself with this....
See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.
Click to expand...
Click to collapse
i was not attempting to be insulting, i run the cmupdater support and have received numerous "app2sd is greyed out" emails when in fact it was the "move to sd" that was greyed out, not the apps2sd toggle. so get down from your high horse and dont assume that you are better than anyone else. in my experience dealing with hundreds of support requests, i have found it is the person who asks the question, not the people who attempt to help, who are the problem.
"computers don't make mistakes, people using computers make mistakes" comes to mind...
although ubuntu is showing it as clean, choose the "repair SD.ext" option in the recovery...
and although it is unlikely to correct it, fix apk uid mismatches. apps2sd can be a funny thing which can work one day and not the other at times.....
i dont know why i am still trying to help you after pretty much calling me mentally retarded, but hey....
oh, and by "the qna section" i meant that you asked a question in the development area, ie. the wrong section

See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.[/QUOTE]
you have to have a partition and it will not be greyed out

Either the poor behavior in this thread is going to stop or I'll close it. There is no need to be insulting in any way.

garok89 said:
i was not attempting to be insulting, i run the cmupdater support and have received numerous "app2sd is greyed out" emails when in fact it was the "move to sd" that was greyed out, not the apps2sd toggle. so get down from your high horse and dont assume that you are better than anyone else. in my experience dealing with hundreds of support requests, i have found it is the person who asks the question, not the people who attempt to help, who are the problem.
Click to expand...
Click to collapse
Ok, a few things to clear:
1/ This has truly been one of my frustrating experiences in all the tech I have ever played with (and that's pushing 30 years). Granted you would not know my experiences and my tenaciousness in following directions, despite them having me going off-the-beaten-path because something does not fit any proposed remedy.
What was insulting was the fact that you assumed that I wouldn't check the most basic thing when the ONLY indication that Apps2SD was not working was that tick being greyed out. But that would be because I didn't go into great detail about that. I was kinda hoping that was a given because without it being ticked, it obviously doesn't work.
So, since there was some bas assumptions made, allow me to be the first to apologize deeply and hopefully we can move forward.
garok89 said:
"computers don't make mistakes, people using computers make mistakes" comes to mind...
although ubuntu is showing it as clean, choose the "repair SD.ext" option in the recovery...
Click to expand...
Click to collapse
Did that, no change. Although I will add in that your quote applies just as well to programmers as it does the users
garok89 said:
and although it is unlikely to correct it, fix apk uid mismatches. apps2sd can be a funny thing which can work one day and not the other at times.....
Click to expand...
Click to collapse
Well, doesn't seem to work at all here.<shrug>
garok89 said:
i dont know why i am still trying to help you after pretty much calling me mentally retarded, but hey....
Click to expand...
Click to collapse
That would be because I think you recognized how frustrated I have been and in reality, I'm not really venting at you but at the lack of a solution, despite there being soo many ways to supposedly fix this issue. That would also be because you are most likely the kind of techie that hates to see things not work and will spend more time trying to fix it rather than give in and simply 'reinstall' because you want to know the reason why it happened in the first place. Maybe I'm wrong there, maybe I'm not. I'm am seriously glad that you are taking your time because not a single other person has.
garok89 said:
oh, and by "the qna section" i meant that you asked a question in the development area, ie. the wrong section
Click to expand...
Click to collapse
Yeah, I forgot to apologize to the mod for that. Sorry Mod....
So, have any other ideas how to fix this? I am rather loathe to just try to 'update in hopes that it automagically fixes the issue' approach.

tdt1345 said:
you have to have a partition and it will not be greyed out
Click to expand...
Click to collapse
You might want to read my first post again.....
"Things I have done to try to get Apps2SD working:
1/ Manually partitioned SD card"

jamesd86 said:
with 2.1 theres an option for all your settings to be backed up to google. if your background is stored in the same folder on the fat32 partition of your sd card, when you load the new rom, your phone will set your background to what it was.
i know because i went from 5.07 with one background to jubeh's 2.2 with another background, needed gps, wiped EVERYTHING(data, system, ext partition etc.) in RAmon's recovery, flashed 5.08 and had my old background from 5.07 set, along with all my old apps downloading automatically...half hour later and my phone was done syncing and set up exactly how i like it, w/o me doing anythin.
that's how your background is still the same. =P
edit: looking at your signature..is your ext fs first on your sd card? i might be wrong but i think the fat32 needs to be first???
Click to expand...
Click to collapse
Yeah...I realized this after I left the house and was getting into the car. Just too frustrated when I posted. It was one of those 'don't drink and drive' but more of a 'don't vent and post' type of deals....well, at least not here. Thanks any ways.

have you tried ext2 before upgrading to ext4?
ext4 didnt like my spare g1 too much....but my main one got along fine with it

JadedTech said:
1/ Manually partitioned SD card"
Click to expand...
Click to collapse
Is the partition system ids correct:
Code:
# fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 8166 MB, 8166309888 bytes
252 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15624 * 512 = 7999488 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 952 7436993 b Win95 FAT32
/dev/block/mmcblk0p2 953 1020 531216 83 Linux
Command (m for help):
The 'b' for the vfat partition and '83' for ext
The startup scripts use there values for some autodetection in cm5.
If all you change is the Id data wont be lost but you are at fault if you don't backup.

garok89 said:
have you tried ext2 before upgrading to ext4?
ext4 didnt like my spare g1 too much....but my main one got along fine with it
Click to expand...
Click to collapse
That is a very interesting observation as I have been automatically upgradeding to EXT4 (as I did read that is what Cyanogen uses...figured if it was good enough for him....) so I just reformatted my SD card from the Recovery partition into EXT2 with a 32MBswap and the rest in FAT32. No change. Damn....seemed like one of those 'simple and yet not obvious' type of answers that may have worked too...

ezterry said:
Is the partition system ids correct:
Code:
# fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 8166 MB, 8166309888 bytes
252 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15624 * 512 = 7999488 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 952 7436993 b Win95 FAT32
/dev/block/mmcblk0p2 953 1020 531216 83 Linux
Command (m for help):
The 'b' for the vfat partition and '83' for ext
The startup scripts use there values for some autodetection in cm5.
If all you change is the Id data wont be lost but you are at fault if you don't backup.
Click to expand...
Click to collapse
Now this produced something interesting.
Code:
# fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 243328.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help):
#
So, how does one go about fixing this if this is the reason that "in certain setups cause problems"? This seems to be a likely candidate for the root of the issue.
Redo partitions in Fdisk?

instead of doing it from recovery
do it from ubuntu via gparted

Sorry for jumping in here but... A while back Dusty wrote a great tut for doing this correctly. Did you follow his thread instructions? If not, take a look. It may have the key to your happiness.
http://forum.xda-developers.com/showthread.php?t=534714&highlight=51dusty

JadedTech said:
So, how does one go about fixing this if this is the reason that "in certain setups cause problems"? This seems to be a likely candidate for the root of the issue.
Redo partitions in Fdisk?
Click to expand...
Click to collapse
The size warning only applies to the short falls of BIOS booting x86 PCs. We don't boot the dream from the sdcard or is the phone booted with a x86 BIOS...
If it was you need to ensure the boot partition is near to the beginning of the disk.. you can safely ignore it

[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?

[HowTo] ClockWorkMod Recovery

Thanks to Trekfan422991 for cluing me in on the Optimus 3D recovery.
Working:
Nandroid
ADB (after special driver install, need to tweak recovery for it to work with normal drivers)
Mounting USB to computer
Flashing zip files
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
I am in the process of making a recovery specifically for our device, it is mostly done and will be posted here when it is ready!
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
If you don't understand something in that list, DO A SEARCH AND LEARN, don't clutter the thread with crap!
Lets get started!
Lets start by getting the recovery.img file on the phone. Open up a cmd prompt and type:
Code:
adb push recovery.img /data
The rest of this will be done on the phone shell. In the cmd prompt type:
Code:
adb shell
We will need to have su access, In the cmd prompt type:
(If you haven't allowed shell su in SuperUser now would be a good time to accept the root request on the phone.)
Code:
su
Now we are going to backup your current recovery to your sdcard. In the cmd prompt type:
(make sure your sdcard is not mounted to your computer)
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
After that is done we are going to flash ClockWorkMod Recovery! In the cmd prompt type:
Code:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
Congrats! You now have ClockWorkMod Recovery! In the cmd prompt type:
(each line is single command)
Code:
rm /data/recovery.img
reboot
How to enable ADB access: (only if it's not working already)
Download and install: (unzip and install the 2 exe files)
http://www.mediafire.com/?j5m1plnvzb8r0zc
While booted into ClockWorkMod Recovery, go into your device manager, you should see an "LGE Android Composite Device" with a yellow triangle on it.
right click on it, update driver software...
select browse my computer for driver software
select let me pick from a list of device drivers on my computer
click the "Have Disk" button
click the "browse" button
browse to;
for 64bit:
C:\Program Files (x86)\LG Electronics\LG Android Driver\64BitADB
for 32bit:
C:\Program Files\LG Electronics\LG Android Driver
and select lgandadb.inf
click "ok"
From that list select "Android Sooner Single ADB Interface"
click "next"
click "yes" on the popup
Click to expand...
Click to collapse

Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose. Good thing I am having issues with permissions with this didn't notice the SD Card Mounting issue till just now. That I can't deal with atm.

malickie said:
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose.
Click to expand...
Click to collapse
I found a few modes, but no drivers yet so I don't know what they are. Even if we break stuff the kernel and recovery are separate, so technically we should always be albe to get back into recovery to fix stuff.

thankyou DG for getting this started..
so now with my clockworkmod i just made a backup of stock rom... if i say change the framework and I get boot loop.. will this clockwork mod be able to restore the original rom without any problems???

tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...

Trekfan422991 said:
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Click to expand...
Click to collapse
I got mixed up as to what partition to flash, you just flashed a recovery image over the kernel... its ok tho.
follow my instructions to the su part, then do this.
// this will restore the kernel
dd if=/sdcard/mmcblk0p5.backup of=/dev/block/mmcblk0p5 bs=4096
// this will backup recovery
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
// this will flash cwm
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
OP is fixed!
edit--
and you have no adb access, this is going to get interesting!

haha... i shoulda noticed
____

LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha

Trekfan422991 said:
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Click to expand...
Click to collapse
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.

47r0n1n said:
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
Click to expand...
Click to collapse
sorry just side note:
how you liking your thrill compared to the evo 3d???

designgears said:
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
Click to expand...
Click to collapse
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?

Komodo Rogue said:
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Click to expand...
Click to collapse
I took it down for now, working on some issues.

Woohoo, got Trekfan422991 all fixed!

its true... i tested out my framework mod and it works great!!! look sway better then stock!!!

designgears said:
I took it down for now, working on some issues.
Click to expand...
Click to collapse
Ah, gotcha. I thought I was going crazy Thanks!

Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!

designgears said:
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
Click to expand...
Click to collapse
After CWM is installed and working on our device, would it be safe to fix permission in "ROM Manager," or does that just fix permissions through whichever recovery is currently installed?
I'm guessing someone here knows how ROM manager works in this regard, but if not, I'd be happy to be a guinea pig... after all, I can make/restore backups now! : )
gtg465x said:
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
Click to expand...
Click to collapse
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be

Komodo Rogue said:
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Click to expand...
Click to collapse
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.

Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?

gtg465x said:
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Click to expand...
Click to collapse
Oh, good to hear! Man I really have to sit down and try to learn some more technical stuff sometime, because ROM creation, and not even just the theming aspects, is so appealing to me.
Maybe you can create a thread placeholder and describe what you've done so far? We're really getting OT, sorry all.
timbrendelaz said:
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
Click to expand...
Click to collapse
Oh, I thought you could flash zips through adb after doing the fix? Or no? (((edit: wait, no, I was thinking about pushing .apks through ADB, not flashing .zip files))) Hopefully this is something DG's new recovery might address. If no to both, could you distribute ROMs via nandroid backup files of a fresh ROM installation? It would be incredibly inefficient, but it would work, right?

delete cm7 with no screen-I have ADB!

My screen broke tonight enough to make it unusable, and I was offered in store exchange when I called B&N support. I am running CM7, and would like to know if it is possible to either restore to stock or wipe the hard drive to remove evidence of rooting before I send it back.
I managed to get into adb and read in another thread to try rm -r *, which is supposed to wipe everything, but I got a bunch of read only errors. It appears that the nook will now not boot into CM7 (which is good), but I fear that I haven't wiped it far enough to be safe from a chargeback. Any ADB wizards out there with some advice?

I think I have done it. I opened up a shell in adb, mounted /system as r/w, then did rm -r *. after a reboot it won't even boot into adb anymore. it comes on for about 4 seconds then shuts off immediately. I can't tell what is happening on the screen because of the damage, but i'm hoping it is enough that the folks who check returns at BN can't prove it was rooted.

What are you wanting it to boot into if you just deleted everything in the system partition?
Sent from my HERO200 using XDA App

I think he wanted it to not boot at all in preference to booting into CM7.
I'm pretty sure that if they looked beyond the broken screen they'd be able to determine that you've rooted it: Having no files but still a filesystem on /system is kinda suspicious, and I imagine that having CWM instead of the stock recovery would be something of a giveaway as well.