adb in recovery "device not found" Droid Bionic

[ravenofdoom]

I was trying to perform the permaroot method by adding the lines to "mount_ext3.sh " and idiotically forgot to change the permission on the system folder to "R/W" before rebooting. Now, I'm faced with a wonderful Bionic-eye boot-loop. My goal is to get into the location where the setting are in R/O mode (e.g. at /system/bin) and change them back to R/W

I have the motorola drivers installed as well as the android sdk. when I run from cmd (i know i'm in the right folder) "adb shell", I get the "device not found" response. I went into the recovery screen "power +volup+voldown" and got into the fastboot as well... I've tried the "adb shell" command from both places (fastboot and recovery screen witht he android bot with the question mark), but it always says device not found. I'm in windows 7 (going to attempt this on an XP machine)

I'm running out of ideas here... shouldn't my PC be able to find the device with the adb shell command within one of those screens? I also tried the adb kill-server" command and then "adb shell" again, but no luck.

Help is greatly appreciated (so that my girlfriend doesn't kill me for screwing up her phone)

 

[Moscow Desire]

Nope. If I remember correctly, you'll need to install the adb drivers manually. You should be able to do it the easy way, and find them through google, or check with the sdk manager and let it find them.

I found it easier to get them with google.

 

[ravenofdoom]

I installed the entire google SDK... and all the components, so I should have those drivers

EDIT - meant to say I also have the motorola 5.2 usb drivers installed

 

[ravenofdoom]

i thnk im going to have to go the route of rsdlite and full restore. really annoying that adb shell won't detect the phone, but fastboot will

 

[Moscow Desire]

I installed the entire google SDK... and all the components, so I should have those drivers

EDIT - meant to say I also have the motorola 5.2 usb drivers installed

Only reason I mentioned installing the drivers manually, is that I just installed the SDK 4 days ago, and same thing happened to me. Wouldn't recognize Desire in debugging mode.

SDK manager showed x64 drivers not installed.

Ehhhh.... systems are different I guess Next time, I'll learn to "right click" and install as administrator under win7.

Hope you get it figured out.

 

[ravenofdoom]

Dear god, i'm getting an error when i flash with rsdlite 5.5 and the stock image.

it's like it's immediately failing as soon as it tried to flash. It says failure on 1/15 step cdt.bin.
I'm using the file image : targa_cdma_targa-user-2.3.4-5.5.1_84_DBN-55-110814-Verizon-US.tar

 

[ravenofdoom]

whoa - weird -... it seems like even though it failed according to rsdlite, it was able to boot into the OS

 

[ravenofdoom]

when i go into "recovery" mode tho, it says "Invalid flash mode (S) (Boot Failure)

 

[ravenofdoom]

so... when I got into the phone OS and attempted to do a factory default reset, it comes up with:
"Invalid flash mode (S) (Boot Failure)

This would mean I can't ever upgrade/flash the phone unless I can figure out why it has this flash failure message

 

[ravenofdoom]

http://forum.xda-dev...d.php?t=1305596

This looks like the same problem but the guy never says if/how he fixed it