Originally Posted by rank2 (Post 2104670)

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.

Hopes this helps

Originally Posted by slimbrown29 (Post 2104661)

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.

Originally Posted by rank2 (Post 2104670)

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

Originally Posted by rank2 (Post 2104866)

Hi,

thank you for the tip holding end button before LK shows up, unfortunately this didn't do the trick.
Meanwhile I ran recovery from fastboot console as eu0741924381 suggested and I could install both updates. However LK still wouldn't jump from udc_start().
Are there possibly any differences in NAND layout? Any way I could send you detailed information about this device?

Best regeards
rank2

Originally Posted by eu0741924381

By running "fastboot boot boot.img" i was able to get to smd0 open -> opened and after that a reboot :(... but that was with sim card in, i've never managed to get this far with sim in... i'll try to fix this and i'll update soon.

Update: can the end key think it's being pressed all the time and that's why it automatically boots into fastboot every time and you can't use it in recovery ( it is the single key that it's not working in recovery)

Update: I can see the animation !

New update: It's working! You guys are the best! I have no signal but Wi-Fi is working! and it's very fast!

Originally Posted by Lmiller1708 (Post 2104884)

Wirelessly posted (TP2: Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; pcdadr6350 Build/FRG83D) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)



It boots into fastboot all the time because you don't have a boot.img installed. Did you install the kernel-update.zip? If that don't work you can run "fastboot flash boot boot.img" .

Good luck and glad to see you made it to the boot animation.

Originally Posted by eu0741924381 (Post 2104892)

i did install the kernel-update.zip and even tried flashing boot.img from fastboot with no success. I am already using "fastboot flash boot boot.img" to boot it up and i have a working android system with no signal.

By booting into fastboot every time i mean it boots to fastboot even when holding power down to boot into recovery.


Update: overclocking does not work for me...

Originally Posted by eu0741924381 (Post 2104660)

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. :smile:

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.