[TESTING] - NAND OMGB (1.2.3)

[argenisaz]

Hi folks.

I decided to start from scratch, and the first thing I did was install de newest LK version.

Well, I'm stuck. My computer will not recognize the phone in fastboot mode so I'm unable to flash recovery. LK says that it's in fastboot mode and processing commands, but nothing happens.

Any pointers?

[boggsie]

Originally Posted by argenisaz

Hi folks.

I decided to start from scratch, and the first thing I did was install de newest LK version.

Well, I'm stuck. My computer will not recognize the phone in fastboot mode so I'm unable to flash recovery. LK says that it's in fastboot mode and processing commands, but nothing happens.

Any pointers?

I am pretty sure that the latest LK needs power button pushed even when plugged into USB.

Sent from my NookColor using Tapatalk

[Nighthawk243]

Originally Posted by boggsie

I am pretty sure that the latest LK needs power button pushed even when plugged into USB.

Sent from my NookColor using Tapatalk

Power button press is to boot into recovery in order to install packages.

Originally Posted by argenisaz

Hi folks.

I decided to start from scratch, and the first thing I did was install de newest LK version.

Well, I'm stuck. My computer will not recognize the phone in fastboot mode so I'm unable to flash recovery. LK says that it's in fastboot mode and processing commands, but nothing happens.

Any pointers?

Do you have the proper drivers installed? If you can show your cmd output when trying to execute the commands, that would probably help.

[vzihome]

Originally Posted by Nighthawk243

Power button press is to boot into recovery in order to install packages.



Do you have the proper drivers installed? If you can show your cmd output when trying to execute the commands, that would probably help.

I believe he said from scratch assuming he had nand before, try different usb cable and or port

Sent from my Touch Pro 2 using Tapatalk

[argenisaz]

Originally Posted by Nighthawk243

Power button press is to boot into recovery in order to install packages.

Do you have the proper drivers installed? If you can show your cmd output when trying to execute the commands, that would probably help.

When I run fastboot devices the output turns out blank.

Originally Posted by vzihome

I believe he said from scratch assuming he had nand before, try different usb cable and or port

Sent from my Touch Pro 2 using Tapatalk

All ready did that, different cable and usb port.

In Windows Vista, the ADB Interface driver installed without a problem (check under device manager).

Same thing under linux, running lsusb shows that a google device is connected (ID 18d1:0001).

Under both os's, fastboot says there is no device connected.

Note: this is not the same pc I used to install nand the first time.

[teemo]

Originally Posted by argenisaz

Hi folks.

I decided to start from scratch, and the first thing I did was install de newest LK version.

Well, I'm stuck. My computer will not recognize the phone in fastboot mode so I'm unable to flash recovery. LK says that it's in fastboot mode and processing commands, but nothing happens.

Any pointers?

In linux try as root.

[argenisaz]

Originally Posted by argenisaz

All ready did that, different cable and usb port.

In Windows Vista, the ADB Interface driver installed without a problem (check under device manager).

Same thing under linux, running lsusb shows that a google device is connected (ID 18d1:0001).

Under both os's, fastboot says there is no device connected.

Note: this is not the same pc I used to install nand the first time.

Ok, so out of sheer need I installed WinMo () and went right back to FRX07. I decided tu run a little test and connected the device under Windows Vista. The phone was recognized right away but this time it installed de Android Composite ADB Interface Driver (using LK it installed ADB Interface Driver), It also installed with a different Id 0BB4:0C02 (using LK it was 18D1:0001).

Using this setup I can ADB without a problem. Is the product ID screwing things up for me?

[mbellot]

Originally Posted by argenisaz

Ok, so out of sheer need I installed WinMo () and went right back to FRX07. I decided tu run a little test and connected the device under Windows Vista. The phone was recognized right away but this time it installed de Android Composite ADB Interface Driver (using LK it installed ADB Interface Driver), It also installed with a different Id 0BB4:0C02 (using LK it was 18D1:0001).

Using this setup I can ADB without a problem. Is the product ID screwing things up for me?

I documented that difficulty when I moved to OMGB here, including how I "fixed" it.

Once I got that rolling I couldn't attach to the phone via adb/fastboot. Windows was popping up a "new device" dialog, so I figured it had to be driver related, even though adb (and droid explorer) work with FRX7.1 without issue.

I ended up editing the Google/Android USB driver to add the VID/PID (18D1/0001) that was shown in the device manager and then allowed Windows to "re-install" the driver. Now I finally have access to the phone via fastboot.

Windows is such a picky b!tch about matching things up. LOL.

[argenisaz]

Originally Posted by mbellot

I documented that difficulty when I moved to OMGB here, including how I "fixed" it.



Windows is such a picky b!tch about matching things up. LOL.

I know my friend, I had already read your post... but your solution didn't work out for me. The driver installed without problems, but for some reason fastboot doesn't see it.

Anyway, thanks a lot for your help!

[trevoroni]

Originally Posted by mbellot

Thanks ACL!

BTW - 24 hours later everything seems good with the latest update. No sleeping/wake/charging lock-ups yet.

Boggsie - Here are the files, you'll still need to put them in the correct places since I have no idea how to wrap this in to a proper update.

I tried this, and the end button works great! But... the power button on top doesn't do anything, so once the phone goes to sleep there's no way to wake it up except for plugging it into USB.

The power button didn't do anything before I replaced the files though so I'm not sure if it was broken before I changed it or not (I'm not sure how it is supposed to act by default, previously the end button was used for sleep/wake).

When I was using FRX the power and end button worked correctly. And the button is not physically broken because it is recognized in LK.

Not sure what's going on, everything looks correct in the keymaps, END=Key 107, POWER=Key 116.