27 replies to this topic

[f3661]

First of all, sorry for the bad english.

Goes with the title. I've got a bricked streak with no Dell Logo, no fastboot, no recovery, and also the qualcomm diagnostic is not available.

What I did was run a batch file:

fastboot-windows.exe -i 0x413c flash dbl images/dbl.mbn
fastboot-windows.exe -i 0x413c flash fsbl images/fsbl.mbn
fastboot-windows.exe -i 0x413c flash osbl images/osbl.mbn
fastboot-windows.exe -i 0x413c flash amss images/amss.mbn
fastboot-windows.exe -i 0x413c flash dsp1 images/dsp1.mbn
fastboot-windows.exe -i 0x413c flash dt images/dt.img
fastboot-windows.exe -i 0x413c flash appsbl images/appsboot.mbn
fastboot-windows.exe -i 0x413c flash boot images/boot.img
fastboot-windows.exe -i 0x413c flash system images/system.img
fastboot-windows.exe -i 0x413c flash userdata images/userdata.img
fastboot-windows.exe -i 0x413c flash rcfile images/rc_id.img
fastboot-windows.exe -i 0x413c flash recovery images/recovery.img
fastboot-windows.exe -i 0x413c flash logfilter images/logfilter.img
fastboot-windows.exe -i 0x413c reboot

Please help...
FYI: Tried DJ_Steve suggestion to see if linux can detect it using dmesg, but still no luck(tried using Ubuntu Lucid Lynx)

Thanks before.

[fards]

You've done something really stupid..most of the mbn aren't suitable for flashing with fastboot.

From what I understand you've now got a true brick...

[f3661]

New buzzwords : "True Bricked"

[Cue_32]

f3661, on Nov 16 2010, 16:42, said:

New buzzwords : "True Bricked"

Sorry but... Congratulations on your new Dell "St-rick"

Perhaps you could still get away with manufacturer warranty??

[f3661]

Warranty void the moment we install unofficial roms

[Cue_32]

f3661, on Nov 16 2010, 17:51, said:

Warranty void the moment we install unofficial roms

I'd time it after Froyo gets released... I know it's a different company but HTC still honored my warranty on my N1 even after having a unlocked bootloader.  The unlocked bootloader is a dead giveaway at boot up and it was supposed to mean you've officially voided warranty. Worth the shot IMO.

Good luck

[f3661]

Well I got this from my friend, so definitely I'm going to ask him to help me with this.
But since he went out of country, I'm hoping someone, anyone here can help.

[Hothan Dao]

Same here, bricked after apply update.pkg for 4399 21 build as instructed at http://android.modac...1-to-00-builds/

Dont know how to continue

[f3661]

Take out the back cover and battery, connect it to computer while pressing volume down button, see on the device manager if it recognized in anyway.

If it's recognized then you're not 'True Bricked'

[Hothan Dao]

f3661, on Nov 16 2010, 23:04, said:

Take out the back cover and battery, connect it to computer while pressing volume down button, see on the device manager if it recognized in anyway.

If it's recognized then you're not 'True Bricked'

Black screen as well. Tried Cam + Power when plugged. Can you show my what DJ_Steve has suggested you with dmesg?

Edited by Hothan Dao, 16 November 2010 - 11:08 PM.

[Hothan Dao]

Hmm, in Device Manager, is is recognized as Qualcomm CDMA Technologies MSM. But I cannot get into bootloader anymore!

[f3661]

It's supposed to be black. Does your computer recognized it as anything at all? If it is use the search tools. Keyword Qualcomm Diagnostic 9002.

[Hothan Dao]

f3661, on Nov 16 2010, 23:09, said:

It's supposed to be black. Does your computer recognized it as anything at all? If it is use the search tools. Keyword Qualcomm Diagnostic 9002.

in Device Manager, is is recognized as Qualcomm CDMA Technologies MSM with (!)

Edited by Hothan Dao, 16 November 2010 - 11:12 PM.

[f3661]

Use search tool.

[untrueparadox]

Hothan Dao, on Nov 16 2010, 15:11, said:

in Device Manager, is is recognized as Qualcomm CDMA Technologies MSM with (!)

thats actually good. it means that your baseband is bad. just download steve's QSDTool a while back and reflash the baseband. hopefully itll get it working again.

[Hothan Dao]

Quote

It's supposed to be black. Does your computer recognized it as anything at all? If it is use the search tools. Keyword Qualcomm Diagnostic 9002.

Quote

thats actually good. it means that your baseband is bad. just download steve's QSDTool a while back and reflash the baseband. hopefully itll get it working again.

Thanks. It works now. I forgot to turn testsigning on  .

[Supra2010]

Hothan Dao, on Nov 17 2010, 00:37, said:

Thanks. It works now. I forgot to turn testsigning on  .

Sorry, it seems that I have the same problem as you. I guess the baseband is somehow broken, the only thing I can do now is to plug into PC via USB without battery.

I am wondering anyway to fix the baseband? and as previously mentioned, what & where can I find Stephen's QSDtool, I do need your help.

Thanks in advance.

[Hothan Dao]

Supra2010, on Nov 16 2010, 23:47, said:

Sorry, it seems that I have the same problem as you. I guess the baseband is somehow broken, the only thing I can do now is to plug into PC via USB without battery.

I am wondering anyway to fix the baseband? and as previously mentioned, what & where can I find Stephen's QSDtool, I do need your help.

Thanks in advance.

Follow this instruction http://forums.whirlp...archive/1557150 to install driver and testsigning on
then
QSDTool is here http://downloads.str...streakflash.zip

Edited by Hothan Dao, 16 November 2010 - 11:50 PM.

[Supra2010]

Hothan Dao, on Nov 17 2010, 00:49, said:

Follow this instruction http://forums.whirlp...archive/1557150 to install driver and testsigning on
then
QSDTool is here http://downloads.str...streakflash.zip

Thanks a lot, really need to have a try!! I will update result soon~~~

[Supra2010]

Supra2010, on Nov 17 2010, 00:52, said:

Thanks a lot, really need to have a try!! I will update result soon~~~

WOOOO, thanks a lot!!!! I really did it...

"IT WOKRS, MY DELL STREAK BACK TO LIFE, THANKS FOR EVERYONE ABOVE"