Hello,
I have an AT&T streak running the android 2.1 build 8105 Update.
I upgraded from 2.1 Leak build 6941, Just downloaded the rom, renamed the 8105 build and flashed it.
Since I did that the proximity sensor has quit working. Example: I'm on a phone call and when I hold the phone to my head. It doesnt turn off the screen like it should.
Any suggestions to fix this issue ?
Related
Can someone point me in the right thread to find out how I can update my AT&T Streak from build 8023 to either build 8105 or Steve's Froyo 2.2?
I know official 2.2 is about to be released next month from AT&T but i was reading on other forums that AT&T put an OTA update pushing 2.1 out a while back. I know they also canceled the update since Dell was working on 2.2 release. I can't seem to find any 2.1 AT&T update packages, all links seem to be broken everything. I don't want to go to 2.2 yet because it seems like it does have issues, but I wouldn't mind installing 2.1 on my while streak for now. Does anyone have that update package for AT&T that I could download and use for now? I'd really appreciate it. Thanks!
AT&T never had a 2.1 Update. To have that on a US Streak, you would have to download build 4399 for overseas version, then update to build 8105(2.1) again, for overseas version. You can look for guide to updating and downgrading either in General or Development section of Dell Streak forums.
Good afternoon all,
a bit of help please, searching these forums for my answer has simply confused me ...
I have a locked Streak;
2.1-update1,
baseband GAUSB1A120321-EU,
kernel 2.6.29-perf,
build number 6941
I have SIM unlocked the phone using dellstreakunlock.exe successfully.
When I try to upgrade via settings>about phone>system updates I get directed to a dead link - update.zinstaging.com
!) CAN I upgrade this firmware to a standard Dell Froyo 2.2 ROM ?
2) If so can someone please post the link I would need to put into my streak's browser?
Much appreciated ...
Dave in Catshill
there are links all over the place to the offiicial o2 froyo build.
try http://mirror2.streakdroid.com/manii/Streak_319_12792_21.pkg
that is the official build.
Thank you for the link ... however, on advice I attempted a manual upgrade from the Streak by entering the OTA link into my browser ...
I now have a bricked Streak.
I have attempted recovery techniques from Modaco, but the Streak only shows the Dell Logo and after a few seconds a blank black screen with just the buttons lit.
Can I upgrade to another 21 pkg from this situation? Would it be better to downgrade to an earlier 21 pkg from the Wiki page?
My question is ... do I need to download the recovery software or the pkg? Upgrade or downgrade?
Sorted ... flashed 1.6 recovery image using flashboot which got me going again, and once working the auto update process started leaving me with a fully operational streak running 2.2.2
FIRLST OF ALL SORRY FOR BAD ENGLISH
I GOT MY LITTEL DEVIL(DELL STREAK 5) 2 MONTHS AGO
THAN I GOT OFFICIAL UPDATE MASSAGE
THIS IS THE DOWNLOADED FILE - Streak_351_15609_00.pkg
I DOWNLOAD IT N UPDATE IT
IT UPDATES EAISLY
EARLIER MY WI-FI WAS WORKING FINE N WORKING UNTILE I DON'T UPDATE 2.2 TO 2.2.2
NOW MY WI-FI IS NOT WORKIN
WI-FI IS SCANING N SCANING............
ANDROID VER. 2.2.2
BASEBAND VER.-GAUSB1A135100-EU
KERNAL VER.-2.6.32.9-PERF
OEM VER.-GAUSB1A135100
BUILD NO.-15609
PLZZZ HELP ME
THNXXX IN ADVANCE
Hello Guys!
I have managed to upgrade my phone from ICS 4.0.4 to JB 4.1.2, but without noticing the Baseband version and Build number. My Baseband version is E160SKSMJH1 while my Build number is JZO54K.E160SKSJMH2. I don't have any problem upgrading, rooting and using the phone except the Menu Button and Back Button doesn't work anymore. My culprit is the difference between the two.
Do you guys think it is because of the difference of baseband and build # as to why my Menu and Back button does not work anymore? Which one should be used to make the buttons work again? Should I upgrade my firmware to JB 4.1.2 MH1? Or change the baseband to MH2?
Your help would be much appreciated.
Thanks!
EDIT: Oct. 13, 15 6:00PM +8GMT
Managed to fix the issue by updating Touch Firmware.