Related
Hi guys,
I decided to give Steve's 1.5.1 another shot and found myself in a dell logo boot loop. I then decided to have a go at fixing it up using the usual tactics but accidentally selected factory reset from recovery (the recovery before you get into clockworkmod). This caused the Streak to enter an loop of attempting a factory reset, rebooting, attempting a factory reset, rebooting, attempting a factory reset, rebooting etc...
The worst part was it wouldn't boot into fastboot mode so I couldn't try pushing stock recovery.
Nothing I tried worked. I wiped everything and re-installed EVERY rom I could get my hands on with no luck. I finally decided to run the QDL Tool and I continually get the following:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Tue Dec 21 09:29:47 2010
Check image DBL: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: D:\androidsdk\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: D:\androidsdk\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 s..
Download Fail! - 2010/12/21 09:30:08
Elapsed Time: 21.18 sec
Click to expand...
Click to collapse
No matter how many times I remove the battery and try again I get the same thing. My big issue now though is that my Streak is fully unresponsive. No power at all.
Any ideas?
Krisbo
UPDATE:
I can now power on the Streak. QDL still fails and it is back to trying to factory reset itself. I can now get into clockworkmod though. Is there anything I can do from there? Maybe a nandroid restore? I don't have a nandroid backup though so I would have to download one
i was trying to install Streakdroid 2.3 ok thats cool right
well it failed hard
when i tryd to flash the new baseband amss.mbn in fastboot
i get this
Flash error -1
now it won't boot up anymore!
only get get in the volUp + power
the rest just dont work
any fixes ?
Hi, i think you must flash the baseband again !
Sry for bad english but i´m a german User
Best Regards
UKSheep
i think if you run the QDL tool that should fix the problem for you.
RDilus said:
i was trying to install Streakdroid 2.3 ok thats cool right
well it failed hard
when i tryd to flash the new baseband amss.mbn in fastboot
i get this
Flash error -1
now it won't boot up anymore!
only get get in the volUp + power
the rest just dont work
any fixes ?
Click to expand...
Click to collapse
Android Development is for Development and not Problems
Moving to General
lufc said:
Android Development is for Development and not Problems
Moving to General
Click to expand...
Click to collapse
sorry my bad
yasir_jan87 said:
i think if you run the QDL tool that should fix the problem for you.
Click to expand...
Click to collapse
more info pls
yasir_jan87 said:
i think if you run the QDL tool that should fix the problem for you.
Click to expand...
Click to collapse
QDL Tool failed also
Code:
###QDLTool: M 2.7.4.5, build ID: 1.302.20100910, time stamp: Sat Jun 11 21:24:42 2011
Check image DBL: C:\Users\RDilux\Desktop\streakflash\images\dbl.mbn ...
Check image FSBL: C:\Users\RDilux\Desktop\streakflash\images\fsbl.mbn ...
Check image OSBL: C:\Users\RDilux\Desktop\streakflash\images\osbl.mbn ...
Check image AMSS: C:\Users\RDilux\Desktop\streakflash\images\amss.mbn ...
Check image DSP1: C:\Users\RDilux\Desktop\streakflash\images\dsp1.mbn ...
Check image APPSBL: C:\Users\RDilux\Desktop\streakflash\images\appsboot.mbn ...
Check image DT: C:\Users\RDilux\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
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#ERROR[DQ4]#Download AMSS Fail!
ERROR: Download fail!
Please remove the battery and try again.
Wait for modem set up ......
Download Fail! - 2011/06/11 21:25:11
Elapsed Time: 28.16 sec
Please flash the Baseband via Fastboot... !
Befor that, check the driver !!!
Best Regards UKSheep
UKSheep said:
Please flash the Baseband via Fastboot... !
Befor that, check the driver !!!
Best Regards UKSheep
Click to expand...
Click to collapse
just like a said before
i only can asses VolUp + Power
the rest dont work so also no fastboot!
you dont need the power buttom,
take battery out,
plug in to you computer while holding the volUP button.
is that the way you do it?
RDilus said:
QDL Tool failed also
Code:
###QDLTool: M 2.7.4.5, build ID: 1.302.20100910, time stamp: Sat Jun 11 21:24:42 2011
Check image DBL: C:\Users\RDilux\Desktop\streakflash\images\dbl.mbn ...
Check image FSBL: C:\Users\RDilux\Desktop\streakflash\images\fsbl.mbn ...
Check image OSBL: C:\Users\RDilux\Desktop\streakflash\images\osbl.mbn ...
Check image AMSS: C:\Users\RDilux\Desktop\streakflash\images\amss.mbn ...
Check image DSP1: C:\Users\RDilux\Desktop\streakflash\images\dsp1.mbn ...
Check image APPSBL: C:\Users\RDilux\Desktop\streakflash\images\appsboot.mbn ...
Check image DT: C:\Users\RDilux\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
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#DEBUG: CQDLCtrl::CmdDlHexWriteImageToNAND target error:Write unsuccessful
#ERROR[DQ4]#Download AMSS Fail!
ERROR: Download fail!
Please remove the battery and try again.
Wait for modem set up ......
Download Fail! - 2011/06/11 21:25:11
Elapsed Time: 28.16 sec
Click to expand...
Click to collapse
There are two versions of qdl tool you ran the older, I have it, but not sure how to get you a copy. Any ideas? Large file over 100mb
vanemburghj said:
There are two versions of qdl tool you ran the older, I have it, but not sure how to get you a copy. Any ideas? Large file over 100mb
Click to expand...
Click to collapse
megaupload upload it there
RDilus said:
megaupload upload it there
Click to expand...
Click to collapse
Fist timer with megaupload think I did it correctly:
http://www.megaupload.com/?d=WJ8J8OMH
should be zip file with version 2.7.4.8, hope it works for you.
vanemburghj said:
Fist timer with megaupload think I did it correctly:
http://www.megaupload.com/?d=WJ8J8OMH
should be zip file with version 2.7.4.8, hope it works for you.
Click to expand...
Click to collapse
gonna download now i thanked you already for the hard work
just another error...
o year i using win7 x64 btw
Code:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Sun Jun 12 17:02:33 2011
Check image DBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\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/06/12 17:03:03
Elapsed Time: 29.57 sec
There are special settings you must use for win 7 64 bit or qdl will not work. On the road right now will post them when I get home roughly 5 hours from time of this post. Think that will fix your qdl problem.
vanemburghj said:
There are special settings you must use for win 7 64 bit or qdl will not work. On the road right now will post them when I get home roughly 5 hours from time of this post. Think that will fix your qdl problem.
Click to expand...
Click to collapse
no problem i will wait
Sorry about the late post, the wife had other ideas for the day's activities anyways here you go:
Ok go to command prompt change directory to C:\Windows\system32.
Enter the following command:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS press enter
Enter next command:
bcdedit -set loadoptions testsigning on
Reboot your computer, should see something your desktop after bootup about being test mode or something like that, at that point you know you are ready use qdl.
Run qdl tool how I do it when really brick it, which I think you did is run old version, let streak reboot or get to black screen (most likely black screen), shut down Streak, most likely by removing battery, than run newer version of qdl, reboot and you should be on BB 305. All this is not a quick process so let your Streak run for awhile, before removing battery after each boot up.
Install custom rom, don’t use Steve’s 2.0.0 amss file it is corrupted use 351 or 354 amss and dsp1.
Once your streak is up and running, need to reset your PC, go to command prompt change directory to C:\Windows\system32. Enter bcdedit /deletevalue loadoptions, once complete, enter bcdedit –set testsigning off, reboot your PC and test mode warning should be gone from your desktop.
Let me know how things turn out.
vanemburghj said:
Run qdl tool how I do it when really brick it, which I think you did is run old version, let streak reboot or get to black screen (most likely black screen), shut down Streak, most likely by removing battery, than run newer version of qdl, reboot and you should be on BB 305. All this is not a quick process so let your Streak run for awhile, before removing battery after each boot up.
Click to expand...
Click to collapse
explain this part pls lol
Do this first and if it works we will leave well enough alone, run version of qdl tool you downloaded from me. Let it go through the process and once it reboots, let it run for a bit, (mine usually takes anywhere from 10 to 20 minutes before OS starts up). If it worked right you are on BaseBand 305 and go from there. Am assuming since you tried once before you have the drivers set to Qualcomm HS-USB Diagnostics 9002, you will see that once you plug the streak in while holding volume up button.
hi guys ,
this is the situation: zenfone 2 laser ze550kl (z00ld) not work.
If i press power and volume+ it go to fastboot mode and with "fastboot devices" it is find on my pc.
If i press power and volume- it no go to recovery and it remain on logo asus in bootloop
I've tryied every guide on this site but nothing work.
Now , i want to try with asus flash tool , i've the compatible version but i have not .raw system.
Someone can help me ?
i've tryied this https://forum.xda-developers.com/ze...nks-asus-zenfone-2-laser-raw-service-t3526083 but don't work.
Thanks for the patience and sorry for my bad english :angel:
Squagghy said:
hi guys ,
this is the situation: zenfone 2 laser ze550kl (z00ld) not work.
If i press power and volume+ it go to fastboot mode and with "fastboot devices" it is find on my pc.
If i press power and volume- it no go to recovery and it remain on logo asus in bootloop
I've tryied every guide on this site but nothing work.
Now , i want to try with asus flash tool , i've the compatible version but i have not .raw system.
Someone can help me ?
i've tryied this https://forum.xda-developers.com/ze...nks-asus-zenfone-2-laser-raw-service-t3526083 but don't work.
Thanks for the patience and sorry for my bad english :angel:
Click to expand...
Click to collapse
just flash twrp using fastboot
Or use raw firmware
addy692 said:
just flash twrp using fastboot
Or use raw firmware
Click to expand...
Click to collapse
How i said i haven't a workly raw system
I've tryied to flash recovery twrp but don't work..power + volume down only restart the smartphone and when go in recovery mode after 10-20 seconds it's restart again
Squagghy said:
How i said i haven't a workly raw system
I've tryied to flash recovery twrp but don't work..power + volume down only restart the smartphone and when go in recovery mode after 10-20 seconds it's restart again
Click to expand...
Click to collapse
use this firmware and flash using qpst or fastboot simply rin fastbokt flash all
https://drive.google.com/file/d/0B43Ue6xY9MmdOGxXZ2RRQUJrOWs/view?usp=sharing
addy692 said:
use this firmware and flash using qpst or fastboot simply rin fastbokt flash all
https://drive.google.com/file/d/0B43Ue6xY9MmdOGxXZ2RRQUJrOWs/view?usp=sharing
Click to expand...
Click to collapse
after flashing nothing news :crying:
it stay on logo asus and with power+volume+ go in fastboot mode and with power+volume- it restart and restart....
p.s. qpst not find ports with phone
Squagghy said:
after flashing nothing news :crying:
it stay on logo asus and with power+volume+ go in fastboot mode and with power+volume- it restart and restart....
p.s. qpst not find ports with phone
Click to expand...
Click to collapse
I have the same problem. I have one of my friend's phone, which his brother gave him. We have no idea what has gone wrong with this phone. It just won't pass the asus logo. Also displays a BLUE SCREEN when i try to boot into recovery.
First i thought recovery must be corrupted, buti had no idea about asus phones (i own a sony phone). So i tried to flash a stock recovery through fastboot, but it didn't work. Then read from some blog to flash system.img, recovery.img and boot.img. Links were also there. Did the same but no still no use. It made it worst because on a normal boot (holding just the power button) the phone shows fastboot mode!!! Not i'm trying asus flash tool.
Tried Asus flash tool : error 5 : access denied. so i'm stuck
C:\Users\Home\Desktop\[firmware27]WW_ZE550KL_1.17.40.1234-rel-user-2016030418590
4-secured-releaseAFT_QC>fastboot_8916 format:ext4 userdata
Creating filesystem with parameters:
Size: 11915980800
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 2909175
Block groups: 89
Reserved block group size: 711
Created filesystem with 11/727664 inodes and 85558/2909175 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'userdata'...
OKAY [ 3.719s]
finished. total time: 3.734s
is the only error that result on flashing.
Squagghy said:
C:\Users\Home\Desktop[firmware27]WW_ZE550KL_1.17.40.1234-rel-user-2016030418590
4-secured-releaseAFT_QC>fastboot_8916 format:ext4 userdata
Creating filesystem with parameters:
Size: 11915980800
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 2909175
Block groups: 89
Reserved block group size: 711
Created filesystem with 11/727664 inodes and 85558/2909175 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'userdata'...
OKAY [ 3.719s]
finished. total time: 3.734s
is the only error that result on flashing.
Click to expand...
Click to collapse
my device was also bricked a month ago i can guide u
ok so now u have to try qpst
Just download qualcomm drivers and then use qpst
Contact me on telegram @ady692
addy692 said:
my device was also bricked a month ago i can guide u
ok so now u have to try qpst
Just download qualcomm drivers and then use qpst
Contact me on telegram @ady692
Click to expand...
Click to collapse
ok i try with qpst
the phone not result in any port of pc :/
Squagghy said:
ok i try with qpst
the phone not result in any port of pc :/
Click to expand...
Click to collapse
install qpst drivers
And goto fastboot and type
Fastboot erase aboot
And then take out battery insert again and connect to pc it should show as qcom 9006 port or 9008
Caution i lost my imei after unbrick so backup ur efs before doing anything
addy692 said:
install qpst drivers
And goto fastboot and type
Fastboot erase aboot
And then take out battery insert again and connect to pc it should show as qcom 9006 port or 9008
Caution i lost my imei after unbrick so backup ur efs before doing anything
Click to expand...
Click to collapse
drivers qualcomm installed, after erase aboot it appears a port 9006 but efs and qpst not found the phone
and it appears on my pc 7 local disk
Squagghy said:
drivers qualcomm installed, after erase aboot it appears a port 9006 but efs and qpst not found the phone
and it appears on my pc 7 local disk
Click to expand...
Click to collapse
firstly i suggest you to backup ur efs man
hey it would be easy if u contact somewhere else
Like telegram or phone cal
Or follow this
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I have followed the instruction but nothing good news ...phone don't work ...local disk doesn't appear on PC , only port appear but qfil failed ...i thinks that the phone cannot be restored
i've read better ..so i'm in old Qualcomm HS-USB QDLoader 9008 mode ....but there is one little problem to resolve this brick....qfil : after i choise the necessary file it fail ..sahara fail..
what's wrong ?
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
in QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
in QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Squagghy said:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
in QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
in QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
it will surely work
Just contact me on phone if
I am also making guide for this but that will take time
Unfortunately time is the only thing I do not have .... if you can post a guide to solve it would be great
Squagghy said:
Unfortunately time is the only thing I do not have .... if you can post a guide to solve it would be great
Click to expand...
Click to collapse
u are almost at the end of guide
Just try usung qfil it will work
Use different version if qpst
addy692 said:
u are almost at the end of guide
Just try usung qfil it will work
Use different version if qpst
Click to expand...
Click to collapse
used different version but nothing...i wrong something i'm sure...xD
13: C:\lui\prog_emmc_firehose_8936.mbn
01:46:17: Requested ID 13, file: "C:\lui\prog_emmc_firehose_8936.mbn"
01:46:17: ERROR: function: rx_data:247 Error occurred while reading from COM port
01:46:17: ERROR: function: sahara_main:854 Sahara protocol error
01:46:17: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Squagghy said:
used different version but nothing...i wrong something i'm sure...xD
13: C:\lui\prog_emmc_firehose_8936.mbn
01:46:17: Requested ID 13, file: "C:\lui\prog_emmc_firehose_8936.mbn"
01:46:17: ERROR: function: rx_data:247 Error occurred while reading from COM port
01:46:17: ERROR: function: sahara_main:854 Sahara protocol error
01:46:17: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
which files u r using
U should use programmef file in raw firmware folder
The link which i given to you there is firmware folder where u will find programmer file xml file and other
Specific to ur device use that
I have a simular problem. On my device gpt was erased by fault.
When I flash the firmware from subfolder "firmware/8939" with qfil (with "emmc_appsboot_8939.mbn" renamed to "emmc_appsboot.mbn"), I end up with the device booting in fastboot. But from there I can do nothing else, because the bootloader is locked. Tryed it with "flashall_AFT.cmd", but it cannot unlock bootloader ("fastboot oem unlock" gives "unkown command" error).
How can I flash partiton "gpt_both0.bin" without unlocking the bootloader? I think I need a modified "rawprogram0.xml" and "patch0.xml" for complete gpt and firmware, but how to do it?
Thanks in advance.
Mikel
Dear mates,
2 days I am trying to find answer to my problem and finally decided to start new post on exact issue I faced.
device is MI A1 with android one and current version on it was according to picture attached from recovery was tissot_10.0.19. when I took this phone from my mate to fix it was not booting with first MIUI page stacked on the screen.
fastboot output were saying:
--------------------------------------------------
C:\WINDOWS\system32>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.058s]
Finished. Total time: 0.059s
------------------------------------------------
getvar is attached
i tried to flash using miflash ver 2020.3.14 in fastboot mode but it was not successful because of locked bootloader and "locked everything".
i tried to load OTA updates using embedded recovery, but not successful, screenshot attached.
i got the error " E:Error in sideload/package.zip (Status 1)
and all time repeating error : fail to clear BCB message fail to fsync /dev/block/bootdevice/by-name/misc: operation not permitted
any option from recovery meny does not provide any result. wipe data/factory reset were stucking with erasing data notification for hours without result.
at the end i cam to EDL mode by shorting hardware test point. quallcomm driver was ok at computer Device Manager, miflash and QFIL are identifying device on com port 20 but flashing does not finish successfully , it stop at 12 sec in Miflash, and at 1,46% in QFIL. verbose log for QFIL is also attached .
main concern in QFIL log file is "IGNORING UNRECOGNIZED Attribute" stats for attributes from TARGET. my impression is phone is asking to send data in rawmode <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data> and Qfil is ignoring this attribute. as the result file copy finish with error
23:37:45: INFO: TARGET SAID: 'Finished sector address 131072'
23:37:45: DEBUG: XML FILE (92 bytes): CharsInBuffer=92-92=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
and we have repeating replies from Target as this : <?xml version="1.0" encoding="UTF-8" ?><data><log value="0 bytes received, 1048576 sectors more to go" /></data>
sorry for long explanation, the goal is to share as clear picture of the situation as possible.
i tried the same procedure with QFIL on other computer and had the same result.
now phone is in all time EDL mode. i suppose it is because i checked "erase all before configuration" option in QFIL firehose configurations.
Thanks to everyone in advance for your time and help if you could provide your suggestions how to solve the issue.
I can't solve this problem for more than 4 days and I have android 8.1 and it gives the same problem, you can do the easiest thing, as they say, edl test point, you can try but I don't recommend how you can mess up something if you were able to solve the problem, please tell me how to solve it
Try to flash stock rom via MiFlash Tool. Make sure to see COM port on MiFlash tool (press refresh to detect com port). Then after you see COM port. Flash it with "clean all" option(on the bottom). If you connect to EDL mode properly, process will be finished succesfully. But if you get some "Invalid argument, unknown error" errors, you are not connected to edl mode.
try to enter edl mode with this code in fastboot
Code:
fastboot oem edl
If it give OKAY, then you are ready to flash with Miflash tool.
There is another way to flash img files with fastboot mode. If you dont success, write here.
atc mode is not worked and I don't want to enter the testpoint, how can I tell you and the loader is not open, so this is also not a small problem as you look at it, so if there are other ideas, please send them to me
PLEASEEEEE
Testpoint is a final way. even if you cant enter testpoint, you cant do more
ivomin said:
It's ALIVE!.
Just to update that after debugging the whole windows com stack I struck on a wall and it seems that windows 7 and 10 block something there (I manage to get out of the driver to win kernel on debug but then it fails and didn't had any more nerves to deal with and I'm not a windows guy myself).
So the only solution for low lvl writing is to use linux with point boot to EDL. It seems that for mi A1 even if Qualcomm's boot chain is broken (https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html) it should fall to EDL in most cases but in our phone (global version at least) it goes to diagnostic mode (not to be confused with Download mode) regardless of drivers in windows - this is hardwired in the chip. So under linux you should fall in to download mode with hardware short of motherboard points to fall in to the correct mode. You should forget about windows as it depends too much on the selected driver (yes you can manually change driver and fu** the whole chain of communication). You need to hardwarely go to Download mode. Don't believe what windows reports.
From there you can use QDL (check documentation on how to install (you'll also need to install gcc (ubuntu - apt get install gcc) https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md).
Then download a full firmware flash from xiaomi (that's for MiFlash) and use the files in the images folder for the command ( for instance to be more easy copy images folder to qdl folder and:
./qdl --debug --storage emmc --include 'images' 'images/prog_emmc_firehose_8953_ddr.mbn' 'images/rawprogram0.xml' 'images/patch0.xml')
This will fix the first part of the qualcomm bootchain from there you will have access to fastboot and then use all other tutorials concerning fixes from fastboot.
If enough ppl want it I'll write extended tutorial in the other section.
Click to expand...
Click to collapse
Try this. It should bring you to mostly original state and from there you can fastboot unlock and proceed with installing shrp or twrp.
Hi, i have zenfone 3 Ze552KL, after 4 year of service, without reseon, the screen cant turn on. i restart phone by power+volume up.
After reboot its stuck on asus logo. After some try to reflash, always have message permission denied, partition not allowed etc...
I try format all but now its stuck on android logo (normal).
But with fastboot i can flash system.img recovery.img modem (NON-HLOS_00460e1.bin) and boot.bin.
Files extracted in WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw with asus tool (RC4).
Asus flash tool dont work (partition not allowed or write not allowed).
But dont boot again. Any idea of what other partition needed for phone boot? and/or tools for making this correctly?
ps : recovery doesnt work (cant access by power + volume down).
ps2 : sorry for bad english , i'm french.
Thanks in advance
When i try flash factory raw :
[2021-03-08T 19:47:04Z] (0x00000000) [H3AZ***********] Detected this device
[2021-03-08T 19:47:15Z] (0x00000000) [H3AZ***********] Getting OS version...
[2021-03-08T 19:47:15Z] (0x00000000) [H3AZ***********] Get the OS Version: WW_ZE552KL-13.20.10.152-
[2021-03-08T 19:47:15Z] (0x00005016) [H3AZ***********] Uploading OS Version...
[2021-03-08T 19:47:16Z] (0x00006003) [H3AZ***********] Upload to as.eservice.asus.com failed!! Server response: Cannot find any on going RMA nubmer!
[2021-03-08T 19:47:18Z] (0x00007002) [H3AZ***********] The FRP Account is Unauthorized by Server!!
[2021-03-08T 19:47:19Z] (0x00000000) [H3AZ***********] Unzip image ...
[2021-03-08T 19:47:29Z] (0x00000000) [H3AZ***********] Run flash image script ...
[2021-03-08T 19:47:31Z] (0x0000401D) [H3AZ***********] Run flash image script failure(FAILED (remote: failed to write partition))
Edit: i can only flash boot, system, modem, recovery (but dont work ...) and one or two other partition. But for example i cant flash aboot, devcfg etc...
When i try erase recovery, phone answer "remote. device is locked. cannot erase