[PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode)

[quakze]

Hahahaha, anybody in this forum brave enough to brick their YU to help us test all the steps posted in this thread? If you do, just download the zip file, extract it in an empty folder, connect your YU in Bootloader mode with your PC, and double click brick.bat. Easy isn't it?

Which OS are U using, BTW I am on Windows 10 TP 10041

What is the driver version U see in device manager for "Qualcomm HS-USB QDLoader 9008"

---------- Post added at 12:54 AM ---------- Previous post was at 12:36 AM ----------

Which OS are U using, BTW I am on Windows 10 TP 10041

What is the driver version U see in device manager for "Qualcomm HS-USB QDLoader 9008"

I have
2.0.8.7
2.0.9.3
2.1.0.5
Which one is working for U?

 

[tirta.agung]

Some Pic

Repeating once again, from point 1.

Just to do this post, I had to bricked and unbricked my YU again. Here are some pics for you:

1. After you entered the "bcdedit" command and rebooted your windows, you'll see a test mode sign (bottom right of your desktop), similar to this image.
   
   
2. Device manager 9008 mode.
   
   
3. Open Qfil, and do the things in sequence, according to marked number.
   
   
4. If succes, you'll find QFil like this.
   
   

 

[tirta.agung]

Which OS are U using, BTW I am on Windows 10 TP 10041

Douch, I'm still in Windows 7, I don't know if it would work on Windows 10. The "bcdedit" command is for Windows 7, perhaps you should search google and find a way for Windows 10.

What is the driver version U see in device manager for "Qualcomm HS-USB QDLoader 9008"

---------- Post added at 12:54 AM ---------- Previous post was at 12:36 AM ----------



I have
2.0.8.7
2.0.9.3
2.1.0.5
Which one is working for U?

I didn't update the driver in that way, though I used to and failed. That's why, the uninstall all drivers and "bcdedit" parts are important, if all success, Windows will install the appropriate driver by itself. So you don't have to choose which version.

Or, if you don't want to repeat the steps, try install the qualcomm driver from the zip attached by updating your "Qualcomm HS-USB QDLoader 9008" through device manager, choose the test folder. If after installation, Windows keeps on telling you that the driver is not signed (you will find a yellow triangle with exclamation mark beside "Qualcomm HS-USB QDLoader 9008"), then you really need to disable driver signing first. Afterwards you can run QFil, but remember to first disconnect your phone, unplug the battery for 5 seconds, replug it, and directly connect it without pressing any buttons.

 

[quakze]

Douch, I'm still in Windows 7, I don't know if it would work on Windows 10. The "bcdedit" command is for Windows 7, perhaps you should search google and find a way for Windows 10.



I didn't update the driver in that way, though I used to and failed. That's why, the uninstall all drivers and "bcdedit" parts are important, if all success, Windows will install the appropriate driver by itself. So you don't have to choose which version.

Or, if you don't want to repeat the steps, try install the qualcomm driver from the zip attached, choose the test one. If after installation, windows said the driver is not signed, then you really need to disable driver signing first. Afterwards you can run QFil, but remember to first disconnect your phone, unplug the battery for 5 seconds, replug it, and directly connect it without pressing any buttons.

Yes windows does install the drivers properly, that is 2.1.0.5.
problem is in the QFIL, it does recognice as the port in download mode, and then fails.
let me take some screen shoots. . .

 

[tirta.agung]

Quakze, do you have a hangouts account? Its better to chat trough it, then later post the success steps in this thread. My gmail is [email protected].

 

[quakze]

Quakze, do you have a hangouts account? Its better to chat trough it, then later post the success steps in this thread. My gmail is [email protected].

how about Gtalk

---------- Post added at 02:00 AM ---------- Previous post was at 01:59 AM ----------

Douch, I'm still in Windows 7, I don't know if it would work on Windows 10. The "bcdedit" command is for Windows 7, perhaps you should search google and find a way for Windows 10.



I didn't update the driver in that way, though I used to and failed. That's why, the uninstall all drivers and "bcdedit" parts are important, if all success, Windows will install the appropriate driver by itself. So you don't have to choose which version.

Or, if you don't want to repeat the steps, try install the qualcomm driver from the zip attached by updating your "Qualcomm HS-USB QDLoader 9008" through device manager, choose the test folder. If after installation, Windows keeps on telling you that the driver is not signed (you will find a yellow triangle with exclamation mark beside "Qualcomm HS-USB QDLoader 9008"), then you really need to disable driver signing first. Afterwards you can run QFil, but remember to first disconnect your phone, unplug the battery for 5 seconds, replug it, and directly connect it without pressing any buttons.

Please right click the "Qualcomm HS-USB QDLoader 9008" in device manager and check in drivers tab what is the version installed.

 

[tirta.agung]

how about Gtalk

ok gtalk, btw I thought they're both is just the same, i mean gtalk and hangouts. Just add my email, [email protected]

 

[quakze]

Quakze, do you have a hangouts account? Its better to chat trough it, then later post the success steps in this thread. My gmail is [email protected].

Invited U on Gtalk, please check !

 

[ekhasti]

Hi Ekhasti, I'll promise you to do some research on this and post a guide in this thread as soon as I 100% revive my YU.

But in a mean time, could you help Quakze and me? Could you post a reply on YU's partition map in this thread?

Here is the result

ls -al /dev/block/bootdevice/by-name/
lrwxrwxrwx root root 1970-01-24 20:23 DDR -> /dev/block/mmcblk0
p18
lrwxrwxrwx root root 1970-01-24 20:23 aboot -> /dev/block/mmcbl
k0p4
lrwxrwxrwx root root 1970-01-24 20:23 abootbak -> /dev/block/mm
cblk0p5
lrwxrwxrwx root root 1970-01-24 20:23 autobak -> /dev/block/mmc
blk0p24
lrwxrwxrwx root root 1970-01-24 20:23 boot -> /dev/block/mmcblk
0p21
lrwxrwxrwx root root 1970-01-24 20:23 cache -> /dev/block/mmcbl
k0p27
lrwxrwxrwx root root 1970-01-24 20:23 fsc -> /dev/block/mmcblk0
p16
lrwxrwxrwx root root 1970-01-24 20:23 fsg -> /dev/block/mmcblk0
p19
lrwxrwxrwx root root 1970-01-24 20:23 hyp -> /dev/block/mmcblk0
p10
lrwxrwxrwx root root 1970-01-24 20:23 hypbak -> /dev/block/mmcb
lk0p11
lrwxrwxrwx root root 1970-01-24 20:23 misc -> /dev/block/mmcblk
0p15
lrwxrwxrwx root root 1970-01-24 20:23 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1970-01-24 20:23 modemst1 -> /dev/block/mm
cblk0p13
lrwxrwxrwx root root 1970-01-24 20:23 modemst2 -> /dev/block/mm
cblk0p14
lrwxrwxrwx root root 1970-01-24 20:23 pad -> /dev/block/mmcblk0
p12
lrwxrwxrwx root root 1970-01-24 20:23 panic -> /dev/block/mmcbl
k0p23
lrwxrwxrwx root root 1970-01-24 20:23 params -> /dev/block/mmcb
lk0p22
lrwxrwxrwx root root 1970-01-24 20:23 persist -> /dev/block/mmc
blk0p26
lrwxrwxrwx root root 1970-01-24 20:23 recovery -> /dev/block/mm
cblk0p28
lrwxrwxrwx root root 1970-01-24 20:23 rpm -> /dev/block/mmcblk0
p6
lrwxrwxrwx root root 1970-01-24 20:23 rpmbak -> /dev/block/mmcb
lk0p7
lrwxrwxrwx root root 1970-01-24 20:23 sbl1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1970-01-24 20:23 sbl1bak -> /dev/block/mmc
blk0p3
lrwxrwxrwx root root 1970-01-24 20:23 sec -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 1970-01-24 20:23 ssd -> /dev/block/mmcblk0
p17
lrwxrwxrwx root root 1970-01-24 20:23 system -> /dev/block/mmcb
lk0p25
lrwxrwxrwx root root 1970-01-24 20:23 tz -> /dev/block/mmcblk0p
8
lrwxrwxrwx root root 1970-01-24 20:23 tzbak -> /dev/block/mmcbl
k0p9
lrwxrwxrwx root root 1970-01-24 20:23 userdata -> /dev/block/mm
cblk0p29
[email protected]:/ #

---------- Post added at 12:23 AM ---------- Previous post was at 12:14 AM ----------

This all things are completely new for me
but if you need any help from my side
Always at your service

If you need to contact me on Hangout (Gtalk) or Skype
ID is "ekhasti"

 

[tirta.agung]

Here is the result

---------- Post added at 12:23 AM ---------- Previous post was at 12:14 AM ----------

This all things are completely new for me
but if you need any help from my side
Always at your service

If you need to contact me on Hangout (Gtalk) or Skype
ID is "ekhasti"

Thank you very much Ekhasti, totally a good one.

 

[tirta.agung]

This all things are completely new for me
but if you need any help from my side
Always at your service
ID is "ekhasti"

Hi again Ekhasti, if you don't mind, could you help me one more time? Could you provide me a partition dump, to complete the original firmware of our YU? The size of all files would be araound 25mb, but if you zip it (best compression), it would be around 2mb. If you don't mind, here is the how to:

1. Connect your phone with ADB and type:
   

   adb shell
   su
   dd if=/dev/block/mmcblk0p13 of=/sdcard/[COLOR="Red"]modemst1.bin[/COLOR]
   dd if=/dev/block/mmcblk0p14 of=/sdcard/[COLOR="Red"]modemst2.bin[/COLOR]
   dd if=/dev/block/mmcblk0p15 of=/sdcard/[COLOR="Red"]MISC.img[/COLOR]
   dd if=/dev/block/mmcblk0p18 of=/sdcard/[COLOR="Red"]DDR.bin[/COLOR]
   dd if=/dev/block/mmcblk0p19 of=/sdcard/[COLOR="Red"]nv.tar.mbn[/COLOR]
   dd if=/dev/block/mmcblk0p22 of=/sdcard/[COLOR="Red"]param.bin[/COLOR]
   dd if=/dev/block/mmcblk0p26 of=/sdcard/[COLOR="Red"]persist.img[/COLOR]
   dd if=/dev/block/mmcblk0p27 of=/sdcard/[COLOR="Red"]cache.img[/COLOR]
   dd if=/dev/block/mmcblk0p23 of=/sdcard/[COLOR="Red"]panic.img[/COLOR]

2. You will find those files, total of 9 files (the names of those files are in red, see the code above), in your internal storage of your YU.
3. Copy those files from your phone, zip it, and please uploaded here in this thread.

I really appreciate it, if you are willing to upload those files.

 

[tirta.agung]

tirta.agung and quakze thumbs up!!
Unzipme2 download link is not there
My Yureka YU is also bricked and i want to try your method(thanks for the steps man!!:good
and i am a complete noob in terms on this, so please help me
Consider posting this yureka forums too

Hi there again, are you using windows 7 or later edition of windows (windows 8 or later). If you are using windows 7, could you reply that all steps work. We can have a google hangouts if you need to, I'll be available around 10pm Kuala Lumpur Time (GMT +8).

 

[tirta.agung]

ok gtalk, btw I thought they're both is just the same, i mean gtalk and hangouts. Just add my email, [email protected]

here all files attached.

 

[tirta.agung]

Hi, I have a question. I have to do the procedure in Coolpad F2, I have the .pcb file, I can not unzip ?.

Thank You

Hi there, the procedure and the software can be found here. Don't forget to get the right CPB files first from here, it is the one with file size 1,660.2M.

By the way, do you use windows 7? I just need to verify that all steps work with windows 7. If you use windows 7 or vista, I can guide you via google hangouts if you need to. I'll be available around 10-11pm (GMT +8, kuala lumpur time).

 

[ekhasti]

Yes, sure
But give me some time

Sent from my AO5510 using XDA Free mobile app

 

[ekhasti]

Hi again Ekhasti, if you don't mind, could y.........
......our YU? The size of all files would be araound 25mb,....
...... upload those files.

For me it's around 164.53 MB
Compress and upload on my Gdrive

 

[tirta.agung]

For me it's around 164.53 MB
Compress and upload on my Gdrive

Thank you very much, i think thats why the phone was not fully revive, the files from coolpad was just a dummy, yes I get it. By the way, do you know somebody who use windows 7 that has a hard bricked YU, that won't turn on and when connected to PC, it is recognised as QHUSB-BULK? I need to confirm that my steps at least work for windows 7. Quakze and I have tried on windows 10, but failed.On the other hand, I succeeded to run all those steps in windows 7 (not virtual edition). So it would be great if you know somebody with hard bricked YU.

 

[ekhasti]

Thank you very much, i think thats why the phone was not fully revive, the files from coolpad was just a dummy, yes I get it. By the way, do you know somebody who use windows 7 that has a hard bricked YU, that won't turn on and when connected to PC, it is recognised as QHUSB-BULK? I need to confirm that my steps at least work for windows 7. Quakze and I have tried on windows 10, but failed.On the other hand, I succeeded to run all those steps in windows 7 (not virtual edition). So it would be great if you know somebody with hard bricked YU.

I don't know any one who use win 7 with this
here attach your required files

 

[preammanikandan]

Hi there again, are you using windows 7 or later edition of windows (windows 8 or later). If you are using windows 7, could you reply that all steps work. We can have a google hangouts if you need to, I'll be available around 10pm Kuala Lumpur Time (GMT +8).

I am Using Windows 8, and i will try to install the driver by going to the advanced reboot and disable driver signature verification
and i am downloading the 1.6gb file (i have 60kbps so it would take a day ),

 

[quakze]

Yes, I can confirm that i finally manage to revive my YU. I had to brick and unbrick my YU for four times just to make sure that all steps really work, well at least for me. However, there are also step backs. Before we can get the complete dump of YU's partition from any fellow member of this forum, we can't 100% revive our YU, as in this steps we have to use YU's twin, the coolpad 8675-W00, partition dump found in its CPB file. The easily notice problem is the power management system. After reviving my YU, I can't get the battery to charge, whether the phone is on or off, or the battery stays 0% during on or off charging although it is full. So, I know that this thread will help others in reviving their death YU, but it can't be done only by Quakze or me, we also need the community, as I think this is what this forum for.

Ok now back to business. Quakze, here are the steps that work for me:

1. Download the UnzipMe2.zip and extract it to an empty folder.
2. Download "QPST 2.7.422" from here and extract it to an empty folder. It has to be this version of "QPST".
3. Download the official YU's firmware from CyanogenOS website here, and extract all the files to:
   • "ADB&fastboot" folder found in the extracted UnzipMe2 folder in STEP 1.
   • The folder that contain the previously unpacked CPB files.
4. Uninstall all the driver related to YU, as well as any Qualcomm driver if you have install any. Uninstall them through device manager FIRST, then program manager. Don't forget to reboot Windows after all process finished.
5. Run "CMD" or "Windows Terminal" as administrator and type:
   

   [COLOR="Red"]bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
   [B][COLOR="Red"]bcdedit -set TESTSIGNING OFF[/COLOR][/B][/COLOR]
   [B]REBOOT WINDOWS WHEN ALL FINISHED[/B]

6. Install the "QPST software" STEP 2) by double clicking setup.exe, not the msi file.
7. Install Qualcomm driver (UnzipMe2 folder STEP 1), according to the version of your Windows (x86 or x64), by double clicking dpinst64.exe.
8. Open "QFil.", this can be found in the install directory of "QPST" that you just installed (inside the bin folder), and afterwards, connect the phone. Upon connecting your phone to your PC, Windows will install the new driver, and "Qfil" will recognise it in 9008 mode.
9. Insert all the necessary file needed by "QFil":
   • The programmer will be prog_emmc_firehose_8936.mbn found inside the folder that contain the previously unpacked CPB files.
   • Load all xml needed:
     • Use the rawprogram0.xml found in the UnzipMe2 folder you had extracted in STEP 1.
     • Use the patch0.xml inside the folder that contain the previously unpacked CPB files.
   • Ignore anything else and click download.
   • If the process finished successfully, the phone will reboot by itself.
10. After the phone rebooted, it will suffer from an endless bootloop. Don't do anything, just disconnect it from your PC, and straight away put your phone into bootloader.
11. Go to the "ADB&fastboot" folder in STEP 3, and run format.bat by double clicking it.
12. If the process finished successfully, you phone will rebooted and it is officially 80% revived.

Please reply to me if you also experiencing battery problem.

On Windows Vista and Windows 7, with the default settings, we can’t install unsigned third party drivers. We need to enable test signing to install such drivers. We can enable this from command prompt using the below command.

bcdedit -set TESTSIGNING ON​