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.
Related
Okay so my phone was rooted, I unrooted it successfully and flashed a stock ROM. Just as I was about to sell the phone as now have galaxy s5 the phone said it needed an update (official Samsung) so I let it do its thing but when the update completed the phone screen went black and did not come back on and since then the phone shows no signs of life what so ever.
After a bit of research I have found out that this is a corrupt boot loader and there is a way to fix it ( the phone is an s4 i9505) this is done by using a piece of software but my problem is I cannot get the software to recognise the phone
I have tried to install the qualcomm drivers with some success in command prompt but I can still not get my computer to successfully install them as the phone is not showing up in the software.
When connecting to the computer I do hear the 'd don' sound showing that the phone is being recognised and the computer attempts to install the windows drivers (using windows 7) but always fails
Any help would be appreciated
Thanks alot
i rule123 said:
Okay so my phone was rooted, I unrooted it successfully and flashed a stock ROM. Just as I was about to sell the phone as now have galaxy s5 the phone said it needed an update (official Samsung) so I let it do its thing but when the update completed the phone screen went black and did not come back on and since then the phone shows no signs of life what so ever.
After a bit of research I have found out that this is a corrupt boot loader and there is a way to fix it ( the phone is an s4 i9505) this is done by using a piece of software but my problem is I cannot get the software to recognise the phone
I have tried to install the qualcomm drivers with some success in command prompt but I can still not get my computer to successfully install them as the phone is not showing up in the software.
When connecting to the computer I do hear the 'd don' sound showing that the phone is being recognised and the computer attempts to install the windows drivers (using windows 7) but always fails
Any help would be appreciated
Thanks alot
Click to expand...
Click to collapse
open in system setting, hardware devices.
if you plug in your phone, you see for few seconds qualcomm qshub or so. then click it right and install the driver manually.
if you have open the properties Menue, you can work with.
konsolen said:
open in system setting, hardware devices.
if you plug in your phone, you see for few seconds qualcomm qshub or so. then click it right and install the driver manually.
if you have open the properties Menue, you can work with.
Click to expand...
Click to collapse
I have tried this method and I can navigate to the driver but when installing I get a message saying that windows cannot install
qualcomm bootmode is very easy to repair.
But only if you know what you must do exactly.
I played with a dead sony sp 6 months, after i get it back to life from qualcomm mode.
now i waked up many sony and samsung from qualcomm boot mode.
if you install the correct driver, i can send you a repair tool.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
i rule123 said:
I have tried this method and I can navigate to the driver but when installing I get a message saying that windows cannot install
Click to expand...
Click to collapse
then you have the wrong driver. which one you installed?
there are for 32 and 64 bit windows. for qualcomm usb mode and also other qualcomm modes.
konsolen said:
qualcomm bootmode is very easy to repair.
But only if you know what you must do exactly.
I played with a dead sony sp 6 months, after i get it back to life from qualcomm mode.
now i waked up many sony and samsung from qualcomm boot mode.
if you install the correct driver, i can send you a repair tool.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
then you have the wrong driver. which one you installed?
there are for 32 and 64 bit windows. for qualcomm usb mode and also other qualcomm modes.
Click to expand...
Click to collapse
Thanks for the reply, I have a 64bit computer so tried all the 64 bit drivers, I installed all 4 .inf driver successfully in command prompt but when I plug the phone in windows attempts to install drivers and fails?
Do you have the drivers I need?
I also added the Microsoft certificates before hand aswell
Facing a similar problem.
Following.
what you need to know is, that your phone is not off. Also if no device is in device manager.
than the phone is in qualcoom download mode and wait for writing.
i look for the right drivers.mom.
Qualcomm HS-USB QDLoader 9008 this number?
---------- Post added at 04:53 PM ---------- Previous post was at 04:45 PM ----------
i found your driver pack my friend.
no worry, you wake this phone up today.
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
https://mega.co.nz/#F!Vpl3xabT!Arcl1YvRDMXOT3O3VGTe-A
the driver pack and the jig tool. with that you can put phone in download mode.
---------- Post added at 05:09 PM ---------- Previous post was at 04:58 PM ----------
give me update pls. iam waiting for input.
konsolen said:
what you need to know is, that your phone is not off. Also if no device is in device manager.
than the phone is in qualcoom download mode and wait for writing.
i look for the right drivers.mom.
Qualcomm HS-USB QDLoader 9008 this number?
---------- Post added at 04:53 PM ---------- Previous post was at 04:45 PM ----------
i found your driver pack my friend.
no worry, you wake this phone up today.
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
https://mega.co.nz/#F!Vpl3xabT!Arcl1YvRDMXOT3O3VGTe-A
the driver pack and the jig tool. with that you can put phone in download mode.
---------- Post added at 05:09 PM ---------- Previous post was at 04:58 PM ----------
give me update pls. iam waiting for input.
Click to expand...
Click to collapse
Okay thanks alot gonna try this pack now. thanks again ill let you know how it goes
konsolen said:
what you need to know is, that your phone is not off. Also if no device is in device manager.
than the phone is in qualcoom download mode and wait for writing.
i look for the right drivers.mom.
Qualcomm HS-USB QDLoader 9008 this number?
---------- Post added at 04:53 PM ---------- Previous post was at 04:45 PM ----------
i found your driver pack my friend.
no worry, you wake this phone up today.
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
https://mega.co.nz/#F!Vpl3xabT!Arcl1YvRDMXOT3O3VGTe-A
the driver pack and the jig tool. with that you can put phone in download mode.
---------- Post added at 05:09 PM ---------- Previous post was at 04:58 PM ----------
give me update pls. iam waiting for input.
Click to expand...
Click to collapse
No luck still cant get drivers to install, i think this is something to do with my computer as i always seem to have trouble whenever i do anything on my mobile devices such as rooting and what not.
the driver file that doesnt seem to wanna go in is the 'qcser.inf' file.
How would you guys go about installing the driver as i am currently using the method shown in this thread: http://forum.xda-developers.com/showthread.php?t=1669498
I may have to give up soon as this is driving me up the wall lool
i rule123 said:
No luck still cant get drivers to install, i think this is something to do with my computer as i always seem to have trouble whenever i do anything on my mobile devices such as rooting and what not.
the driver file that doesnt seem to wanna go in is the 'qcser.inf' file.
How would you guys go about installing the driver as i am currently using the method shown in this thread: http://forum.xda-developers.com/showthread.php?t=1669498
I may have to give up soon as this is driving me up the wall lool
Click to expand...
Click to collapse
this install version is old my friend.It works with device manager. BUT....use a USB port that direct connect on your mainboard (no hub or USB 3.0), and youse the org. cabel. thats important.
You can also try the driver from the riffbox.they must also work.
---------- Post added at 11:49 AM ---------- Previous post was at 11:38 AM ----------
konsolen said:
this install version is old my friend.It works with device manager. BUT....use a USB port that direct connect on your mainboard (no hub or USB 3.0), and youse the org. cabel. thats important.
You can also try the driver from the riffbox.they must also work.
Click to expand...
Click to collapse
I load you up the chimera and the riffbox drivers..install it.
in device manager when your qualcomm pop up, click it and tick install driver manually.
then you must scroll down and choose the qualcomm.
Also upload a logfile from a i9505. So it looks like when repair is done
konsolen said:
this install version is old my friend.It works with device manager. BUT....use a USB port that direct connect on your mainboard (no hub or USB 3.0), and youse the org. cabel. thats important.
You can also try the driver from the riffbox.they must also work.
---------- Post added at 11:49 AM ---------- Previous post was at 11:38 AM ----------
I load you up the chimera and the riffbox drivers..install it.
in device manager when your qualcomm pop up, click it and tick install driver manually.
then you must scroll down and choose the qualcomm.
Also upload a logfile from a i9505. So it looks like when repair is done
Click to expand...
Click to collapse
I only used that method of installation, I didn't use the drivers from there, the drivers I used where from a forum thread which was specifically for the dead boot of a galaxy s4, this is also where I got the dead boot repair software from
How would you guys go about installing these drivers if you had t cause that must be where I'm going wrong or its just simply my stupid computer making everything difficult
I have the Same prop. Can anyone help?
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?
Hello there. I think I've made something stupid, but dunno what.
Now I've a G2 with firmware update screen. But it doesn't say download mode at the beginning. vol+ and power throws me straight to the firmware mode. vol- and power (factory reset thing) does the same. No download mode, straight to the firmware. And also, my pc doesnt recognise the phone. Here's what I've done so far;
FLASH TOOL
I've downloaded and installed lg drivers, lots of them. (uninstalled and restarted my pc every time) My lg usb serial port with com41 is working but LGE Android MTP Device had yellow exclamation mark, always. Nonetheless I've tried. Changed the dlls, downloaded the correct tot file, changed the port to 41, replug the usb. Returns with 1 sec error, crossdl {rectangle} to D802 bla bla. No luck
LG MOBİLE SUPPORT TOOL
Found my phone. It said I've already latest software. (D802TR30C) I tried to upgrade recovery from the tool. Downloaded my software but it couldn' install to my phone because of unknown error. So, No luck again
LG FLASH TOOL 2014
I've downloaded the correct KDZ's. Installed my drivers. Started program with admin rights. Selected kdz and CSE flash. And then Start. Always stopped at %4 because of usb connection lost. No luck again and again
NOW I'M OUT OF IDEAS AN OPTIONS. PLEASE SOMEONE, HELP FOR GOD'S SAKE.
someone? anyone?
oblitus said:
someone? anyone?
Click to expand...
Click to collapse
Follow this link http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
---------- Post added at 03:34 PM ---------- Previous post was at 03:33 PM ----------
shubdya4u said:
Follow this link http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
I too similar problems but then this steps resolved it
Hello people of XDA.
Can someone help me please?
I woke up this morning only to find out that my phone won't turn on.
There's 75% left in the battery before I went to sleep.
I tried pressing and holding the power button but it won't turn on.
I also tried charging but the LED is blinking red.
Any solution? TIA
UPDATE:
After more than a month (because of quarantine/lockdown), I finally had my phone checked and repaired. It turns out it's a hardware problem: POWER SUPPLY.
Can you go into recovery mode? If yes, clean flash the rom otherwise use qfil tool to restore your phone
try to plug charger and check if battery is low even if you left it at 75% before you sleep, then try press and hold power button until it boots
otherwise reboot to recovery and fastboot - from here you can do the steps to recover your data or format the phone
Here is the same problem but in the morning i saw my phone in recovery mode..I tried all the possible solution :
1.Flashing fastboot rom through adb
2.Flashing firware through qfill tool
Better to mentioned that above 2 flash procedure were successful bt in the end of all successful flashing my phone booted into again recovery mode instead of system..
So,if there any other solution please help me..Its 48hours i'm working on it bt in the end i
get nothing but failure..!
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
swarup16 said:
Here is the same problem but in the morning i saw my phone in recovery mode..I tried all the possible solution :
1.Flashing fastboot rom through adb
2.Flashing firware through qfill tool
Better to mentioned that above 2 flash procedure were successful bt in the end of all successful flashing my phone booted into again recovery mode instead of system..
So,if there any other solution please help me..Its 48hours i'm working on it bt in the end i
get nothing but failure..!
Click to expand...
Click to collapse
:crying:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Random Member said:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Click to expand...
Click to collapse
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
Random Member said:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Click to expand...
Click to collapse
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
How would you know if it's working?
Do you have Telegram?
Here's what I've done:
1. Installed Qualcomm drivers for Windows.
2. Downloaded/installed QFIL.
3. Launched QFIL.
4. Press vol + and vol - at the same time and connected data cable.
5. QFIL still shows "NO PORT AVAILABLE."
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
Problem still not fixed. I'm sure "USB debugging" is enabled on my phone.
When I charge or connect my phone via USB, there is no charging animation.
black screen and vibration ??
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
soufkas said:
black screen and vibration ??
Click to expand...
Click to collapse
no vibration and battery animation when plugging
soufkas said:
black screen and vibration ??
Click to expand...
Click to collapse
no vibration and battery animation when plugging in the charger
same
Random Member said:
no vibration and battery animation when plugging in the charger
Click to expand...
Click to collapse
have the same problem any update on how to solve this XD
My asus zenfone max pro m1 has not been booting since the april 21st update.
It boots completely, asks for pattern to decrypt storage and irrespective of whether or not i enter the pattern, it reboots. Looks like some system services are failing after boot and hence i need to wipe or clean flash the system partition.
Situation:
This is my dad's phone and it wasn't tampered with at all. Unfortunately boot loader is locked and usb debugging is off.
None of my 2 laptops detect it in fastboot or adb in windows and linux. I've installed proper drivers but it doesn't even show up in device manager as unknown or whatever.
It normally enters fastboot and recovery modes.
I did the root integrity check from recovery and it reported 92 files missing and 90 unknown files.
What i tried:
Reinstalling the same update through recovery (makes no difference)
Installing older updates ( recovery doesn't allow)
Factory reset through recovery (makes no difference)
flashing via fastboot (fastboot doesn't detect)
The only thing i did not try is qfil and I'm not doing that because a lot of people have reported losing their IMEI and other hardware information.
Also, I couldn't find a stock qfil firmware they were stock based made by other people.
Asus's update broke the phone. But I don't see a lot of people posting about it. I could use some help.
Thank you
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
axit50 said:
Can you go into recovery mode? If yes, clean flash the rom otherwise use qfil tool to restore your phone
Click to expand...
Click to collapse
The update messed up its own system files. Clean flash means wiping partition and installing again.
How can we do that from stock recovery where it doesn't wipe /system ?
All installations from recovery are dirty.
dev.kasibhatla said:
My asus zenfone max pro m1 has not been booting since the april 21st update.
It boots completely, asks for pattern to decrypt storage and irrespective of whether or not i enter the pattern, it reboots. Looks like some system services are failing after boot and hence i need to wipe or clean flash the system partition.
Situation:
This is my dad's phone and it wasn't tampered with at all. Unfortunately boot loader is locked and usb debugging is off.
None of my 2 laptops detect it in fastboot or adb in windows and linux. I've installed proper drivers but it doesn't even show up in device manager as unknown or whatever.
It normally enters fastboot and recovery modes.
I did the root integrity check from recovery and it reported 92 files missing and 90 unknown files.
What i tried:
Reinstalling the same update through recovery (makes no difference)
Installing older updates ( recovery doesn't allow)
Factory reset through recovery (makes no difference)
flashing via fastboot (fastboot doesn't detect)
The only thing i did not try is qfil and I'm not doing that because a lot of people have reported losing their IMEI and other hardware information.
Also, I couldn't find a stock qfil firmware they were stock based made by other people.
Asus's update broke the phone. But I don't see a lot of people posting about it. I could use some help.
Thank you
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
The update messed up its own system files. Clean flash means wiping partition and installing again.
How can we do that from stock recovery where it doesn't wipe /system ?
All installations from recovery are dirty.
Click to expand...
Click to collapse
I am using custom ROM (MiUI) when my problem happened.
Random Member said:
I am using custom ROM (MiUI) when my problem happened.
Click to expand...
Click to collapse
I have same prob, did you find a solution
phone is dead ( problem mother boad dead ) any aftermarket service or website ?
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
I'm really appreciate your hardwork ?
Only one solution you have left, open back panel of your phone and find two golden point of EDL mode and then hold two points with joint pin and remember your phone battery should be removed and then connect to pc with hold two golden points now your phone is in EDL MODE then flash with stock rom through mi flash tool and remember inside your pc Modem driver is installed which is required in EDL MODE then that's easier to roll back at initial state of phone ? now your phone work smoothly.
---------- Post added at 01:12 PM ---------- Previous post was at 01:11 PM ----------
I'm really appreciate your hardwork ?
Only one solution you have left, open back panel of your phone and find two golden point of EDL mode and then hold two points with joint pin and remember your phone battery should be removed and then connect to pc with hold two golden points now your phone is in EDL MODE then flash with stock rom through mi flash tool and remember inside your pc Modem driver is installed which is required in EDL MODE then that's easier to roll back at initial state of phone ? now your phone work smoothly.
Check
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Thus is edl mode test pin points.
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Edl mode via shorting out the tester point is the only way for you , I beleive your presist or crust partition might have been totally messed up that's why you phone is like this or maybe you didn't enable usb debugging by default luckily your bootloader isn't locked it it was locked then your might have become something like a paperblock of 200grams.
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Have you tried flashing a rom using miflash https://www.xiaomiflash.com/?
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
---------- Post added at 06:40 PM ---------- Previous post was at 06:17 PM ----------
Yakusha90 said:
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
Click to expand...
Click to collapse
A lot of time an hard rebot can help... try you can't lose anything ...
I'm curious... let me know if it worked ...
---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------
Yakusha90 said:
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
---------- Post added at 06:40 PM ---------- Previous post was at 06:17 PM ----------
A lot of time an hard rebot can help... try you can't lose anything ...
Click to expand...
Click to collapse
I mean with this method...
Yakusha said:
I'm curious... let me know if it worked ...
---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------
I mean with this method...
Click to expand...
Click to collapse
This method didn't work, I will try the esl option next. I tried it before tho with no success, maybe because I didn't install the qualcomm driver. What could be the problem if my phone still doesn't get recognized?
It's so weird that a software issue causes my phone to not be able to connect to my computer on the recover layer
Try this:. Go in twrp - advanced - terminal - and write reboot edl in the terminal and after that flash the official MIUI rom.... try and let me know...
---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------
bCid_diCb said:
This method didn't work, I will try the esl option next. I tried it before tho with no success, maybe because I didn't install the qualcomm driver. What could be the problem if my phone still doesn't get recognized?
It's so weird that a software issue causes my phone to not be able to connect to my computer on the recover layer
Click to expand...
Click to collapse
Don't open the phone...
Yakusha said:
Try this:. Go in twrp - advanced - terminal - and write reboot edl in the terminal and after that flash the official MIUI rom.... try and let me know...
---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------
Don't open the phone...
Click to expand...
Click to collapse
if i type reboot edl in the terminal of twrp, my phone goes into a bootloop, showing the mi.com logo, my computer doesnt recognize anything sadly
Did you try to decrypt in twrp with your account's password?
Yakusha said:
Did you try to decrypt in twrp with your account's password?
Click to expand...
Click to collapse
How to do it?
Yakusha said:
Did you try to decrypt in twrp with your account's password?
Click to expand...
Click to collapse
There is nothing left to decrypt I think. How to do it though(for the next time things go wrong)?
bCid_diCb said:
There is nothing left to decrypt I think. How to do it though(for the next time things go wrong)?
Click to expand...
Click to collapse
With the official rom encrypted when you boot in twrp it ask your password for decrypt... But if you bot in twrp and it don't ask anything then you don't have anything to decrypt...
Try to check the others threads...
I'm pretty sure that you can fix it without open it...
Mouths ago I solved a hard brick on my pixel 2xl that was without fastboot, twrp and pc didn't recognize it... I used a tool for reinstall usb drivers and official rom... I will try to find the guide and send it to you as information...
---------- Post added at 04:24 PM ---------- Previous post was at 03:53 PM ----------
How Windows see you device?... Try to go in device manager and check... if your phone appears in device manager as "QHSUSB_BULK" or unknow device, you have to install the proper driver....
And try this tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
So I tried a lot of things, reboot edl didn't work, Testpoint short-circuit didn't work either.
It's hard to say, but I don't know what happened and I have to say goodbye to my beloved phone. It drives me crazy that I didn't found what happened. I don't even know, if I will flash my next phone.
Thanks for your support, if you want to try your luck, or need a display (2weeks old) or any other part, just pm me.
:crying:
bCid_diCb said:
So I tried a lot of things, reboot edl didn't work, Testpoint short-circuit didn't work either.
It's hard to say, but I don't know what happened and I have to say goodbye to my beloved phone. It drives me crazy that I didn't found what happened. I don't even know, if I will flash my next phone.
Thanks for your support, if you want to try your luck, or need a display (2weeks old) or any other part, just pm me.
:crying:
Click to expand...
Click to collapse
Did you try XiaoMiToolV2 ? When you have all drivers, type in program "my phone is bricked", the program should recognize the phone (turning on in twrp) running in recovery and forcing to fastboot mode.
crt-shadow said:
Did you try XiaoMiToolV2 ? When you have all drivers, type in program "my phone is bricked", the program should recognize the phone (turning on in twrp) running in recovery and forcing to fastboot mode.
Click to expand...
Click to collapse
"No devices found[...]"