Gone back to 6941.. but one issue remains

[Guest rovex]

Ok the O2 update 2.1 is terrible so i went back to 6941 which is much better. However some apps wont install, especially google Earth 1.1. Can this be fixed? It works with 8105, so can it be fixed by moving files over? (maybe build.prop)?

[Guest rovex]

Ok. Im now using 6941 with the 8105 build.prop. Seems to work ok more apps appear in the market. Its just soo much better than 8105.

Id like to see this build as an MCR. Its faster, more reliable and has better icon spacing than the awful official release.

Edited September 5, 2010 by rovex

[Guest spacecat46]

F

Ok. Im now using 6941 with the 8105 build.prop.

How you do dat?

[Guest rovex]

Just use root explorer to replace it. They are almost identical except for the parts that identify the unit and build.

[Guest radddogg]

Rovex - How did you go back to 6941? I've tried to but I get "Software is up to date. System will reboot in 30 seconds.". I've tried both 6941 and stock 1.6 in both clockwork and stock recovery but clockwork spazzes out and does nothing and stock just gives me "Software is up to date. System will reboot in 30 seconds."

The guides here are very ambiguous and make many assumptions. I'm compiling my own newb friendly FAQ but this is one thing I'm struggling with. Hopefully its something simple.

[Guest alert_bri]

I'm having the same problem here... I've used Universal Androot to root and can get a fastboot connection but when I try :

> adb-windows shell

I get the following response :

* daemon not running. starting it now *

* daemon started successfully *

error : device not found

I'd be very grateful for any pointers?

Cheers

Brian

[Guest radddogg]

I'm having the same problem here... I've used Universal Androot to root and can get a fastboot connection but when I try :

> adb-windows shell

I get the following response :

* daemon not running. starting it now *

* daemon started successfully *

error : device not found

I'd be very grateful for any pointers?

Cheers

Brian

Can you connect via fastboot? I have better success with fastboot rather than adb. Once connected you have to use the device identifier -i 0x413c after each fastboot command i.e. fastboot -i 0x413c flash recovery recovery.img

[Guest radddogg]

Actually thinking about it, your problem is probably drivers related. Is there an android 1.0 error in device manager? If so you need to manually installation the driver. There will be a bootloader driver under google inc if you search under all drivers.

Sorry for the crappy eexplanation but this keyboard is driving me crazy!!!!

[Guest alert_bri]

Actually thinking about it, your problem is probably drivers related. Is there an android 1.0 error in device manager? If so you need to manually installation the driver. There will be a bootloader driver under google inc if you search under all drivers.

Sorry for the crappy eexplanation but this keyboard is driving me crazy!!!!

Thanks raddogg, I'm using the Android Composite ADB Interface from the Google Inc as you suggest... but still I get the error : device not found :P

Concerning the official v2.1, I think there's a memory leak or something because if I do a factory restart, it's beautifully smooth and lag free for a half an hour or so (depending I guess, on how many apps I load and start accessing)... but then slows to an infuriating crawl. I'm surprised more people haven't reported this behaviour?

Cheers

Brian

[Guest radddogg]

Can you list what you have done so far?

[Guest alert_bri]

Can you list what you have done so far?

I bought my Dell Streak from O2 with v1.6 installed

When I tried to upgrade to the leaked v2.1 (v6941), it failed... sticking on blank screen if I remember right

I loaded v4399 first which was successful...

I then loaded v6941 loaded successfully

Then I loaded the O2 release version of v8105 - which initially gave me the flashing icons (home/menu/return) every 40 secs or so... and slowed to a crawl when that happened.

After trying lots of stuff I didn't track too closely (involving fastboot attempts to load stock image 4399 as above without the shell -> su bit) I used Universal Andboot and did a factory reset - the O2 release has settled down a little, flashing has stopped but after a few minutes still slows to a crawl.

And I've just re-loaded the O2 release version from Update.pkg to see whether that will resolve the slow down after a few minutes of use... will continue to report back progress.

I have a hope given Loconinja's post here that the official O2 release version 2.1 is good, and all I've been seeing is clashes with the previously stable and fast, installed v2.1 (v6941)

...unfortunately, that hope seems poorly founded because it's slowed to a crawl again - grrr is this only my O2 v2.1 official release which is screwed up? I haven't read anyone else having their Streak slow to a crawl after a few minutes use???

This is particularly obvious with SlideIT - which I find invaluable, and which becomes unusable. I need to find a way to go back to v6941 - is there a terminal emulator I can use instead of adb-windows?

Cheers

Brian

Edited September 5, 2010 by alert_bri

[Guest radddogg]

I would use the actual fastboot exe to flash the stock recovery then update the stock 1.6 before upgrading to 2.1

[Guest alert_bri]

I would use the actual fastboot exe to flash the stock recovery then update the stock 1.6 before upgrading to 2.1

Tried that - unfortunately, as Paul has added to the bottom of this post :

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:

...which is why I'm struggling to get adb-windows to recognise my Streak using the Google Android USB driver for windows XP - but it says error : device not found.

I'm trying the download method from the post here to get back to v1.6... if that works I should be able to continue to the leaked v2.1

...no joy, after downloading the v1.6 package, machine starts to load and then the message "software is up to date - system resetting"

...and then I'm back to square one... official v2.1 nice and responsive for a few minutes, and then slows to a crawl and the SlideIT keyboard becomes unusable.

Still wondering whether this is just my machine with official v2.1 which slows to a crawl after a few minutes from reset?

Cheers

Brian

Edited September 5, 2010 by alert_bri

[Guest flapheadx]

I was having some difficulties with this yesterday as well, here's what worked for me:

I went back from 2.1 (8105) to 1.6 (4399) and then on to 2.1 (6941) using the method and recovery rom found here: http://www.streaksmart.com/2010/08/how-to-...-21-update.html .

I used a terminal emulator on the rooted phone, to remove the 2.1 recovery link.

I also tried to use the 1.6 / 4399 recovery image, to go back from 2.1 / 8105, but that didn't work. It just gave me a black screen on flashing. However, the recovery ROM from the link above worked perfectly.

Before I was able to flash any recovery ROM, I first had to manually install a Windows driver for my device in fastboot mode. I picked "Android Phone" and then "Android Bootloader Interface".

Hope that helps...

[Guest radddogg]

I'll have a good look when I get home in a bit.

[Guest radddogg]

Just reading that streaksmart guide I've got an idea what it could be. I am flashing the recovery THEN copying the rom over. Maybe the overwriting of the recovery is occuring before I try to roll back to 1.6.

I'll let you know shortly

[Guest alert_bri]

I was having some difficulties with this yesterday as well, here's what worked for me:

I went back from 2.1 (8105) to 1.6 (4399) and then on to 2.1 (6941) using the method and recovery rom found here: http://www.streaksmart.com/2010/08/how-to-...-21-update.html .

I used a terminal emulator on the rooted phone, to remove the 2.1 recovery link.

I also tried to use the 1.6 / 4399 recovery image, to go back from 2.1 / 8105, but that didn't work. It just gave me a black screen on flashing. However, the recovery ROM from the link above worked perfectly.

Before I was able to flash any recovery ROM, I first had to manually install a Windows driver for my device in fastboot mode. I picked "Android Phone" and then "Android Bootloader Interface".

Hope that helps...

Well, that linked article worked pretty well for me (THANK YOU!!!)... I followed the instructions - but used the stock.bat file to do the flash recovery instead of the command line at step 9, and had to copy the fastboot-windows.exe file from elsewhere.

Because I really want to be sure that it's not some problem with my previous install of the leaked v2.1... I'm going straight to upgrading to official 2.1 from here, and if it's still wrong, I'll go back to 1.6 using this method, and then to the leaked v2.1

Cheers

Brian

[Guest alert_bri]

OMG, official v2.1 release installed over v1.6 stock from above and it's just awful - unbelievably slow and laggy... there must be something dreadfully wrong here.

Right, back to stock v1.6 and then back to leaked v2.1 (6941) - back where I started 2 days ago! O2 FAIL :P

Cheers

Brian

[Guest radddogg]

O2 FAIL :P

Quite!

[Guest radddogg]

Well that stock recovery worked. What's annoying is that I already had that version saved but was using the Modaco stock recovery off the FAQ :P/