Database Users

[Q] [Help] Bricked UMI ZERO

Hey people, can anyone get me a MTK droid backup of UMI ZERO? I need it to see if i can recover my bricked UMI
pleaaasseee.....
Also, it seems my scatter file backup from MTK does not have all t info?? and SP flashtools does not accept the ones included in the Ota-updates... so if anyone please can also get me a good scatter file ... i would be much apreciated.

Hello, you can get the rom including scatter file from Needrom! Just flash trough sp tool and you will be fine.
Sent from my UMI ZERO using XDA Free mobile app

I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway

reisamm said:
I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway [/QUOTE
please tell me how did you make it work...as i am in the same boat..the pc wont recognise it
Click to expand...
Click to collapse

reisamm said:
I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway
Click to expand...
Click to collapse
please tell mew how you did it . i am so upset that my phone is absoluteley dead

Hi there raducux,
Well, this was about another situation, but mixing with ROM's cooking I was able to brick it again it was mrsim who help me (mod at china-devices.com, credit where is due). But I will tell you how I did it.
You need to have the adb android drivers installed and flashtool v5.1 or up (the one I used, but some people use the 3.1 version).
Download this ROM from needrom (scatter file compatible with FT).
Link: http://www.needrom.com/wp-content/uploads/2014/11/Y800_UMI_20141104_1907xx-s7yler.zip or
http://www.needrom.com/download/umi-zero/
Extract, and in flashtools select the scatter file inside the directory you extracted. Press flash, and (after pressing flash) connect the phone to the USB port holding the volume down key (so the phone connects in META mode), and the process should begin.
If all works well after flashing the phone should boot the new ROM, its version 3.01 so you have to upgrade it.
If that does not work, tell me a few things... I suppose the phone does not start or appear the 'Zero' logo, but tell me if when you connect it to the computer you ear the normal plugin USB sound?
FlashTools (all versions)
http://helpadude.com/sp-flash-tools/
Universal ADB Driver
http://www.needrom.com/download/universal-adb-driver/
Tell me if it worked, or if you need more help tell me what happened and how the phone responds. lot of people here also that can help. My 1st thing I check when buying a new phone (for many years now), is if it's 'XDA' Supported...
cheers

reisamm said:
Hi there raducux,
Well, this was about another situation, but mixing with ROM's cooking I was able to brick it again it was mrsim who help me (mod at china-devices.com, credit where is due). But I will tell you how I did it.
You need to have the adb android drivers installed and flashtool v5.1 or up (the one I used, but some people use the 3.1 version).
Download this ROM from needrom (scatter file compatible with FT).
Link: http://www.needrom.com/wp-content/uploads/2014/11/Y800_UMI_20141104_1907xx-s7yler.zip or
http://www.needrom.com/download/umi-zero/
Extract, and in flashtools select the scatter file inside the directory you extracted. Press flash, and (after pressing flash) connect the phone to the USB port holding the volume down key (so the phone connects in META mode), and the process should begin.
If all works well after flashing the phone should boot the new ROM, its version 3.01 so you have to upgrade it.
If that does not work, tell me a few things... I suppose the phone does not start or appear the 'Zero' logo, but tell me if when you connect it to the computer you ear the normal plugin USB sound?
FlashTools (all versions)
http://helpadude.com/sp-flash-tools/
Universal ADB Driver
http://www.needrom.com/download/universal-adb-driver/
Tell me if it worked, or if you need more help tell me what happened and how the phone responds. lot of people here also that can help. My 1st thing I check when buying a new phone (for many years now), is if it's 'XDA' Supported...
cheers
Click to expand...
Click to collapse
indeed. i too have been messing on xda a lot for a long time.
i managed to get into twrp again.
so that must be good...after. the battery died..;.butr mtk preloader doesnt instal;l
please tell me..first i need to hit download only...and after that.... ? the steps are a bit missleding .
---------- Post added at 03:10 PM ---------- Previous post was at 02:58 PM ----------
i managed to bioot the device in emui !!!! this morning..i could acces twrp. pressing volume down when connected to pc ..and the chinesse recovery pressing volume up ... rootjoy cant flash the device as it sais it is unsupported, now...i reeallly need to know the steps for going back to stock
---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------
i am running antarct s emui . with twrp recovery... i need dto know the sp flash tools steps correctly to flash back to stock
preloader doesnt install correctly in pc because volume down...takes me to twrp...and volume up...to the chinesse recovery of huawei,
so preloader starts installing, but when in recovery..it gets dissconected

Could you tell how did you put it in meta mode? I have a Zero with no preloader and in windows it shows up as unknown device. No matter how I try to boot it up (vol- vol+). Other than showing in windows, it's dead. Is there a way to revive ti?

My Zenfone 5 Hard Bricked

My zenfone 5 hard bricked It does not go to recovery or fastboot and droidboot.It also does not have USB logo on charging and led light does not work on charging only Intel inside logo appear.

Pic

Rahulraj943472 said:
My zenfone 5 hard bricked It does not go to recovery or fastboot and droidboot.It also does not have USB logo on charging and led light does not work on charging only Intel inside logo appear.
Click to expand...
Click to collapse
Use xFSTK Downloader to solve it, tested by me,
install cloverview driver and intel SoC.
don't forget to press vol + up when plug in your phone into computer.
:good:
---------- Post added at 01:17 PM ---------- Previous post was at 01:07 PM ----------
Rahulraj943472 said:
My zenfone 5 hard bricked It does not go to recovery or fastboot and droidboot.It also does not have USB logo on charging and led light does not work on charging only Intel inside logo appear.
Click to expand...
Click to collapse
Use xFSTK Downloader to solve it, tested by me,
install cloverview driver and intel SoC.
don't forget to press vol + up when plug in your phone into computer.
:good:

try this
http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911

Cloverview driver where

ryanjms07 said:
Use xFSTK Downloader to solve it, tested by me,
install cloverview driver and intel SoC.
don't forget to press vol + up when plug in your phone into computer.
:good:
---------- Post added at 01:17 PM ---------- Previous post was at 01:07 PM ----------
Use xFSTK Downloader to solve it, tested by me,
install cloverview driver and intel SoC.
don't forget to press vol + up when plug in your phone into computer.
:good:
Click to expand...
Click to collapse
I use it but my device does not detected.

Z00TD ZE551KL Zenfone 2 Laser *hard bricked*

I somehow managed to lock myself out of the phone, no boot, no fastboot recovery mode, no access through adb (device not recognized), no nothing. Anyways just looking for assistance in this. I know there must be a way, but I haven't seen anything clear enough to precisely *unbrick* my beloved ASUS Zenfone 2 Laser ZE551KL Z00TD. I've resorted to a Samsung Galaxy S5 that I rebuilt from an old broken ones spare parts. I'm more of a hardware repairer so flashing ROMS and all that is rather new to me. But I was having some success early on when trying to flash CM.13 onto it using ADB and TWRP, which is when the trouble started. I flashed the wrong recovery.img I think and somehow locked myself out completely. I'm not sure exactly what I did wrong, but after many failed attempts to flash CM.13 Marshmallow, I tried to revert back to the stock ROM and then realized that I didn't make a backup recovery.img. Doh! So now I'm completely stuck with a really nice looking paper weight. Please help! :angel:

okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...

crossmanx said:
okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...
Click to expand...
Click to collapse
I did plug in the device, while the battery was still in it, and it came up as an unrecognized device when the balloon popped up at the bottom right of the PC screen. I unplugged it, took out the battery, and plugged back in, but nothing showed up this time. Although I didn't look in device manager though. But I will try that next. What's your thoughts on helping me solve this issue? I'd really like to learn how the actual company first loads their firmware onto the devices. Like what kinds of software and equipment they use. I'm sure it's on a major scale though and probably have machines doing most of the work, just like an automobile assembly line. LOL. But I really want to get this ASUS Zenphone unbricked. So any help would be awesome. Thanks very much!

thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.

Thanks Man!!! I really appreciate the help. I'll try all this and report back. Thanks Again!

Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!

WormholeMatt said:
Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!
Click to expand...
Click to collapse
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.

crossmanx said:
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.
Click to expand...
Click to collapse
Well, here I am ready to upload the ROM to the phone using QFIL. The phone is identified by the port. The only thing I'm having trouble with now is finding the "RAWPROGRAMMER" file to load from the firmware.
I'm not sure what else to do, I can't find the file anywhere.
Maybe this is when they say I need to get ahold of someone else exact same phone, root it, load twrp, and backup their original stock rom? I'm not sure. I just feel soo close to getting this done, but I keep missing files. I'm trying to load CM.13 but inside the folders for the firmware, there isn't any file in there. I've already found the patch file and the .mbn file that I need. Just missing the rawprogrammer file.
This is giving me a headache. LOL

Actually the only file I need is the .xml file that it asks for in QFIL. Which I guess is supposed to be in the stock rom somewhere. But in order to get that, I'm guessing I'll have to use my wifes phone (she has the exact same model as I do). I'll just have to make sure to not delete anything or mess up her phone. lol
And I'm also thinking that I will have to install stock ROM first before flashing the CM.13. So I'll have to get that stock ROM from her phone, since I deleted mine on accident.

that xml file is basically a partition structure file for your phone emmc. i think it might be there in your firmware.zip
you just have to find rawprogrammer file, i think it is there where you find unbrick guide for all qualcomm devices.....you just try that file it might work for your phone too..and after adding rawprogrammer you can add firmware parts from firmware.zip file or you also can clone your wife's phone emmc, using emmc dump to raw extension.
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
you dont need to install stock rom first, only you need to send droidboot,recovery or maybe boot partitions, if you have deleted modem and other partitions, then those will also. if you get fastboot then you can flash twrp and can flash cm13.
---------- Post added at 03:09 PM ---------- Previous post was at 03:00 PM ----------
there will be different named xml file in firmware.zip for you phone's firmware you just try try yourself available xml files in firmware. if it will be wrong xml then it will auto terminate no need to worry.

What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.

flash stock firmware using this tool: maybe it works
https://androiddatahost.com/326a2

crossmanx said:
What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.
Click to expand...
Click to collapse
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol

Same problem ZE601Kl
WormholeMatt said:
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol
Click to expand...
Click to collapse
Hi Guys ,
Same problem happened for me with my Asus Zenfone 2 laser Ze601Kl.
I have tried QFIL , QPST all the qualcomm related softwares to make it work , but everytime i am getting same error " SAHARA FAIL "
I have tried with COLOR OS for One Plus One and which was having one chinese flasher and sadly that also showing the same error ,
AS far as i know i have installed the qualcomm drivers successfully and it is showing in device manager also . I have tried with Windows 7 X64 , Windows XP SP 2 . Still no luck
My phone has been dead since 1 month Somebody please help me

ZB500KL in Qualcomm HS-USB QDLoader 9008 no fastboot
Please help
I in Russia
Asus ZenFone Go ZB500KL in Qualcomm Snapdragon 410 MSM8916 detected pc only Qualcomm HS-USB QDLoader 9008. Please help

Try this https://forum.xda-developers.com/zenfone-3/help/hard-brick-asus-zenfone-3-ze520kl-t3483874/page3
Follow last post, technically you only need adb connectivity to flash all at once with one click. Hope this will help you.
Of course, now you need the rom for your device.
Sent from my ZenFone 3 using XDA Labs

crossmanx said:
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
Click to expand...
Click to collapse
Good to see anyone talking about LINUX here! I have my ZE550KL briked and the only thing I've been able to do till now are booting in fastboot and Android Recovery modes.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
Click to expand...
Click to collapse
Wow, this helped me a lot! My Linux system was not able to recognize the device but reinserting the battery and trying volumeUP+PowerButton did the trick! Now running 'fastbood devices' lists it and of course that made it visible through Virtualbox too [Windows 7 guest OS].
Now, considering that I would really like to resuscitate my phone by using LINUX, what else should I do in order to succeed?
Thanks a lot and best regards.

crossmanx said:
thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.
Click to expand...
Click to collapse
can you help me
same mode, manage to flash and download finish success.
Finish Download
Start Download
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download

sorry dude, i have no more info about asus devices. so can't help. remember only buy phones which have flashtools available like lenovo, mi, oppo, zuk etc.

ZUK Z1 Hard Bricked!!!

please help me unbricking my device currently i am unable to boot into edl, fastboot or recovery. The phone keeps on vibrating and no display.
What i did wrong was that I tried flashing a custom boot logo as said in a thread and flashed splash.img and it resulted in this.
Please help me!!!

Akshatpunj said:
please help me unbricking my device currently i am unable to boot into edl, fastboot or recovery. The phone keeps on vibrating and no display.
What i did wrong was that I tried flashing a custom boot logo as said in a thread and flashed splash.img and it resulted in this.
Please help me!!!
Click to expand...
Click to collapse
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
links :
drivers: https://mega.nz/#!FJRH2b6B!QlS9-7ppEiP9Nw_htWSMtYQWOk9KDxDxImtJZ66usaw
QPST: https://mega.nz/#!dcAQgSZT!C5JhNLnsOru6y_cX52yGzMkgfnriBY0am7nW45Bzsm0
rom: https://mega.nz/#!dFpn3BYb!Eq2i2ldpA8UJnlkjijCh4fM7EdLSaleWBRmW5rJNI84

ADDICTED777 said:
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
links :
drivers: https://mega.nz/#!FJRH2b6B!QlS9-7ppEiP9Nw_htWSMtYQWOk9KDxDxImtJZ66usaw
QPST: https://mega.nz/#!dcAQgSZT!C5JhNLnsOru6y_cX52yGzMkgfnriBY0am7nW45Bzsm0
rom: https://mega.nz/#!dFpn3BYb!Eq2i2ldpA8UJnlkjijCh4fM7EdLSaleWBRmW5rJNI84
Click to expand...
Click to collapse
Thank you sooooooo muchh!!! I almost tried everything and lost hope! This method worked like a miracle, i wish i could hit the thanks button a 1000 times! Thanks again!

Akshatpunj said:
Thank you sooooooo muchh!!! I almost tried everything and lost hope! This method worked like a miracle, i wish i could hit the thanks button a 1000 times! Thanks again!
Click to expand...
Click to collapse
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..

ADDICTED777 said:
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
Click to expand...
Click to collapse
Sure, thanks for the advice.
Btw were you able to change the splash.img/boot logo?

This state isn't named as it is hard bricked ...if it was it won't even vibrate at all...that's we call it as a hard bricked device... it was soft bricked .... in a BOOOOOOOTLOOOOOOOOOOP...
There r various type of bootloops
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
Akshatpunj said:
Sure, thanks for the advice.
Btw were you able to change the splash.img/boot logo?
Click to expand...
Click to collapse
Oh yeah two times...listen here the main thing for the devices is to choose the r8 image...should be less then 200kb & as much as less color... make sure to do it with 16bit(or less) for PNG

ADDICTED777 said:
This state isn't named as it is hard bricked ...if it was it won't even vibrate at all...that's we call it as a hard bricked device... it was soft bricked .... in a BOOOOOOOTLOOOOOOOOOOP...
There r various type of bootloops
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
Oh yeah two times...listen here the main thing for the devices is to choose the r8 image...should be less then 200kb & as much as less color... make sure to do it with 16bit(or less) for PNG
Click to expand...
Click to collapse
Oh ok! I thought i hard bricked my device but luckily you helped me
Okay i will try to change boot logo tomorrow again. Thanks a lot!

Akshatpunj said:
Oh ok! I thought i hard bricked my device but luckily you helped me
Okay i will try to change boot logo tomorrow again. Thanks a lot!
Click to expand...
Click to collapse
Yo there is a button for that ...u know I'm kind of GREEDY...

ADDICTED777 said:
Yo there is a button for that ...u know I'm kind of GREEDY...
Click to expand...
Click to collapse
Already done...

ADDICTED777 said:
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
Click to expand...
Click to collapse
I have the same problem. I went to flash a boot image and I messed up. QFIL does not detect my phone maybe beacuse Qualcomm drivers are not getting installed using the INF file.
I have shut the vibrations using the power button step. But as soon as I plug it in with volume up held down, it starts all over again.
---------- Post added at 12:26 PM ---------- Previous post was at 11:43 AM ----------
I have disabled the driver signature verification while rebooting using F8 key.
However, I still get the same error message while installing the INF file that The INF file you selected does not support this method of installation.
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
Please help!!!!

Sahaj Desai said:
I have the same problem. I went to flash a boot image and I messed up. QFIL does not detect my phone maybe beacuse Qualcomm drivers are not getting installed using the INF file.
I have shut the vibrations using the power button step. But as soon as I plug it in with volume up held down, it starts all over again.
---------- Post added at 12:26 PM ---------- Previous post was at 11:43 AM ----------
I have disabled the driver signature verification while rebooting using F8 key.
However, I still get the same error message while installing the INF file that The INF file you selected does not support this method of installation.
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
Please help!!!!
Click to expand...
Click to collapse
u need a video tutorial that shows how to install .inf file
here is the one:
https://www.youtube.com/watch?v=lJ7WTRW7psA
Now before u proceed make sure u have disabled the driver signature verification.

ADDICTED777 said:
u need a video tutorial that shows how to install .inf file
here is the one:
Now before u proceed make sure u have disabled the driver signature verification.
Click to expand...
Click to collapse
I did it using Qualcomm drivers in .exe format.
Now the phone is working fine.

Sahaj Desai said:
I did it using Qualcomm drivers in .exe format.
Now the phone is working fine.
Click to expand...
Click to collapse
:good::good::good:

Hei!!! You are the best. I followed your instructions and it seems it works 100%. You saved my day. I cant thank you enough.

ADDICTED777 said:
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
Click to expand...
Click to collapse
hey bro I just accidentally rebooted my zuk z1 in edl mode via all in one tool, but after rebooting in edl mode, screen went off and it didn't boot up again and now pc is not recognizing my device nor does the qfil detects it, its power button does not work so tried it while holding the volume up button but it's not working. I have got qpst file and zuk drivers are also installed. now please someone help me out bro. ;(

Walter Black said:
hey bro I just accidentally rebooted my zuk z1 in edl mode via all in one tool, but after rebooting in edl mode, screen went off and it didn't boot up again and now pc is not recognizing my device nor does the qfil detects it, its power button does not work so tried it while holding the volume up button but it's not working. I have got qpst file and zuk drivers are also installed. now please someone help me out bro. ;(
Click to expand...
Click to collapse
keep it charged overnight... fix the power button...then try the mentioned method...

ZUK Z1 Hard Bricked
Greetings, everyone. I've got a hard bricked zuk z1 which just went into the state all of a sudden.
I was using lineage o.s pie roms, and had faced some Random Reboots also. Not sure what happened, but here's what i did:
Installed zuk drivers
installed qualcomm drivers
installed adb and fastboot(minimal abd and fastboot)
installed qfil, which comes with QPST v2.7.0.460
--------------------------------------------------------------------------------
Downloaded the zuk stock firmware files
pressed vol+ and plugged the usb
Got detected in 9008 mode
QFIL also detected it and chose the correct files and started downloading in FLAT build
mode
now, QFIL shows this error at the end:-
Code:
10:17:52: INFO: Looking for file 'gpt_main0.bin'
10:17:52: INFO: Looking for file 'gpt_backup0.bin'
10:17:52: INFO:
Total to be tansferd with <program> or <read> is 78.85 MB
10:17:52: INFO: Sending <configure>
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
10:18:17: {ERROR: Could not write to '\\.\COM3', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times}
Writing log to 'C:\Users\HARRY\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
Log is 'C:\Users\HARRY\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Fail:Process fail
Finish Download
Hope someone can help me . Oh, by the way, the bricking is like "fully-dead" bricking. No vibrations, display, led, nothing.
I feel i haven't done anything wrong in the steps also. SO, How to decode this situation??

i am face same problem "help please expert" my zuk z1 show logo and blew light after 10se not display on screen when touch with pc via usb many partition opening with error how to solve it

Hard partition damaged
helo expert zuk z1 vibrate and show blue light black screen no display after firmware via qfil completed on PC many partition apeared not writeable only show a partition with "image" folder in witch all firmware file stored who write via qfil

naseera422 said:
helo expert zuk z1 vibrate and show blue light black screen no display after firmware via qfil completed on PC many partition apeared not writeable only show a partition with "image" folder in witch all firmware file stored who write via qfil
Click to expand...
Click to collapse
Hello there!. As far as i know, from what you've said,
The phone still vibrates and shows led, which is a good thing.
About the qfil:
Check whether you are using the latest version of QFIL. Many errors did arise while using the earlier ones.
Make sure you haven't messed up any QFIL configuration settings, and check whether the selected build type is "FLAT".
If you are having trouble with the current firmware files, then download another one for the zuk z1, and check if it works. This is because errors can come from wrong/bad programmer files.
::::: This is all assuming that there are no driver issues & that you know well, how to work with QFIL :::::
Hope this helps....

Sharp Z2 brick, no fastboot, black screen, not booting

Hi @xda Team,
couldn't find any threads releted to Sharp Z2, which would match to my issue, so that's why I'm trying it in this forum.
I have Sharp Z2 phone (https://www.gsmarena.com/sharp_z2-8410.php).
I tried to root it and to install/flash TWRP recovery on it. Because of realy less information for this phone it was difficult to find proper files.
So I tried with an official version of TWRP.... didn't worked.... after long time, I found on an chineese forum some instructions for flashing the TWRP through ADB/Fastboot.
Bacause I have successfully used this technology already several times on other phones, I was happy to have finaly found something AND forgot to check the skripts
The result is, that after unsuccessfully flashing the bootloader got blocked trough this script (OEM blocked). Now my phone is not booting. I have no access to FASTBOOT and to RECOVERY mode.
I have found an unbrick instruction for LeEco s3 (based on x620) using the SP Flashtool (I have used it successfully for my other phone LeEco S3).
Following this intruction on my Sharp I'm getting following message:
"BROM ERROR: STATUS_SEC_PL_VFV_FAIL......."
It looks to my, that I have not all permissions to flash the phone.
SO still NOT BOOTING, NO ACCESS to FASTBOOT AND TO RECOVERY MODE.
Also on XDA Forum I found this guide for an ASUS Phone (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785)
UPDATE:
SP Flashtool is not able to load the preloader file. Always stops with the same error: BROM ERROR: STATUS_SEC_PL_VFV_FAIL......."
In some forums I've read that flashing with wrong preloader can cause my issue and that in this case there is nothing there to save / recover the phone.
I still hope, that because of the Android OS there is still a chae to unbrick it.
Please HELP!!!
Thanks in advance.

mine is in a similar state but i still have access to the fastboot; i can reboot to bootloader or recovery but only to acccess fastboot. there is no recovery tool left on it and attempt to flash twrp - various versions of those have all been failed attempts. handset is still in the brick state with access to fastboot but no use.
please help to get this working again, given the fastboot is working, can i use any other recovery tool except for twrp to maybe get to having OS flashed?

Hi. On the forum 4pda have firmware under flashtool

can anybody provide correct preloader file for this phone (Sharp Z2 FS8002).?

taulu7 said:
Hi. On the forum 4pda have firmware under flashtool
Click to expand...
Click to collapse
Port Miui Hellas TEAM, my logo and splashlogo
HTML:
https://www.needrom.com/download/twrp-for-sharp-z2/
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
VanDragon said:
can anybody provide correct preloader file for this phone (Sharp Z2 FS8002).?
Click to expand...
Click to collapse
HTML:
https://4pda.ru/forum/index.php?s=&showtopic=870393&view=findpost&p=76931735

Anyone can port EUI/MIUI/Flyme or Nougat (lineage/CrDroid/RR) to Z2?
Both has same chipset Helio X20 (4/32)
LeEco Le2 X62x ROM [4pda.ru]

no changes
taras-fedora-syn said:
Port Miui Hellas TEAM, my logo and splashlogo
HTML:
https://www.needrom.com/download/twrp-for-sharp-z2/
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
HTML:
https://4pda.ru/forum/index.php?s=&showtopic=870393&view=findpost&p=76931735
Click to expand...
Click to collapse
-
-
So i follow every step but after flashing preloader there is only black screen again.
What should i do next?

zeronavigator said:
-
-
So i follow every step but after flashing preloader there is only black screen again.
What should i do next?
Click to expand...
Click to collapse
I don't understand why to flashing preloader
TWRP --- Install ROM or SuperSu.zip
firmware under flashtool
Click on the SP Flash Tool "Download" and connect the switched off phone with the Vol "-" key pressed as on the screen, the tick on the Preloader is not worth it! Release the key a few seconds after filling the 100% red bar. Wait for the end of the firmware and the appearance of a green tick. Disconnect the phone from the PC and try to turn it on

taras-fedora-syn said:
firmware under flashtool
Click on the SP Flash Tool "Download" and connect the switched off phone with the Vol "-" key pressed as on the screen, the tick on the Preloader is not worth it! Release the key a few seconds after filling the 100% red bar. Wait for the end of the firmware and the appearance of a green tick. Disconnect the phone from the PC and try to turn it on
Click to expand...
Click to collapse
So i did with a firmware i found on 4pda forum for sharp z2 using this guide http://4pda.ru/forum/index.php?showtopic=870393&st=100#entry76931735
I managed to flash using vol- with VCOM drivers.
Tried to boot the phone and nothing changed.
Black screen, short vibration on power button but no progress, no fastboot no recovery no nothing.
i also tried to find this firmware TSP-1360-0-00WW-A03-update.zip in case i was flashing wrong files but there is nowhere available for download except baidu server on witch it need an acount with a phone verification.
Still dont understand what i am doing wrong..
Any ideas?

zeronavigator said:
Any ideas?
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=870393&view=findpost&p=77195440
Spoiler - P.S.
If it doesn't work then yo need to flash the full backup,
I don't want to give my because my IMEI are there

So i managed to revive the phone.. but as expected no IMEI no Baseband blah blah blah..
..and of curse i have no backup of it.
Is there a tutorial \ guide on how to fix this problem on my sharp z2 ?
Thank you in advace

help me
can get the original rom from sharp-z2 and send the link to me download
I cannot go to baidu to download it because I am Brazilian and my number does not accept