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

[muziling]

Originally Posted by [ACL]

I need more tests from you about the wifi. I have full wifi with the exact setup. Now you sure you are using the update.zip i have posted up?

Also wifi issues are usually because the txt file generated on startup isnt working. Look for /data/wifi-nvram.txt. Check the contents of that file and if it looks all garbled (not plain text) then removed it. This will be fixed on next build. Lmiller already made a patch for it. Eventually im hoping to move to the true android way of doing this using atags instead of these scripts.

Camera wont work for a while. Not really concerned with it right now. BT works? wow news to me. But ok.

New rill will come. No worries. We are just waiting for frx7 release.

Also have you tried over clocking? i never overclocked before so feedback is helpful here.

Yes ,i use update.zip, wifi message is identication, disconnected, identication, disconnected.
never overclocked too, so try next time.

[eu0741924381]

managed to boot into recovery via "fastboot boot recovey.img"
but now recovery shows me msmeadata/ and wmdrm/ with are not there but not the files in my sd..

and also i got " E:bad boot message"

[[ACL]]

Originally Posted by eu0741924381

managed to boot into recovery via "fastboot boot recovey.img"
but now recovery shows me msmeadata/ and wmdrm/ with are not there but not the files in my sd..

and also i got " E:bad boot message"

not sure what any of that is bro.. nothing makes sense to me about what ur reporting.

[muziling]

Hello ACL,
Does your kernel base on neweast xdandroid or WisTilt2?
Your kernel wake up fail many many times, I decide flash back to non-NAND version, when make a call, I need to wake up to press number key, but wake fail and fail. WisTilt2's kernel is great to wake up and sleep.

W/BatteryStatsImpl( 149): Couldn't get kernel wake lock stats

I know neweast kernel had resolve this, and USB tether is ok now.


http://forum.xda-developers.com/show...56&postcount=1

In addition to all of the 20110510_201546 autobuild kernel code, this kernel also has WisTilt2's power manager and framebuffer fixes, as well as button lights. Also, it has my sleep LEDs - solid green means a wakelock is present, blinking green means the phone is asleep. Don't confuse this with WisTilt2's previous testing kernels.

[[ACL]]

Originally Posted by muziling

Hello ACL,
Does your kernel base on neweast xdandroid or WisTilt2?
Your kernel wake up fail many many times. WisTilt2's kernel is great to wake up and sleep.
I know neweast kernel had resolve this, and USB tether is ok now.

Neither, we have our own kernel which is a fork of the linux-msm kernel.

You test the overclock? i cant for the life of me tell if its going any faster. I'm too used to my galaxy S .

[eu0741924381]

Originally Posted by [ACL]

not sure what any of that is bro.. nothing makes sense to me about what ur reporting.

Well i think Recovery or LK might try to read the recovery partition as Sd. What i am trying to say is that maybe it reads the in wrong order? maybe that's why i and many others can't access Recovery by pushing the power button.

[cris11368]

What happened to the RHODIMG.NBH with the recovery built in? I can't figure out for the life of me how to do the non recovery one and then flash the recovery img onto the phone.

[eu0741924381]

Originally Posted by cris11368

What happened to the RHODIMG.NBH with the recovery built in? I can't figure out for the life of me how to do the non recovery one and then flash the recovery img onto the phone.

Actually flashing recovery to your device is easy, just read [GUIDE] ADB, Fastboot, and Nandroid for Noobs - xda-developers oh how to get drivers and fastboot up and running.

Place the recovery.img in your fasboot/adb folder;

The open a command prompt and "cd" to your fasboot/adb folder;

Then type "fasboot devices" to print a list of your connected fasboot devices (mine is "? fasboot");

Then type "fastboot flash recovery recovery.img", this will flash recovery.img to your recovery partition;

Then type "fastboot reboot" to reboot your phone.

You should now be able to boot your phone into recovery by holding the power button once the blue screen turns on.

Also a lot of people that reported that in recovery end button does not work but you can use the psihical keyboard to navigate recovery, up and down arrows to select and enter key to choose.

If you can't get the drivers running try googleing for them, some android file explorers install the drivers as well.

Hope this helps.

[slimbrown29]

Quick question. Will I be able to use the SIM card when running Android on NAND on my Sprint Touch Pro 2?

I am currently working in an are where I have to use GSM networks and WM6.5 is not doing it for me

Thanks.

[rank2]

Rhod100_DE:

Fastboot stops with

fastboot_init()
udc_start()

no matter what button I hold pressed.
Since plugging in USB after these messages makes

fastboot: processing commands

appear, I gues the phone didn't freeze.
Is there a way to load recovery from fastboot?
I flashed the nbh without recovery and fastbooted the recovery.img a few pages back.

Btw. just a blind guess but Rhod100 with german keyboard has keycode 107 on end call - maybe they're different.

Hopes this helps