NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery - Page 159

**Lmiller1708** · #**1581** (**permalink**) 03-09-2011, 12:58 PM

Quote:

Originally Posted by lionedas

arrrghhh

With the setup from the OP i get a wifi error when I try an enable wifi,
with the files from Lmiller I get obtaining ip over and over.

What am I doing wrong?

If you are using my lastst package. It should work.

Remove the andriodinstall.tgz and andriodupdate.tgz and add my files to your sdcard/andboot folder.

Reflash. Run the second option of the Boot Menu. And you should be good to go.

**arrrghhh** · #**1582** (**permalink**) 03-09-2011, 12:59 PM

Quote:

Originally Posted by lionedas

arrrghhh

With the setup from the OP i get a wifi error when I try an enable wifi,
with the files from Lmiller I get obtaining ip over and over.

What am I doing wrong?

Don't know, perhaps your modules don't match. Don't tell me your network is "secured" with WEP...

Reason I put secured in quotes above is WEP isn't really much for security.

tiger2wander · #**1583** (**permalink**) 03-09-2011, 01:06 PM

I have see the launcher selection screen, I have wait a few minutes then screen off, push power button to turn it but seen it crashed, after reboot I have face again with error message "Waiting for SDCard" then reboot, boot loop here.

I think we need to remove or add a condition check if Android system is installed on NAND then SDCard is not required in boot process! It will avoid this boot loop.

Trying to re-format can not get out of rid, I'm going to create new partition table on it and start over again as I have success earlier

Good luck guys!

**[ACL]** · #**1584** (**permalink**) 03-09-2011, 01:08 PM

if touch screen isnt calibrated when you boot, then chances are wifi is broken as well. Means bad install or old version. Check that

lionedas · #**1585** (**permalink**) 03-09-2011, 01:14 PM

Quote:

Originally Posted by [ACL]

if touch screen isnt calibrated when you boot, then chances are wifi is broken as well. Means bad install or old version. Check that

ALC the screen calibration did not pop up for any of the builds I tried
so far, if thats what you mean above.

I used task29 to wipe the phone, flashed via the nbh,
had the 3 files on my sdcard in the andboot folder, installation started on its own, and after a few minutes I had a screen asking if I wanted to use awd or the other launcher for my home screen.

**[ACL]** · #**1586** (**permalink**) 03-09-2011, 01:30 PM

Quote:

Originally Posted by lionedas

ALC the screen calibration did not pop up for any of the builds I tried
so far, if thats what you mean above.

I used task29 to wipe the phone, flashed via the nbh,
had the 3 files on my sdcard in the andboot folder, installation started on its own, and after a few minutes I had a screen asking if I wanted to use awd or the other launcher for my home screen.

No i mean the screen uses default settings on boot. When there is a broken install, the screen wont work. You wont even be able to enter into android. When that happens, wifi will fail as well. If thats not the case here, then sounds like something else.

lionedas · #**1587** (**permalink**) 03-09-2011, 01:36 PM

Quote:

Originally Posted by [ACL]

No i mean the screen uses default settings on boot. When there is a broken install, the screen wont work. You wont even be able to enter into android. When that happens, wifi will fail as well. If thats not the case here, then sounds like something else.

No screen works good, I noticed it takes a bit to wake it up sometimes though.

I'm using wpa2 its worked before with no problems....

**natemcnutty** · #**1588** (**permalink**) 03-09-2011, 01:40 PM

Quote:

Originally Posted by lionedas

ALC the screen calibration did not pop up for any of the builds I tried
so far, if thats what you mean above.

I used task29 to wipe the phone, flashed via the nbh,
had the 3 files on my sdcard in the andboot folder, installation started on its own, and after a few minutes I had a screen asking if I wanted to use awd or the other launcher for my home screen.

Why would it ask which launcher you want to use? It almost sounds like you have an old NBH that used an old init which loaded up your data.img from the sdcard or something weird.

lionedas · #**1589** (**permalink**) 03-09-2011, 04:42 PM

Quote:

Originally Posted by natemcnutty

Why would it ask which launcher you want to use? It almost sounds like you have an old NBH that used an old init which loaded up your data.img from the sdcard or something weird.

If you install Lmillers updates istead of the one on the OP you have a choice of awd launcher, and it pops up on first boot.

I have tried both builds, at least 3 times each, task29 everytime,
I even flashed winmo back on and then task29, flashed nbh,
wireless just says obtaining ip then disconnects over and over.

Me and a buch of others had the axact same wifi problem with one of tiad8's releases
even though he didnt have the issue, but he was able to fix it in his 03/06 release.

Anywho ill wait someone will think of something.

I have an optimus s running 2.2 but I cant stand the phone
i'm hoping someone gets the TP2 closer to prime time
before I smack the Optimus in the wall !

JTuck · #**1590** (**permalink**) 03-09-2011, 05:05 PM

Quote:

Originally Posted by Lmiller1708

Try my newest files again: Free File Hosting Made Simple - MediaFire
The andriodupdate.tar is still the same so there is no need to re-download that.

ACL I think I figured out how to make a patch.

So if will be sending you something for my replimenu until you get the recovery working.

Still not working.

Log: Android Log - Pastebin.com

I am also not able to connect to WiFi (WAP2) get the same obtaining IP over and over. Can get a log of that too if you would like?