8
OnePlus One Unbrick Tutorial- HARDBRICK- 100% dead phone only

  1. soare95
    Honeycomb Apr 7, 2015

    soare95 , Apr 7, 2015 :


    OnePlus Unbrick Tutorial- HARDBRICk- 100%dead phone only

    https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
    https://mega.co.nz/#!BkpwyYSB!rkYSkFI...
    16GB Firmware: https://www.hightail.com/download/UlR...
    64GB Firmware: https://www.hightail.com/download/UlR...

    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
    bcdedit.exe -set TESTSIGNING ON


    fastboot flash modem NON-HLOS.bin
    fastboot flash sbl1 sbl1.mbn
    fastboot flash dbi sdi.mbn
    fastboot flash aboot emmc_appsboot.mbn
    fastboot flash rpm rpm.mbn
    fastboot flash tz tz.mbn
    fastboot flash LOGO logo.bin
    fastboot flash boot boot.img
    fastboot flash userdata userdata/64G.img
    fastboot flash system system.img
    fastboot flash recovery recovery.img
    fastboot flash cache cache.img
     

    #1
  2. mihaignat
    Froyo Apr 17, 2015


    #2
  3. srsdani
    Gingerbread Apr 23, 2015


    #3
  4. Fantomy
    Ice Cream Sandwich Apr 26, 2015

  5. Fantomy
    Ice Cream Sandwich Apr 26, 2015


    #5
  6. Marmota
    Jelly Bean May 6, 2015

    Marmota , May 6, 2015 :
    Modificati numele la titlu in SOFTBRICK

    Hardbrick nu se mai poate repara prin nicio metoda.
     

    #6
    zahar likes this.
  7. xelybry
    Donut Jun 1, 2015

    xelybry , Jun 1, 2015 :
    am si eu o mare problema, si poate cineva de aici, poate sa ma indrume si pe mine... am cumparat un OPO 64GB de la un amic care l-a comandat de afara. Telefonul a venit sigilat, fara nici o problema, varianta internationala si cu incarcator de europa... frumos, dragalas, nimic de zis... l-am desigilat, am bagat carteluta, l-am pornit, si de aici a inceput cosmarul... dupa setarile de baza, telefonul a inceput sa descarce actualizari... m-am gandit ca sunt doar la aplicatii, si nicidecum ca descarca automat si actualizarea de sistem android... am dat "instaleaza" si m-am pomenit cu "ACADEAUA"... am spus ca n-o fi mare scofata, si am incercat sa-l utilizez... fratilor, nush cum sa va spun, dar telefonul imi depaseste toate dezamagirile pe care le-as putea avea... sotia mea are un Mobistel Cynus T5, de generatie mai veche (Android 4.2(Jelly Bean), Quad Core Processor with 4 x 1,2GHZ, 5,0″ HD(1.280 x 720 Pixel), IPS LCD, Capacitive Touchscreen, 12 Megapixel Camera and 2Megapixel FrontCamera, 4GB Rom, 1GB Ram, External MicroSD-card slot up to 32GB) pe care am instalat un live wallpaper cu un acvariu cu pesti... pe acest telefon minune, respectiv OPO, acest wallpaper nu poate sa ruleze oricat m-as chinui... a doua mare problema, este ca orice soft de navigare as instala, partea de GPS face figuri si nu vrea sa functioneze nicicum atunci cand sunt in afara, conectat la GPS, DATE MOBILE, 3G, si toate optiunile de localizare bifate pe ACTIV... a mai intalnit cineva aceasta problema, sau doar eu m-am "usurat in scaldatoare cand eram mic" de am un asa noroc?
     

    #7
  8. srsdani
    Gingerbread Jun 9, 2015

    srsdani , Jun 9, 2015 :
    E hardbrick toata ziua dar ai vrut sa faci si tu un post acolo sa fie la numar. Softbrick e cand e un bootloop, sau ramane oneplus pe ecran sau lucruri de gen. Ala e hardbrick toata ziua.
     

    #8
    FirstAdvisor likes this.
  9. Marmota
    Jelly Bean Jun 17, 2015

    Marmota , Jun 17, 2015 :
    Din pacate nu fac spam ca multi de pe acest forum.
    Asa ca daca nu stii istoria pentru post te-as sfatui sa nu comentezi degeaba si ma simt ciudat sa iti zic tie asta mai ales ca am vazut ca te mai pricepi la chestii de genu asta ... dar deh poate unii chiar fac post cont.

    Daca te uiti la film scrie "press ... until you see fastboot mode" si ala din pacate nu este hard brick este un soft.

    Hardbrick este atunci cand nu ai disponibil fastboot mode sau recovery sau orice vrei tu - aka telefonul nu porneste sub nicio forma nu afiseaza nimic pe ecran (nici ledul de power).
    Singura metoda e cu driverele de Qualcom si cu mdm downloader (sau toolul de recovery) care sa rescrie toate partitiile ca sa poti intra apoi in fastbood mode
     

    #9
    zahar and Deactivated User like this.
  10. srsdani
    Gingerbread Jun 17, 2015

    srsdani , Jun 17, 2015 :
    Vrei sa pari interesant. Dupa ce rescrii partitiile normal ca intri în fastboot. Un alt comentariu inutil din partea ta. Bravo.
     

    #10
  11. FirstAdvisor
    Gingerbread Jun 20, 2015

    FirstAdvisor , Jun 20, 2015 :
    Pai omul asta a facut, pana nu a rescris partitiile, nu a putut intra in modul fastboot. Ergo HARD BRICK...

    Acuma, na... e clar.. La Braila iti da cu vaporul in cap...
     

    #11
    bopedo and Rolodex like this.
  12. ljflevy
    Gingerbread Sep 4, 2015

  13. sam1502
    Cupcake Oct 10, 2015

    sam1502 , Oct 10, 2015 :

    When I press "start" my phone gets disconnected,can somenone advice me on what to do,or can someone give me the commands that the Tool does when flashing on the phone so I can do it mannualy?


    Cand apas "start" telefonul se deconecteaza(nu mai apare nici la Device manager),orice fac se deconecteaza dupa ce apas start,poate cineva binevoitor sa ma sfatuiasca cu privire la ce este de facut,sau sa-mi spuna mai exact ce face Msmtool,astfel sa pot sa scriu comenzile manual fara tool(desi cred ca ar fii super greu atat timp cat am de flash-uit vreo 40 de lucruri)
     
    Last edited: Oct 10, 2015

    #13
  14. wapmaster13
    Cupcake Oct 31, 2015


    #14
  15. srazvan2005
    Cupcake Nov 20, 2015

    srazvan2005 , Nov 20, 2015 :
    salut
    1. dupa update ai facut factory reset?
    eventual din recovery (la alt telefon a trebuit sa recurg la acest pas recomandat chiar de producator sa fie facut dupa update
    2. incerca sa nu ai nimic in tel cand faci primul boot dupa factory reset (cartela sim sau card)
    sper sa te ajute
     

    #15
  16. alay_30
    Cupcake Jan 10, 2017

    alay_30 , Jan 10, 2017 :
    hey i hardbricked my phone recently and i tried the above method and i did manage to enter in fastboot mode. But now the problem is that my bootloader is locked and i even tried to unlock with the command oem unlock but it still doen't unlock. Can someone please help me!!
     

    #16
  17. Borisake
    Cupcake Oct 29, 2017

    Borisake , Oct 29, 2017 :
    Va salut! Apelez si eu la voi cu o rugaminte. Am un OnePlus 2, si pe langa simul de la DIGI, am bagat si un sim de la Vodafone doar de net. Ei din momentul ala, telefonul a luat-o razna.
    Daca-l aprind nu pot sa-i deblochez displayul, trebuie sa-l lasa sa se inchida si dupa sa mai incerc, ba mi se inchide din senin daca urmaresc ceva pe el, si tot asa. Nu mai functioneaza ca in prima zi. Ma dispera. Sau reactioneaza foarte greu si foarte tarziu. Gen, apelez pe cineva si nu face nimic si fara sa exagerez, dupa un minut apeleaza singur si el...
    Am incercat sa-i dau revenire la setarile de fabrica, nimic. Am intrat in meniul ascuns sau cum se numeste (nu ma pricep la informatica, bata este desteapta la treaba asta) am dibuit ce sa-i fac, dar tot asa fara niciun rezultat. Banuiesc ca i-a crapat ANDROIDUL.
    Intrebarea si rugamintea mea, este cineva din Bucuresti care se pricepe sa reinstaleze androidul? Am fost la un service de telefoane si mi-a recomandat sa caut pe cineva care a mai facut treaba asta ca cica este un android mai special OxygenOS 3.6.0 asta si ca ei nu se baga.
    Va rog frumos daca puteti sa ma indrumati la cineva din Bucuresti care sa ma scape de beleaua asta. In teorie mai am garantie la telefon, l-am cumparat acum 1 an de la cineva, dar am inteles caci garantia este in CHINA...deci...
    Va multumesc frumos!
     

    #17
  18. bitsgoanitin
    Cupcake Sep 24, 2018

    bitsgoanitin , Sep 24, 2018 :
    Hi
    Thanks a lot for wonderful tool. But I have an issue and few others at different forums asked about that..I could not find solution to that.. The issue is, even after following all the instructions properly.. my phone keeps installing the same file, i.e., "8974_msimage.mbn" in loop. I also noticed that after every installation of this file phone gets disconnected from PC and again gets connected automatically.. The loop continues indefinitely..
    Therefore I tried QFIL to do the same thing (I guess it does same thing).. I got the files installed (at least QFIL showed it as successfully done) but nothing happens even after that... Not sure if it is actually installed or not.. It will be very kind of you if you can suggest how to get out of loop... and is it possible to recover my OPO? TIA...I am sharing the log file of QFIL as follows:
    2018-09-24 12:47:08.837 12:47:08: INFO: {percent files transferred 100.00%}
    2018-09-24 12:47:08.837 12:47:08: INFO: ==============================================================
    2018-09-24 12:47:08.837 12:47:08: INFO: Files used and their paths
    2018-09-24 12:47:08.837 12:47:08: INFO: 1 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
    2018-09-24 12:47:08.837 12:47:08: INFO: 2 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\rawprogram0_64G.xml'
    2018-09-24 12:47:08.837 12:47:08: INFO: 3 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\system.img'
    2018-09-24 12:47:08.837 12:47:08: INFO: 4 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\persist.img'
    2018-09-24 12:47:08.837 12:47:08: INFO: 5 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\cache.img'
    2018-09-24 12:47:08.837 12:47:08: INFO: 6 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\userdata_64G.img'
    2018-09-24 12:47:08.837 12:47:08: INFO: 7 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\NON-HLOS.bin'
    2018-09-24 12:47:08.837 12:47:08: INFO: 8 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\sbl1.mbn'
    2018-09-24 12:47:08.837 12:47:08: INFO: 9 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\sdi.mbn'
    2018-09-24 12:47:08.837 12:47:08: INFO: 10 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\emmc_appsboot.mbn'
    2018-09-24 12:47:08.837 12:47:08: INFO: 11 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\rpm.mbn'
    2018-09-24 12:47:08.853 12:47:08: INFO: 12 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\boot.img'
    2018-09-24 12:47:08.853 12:47:08: INFO: 13 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\tz.mbn'
    2018-09-24 12:47:08.853 12:47:08: INFO: 14 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\modemst.bin'
    2018-09-24 12:47:08.853 12:47:08: INFO: 15 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\dynamic_nvbk.bin'
    2018-09-24 12:47:08.853 12:47:08: INFO: 16 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\static_nvbk.bin'
    2018-09-24 12:47:08.853 12:47:08: INFO: 17 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\recovery.img'
    2018-09-24 12:47:08.853 12:47:08: INFO: 18 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\logo.bin'
    2018-09-24 12:47:08.853 12:47:08: INFO: 19 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\DRIVER.ISO'
    2018-09-24 12:47:08.853 12:47:08: INFO: 20 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\reserve4.img'
    2018-09-24 12:47:08.853 12:47:08: INFO: 21 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\gpt_main0_64G.bin'
    2018-09-24 12:47:08.853 12:47:08: INFO: 22 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\gpt_backup0_64G.bin'
    2018-09-24 12:47:08.853
    2018-09-24 12:47:08.853 12:47:08: INFO: _ (done)
    2018-09-24 12:47:08.853 12:47:08: INFO: | |
    2018-09-24 12:47:08.853 12:47:08: INFO: __| | ___ _ __ ___
    2018-09-24 12:47:08.853 12:47:08: INFO: / _` |/ _ \| '_ \ / _ \
    2018-09-24 12:47:08.868 12:47:08: INFO: | (_| | (_) | | | | __/
    2018-09-24 12:47:08.868 12:47:08: INFO: \__,_|\___/|_| |_|\___|
    2018-09-24 12:47:08.868 12:47:08: INFO: {All Finished Successfully}
    2018-09-24 12:47:08.868
    2018-09-24 12:47:08.868 12:47:08: INFO: Overall to target 113.015 seconds (9.41 MBps)
    2018-09-24 12:47:08.868 12:47:08: INFO: {percent files transferred 100.00%}
    2018-09-24 12:47:08.868
    2018-09-24 12:47:08.868 Writing log to 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
    2018-09-24 12:47:08.868
    2018-09-24 12:47:08.868
    2018-09-24 12:47:08.868 Log is 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
    2018-09-24 12:47:08.868
    2018-09-24 12:47:08.868 ***** Working Folder:C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
    2018-09-24 12:47:09.724
    2018-09-24 12:47:09.724 Base Version: 17.11.16.14.34
    2018-09-24 12:47:09.724 Binary build date: Nov 21 2017 @ 02:53:33
    2018-09-24 12:47:09.724 Incremental Build version: 17.11.21.02.53.33
    2018-09-24 12:47:09.740
    2018-09-24 12:47:09.740 12:47:09: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
    2018-09-24 12:47:09.740 ************************************************
    2018-09-24 12:47:09.740 C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --sendxml=patch0.xml --search_path=E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
    2018-09-24 12:47:09.740 ************************************************
    2018-09-24 12:47:09.740
    2018-09-24 12:47:09.740 12:47:09: INFO: Current working dir (cwd): C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
    2018-09-24 12:47:09.740 12:47:09: INFO: Showing network mappings to allow debugging
    2018-09-24 12:47:09.740 12:47:09: INFO:
    2018-09-24 12:47:09.740
    2018-09-24 12:47:09.740
    2018-09-24 12:47:09.740
    2018-09-24 12:47:09.740 12:47:09: INFO: Trying to store 'patch0.xml' in string table
    2018-09-24 12:47:09.740 12:47:09: INFO: Looking for file 'patch0.xml'
    2018-09-24 12:47:09.740 12:47:09: INFO: User wants to talk to port '\\.\COM6'
    2018-09-24 12:47:09.740 12:47:09: INFO: Took 0.00000000 seconds to open port
    2018-09-24 12:47:09.740 12:47:09: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
    2018-09-24 12:47:09.755 12:47:09: INFO: If you don't want this, use --dontsorttags
    2018-09-24 12:47:09.755
    2018-09-24 12:47:09.755 12:47:09: INFO: Sending <configure>
    2018-09-24 12:47:09.755
    2018-09-24 12:47:09.755 12:47:09: INFO: TARGET SAID: 'Host's payload to target size is too large'
    2018-09-24 12:47:09.755 12:47:09: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 131072
    2018-09-24 12:47:09.755 12:47:09: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 131072
    2018-09-24 12:47:09.755 12:47:09: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
    2018-09-24 12:47:09.755
    2018-09-24 12:47:09.755 12:47:09: INFO: TARGET SAID: 'Patched sector 9 with 0747BFDE'
    2018-09-24 12:47:09.755
    2018-09-24 12:47:09.755 12:47:09: INFO: TARGET SAID: 'Patched sector 122142694 with 0747BFDE'
    2018-09-24 12:47:09.755
    2018-09-24 12:47:09.755 12:47:09: INFO: TARGET SAID: 'Patched sector 1 with 0747BFDE'
    2018-09-24 12:47:09.755
    2018-09-24 12:47:09.755 12:47:09: INFO: TARGET SAID: 'Patched sector 122142719 with 0747BFDE'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'Patched sector 1 with 0747BFFF'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'Patched sector 122142719 with 0747BFFF'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'Patched sector 122142719 with 0747BFDF'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'crc start sector 2, over bytes 4096'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'Patched sector 1 with 89C2BFC0'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'crc start sector 122142687, over bytes 4096'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'Patched sector 122142719 with 89C2BFC0'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'Patched sector 1 with 00000000'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'crc start sector 1, over bytes 92'
    2018-09-24 12:47:09.771
    2018-09-24 12:47:09.771 12:47:09: INFO: TARGET SAID: 'Patched sector 1 with EE76EF2D'
    2018-09-24 12:47:09.787
    2018-09-24 12:47:09.787 12:47:09: INFO: TARGET SAID: 'Patched sector 122142719 with 00000000'
    2018-09-24 12:47:09.787
    2018-09-24 12:47:09.787 12:47:09: INFO: TARGET SAID: 'crc start sector 122142719, over bytes 92'
    2018-09-24 12:47:09.787
    2018-09-24 12:47:09.787 12:47:09: INFO: TARGET SAID: 'Patched sector 122142719 with 07B434E9'
    2018-09-24 12:47:09.787 12:47:09: INFO: ==============================================================
    2018-09-24 12:47:09.787 12:47:09: INFO: Files used and their paths
    2018-09-24 12:47:09.787 12:47:09: INFO: 1 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
    2018-09-24 12:47:09.787 12:47:09: INFO: 2 'E:\OPORecoveryTool(64GB) (1)\OnePlusRestoreTool\patch0.xml'
    2018-09-24 12:47:09.787
    2018-09-24 12:47:09.787 12:47:09: INFO: _ (done)
    2018-09-24 12:47:09.787 12:47:09: INFO: | |
    2018-09-24 12:47:09.787 12:47:09: INFO: __| | ___ _ __ ___
    2018-09-24 12:47:09.787 12:47:09: INFO: / _` |/ _ \| '_ \ / _ \
    2018-09-24 12:47:09.787 12:47:09: INFO: | (_| | (_) | | | | __/
    2018-09-24 12:47:09.787 12:47:09: INFO: \__,_|\___/|_| |_|\___|
    2018-09-24 12:47:09.802 12:47:09: INFO: {All Finished Successfully}
    2018-09-24 12:47:09.802
    2018-09-24 12:47:09.802 12:47:09: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.407 seconds (0.00 Bps)
    2018-09-24 12:47:09.802
    2018-09-24 12:47:09.802 Writing log to 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
    2018-09-24 12:47:09.802
    2018-09-24 12:47:09.802
    2018-09-24 12:47:09.802 Log is 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
    2018-09-24 12:47:09.802
    2018-09-24 12:47:09.802 ***** Working Folder:C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
    2018-09-24 12:47:09.990
    2018-09-24 12:47:09.990 Base Version: 17.11.16.14.34
    2018-09-24 12:47:10.005 Binary build date: Nov 21 2017 @ 02:53:33
    2018-09-24 12:47:10.005 Incremental Build version: 17.11.21.02.53.33
    2018-09-24 12:47:10.005
    2018-09-24 12:47:10.005 12:47:09: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
    2018-09-24 12:47:10.005 ************************************************
    2018-09-24 12:47:10.005 C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --setactivepartition=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
    2018-09-24 12:47:10.005 ************************************************
    2018-09-24 12:47:10.005
    2018-09-24 12:47:10.005 12:47:09: INFO: Current working dir (cwd): C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
    2018-09-24 12:47:10.005 12:47:09: INFO: Showing network mappings to allow debugging
    2018-09-24 12:47:10.021 12:47:09: INFO: User wants to talk to port '\\.\COM6'
    2018-09-24 12:47:10.021 12:47:09: INFO: Took 0.00000000 seconds to open port
    2018-09-24 12:47:10.021 12:47:09: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
    2018-09-24 12:47:10.021 12:47:09: INFO: If you don't want this, use --dontsorttags
    2018-09-24 12:47:10.021
    2018-09-24 12:47:10.021 12:47:09: INFO: Sending <configure>
    2018-09-24 12:47:10.021
    2018-09-24 12:47:10.021 12:47:09: INFO: TARGET SAID: 'Host's payload to target size is too large'
    2018-09-24 12:47:10.021 12:47:09: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 131072
    2018-09-24 12:47:10.021 12:47:09: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 131072
    2018-09-24 12:47:10.021 12:47:09: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
    2018-09-24 12:47:10.021 12:47:09: INFO: Sending <setbootablestoragedrive>
    2018-09-24 12:47:10.021
    2018-09-24 12:47:10.021 12:47:09: INFO: TARGET SAID: 'Set bootable drive to 0.'
    2018-09-24 12:47:10.037 12:47:09: INFO: ==============================================================
    2018-09-24 12:47:10.037 12:47:09: INFO: Files used and their paths
    2018-09-24 12:47:10.037 12:47:09: INFO: 1 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
    2018-09-24 12:47:10.037
    2018-09-24 12:47:10.037 12:47:09: INFO: _ (done)
    2018-09-24 12:47:10.037 12:47:09: INFO: | |
    2018-09-24 12:47:10.037 12:47:09: INFO: __| | ___ _ __ ___
    2018-09-24 12:47:10.037 12:47:09: INFO: / _` |/ _ \| '_ \ / _ \
    2018-09-24 12:47:10.037 12:47:09: INFO: | (_| | (_) | | | | __/
    2018-09-24 12:47:10.037 12:47:09: INFO: \__,_|\___/|_| |_|\___|
    2018-09-24 12:47:10.037 12:47:09: INFO: {All Finished Successfully}
    2018-09-24 12:47:10.037
    2018-09-24 12:47:10.037 12:47:09: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.063 seconds (0.00 Bps)
    2018-09-24 12:47:10.037
    2018-09-24 12:47:10.037 Writing log to 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
    2018-09-24 12:47:10.037
    2018-09-24 12:47:10.037
    2018-09-24 12:47:10.037 Log is 'C:\Users\NITIN SHARMA\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
    2018-09-24 12:47:10.052
    2018-09-24 12:47:10.068 Download Succeed
    2018-09-24 12:47:10.068 Finish Download


     

    #18