[Streak 5 Q&A, Help & Troubleshooting] MySeLfPT:
Hi everybody,

I received a Dell's RMA some days ago and allowed it to update OTA straight from the box. It failed somehow.

Afer fastboot flashing official recovery and flashing 351's things started to work.

But then the weird behavior started when trying to update to 354's.

Flashed 354's / 351's Recovery/bb's, tried update.pkg (Md5sum verified) and it allways fails.

It doesn't update

It starts to update (stage 1), and then, when its suposed to enter stage 2 (the one where you can see a larger strong yellow bar) it just shows Dell Logo and sits there stuck.

QDL tool expires

[NOTE] I need to say that I am very familiar with the QDLtool procedure. I allways run windows in test mode and allways use the same drivers. That works fine with my old streak.

QDLtool fails too. It goes like this:

###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Mon Jul 25 14:59:41 2011
Check image DBL: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: S:\Android\# QDL\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/07/25 15:00:20
Elapsed Time: 39.59 sec

And then it boots only to show Battery percentage and turns itself off.

Old QDLtool thinks it works but it doesn't

Old QDLtool (streakflash) shows the same behavior but it actually thinks it worked showing a Green status:

Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl
Check images ok
###QDLTool: M 2.7.4.5, build ID: 1.302.20100910, time stamp: Mon Jul 25 14:47:35 2011
Check image DBL: S:\Android\# QDL\streakflash\streakflash\images\dbl.mbn ...
Check image FSBL: S:\Android\# QDL\streakflash\streakflash\images\fsbl.mbn ...
Check image OSBL: S:\Android\# QDL\streakflash\streakflash\images\osbl.mbn ...
Check image AMSS: S:\Android\# QDL\streakflash\streakflash\images\amss.mbn ...
Check image DSP1: S:\Android\# QDL\streakflash\streakflash\images\dsp1.mbn ...
Check image APPSBL: S:\Android\# QDL\streakflash\streakflash\images\appsboot.mbn ...
Check image DT: S:\Android\# QDL\streakflash\streakflash\images\DT.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#AMSS to DDR success
#DSP1 to DDR success
#DT to DDR success
#APPSBL to DDR success
#backup FSBL to DDR success
#backup OSBL to DDR success
#backup DT to DDR success
#backup APPSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download AMSS success
#Download DSP1 success
#Download DT success
#Download APPSBL success
#Download backup FSBL success
#Download backup OSBL success
#Download backup DT success
#Download backup APPSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Download success - 2011/07/25 14:48:57
Elapsed Time: 82.08 sec

It then restarts and goes the infamous stuck Dell Logo. (Yeah... i gave it a lot of time... half an hour or more).

It start's some kind of "emergency recovery" but fails

Sometimes when trying to enter fastboot mode or recovery the device shows something like this:

[White screen, black font] Starting emergency recovery ..... [after some seconds] Done.

It restarts, enters 318's recovery, flashes something (318?) and then again, reboots stuck Dell Streak Boot logo. Any idea of what this might be?

Flashing manii's update.zip of any version gives me an error with streakmod:

Afraid to flash images trough fastboot

At this point what I really want to do is flash everything trough fastboot to make whatever parts of it gone boinkers but fard's says "IT WILL BRICK YOUR STREAK FOREVER!" (no explanation given or effort to clarify).

I remember flashing boot.img and system.img before trough fastboot and it worked great. Maybe flashing some files breaks the streak?

Would anyone care to shed some light in this subject? What file's flashing breaks the streak? Why? What doesn't?

Nandroid Restore works

The only way I have to make it work and the only official ROM I am allowed to run is 351's because I have a Nandroid backup that I made before trying flashing 354's.

I can run xxx.zip's (streakdroid, simplestreak, etcetc) trough recovery. But as far as official version I am stuck with 351 unless i get a 354's nandroid backup.

Sugestions please

Any kind of information / sugestion would be of great help. But please try to stick with things that you know for a fact, "maybe this is like this" does not help me at all, it just contributes to massive confusion.

Thanks in advance,

MySeLf