So i recently got hold of a job lot of streaks, managed to resurrect a couple by running the qdl tool (older streakflash version) and one worked with the latest qdl tool ('repairtool' as the folder is named). These have now gone to friends and family and are all working fine so a sucess story there.
I now have the 3 'faulty' devices left, none of whice turn on show any signs of life BUT 2 were detected through volume up + usb and i ran qdl on both of them, both suceeded (see log below) but still show no signs of life and are now no longer detected through volume up + usb.
Just thought id post here before going down the JTAG route to see if anyone had any ideas first.
Code:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Tue Nov 02 15:53:54 2010
Check image DBL: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: B:\dell\DS22OFW\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 ......... Okay
Check version ... DT:y3.752
version-baseband: AUS_100908_01_BOSS_EVT3_FROYO_RE
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
fastboot download: DSP1, checksum: 0x29ca9e8d ...
fastboot download: DT, checksum: 0xce136d64 ...
fastboot download: APPSBL, checksum: 0xf55e1594 ...
fastboot download: boot, checksum: 0x22a73395 ...
INFO: download system would take more than 1 minute, please wait ...
fastboot download: system, checksum: 0x28ea5dd5 ...
fastboot download: userdata, checksum: 0xfe9ef69a ...
erasing 'logfilter'... OKAY
fastboot download: recovery, checksum: 0x8872a076 ...
fastboot download: rcfile, checksum: 0x77fbeecc ...
fastboot download: osbl_bak, checksum: 0x29dcffb8 ...
fastboot download: amss_bak, checksum: 0x8bcb76e2 ...
fastboot download: dsp1_bak, checksum: 0x29ca9e8d ...
fastboot download: dt_bak, checksum: 0xce136d64 ...
fastboot download: appsboot_bak, checksum: 0xf55e1594 ...
fastboot download: recovery_bak, checksum: 0x8872a076 ...
fastboot download: logfilter, checksum: 0x1bad7a9c ...
.......Download android successed.
Download success - 2010/11/02 15:56:51
Elapsed Time: 177.40 sec
Code:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Thu Oct 28 14:53:36 2010
Check image DBL: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\DS22OFW\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 ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A120621
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
fastboot download: DSP1, checksum: 0x29ca9e8d ...
fastboot download: DT, checksum: 0xce136d64 ...
fastboot download: APPSBL, checksum: 0xf55e1594 ...
fastboot download: boot, checksum: 0x22a73395 ...
INFO: download system would take more than 1 minute, please wait ...
fastboot download: system, checksum: 0x28ea5dd5 ...
fastboot download: userdata, checksum: 0xfe9ef69a ...
erasing 'logfilter'... OKAY
fastboot download: recovery, checksum: 0x8872a076 ...
fastboot download: rcfile, checksum: 0x77fbeecc ...
fastboot download: osbl_bak, checksum: 0x29dcffb8 ...
fastboot download: amss_bak, checksum: 0x8bcb76e2 ...
fastboot download: dsp1_bak, checksum: 0x29ca9e8d ...
fastboot download: dt_bak, checksum: 0xce136d64 ...
fastboot download: appsboot_bak, checksum: 0xf55e1594 ...
fastboot download: recovery_bak, checksum: 0x8872a076 ...
fastboot download: logfilter, checksum: 0x1bad7a9c ...
.......Download android successed.
Download success - 2010/10/28 14:57:26
Elapsed Time: 229.76 sec
EDIT: I would just like to add that during the sucessfull qdl runs above neither of the devices actually powered up and went into fastboot mode as they usually would.
I've since opened these streaks up to check the internals, on looking everything looks intact so i think i can rule out an internal hardware fault. The internal sd cards however i removed and inserted into a windows 7 machine at which point i was asked to format, both are wanting to format at 244 mb so it seems the qdl tool has wiped them both clean. I've never seen this behaviour before running the qdl tool so i have no idea whats happened any thoughts anyone ? also what could have caused the streak to be no longer recognised after running qdl on them ?
p.s. i've been on the streaks irc channel a few times but no ones seems to be around.
drkdeath5000 said:
I've since opened these streaks up to check the internals, on looking everything looks intact so i think i can rule out an internal hardware fault. The internal sd cards however i removed and inserted into a windows 7 machine at which point i was asked to format, both are wanting to format at 244 mb so it seems the qdl tool has wiped them both clean. I've never seen this behaviour before running the qdl tool so i have no idea whats happened any thoughts anyone ? also what could have caused the streak to be no longer recognised after running qdl on them ?
p.s. i've been on the streaks irc channel a few times but no ones seems to be around.
Click to expand...
Click to collapse
you really dont know how internal sd partition works do you?
internal sd using ext2 partition.. therefore it is not working in windows environment and thats why windows suggest to format ...
internal sd is partitioned to 2 split... 244mb and the rest...
the reason that it shows 244mb is because windows unable to recognize any partition more than 1 for anything similar to thumbdrives...
and for qdl.. sorry i cant answer because i never used it even once...
deysmacro said:
you really dont know how internal sd partition works do you?
internal sd using ext2 partition.. therefore it is not working in windows environment and thats why windows suggest to format ...
internal sd is partitioned to 2 split... 244mb and the rest...
the reason that it shows 244mb is because windows unable to recognize any partition more than 1 for anything similar to thumbdrives...
and for qdl.. sorry i cant answer because i never used it even once...
Click to expand...
Click to collapse
Thanks for taking the time to reply i have no idea how the internal sd card partition works but i have loaded up my linux virtual machine and can see the partitions so it seems qdl has done its work after all. So something else must be preventing it from booting up.
Im considering the JTAG route but im not convinced even that would fix them. Considering the QDL (streakflash) tool bricked them in the first place whats the chances of it working the next run ? I may end up paying for the JTAG only to find that QDL bricks them again so im wondering what to do. The problem is i have no history of these devices so it could be anything really, unless i can be certain of what caused it well its not really worth the risk is it...
drkdeath5000 said:
Im considering the JTAG route but im not convinced even that would fix them. Considering the QDL (streakflash) tool bricked them in the first place whats the chances of it working the next run ? I may end up paying for the JTAG only to find that QDL bricks them again so im wondering what to do. The problem is i have no history of these devices so it could be anything really, unless i can be certain of what caused it well its not really worth the risk is it...
Click to expand...
Click to collapse
if you are using jtag route... most probably the streak could only be used as wifi tablet... no more phone function anymore... that is what being reported though...
deysmacro said:
if you are using jtag route... most probably the streak could only be used as wifi tablet... no more phone function anymore... that is what being reported though...
Click to expand...
Click to collapse
Think I had a kind of breakthrough here - I've been scratching my head considering sending my Streak off to one of those jtag places to get it working again. But alas! No need.
I've tried the QDL tool maybe 25 times and though it says success, I still couldn't boot or get into fastboot by any combinations of keys.
But tonight I successfully booted into the stock rom - this is how:
Make sure all your drivers are there. I used Win7 x64 so I know it can be done. Then get your hands on the QDL tool. Start the QDL.exe. Plug your bricked Streak in with the usb cable. Hold the volume up button (or whatever the button closest to the headphone jack is) until you see your Qualcomm HS-USB Diagnostics 9002 port in the QDL application. Click "Run". Let the application do its thing for a few seconds until the moment you see "DT is in fastboot mode" (I think it said) on your device with white text on an otherwise black screen. Yank your usb cable out! If you see the "Fastboot mode" you waited too long. In that case, pull your battery and start again. Then start a command window where you have your fastboot.exe and recovery.img. Mine was in C:\Fastboot. I then ran fastboot flash recovery recovery.img. After a few seconds the device reported success. Then I ran fastboot reboot. I then waited maybe 20 seconds. Nothing happened. So I tried the power button. Holy fark a Dell logo! I don't know why, but it worked.
So maybe you could give this a try before jtagging your Streak and reportedly risking losing all GSM functionality. If this helped you out, make sure to thank and share your success story. Peace.
I havent done that,but i will remember. . . . . But i like the way your thinking. . . . . Good job
posted from my Pimped out Dell
sturmavik said:
Think I had a kind of breakthrough here - I've been scratching my head considering sending my Streak off to one of those jtag places to get it working again. But alas! No need.
I've tried the QDL tool maybe 25 times and though it says success, I still couldn't boot or get into fastboot by any combinations of keys.
But tonight I successfully booted into the stock rom - this is how:
Make sure all your drivers are there. I used Win7 x64 so I know it can be done. Then get your hands on the QDL tool. Start the QDL.exe. Plug your bricked Streak in with the usb cable. Hold the volume up button (or whatever the button closest to the headphone jack is) until you see your Qualcomm HS-USB Diagnostics 9002 port in the QDL application. Click "Run". Let the application do its thing for a few seconds until the moment you see "DT is in fastboot mode" (I think it said) on your device with white text on an otherwise black screen. Yank your usb cable out! If you see the "Fastboot mode" you waited too long. In that case, pull your battery and start again. Then start a command window where you have your fastboot.exe and recovery.img. Mine was in C:\Fastboot. I then ran fastboot flash recovery recovery.img. After a few seconds the device reported success. Then I ran fastboot reboot. I then waited maybe 20 seconds. Nothing happened. So I tried the power button. Holy fark a Dell logo! I don't know why, but it worked.
So maybe you could give this a try before jtagging your Streak and reportedly risking losing all GSM functionality. If this helped you out, make sure to thank and share your success story. Peace.
Click to expand...
Click to collapse
Ive been pretty much having the same issue as you. My streak was completely dead showing no signs of life, however it was being detected by QDL tool. Unfortunately before i could do anything to get the streak working, i know can no longer get the device to be detected by device manager or QDL tool. All the necessary drivers are installed as the device was previously being detected. Any idea as to what may have happened?
Thanks
Related
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:
PHP:
###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:
PHP:
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:
!less_then_int(1291344359, getprop("ro.build.date.utc"))
E: error in /sdcard/update.zip
(status 7)
Installation aborted
Click to expand...
Click to collapse
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
Anyone? :s
Sent from the Streak, because size matters.
At this point ill be happy if someone sent me a full nandroid backup.of 360.
Sent from the Streak, because size matters.
still having the same problem.
Could someone PLEASE send me a 407 nandroid backup?
thanks in advance
MySeLfPT said:
still having the same problem.
Could someone PLEASE send me a 407 nandroid backup?
thanks in advance
Click to expand...
Click to collapse
no one is going to send you a nandroid because it contains all their account information, I don't understand why people don't get that.
If a nandroid will restore your phone but you are unable to flash a recovery and then an update.pkg then that means you are flashing corrupt files that are not being correctly read OR you have a corrupt SD card that has sectors that can't be overwritten and are only compatible with the nandroid you have. So my suggestion is to download EVERYTHING again for whatever ROM you want to be on and start over, if it won't go through, then use your nandroid to get running again and replace your inner sd
A nandroid backup of a freshly "factory reseted" ROM does not contain, AFAIK user data.
No corrupt data (double checked by Md5).
2nd device with the same simptoms (both refursbs straight from Dell). While it may be in fact, the inner SD, the device works 100% OK with custom ROM's and opening a brand new streak "just because" seems a bit overkill for me.
So, could someone please send my a nandroid backup of 407 (freshly Factory reseted)?
Thanks in Advance
MySeLfPT said:
A nandroid backup of a freshly "factory reseted" ROM does not contain, AFAIK user data.
No corrupt data (double checked by Md5).
2nd device with the same simptoms (both refursbs straight from Dell). While it may be in fact, the inner SD, the device works 100% OK with custom ROM's and opening a brand new streak "just because" seems a bit overkill for me.
So, could someone please send my a nandroid backup of 407 (freshly Factory reseted)?
Thanks in Advance
Click to expand...
Click to collapse
A nandroid of a fresh factory reset is like painting a new car... that makes zero sense, do you understand the irrelevance of what you are asking for?
It makes sense because its the only way that allows me to flash it. If I could flash with standart pkgs it wouldnt make sense.
How about a nandroid of DSC ROM fresh or the Cyanogen that a lot of us are trying out....?
I'm tempted to flash 407 clean and create a nandroid just to send to ya and see if that helps, your situation has me intrigued
Aight my man, I have you a fresh nandroid of stock Olleh 407.
Already rooted
ESFileExplorer installed with root permission so that I could rename the install-recovery.sh file with .bak so it wouldn't overwrite StreakMod
And except for that I haven't done anything else to it.
How do you suggest we go about getting this to you?
Thanks, thats really great. Please, upload a passworded rar/7zip/whatever to mediafire or anyoother file.host and send me a private message with details. Ill give u feedback asap.
Thanks in advance.
Thank you for sending the nandroid backup. It worked beautifully. My Streak is now on Official 407 flashed via Nandroid restore.
Will try a update.pkg update now.
MySeLfPT said:
Thank you for sending the nandroid backup. It worked beautifully. My Streak is now on Official 407 flashed via Nandroid restore.
Will try a update.pkg update now.
Click to expand...
Click to collapse
Hit that thanks button several times
That's odd as heck, but I hope you can get something to flash, I've never seen such. I don't understand how the innerds of the Streak are accepting to be rewritten via the nandroid, but won't let the stock recovery unpack the update.pkg
.... now something just hit me... have you tried going into the LOST.DIR folder on your SD card, deleting everything in it, and then trying to flash again...?
If you didn't know (and I didn't know this for the longest time), that's where all your files are unpacked to. If you take one of those files and copy it to your computer and all the extension .zip to it, those are the files from the update.pkg
Apparently there isn't any software anywhere that can decrypt Dell .pkg files except for the factory recovery.
Just a quick update:
Installing 407's update (with 407's recovery) package still fails (reboots in the middle of the process and hangs at Dell logo).
Ill try and clean "Lost.Dir" to see if it makes any diference.
nope, it doesnt make any diference (deleting LOST.DIR). replacing external SD card doesnt help too. :S
Ok... Only thing I can think left to do is maybe send a PM to TheManii or one of the other recognized devs and ask them nicely to take a peek at the thread and and the same time log the update process. Do you know what I mean? Run adb logcat DURING the update process and have it writing to a text file so that they can dissect it and see why it fails
SGS II I9100 from TapaTalk
Hello!
I can't flash my dell streak via QDLTool and my device is bricked now
Kind Regards!
log:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Fri Sep 30 23:33:32 2011
Check image DBL: C:\Streak\repairtool\images\dbl.mbn ...
Check image FSBL: C:\Streak\repairtool\images\fsbl.mbn ...
Check image OSBL: C:\Streak\repairtool\images\osbl.mbn ...
Check image AMSS: C:\Streak\repairtool\images\amss.mbn ...
Check image DSP1: C:\Streak\repairtool\images\dsp1.mbn ...
Check image APPSBL: C:\Streak\repairtool\images\appsboot.mbn ...
Check image DT: C:\Streak\repairtool\images\DT.img ...
Check image boot.img: C:\Streak\repairtool\images\boot.img ...
Check image system.img: C:\Streak\repairtool\images\system.img ...
Check image userdata.img: C:\Streak\repairtool\images\userdata.img ...
Check image recovery.img: C:\Streak\repairtool\images\recovery.img ...
Check image logfilter.img: C:\Streak\repairtool\images\logfilter.img ...
Check image Region: C:\Streak\repairtool\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/09/30 23:34:17
Elapsed Time: 45.03 sec
same problem here
i try streakflash also, all done successfully,but still in same situation ,no fastboot no recovery , only hang on dell logo
Any solution for this? I'm also in this jam.
are you running 64 bit windows? If so there are some special instructions that need to be followed. There is a flash video here that shows you how:http://www.streakdroid.com/modules.php?name=Downloads&d_op=viewdownload&cid=2
It's the win64 tutorial file at the bottom. I just used it Monday and it worked flawlessly.
lordmorphous said:
are you running 64 bit windows? If so there are some special instructions that need to be followed. There is a flash video here that shows you how:http://www.streakdroid.com/modules.php?name=Downloads&d_op=viewdownload&cid=2
It's the win64 tutorial file at the bottom. I just used it Monday and it worked flawlessly.
Click to expand...
Click to collapse
Thanks for the links, but I think its broken...I am also stuck at the same place...can you please help?
Thanks!
I don't know how much help I can be aside from the tutorial videos. I just followed them and it worked.
Make sure your drivers are installed correctly for adb. You can start with this post:
http://forum.pocketables.net/showpost.php?p=59264&postcount=2
Hi everyone,
yes, I have done a lot of reading of unbricking tutorials and threads, including this one:
http://forum.xda-developers.com/showthread.php?t=982906&highlight=bricked&page=2
Unfortunately, the solutions that work for others, did not work for me.
I bought used Streak off Ebay, The seller stated that the Streak was flashed with custom 2.4.4 version. Upon receive I switched it on, the Streak booted up, then suddenly rebooted in, like 10 seconds. After that, it stuck at Dell logo.
Since it has the custom recovery ClockworkMod v2.5.0.1, I downloaded some custom ROMs and tried to flash them. I was able to get to recovery mode and install the ROM stored on the CD card. After rebooting the device, it never booted up completely. It just freeze on StreakDroid logo, when I installed StreakDroid 2.0, or just rebooting in a loop with "resetting factory defaults. please wait" sign when I flashed ver.2.4.4
Well, I decided to go ahead and to install the factory recovery and stock ROM.
No luck! (I guess, that's important point): I can't get to fastboot mode by pressing [camera]+[power] buttons. The white screen does not come up (as it should, I believe), the screen and buttons remain dark.
Next, I tried the Streakflash.It has done it's job with a green background screen,
and messaged something like this:
Code:
blahblahblah
#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/11/25 10:25:16
Elapsed Time: 82.69 sec
After that, instead of switching to fastboot mode, the device just turns off and I just can see the battery charge indicator for about 5 seconds.
Afterwards, I tried the QDLTool (which I believe is extended version of the StreakFlash)
This one returned the timeout error:
Code:
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.
I double checked that the Dell R288920 drivers were installed, and tried it on different PCs and different USB ports.
Another reason it's NOT a driver issue is that the Streak can't get into fastboot mode aside of PC, by pressing [camera]+[power] buttons
After all, the Streak is "attempting" to load the OS, if I disconnect the battery for about 20 minutes or longer. But it never completed the boot-up process, freezing halfway.
Will much appreciate if any of you guys can point me to a right direction, how possibly can I get my streak back to life.
Thanks.
PS. I'm using 32 bit win7 ultimate
which version of qdltool did you use?? i had same problam with mine and once qdltool got to the point of looking for the phone in fastboot mode it would fail
what i had to as download the oldest version of qdltool from here
http://mirror2.streakdroid.com/manii/Tools/
download version (10323)
it worked for me , let me know if this helps
[email protected] said:
which version of qdltool did you use?? i had same problam with mine and once qdltool got to the point of looking for the phone in fastboot mode it would fail
what i had to as download the oldest version of qdltool from here
mirror2.streakdroid.com/manii/Tools
download version (10323)
it worked for me , let me know if this helps
Click to expand...
Click to collapse
are you referring to the QDLtool, or a command prompt fastboot and ADB programs?
It looks like that version 10323 you are referring to is a fastboot zip archive, not QDLtool
The qdltool I have is M 2.7.4.5 and M 2.7.4.8
Thanks.
right let me think here lol i have so many files on ,my comp trying to find right ones,
so youve tried both those versions and none work?
after using the 2.7.4.5 version, have you tried getting into fastboot mode by holding the camera button?
---------- Post added at 01:16 PM ---------- Previous post was at 12:59 PM ----------
ok it was 2.7.4.5 i used heres the log from it
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: Wed Dec 07 01:19:45 2011
Check image DBL: C:\Documents and Settings\andy\Desktop\streakflash\images\dbl.mbn ...
Check image FSBL: C:\Documents and Settings\andy\Desktop\streakflash\images\fsbl.mbn ...
Check image OSBL: C:\Documents and Settings\andy\Desktop\streakflash\images\osbl.mbn ...
Check image AMSS: C:\Documents and Settings\andy\Desktop\streakflash\images\amss.mbn ...
Check image DSP1: C:\Documents and Settings\andy\Desktop\streakflash\images\dsp1.mbn ...
Check image APPSBL: C:\Documents and Settings\andy\Desktop\streakflash\images\appsboot.mbn ...
Check image DT: C:\Documents and Settings\andy\Desktop\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/12/07 01:21:09
Elapsed Time: 83.73 sec
as you can see it doesnt do the (wait for adb device)
this is the version that fixed mine
[email protected] said:
Download success - 2011/12/07 01:21:09
Elapsed Time: 83.73 sec
as you can see it doesnt do the (wait for adb device)
this is the version that fixed mine
Click to expand...
Click to collapse
I just edited my post, so you can see, I tried both versions.
Earlier one returned no error message, nor fixed the phone.
UPDATE:
I left the battery out of the phone for approx 1 hour. After I put it back and switched the phone on, the Streak loaded the OS completely!
It was alive for about 5 minutes, I even caught some text messages, before it froze completely.
have you tried a factoey reset via the dell recovery menu?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
why was this moved to q+a, this isnt a question, hes looking for help, wasnt asking anything
He hung a [Q] label on the original post, thus it was moved.
Please! help me!
I`m using Rom 360 and last night, i up rom 407 Olleh. When rom updating finish, Streak reboot and freeze logo Dell, not bootting fastboot = Power + Camera.
i`m tried QDL:
1/ Streakflash:.......ok and reboot
2/ QDLtool 2.7.4.8: .....
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Mon Feb 13 02:52:51 2012
Check image DBL: D:\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: D:\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: D:\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: D:\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: D:\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: D:\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: D:\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: D:\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: D:\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: D:\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: D:\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: D:\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: D:\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! - 2012/02/13 02:53:20
Elapsed Time: 29.04 sec
Streak no change ADB device, I don`t undertand what happned?
I need to get into fastboot mode (to flash the correct files) or anyhow get my phone working
I`m tried:
1) Run streakflash version from the streakflash.zip(after extraction though).
2) Boot into diagnostic mode (Vol Up + Power button) and connect the USB cable to the computer. 'Qualcomm HS-USB Diagnostics 9002' will show in the port field in streakflash QDL tool.
3) Hit the run button. The process should stop at success.
4) Disconnect USB cable and close streakflash QDL tool.
5) Now run the QDL tool that came in repairtool.zip (after extraction though).
6) Boot the Streak into diagnostic mode (Vol Up + Power button) and connect the USB cable to the computer. 'Qualcomm HS-USB Diagnostics 9002' will show in the port field in QDL tool.
7) Hit the run button. The process should stop at success. If not, dont forget try again and again. Make sure you change USB ports (to which you are connecting ur streak) on ur system too.
...but...not work.....!!
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
Try again but just with the old qdl called also streakflash , don't repeat with the new qdl the process, immediately go to fasbootmod after ONLY the first step , fastboot will be there, the rest you already know
This should help a lot of people if their Streak is in a bricked/non functional state or if you want to reset everything to stock 2.2. QDL Tool will Unbrick/Repair your phone and install Froyo 2.2 on it from the image. You should then be able to root /install custom ROMs or simply update it with stock 2.3.3.
QDL Repair Tool: https://www.dropbox.com/sh/zafy2mn4ygcflez/k_NG62Q1MI
ADB Driver: ftp://ftp.dell.com/Handheld/R288920.exe
Here's what you need to do:
Download the QLD Tool folder from the Dropbox as a zip file.
Unzip the contents in C:
1. Press the volume up button and keep holding it after five seconds(approx) connect the USB cable(The other end should always be connected to the computer) while holding the volume up button until you hear a ding sound from your windows pc. Now open device manager and check for driver listing in the "Unknown" section named "Qualcomm CDMA Technologies MSM".
If the device is listed as “Qualcomm CDMA Technologies MSM” under “Other Devices”…
a.Right-click on it and select “Update Driver Software”.
b.Select “Browse my computer for driver software”.
c.Select “Let me pick from a list of device drivers on my computer”.
d.Click “Show All Devices” and then click “Next”.
e.Select “Have Disk”.
f.Select “Browse”.
g.Select the folder containing the drivers. For us, the drivers will be located somewhere like “C:\Streak\repairtool\QDLTool…\Drivers\Driver_2.067\Win32”. (Without the quotes, of course.)
h.Select “qcser.inf”, and hit “OK”.
i.Under “Manufacturer”, select “Qualcomm Incorporated”.
j.Under “Model”, select “Qualcomm HS-USB Diagnostics 9002”. Select “Next”.
k.You may get a warning. Hit “Yes” if you do.
l.Once Windows installs those drivers, hit “Close”.
m.Your Streak should now be listed as “Qualcomm HS-USB Diagnostics 9002”, under “Ports”.
2. Download the adb driver and install it. To check whether the driver has installed properly. power on the dell streak holding the camera button simultaneously. streak will give a white screen with fastboot on the right most corner. Enter fast boot mode by tapping on it and the screen will tell that it is waiting for a usb connection. Now connect the streak to the PC. You should hear a ding and the device manager will show "Android 1.0" if the drivers are installed correctly.
Now we have the pre-requisites for the diagnostic mode and fast boot mode.
Run the QDL tool. Now press and hold the volume button while connecting the computer. If the qualcomm drivers were correctly installed you will see that name(qualcomm …) in the port setion.
Click Run. This tool is going to take a lot of time. Here we are carrying out diagnostics and also installing Froyo with BB 306.
It will reboot several times since it has to enter fast boot mode to install recovery and flash the rom. If at the end, all the logs turn out green, Congrats, you have repaired your device. Exit the tool, unplug the device and reboot.
I successfully revived my Streak using this method. Wish you all good luck.
TheManii has had the flashing tools available for some time, but the link has admittedly been difficult to find. Not having an alternate link to download the files from will lead to disaster if the site ever permanently goes down, so keep your links up and running as long as you can. Pinning this thread would be useful.
Dell Streak Flashing Tools
Strephon Alkhalikoi said:
TheManii has had the flashing tools available for some time, but the link has admittedly been difficult to find. Not having an alternate link to download the files from will lead to disaster if the site ever permanently goes down, so keep your links up and running as long as you can. Pinning this thread would be useful.
Dell Streak Flashing Tools
Click to expand...
Click to collapse
Thanks mate! I will do my best.
baba_baba said:
This should help a lot of people if their Streak is in a bricked/non functional state or if you want to reset everything to stock 2.2. QDL Tool will Unbrick/Repair your phone and install Froyo 2.2 on it from the image. You should then be able to root /install custom ROMs or simply update it with stock 2.3.3.
QDL Repair Tool: https://www.dropbox.com/sh/zafy2mn4ygcflez/k_NG62Q1MI
ADB Driver: ftp://ftp.dell.com/Handheld/R288920.exe
Here's what you need to do:
Download the QLD Tool folder from the Dropbox as a zip file.
Unzip the contents in C:
1. Press the volume up button and keep holding it after five seconds(approx) connect the USB cable(The other end should always be connected to the computer) while holding the volume up button until you hear a ding sound from your windows pc. Now open device manager and check for driver listing in the "Unknown" section named "Qualcomm CDMA Technologies MSM".
If the device is listed as “Qualcomm CDMA Technologies MSM” under “Other Devices”…
a.Right-click on it and select “Update Driver Software”.
b.Select “Browse my computer for driver software”.
c.Select “Let me pick from a list of device drivers on my computer”.
d.Click “Show All Devices” and then click “Next”.
e.Select “Have Disk”.
f.Select “Browse”.
g.Select the folder containing the drivers. For us, the drivers will be located somewhere like “C:\Streak\repairtool\QDLTool…\Drivers\Driver_2.067\Win32”. (Without the quotes, of course.)
h.Select “qcser.inf”, and hit “OK”.
i.Under “Manufacturer”, select “Qualcomm Incorporated”.
j.Under “Model”, select “Qualcomm HS-USB Diagnostics 9002”. Select “Next”.
k.You may get a warning. Hit “Yes” if you do.
l.Once Windows installs those drivers, hit “Close”.
m.Your Streak should now be listed as “Qualcomm HS-USB Diagnostics 9002”, under “Ports”.
2. Download the adb driver and install it. To check whether the driver has installed properly. power on the dell streak holding the camera button simultaneously. streak will give a white screen with fastboot on the right most corner. Enter fast boot mode by tapping on it and the screen will tell that it is waiting for a usb connection. Now connect the streak to the PC. You should hear a ding and the device manager will show "Android 1.0" if the drivers are installed correctly.
Now we have the pre-requisites for the diagnostic mode and fast boot mode.
Run the QDL tool. Now press and hold the volume button while connecting the computer. If the qualcomm drivers were correctly installed you will see that name(qualcomm …) in the port setion.
Click Run. This tool is going to take a lot of time. Here we are carrying out diagnostics and also installing Froyo with BB 306.
It will reboot several times since it has to enter fast boot mode to install recovery and flash the rom. If at the end, all the logs turn out green, Congrats, you have repaired your device. Exit the tool, unplug the device and reboot.
I successfully revived my Streak using this method. Wish you all good luck.
Click to expand...
Click to collapse
Hi I have Windows 7 with 64 bit. I have tried with above drivers as mentioned but due to OS version problem I couldn't follow the steps. Is there any solution for this?
nsrpani said:
Hi I have Windows 7 with 64 bit. I have tried with above drivers as mentioned but due to OS version problem I couldn't follow the steps. Is there any solution for this?
Click to expand...
Click to collapse
The following drivers should work for Windows 7 64 bit:
http://www-307.ibm.com/pc/support/site.wss/MIGR-69999.html
If not, you may need to install more drivers. Please follow the post
http://anomaloushacker.blogspot.com.au/2011/01/qualcomm-usb-drivers-for-windows-7-x64.html
It is a bit complicated and over detailed but the drivers should work
Cheers
baba_baba said:
The following drivers should work for Windows 7 64 bit:
http://www-307.ibm.com/pc/support/site.wss/MIGR-69999.html
If not, you may need to install more drivers. Please follow the post
http://anomaloushacker.blogspot.com.au/2011/01/qualcomm-usb-drivers-for-windows-7-x64.html
It is a bit complicated and over detailed but the drivers should work
Cheers
Click to expand...
Click to collapse
Thanks for your quick response. While clicking on first link, it is going to Lenovo site - http://support.lenovo.com/en_ZA/ . Suggest me on this.
Update
Hi
As we all know Dell Streak is a tricky phone to work with and if this process doesn't work for you or f you get stuck somewhere, please try and repeat the process from the beginning. This has worked for many of us.
I apologize if the links get broken in time. I had to spend hours and hours to locate the drivers/links. If they get deleted, I am happy to send the files to you if required.
Cheers
Baba
hi can you post the driver for win 7 64 bit?
the links r dead
thanks
baba_baba said:
Hi
As we all know Dell Streak is a tricky phone to work with and if this process doesn't work for you or f you get stuck somewhere, please try and repeat the process from the beginning. This has worked for many of us.
I apologize if the links get broken in time. I had to spend hours and hours to locate the drivers/links. If they get deleted, I am happy to send the files to you if required.
Cheers
Baba
Click to expand...
Click to collapse
Driver
jakmal said:
hi can you post the driver for win 7 64 bit?
the links r dead
thanks
Click to expand...
Click to collapse
Please try the following:
http://www.driverscape.com/download/qualcomm-cdma-technologies-msm
i got stuck here after following every single steps........
Code:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Mon Jan 27 10:09:21 2014
Check image DBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\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 ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A1355B00
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
[color=red]sending 'AMSS' (15708 KB)... FAILED (data transfer failure (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...[/color]
ERROR[DA1]: download AMSS Fail!
whalesplaho said:
i got stuck here after following every single steps........
Code:
................
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
[color=red]sending 'AMSS' (15708 KB)... FAILED (data transfer failure (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...[/color]
Click to expand...
Click to collapse
same happen to me
is there any body ???
HELPPP !!!
After installing right ADB driver now another error
......................
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A140614
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
sending 'AMSS' (15708 KB)... FAILED (status read failed (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...
sending 'boot' (3180 KB)... FAILED (command write failed (Too many links))
ERROR[DA1]: download boot Fail!
Best of luck!! There are tons of info for Streak. I switch between moto x and streak.
Sent from my XT1053 using xda app-developers app
Did someone have same problem as me ?
My Dell was keep restarting on Dell logo and there was no access to recovery and fastboot.
I tried with QDL and everything went good , but still no access to fastboot and recovery.
Only change is that Dell is no more restarting , only stays on Dell logo.
Please help
Streak 5 - Cannot copy system via QDL
Dear all,
I have a DELL streak 5 and having already stoned at DELL logo.
I tried QDL yet it ends like below:
HW:
Board ID:
Comment:
--
LOG
--
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Sat Aug 08 07:49:43 2015
Check image DBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: D:\DELL\TOOL1\QDL Tool\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 ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A130500
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
fastboot download: DSP1, checksum: 0x29ca9e8d ...
fastboot download: DT, checksum: 0xce136d64 ...
fastboot download: APPSBL, checksum: 0xf55e1594 ...
fastboot download: boot, checksum: 0x22a73395 ...
INFO: download system would take more than 1 minute, please wait ...
fastboot download: system, checksum: 0x28ea5dd5 ...
sending 'system' (212695 KB)... FAILED (unknown status code)
ERROR[DA1]: download system Fail!
Download Fail! - 2015/08/08 07:52:14
Elapsed Time: 151.30 sec
Please tell me what to do.
thank you.
@jayanthap: http://forum.xda-developers.com/showpost.php?p=62244448&postcount=3