Jump to content

Recommended Posts

Guest BooToo
Posted

Hi,

I am creating this new tread to sort once the "Device not found" problem when following the install instruction in Paul's tread

http://android.modaco.com/content/dell-str...erboot-recovery

For the ones, like me, who have installed the official 2.1 from O2 on their Streak, there are some codes lines required to disable the safe mechanism prevention to flash with the new recovery image.

Assumption: when using ADB from the Android SDK and typing su, I get the admin prompt (#), therefore, I assume, my 2.1 Streak is already rooted and have done nothing else

So, it is said that the following code need to be entered as explained below:

@@@@@@@@@@@@@@@@@

"Update: The stock 2.1 build has a built in mechanism that is overwriting the stock recovery image. To disable this, with your device booted and rooted, enter the following at a command prompt (in the directory where you extracted the zip above) before re-flashing the recovery image using the instructions above:"

adb-windows shell

su

mount -o remount,rw /dev/block/mtdblock6 /system && rm /system/etc/install-recovery.sh && mount -o remount,ro /dev/block/mtdblock6 /system

exit

exit

@@@@@@@@@@@@@@@@@

As soon as I enter the "adb-windows shell", I get:

"Daemon started sucessfully"

error: Device not found

If I do the same from the android SDK tool folder, it works and I get the $ prompt

I have check my device manager in case it was a driver problem and I have Android Phone and Android ADB interface under so all is looking great.

What am I missing??????

Thanks in advance for cracking this one as it is quite sticky...

Guest Alkiera
Posted
Hi,

I am creating this new tread to sort once the "Device not found" problem when following the install instruction in Paul's tread

http://android.modaco.com/content/dell-str...erboot-recovery

For the ones, like me, who have installed the official 2.1 from O2 on their Streak, there are some codes lines required to disable the safe mechanism prevention to flash with the new recovery image.

Assumption: when using ADB from the Android SDK and typing su, I get the admin prompt (#), therefore, I assume, my 2.1 Streak is already rooted and have done nothing else

So, it is said that the following code need to be entered as explained below:

@@@@@@@@@@@@@@@@@

"Update: The stock 2.1 build has a built in mechanism that is overwriting the stock recovery image. To disable this, with your device booted and rooted, enter the following at a command prompt (in the directory where you extracted the zip above) before re-flashing the recovery image using the instructions above:"

adb-windows shell

su

mount -o remount,rw /dev/block/mtdblock6 /system && rm /system/etc/install-recovery.sh && mount -o remount,ro /dev/block/mtdblock6 /system

exit

exit

@@@@@@@@@@@@@@@@@

As soon as I enter the "adb-windows shell", I get:

"Daemon started sucessfully"

error: Device not found

If I do the same from the android SDK tool folder, it works and I get the $ prompt

I have check my device manager in case it was a driver problem and I have Android Phone and Android ADB interface under so all is looking great.

What am I missing??????

Thanks in advance for cracking this one as it is quite sticky...

If the one in the sdk window works, just use it. There shouldn't be any reason to use the provided one unless you don't have the sdk installed. The reason it's called adb-windows is the .zip has multiple versions of adb for different OS.

Guest LorD CLockaN
Posted
If the one in the sdk window works, just use it. There shouldn't be any reason to use the provided one unless you don't have the sdk installed. The reason it's called adb-windows is the .zip has multiple versions of adb for different OS.

+1

Posted (edited)

Ok.

Here was the problem...

I made the mistake to beleive that because I had a root access via ADB, I did not need to root the phone...

I did it with superboot (the superuser icon appeared in my apps list) and that was it.

Just in case other have the same issue ;-)

Edited by BooToo

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.