I am trying to unbrick via 7z firmware with QFIL with a Deep Flash/ EDL cable. Still getting a lot of errors (especially Saharas). Anyhoo, my question is.....
Upon a failed "download" on QFiL, can I just move along and just load up and attempt different settings or firmwares from there? Do I need to OFF the phone or restart QFIL or anything?
I don't want to think I am testing for a different result , if a different result is impossible. Thanks.
enzyme said:
I am trying to unbrick via 7z firmware with QFIL with a Deep Flash/ EDL cable. Still getting a lot of errors (especially Saharas). Anyhoo, my question is.....
Upon a failed "download" on QFiL, can I just move along and just load up and attempt different settings or firmwares from there? Do I need to OFF the phone or restart QFIL or anything?
I don't want to think I am testing for a different result , if a different result is impossible. Thanks.
Click to expand...
Click to collapse
Try to install the latest qfil and usb drivers for zuk z2 pro, uninstall qfil and old usb drivers and install new ones. Also try inserting to different usb ports.
Had the same problem weeks ago and its a hard brick. Took me a week to solve it...hehehe
enzyme said:
Upon a failed "download" on QFiL, can I just move along and just load up and attempt different settings or firmwares from there? Do I need to OFF the phone or restart QFIL or anything?
Click to expand...
Click to collapse
As long as the phone stays in 9008 mode (check that in windows device management), you can start flashing. No reboot required.
Remember, this device is unbrickable (except if you have faulty hardware), stay patient & follow the howto's to the letter.
Yeah I understand. With this phone it is so spotty and inconsistent as far as how and when things work. I was bricked then was able to do a download successfully with no error once. Ironically, that flash just bricked it differently.
I haven't managed to brick it once.... did manage to flash wrong ROM on top of wrong firmware. Try that with most other devices, and you're in a world of hurt.
Related
Hello guys, i'm new here. First of all english is not my native language so sorry if i make any mystakes.
I flashed my phone to Lollipop. Then i tried to install twrp (with Flashify) recovery so then i could install Xposed... but the thing is that i may have used the wrong file..
My phone doesn't start. The only sign of live that it gives is when i plugged it to the PC, the pc makes the usual sound when you plug a USB. And it shows my phone as a usb with 63MB of storage (obviouly my phone has more storage). And when i go to Disk admin it shows me all the partitios that my phone has.
Also in Devices admin it shows my phone as: LGE AndroidNet USB Serial Port (COM6)
Do you know what can i do to unbrick my phone? :crying::crying:
LG D410H with lollipop 5.0
Did you unlocked the bootloader before flashing twrp?
Did you tried to hold vol + and plug USB cable to enter in download mode?
F. Gacrux said:
Did you unlocked the bootloader before flashing twrp?
Did you tried to hold vol + and plug USB cable to enter in download mode?
Click to expand...
Click to collapse
Hello, thanks for your reply.
Yes i have tried that already. Nothing seems to work :crying:
When i tried Volume up and plug the cable it shows nothing in my phone's screen. Just in my PC i sounds like a disconected or connected device
You probably flashed the wrong bootloader, which is a fatal error.
I know users that managed to recover other phones from this brick with LGBoardDiag as explained in this topic: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
I don't know how to get this TOT file, but the same partitions shown can be retrieved from your KDZ in BIN extension with LGFirmwareExtract, I think it's just a matter of renaming the files.
F. Gacrux said:
You probably flashed the wrong bootloader, which is a fatal error.
I know users that managed to recover other phones from this brick with LGBoardDiag as explained in this topic: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
I don't know how to get this TOT file, but the same partitions shown can be retrieved from your KDZ in BIN extension with LGFirmwareExtract, I think it's just a matter of renaming the files.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-l90/help/bootstack-flash-gone-wrong-t3120536
i have this problem exactly the same
I found this interesting topic, you probably can recover from this brick to allow you to enter in download mode using LGFlashTool (not the one that flashes KDZ) like this: http://forum.xda-developers.com/showthread.php?t=2475045
But we still need this TOT file and the DLL for your D410H that I do not know where to find or to create from the KDZ.
F. Gacrux said:
I found this interesting topic, you probably can recover from this brick to allow you to enter in download mode using LGFlashTool (not the one that flashes KDZ) like this: http://forum.xda-developers.com/showthread.php?t=2475045
But we still need this TOT file and the DLL for your D410H that I do not know where to find or to create from the KDZ.
Click to expand...
Click to collapse
But i can't go download modde :/ my phone does not show anything on it's screen..
i've been trying with this post:
http://forum.xda-developers.com/lg-g2/general/tool-unbrick-lg-g2-qualcomm-9008-board-t3072073
but it gives me the error that appears at the beggining of the thread. I unplugged it, remove battery, then put it back again and reconnect the usb, but the same problem :/ :crying:
also i have found not the TOT file but this thread:
http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
I meant that will lead you to a working download mode, which is enough to restore everything, including partition table.
I have a suggestion, you said Windows detects as a mass storage unit, can you boot Linux and follow this thread http://forum.xda-developers.com/showthread.php?t=2582142 to see if can see all the partitions?
If yes, it's just a matter of extracting the KDZ of your variant and flashing the said partitions to get a working download mode to make a complete kdz flash.
lg l90 405 is believed to be 410 dual sim
hi to all guys, I would like to submit for your ATTENTION What I And Success Knowing and possibly come to restore rate.
I am the owner of an LG L90 model d405n, Wanting to make the Unlock bootloader I used an Application That I would have to just unlock the bootloader and recovery modified Install A.
In the cell AFTER tale reality 'hack And practically dead, he would not turn on even.
I Put in search tool various programs and various vain, the cell showed no signs of life.
Then, Dandolo now hope for him I tried to go for broke, I formatted a low debits and then with an Application (umbrick) I managed to flesciare start and everything else. Now the cell was lit and was anche in update download mode '.
I downloaded the firmware 405 and KDZ I Tried to use the flash tool but the procedure is always blocked at 2% giving an error.
With the instrument of 'LG I discovered sensationally That cell was identified coming D410, exhausted from the various prove not go into port I wanted to download the KDZ model 410D and, come by magic, flash tool worked! I installed the latest version information and cellphone works beautifully!
So now I have a phone with a firmware His (among other things the 410D E anche dual sim).
I would like to restore your system orifginale, That the 405 but I'm afraid to rate other trouble ....
I hope someone can give me a hand ...
LG L90 D410 Totally bricked. Please someone help.
I an LG L90 D410. I tried to install boot loader and after rebooting the phone, it was unusable. It is not showing any QhSUB_BUlk as well as any partition in My Computer. its not showing anything in PC. Please help someone how can i unbrick my phone.
Hello please try to follow this thread http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
This works 100% it helped me unbrick my phone. Hope it will work for you as well
Enviado desde mi LG-D410 usando XDA Forums
Hi!
I tried to flash a QFIl Rom on my Z2 Pro, because its bricked... I can enter EDL Mode (Port 908) but it always says "cannot read hellopackage" in Miflash and "Sahara: Fail" in QFIL...
I tried 4 hours now, i can cry...
Whats the problem here? Do i need another ROM?
PLS HELP!!!
Stift01 said:
Hi!
I tried to flash a QFIl Rom on my Z2 Pro, because its bricked... I can enter EDL Mode (Port 908) but it always says "cannot read hellopackage" in Miflash and "Sahara: Fail" in QFIL...
I tried 4 hours now, i can cry...
Whats the problem here? Do i need another ROM?
PLS HELP!!!
Click to expand...
Click to collapse
In QFIL you have to make sure to use short path names with no spaces. Otherwise you get that Sahara error.
That doesnt help... Its always the same error..
Stift01 said:
That doesnt help... Its always the same error..
Click to expand...
Click to collapse
Perhaps you'll find more information on ZUKFans. I can feel your pain, I bricked my ZUK Pro twice, last time it was hard-bricked. I was about to throw it into the trash (literally) but finally managed to revive it and flash a ROM via QFIL.
Which ROM are you trying to flash and where did you download it? Is it the right version for QFIL? Because there are different versions for flashing via SDFuse method.
I downloaded the tool and the ROM from androidfilehost.com! I searched for zuk z2 pro and took it from "No|Name"! (Sorry, i cannot post the link directly but its easy to find)
Both from the same...
Maybe you have a download for me which you are prefering???
I tried another QFIL Rom but it didnt work too... I made a break for two hours now, otherwise i will throw my device in the fire... think i tried it hundred of times... Maybe i forgot something, but im sure that i've done everything needed...
- device is in edl mode (tried with deepflash cable and normal usb)
-qfil installed and runed (normal and a admin)
-tried two different qfil roms
I work with win10...
Thx a lot man for your help :good::good::good:
Stift01 said:
I downloaded the tool and the ROM from androidfilehost.com! I searched for zuk z2 pro and took it from "No|Name"! (Sorry, i cannot post the link directly but its easy to find)
Both from the same...
Maybe you have a download for me which you are prefering???
I tried another QFIL Rom but it didnt work too... I made a break for two hours now, otherwise i will throw my device in the fire... think i tried it hundred of times... Maybe i forgot something, but im sure that i've done everything needed...
- device is in edl mode (tried with deepflash cable and normal usb)
-qfil installed and runed (normal and a admin)
-tried two different qfil roms
I work with win10...
Thx a lot man for your help :good::good::good:
Click to expand...
Click to collapse
Try with another PC with Windows 7. Maybe this will save you.
Stift01 said:
I downloaded the tool and the ROM from androidfilehost.com! I searched for zuk z2 pro and took it from "No|Name"! (Sorry, i cannot post the link directly but its easy to find)
Both from the same...
Maybe you have a download for me which you are prefering???
I tried another QFIL Rom but it didnt work too... I made a break for two hours now, otherwise i will throw my device in the fire... think i tried it hundred of times... Maybe i forgot something, but im sure that i've done everything needed...
- device is in edl mode (tried with deepflash cable and normal usb)
-qfil installed and runed (normal and a admin)
-tried two different qfil roms
I work with win10...
Thx a lot man for your help :good::good::good:
Click to expand...
Click to collapse
If your phone is bricked make sure you flash 1.9 which basically resets everything. That worked for me. And make sure if on Win10 to turn off driver verification or whatever it is called.
Dont worry. If QFIL detects your phone as a qualcomm device its ok. Try the roms below. Make sure that you unzip the files in a c:/folder.
Here is a tutorial: http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/#post-624
QFIL rom:
https://drive.google.com/open?id=0Bz_ewncbv3n9Z1NuRFlKdjJxREk
https://drive.google.com/open?id=0Bz_ewncbv3n9NVcteTBsUHdCV2s
Try updating the firmware to 1.9 and make sure the folder that you extract the files to is renamed to a shorter name like a single alphabet. Also make sure your drive isnt bitlocked, Make sure you right click on all the extracted files and select properties and uncheck readonly . Use a different USB port and the stock cable. Run the qfil program as an administrator. Sorry if you have already tried these steps, Just that I had faced the issue and had to go through the above mentioned steps.
this morning i set up lgup tool and updated my phone from 10N (lollipop) to 20i
when lgup tool done flashing and went to rebooting[150s] step i saw the phone died
but lgup was doing its job after reaching 100% i tried turning on the phone but no lock and even tried to enter download mode but it connects to pc as QHSUSB_BULK its been nearly 6 hours and i did what this said and put the sd card in the phone but it still wont turn on and no download mode neither i really appriciate if some one could help me with this half dead phone
Note:
OEM unlock ticked from developer tools and usb debugging on too
Just make sure to follow every step, it sometimes does work in first attempt
jam1445 said:
Just make sure to follow every step, it sometimes does work in first attempt
Click to expand...
Click to collapse
should i install any other driver beside usb driver?
i saw people not getting qhsusb_bulk but qualcomm 9008...
Update:
i managed to get out of qualcomm 9008 state with this guide now a new problem comes out:no download mode and nothing else only a charging message on screen even with using hotkeys please note that the phone is not recognizable by the pc or laptop in any way no beep while connecting the usb too
tried sd card solution but no luck
Then u must be facing permanent bootloop
Update:
Battery was short circuited some how
Tested with springs and a working battery of LG l90 model and phone started showing LG sign then sucure boot failed 1009
Just made a factory reset phone booted up completely but camera stopped working.
Need to flash 20i again or another rom?will find out
jam1445 said:
Then u must be facing permanent bootloop
Click to expand...
Click to collapse
found out how to fix my phone but problem is i need h811 .mbn and .xml files in order to use in qfil and i turned the whole internet upside down but could nt find any can you provide help with those eMMc files i mentioned? so many diffrences between ls991 and h811 mbn files and flashing them with qfil boots up my phone but no imei and no camera working also the baseband is unknown all i need is correct QFIL files
if you have...or if you know how can i get them please help
Hello Everyone, so 2 days ago i hard bricked my MI 8 with flashing an eu rom over global mi 8 rom with twrp then when i rebooted the phone it stuck at mi logo so i tried to goto recovery mode again but nothing happens when i press power + volume up its just mi logo and i tried to go to fastboot mode but not luck i get a black screen....................so i decided to connect it to a computer but no signs of anything(not detected).....so i searched google a little and i found a solution wich envolved disassembling the phone the method called EDL method with test point,,,,,,,so i opened my phone with my friends and tried to do the test points,,,when i joined the testpoints and then connecting the phone to pc.....nothing happened.....it should detect the phone but nothing happens.....please help guys!!!
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone ?
mi_guel said:
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone
Click to expand...
Click to collapse
I have been trying....but no luck till now:crying::crying::crying:
alandxaled said:
I have been trying....but no luck till now:crying::crying::crying:
Click to expand...
Click to collapse
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
tsongming said:
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
Click to expand...
Click to collapse
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
alandxaled said:
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
Click to expand...
Click to collapse
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
tsongming said:
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
Click to expand...
Click to collapse
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
alandxaled said:
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
Click to expand...
Click to collapse
The EU rom does not lock the bootloader, the developers actually removed the bit of code that will allow MiFlash to lock the bootloader. Whenever leaving or returning to Miui, storage must be formatted.
The problem with these custom roms for the Mi8 is that These mi8 developers do not work together ( like most do, on other threads) These developers are always fighting and arguing and accusing each other of stealing their code, while they do it themselves and they all have their own way of doing things. Ideally every rom should use the same device tree, firmware and vendor...The basics! But no, everyone does things differently.
I would suspect that your phone bricked due to firmware encryption or just corruption. Even though it seems that it can't be fixed, you will surely be able to fix it eventually.
Many people were eventually able to solve this exact issue in the past with success. so start with the basics., and dont give up when or if it fails, just try again on a different device, and be sure to disable Windows defender. Because it's possible you could have your computer setup in a way that it will make this process harder to resolve, temporarily disable the antivirus and firewall etc.
Download the All in One tool: https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807 If it gets flagged, and completely disabled. then your computer is helping contribute to this issue.
If you can successfully install and open the tool, use it to update adb and android drivers and to apply system wide adb access. Next manually setup the phone , even if it claims to not see a fastboot device. and attempted to remove encryption. if this fails find a Linux machine to complete these tasks.
See if you can leave EDL, by pressing and holding the power and volume down. >>>>> Even if you dont see the fastboot screen the computer may see the phone in fastboot.
I definitely believe that you will have a easier path to getting this issue resolved sooner by using linux. If you can "format" ( not wipe) user data, install TWRP and root the rest will obviously be easy.
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
Boiisxu said:
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
Click to expand...
Click to collapse
He didn't format user data, or the file was somehow corrupted
Hi everyone,
I was wondering does anyone know the Nokia TA-1004 JTAG points by any chance?
I tried looking around and I can't seem to find anything.
Because of my bricked device, I am thinking of going down the JTAG route to extract my data.
This is the absolute last resort as I REALLY don't want to loose any of my data, primarily Contacts and Messages
Hope to hear back from you wonderful lot ?
Nokia_8_fan said:
Hi everyone,
I was wondering does anyone know the Nokia TA-1004 JTAG points by any chance?
I tried looking around and I can't seem to find anything.
Because of my bricked device, I am thinking of going down the JTAG route to extract my data.
This is the absolute last resort as I REALLY don't want to loose any of my data, primarily Contacts and Messages
Hope to hear back from you wonderful lot
Click to expand...
Click to collapse
I don't know what JTAG is. Please give some more info about your bricked device, how you bricked it etc. It might be possible to recover it without hardware intervention. Looking at your current post I am guessing you have a hard brick. In that case you have 2 options:
1.) Press and hold power button for about 2-4 minutes and wait for the device to shut down. When the device shuts down, boot to fastboot mode and fix any broken partitions.
2.) If that doesn't work you need hardware based methods. You need to open your device and short some pins to enter Qualcomm EDL (Emergency Download) mode. From there you can recover your device.
emufan4568 said:
I don't know what JTAG is. Please give some more info about your bricked device, how you bricked it etc. It might be possible to recover it without hardware intervention. Looking at your current post I am guessing you have a hard brick. In that case you have 2 options:
1.) Press and hold power button for about 2-4 minutes and wait for the device to shut down. When the device shuts down, boot to fastboot mode and fix any broken partitions.
2.) If that doesn't work you need hardware based methods. You need to open your device and short some pins to enter Qualcomm EDL (Emergency Download) mode. From there you can recover your device.
Click to expand...
Click to collapse
Thanks for getting back to me.
I have done both suggestions and they don't work.
It is probably a hard bricked device, the only thing I can get is a 9008 recognition in Device Manager.
QFIL, OST and NOST doesn't seem or want to communicate with the device either
Did you open your device and short the pins required? EDL mode is different than Download mode. OST and NOST work in Download Mode not EDL. QFIL does support EDL mode. If you look at this article (https://xiaomitools.com/how-to-use-qualcomm-flash-image-loader-tool-qfil/) at Step 5 it mentions that the device should be recognised as 9008 which you mention it does. Have you installed the Qualcomm drivers? Please provide some screenshots too, it is difficult to help you without specific info about your problem
emufan4568 said:
Did you open your device and short the pins required? EDL mode is different than Download mode. OST and NOST work in Download Mode not EDL. QFIL does support EDL mode. If you look at this article (https://xiaomitools.com/how-to-use-qualcomm-flash-image-loader-tool-qfil/) at Step 5 it mentions that the device should be recognised as 9008 which you mention it does. Have you installed the Qualcomm drivers? Please provide some screenshots too, it is difficult to help you without specific info about your problem
Click to expand...
Click to collapse
@emufan4568
Sorry for my late reply, but I thought Download Mode is the same as EDL mode???
And yes, I have the Qualcomm drivers installed.
I have also shorted the EDL pins on the board, this did not do anything at all.
I have tried QFIL many times and it keeps giving me error messages.
I have done so many things and posted screenshots across the forums that I am at a complete lost!
Nokia_8_fan said:
@emufan4568
Sorry for my late reply, but I thought Download Mode is the same as EDL mode???
And yes, I have the Qualcomm drivers installed.
I have also shorted the EDL pins on the board, this did not do anything at all.
I have tried QFIL many times and it keeps giving me error messages.
I have done so many things and posted screenshots across the forums that I am at a complete lost!
Click to expand...
Click to collapse
EDL mode is Emergency Download Mode in Qualcomm devices for recovering the device at a low level. QFIL calls it download mode but it really is not. Download mode in Nokia phones is really fastboot mode or bootloader mode where you basically communicate with the bootloader and flash/erase images from the device. From what I have seen though NOST supports EDL mode too (with the Emergency Download option) but it does not really work well.