Related
good day to all. i keep receiving these error while connecting my watch to the flash tool. please kindly guide me on how to solve this problem. am i doing anything wrong. i followed all the instruction and using the files and flash tool.
__________________________________________________ _____________
FLASHTOOL ERROR : S DL MAUI FLASH ID NOT MATCHED WITH TARGET (5095)
(MAUI) SingleMemory the flash id of MAUI BIN is not match to target phone flash!
please check MAUI load is build correctly and fits this target.
HINTL:
_________________________________________________________________
hi guys ,
this is the situation: zenfone 2 laser ze550kl (z00ld) not work.
If i press power and volume+ it go to fastboot mode and with "fastboot devices" it is find on my pc.
If i press power and volume- it no go to recovery and it remain on logo asus in bootloop
I've tryied every guide on this site but nothing work.
Now , i want to try with asus flash tool , i've the compatible version but i have not .raw system.
Someone can help me ?
i've tryied this https://forum.xda-developers.com/ze...nks-asus-zenfone-2-laser-raw-service-t3526083 but don't work.
Thanks for the patience and sorry for my bad english :angel:
Squagghy said:
hi guys ,
this is the situation: zenfone 2 laser ze550kl (z00ld) not work.
If i press power and volume+ it go to fastboot mode and with "fastboot devices" it is find on my pc.
If i press power and volume- it no go to recovery and it remain on logo asus in bootloop
I've tryied every guide on this site but nothing work.
Now , i want to try with asus flash tool , i've the compatible version but i have not .raw system.
Someone can help me ?
i've tryied this https://forum.xda-developers.com/ze...nks-asus-zenfone-2-laser-raw-service-t3526083 but don't work.
Thanks for the patience and sorry for my bad english :angel:
Click to expand...
Click to collapse
just flash twrp using fastboot
Or use raw firmware
addy692 said:
just flash twrp using fastboot
Or use raw firmware
Click to expand...
Click to collapse
How i said i haven't a workly raw system
I've tryied to flash recovery twrp but don't work..power + volume down only restart the smartphone and when go in recovery mode after 10-20 seconds it's restart again
Squagghy said:
How i said i haven't a workly raw system
I've tryied to flash recovery twrp but don't work..power + volume down only restart the smartphone and when go in recovery mode after 10-20 seconds it's restart again
Click to expand...
Click to collapse
use this firmware and flash using qpst or fastboot simply rin fastbokt flash all
https://drive.google.com/file/d/0B43Ue6xY9MmdOGxXZ2RRQUJrOWs/view?usp=sharing
addy692 said:
use this firmware and flash using qpst or fastboot simply rin fastbokt flash all
https://drive.google.com/file/d/0B43Ue6xY9MmdOGxXZ2RRQUJrOWs/view?usp=sharing
Click to expand...
Click to collapse
after flashing nothing news :crying:
it stay on logo asus and with power+volume+ go in fastboot mode and with power+volume- it restart and restart....
p.s. qpst not find ports with phone
Squagghy said:
after flashing nothing news :crying:
it stay on logo asus and with power+volume+ go in fastboot mode and with power+volume- it restart and restart....
p.s. qpst not find ports with phone
Click to expand...
Click to collapse
I have the same problem. I have one of my friend's phone, which his brother gave him. We have no idea what has gone wrong with this phone. It just won't pass the asus logo. Also displays a BLUE SCREEN when i try to boot into recovery.
First i thought recovery must be corrupted, buti had no idea about asus phones (i own a sony phone). So i tried to flash a stock recovery through fastboot, but it didn't work. Then read from some blog to flash system.img, recovery.img and boot.img. Links were also there. Did the same but no still no use. It made it worst because on a normal boot (holding just the power button) the phone shows fastboot mode!!! Not i'm trying asus flash tool.
Tried Asus flash tool : error 5 : access denied. so i'm stuck
C:\Users\Home\Desktop\[firmware27]WW_ZE550KL_1.17.40.1234-rel-user-2016030418590
4-secured-releaseAFT_QC>fastboot_8916 format:ext4 userdata
Creating filesystem with parameters:
Size: 11915980800
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 2909175
Block groups: 89
Reserved block group size: 711
Created filesystem with 11/727664 inodes and 85558/2909175 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'userdata'...
OKAY [ 3.719s]
finished. total time: 3.734s
is the only error that result on flashing.
Squagghy said:
C:\Users\Home\Desktop[firmware27]WW_ZE550KL_1.17.40.1234-rel-user-2016030418590
4-secured-releaseAFT_QC>fastboot_8916 format:ext4 userdata
Creating filesystem with parameters:
Size: 11915980800
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 2909175
Block groups: 89
Reserved block group size: 711
Created filesystem with 11/727664 inodes and 85558/2909175 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'userdata'...
OKAY [ 3.719s]
finished. total time: 3.734s
is the only error that result on flashing.
Click to expand...
Click to collapse
my device was also bricked a month ago i can guide u
ok so now u have to try qpst
Just download qualcomm drivers and then use qpst
Contact me on telegram @ady692
addy692 said:
my device was also bricked a month ago i can guide u
ok so now u have to try qpst
Just download qualcomm drivers and then use qpst
Contact me on telegram @ady692
Click to expand...
Click to collapse
ok i try with qpst
the phone not result in any port of pc :/
Squagghy said:
ok i try with qpst
the phone not result in any port of pc :/
Click to expand...
Click to collapse
install qpst drivers
And goto fastboot and type
Fastboot erase aboot
And then take out battery insert again and connect to pc it should show as qcom 9006 port or 9008
Caution i lost my imei after unbrick so backup ur efs before doing anything
addy692 said:
install qpst drivers
And goto fastboot and type
Fastboot erase aboot
And then take out battery insert again and connect to pc it should show as qcom 9006 port or 9008
Caution i lost my imei after unbrick so backup ur efs before doing anything
Click to expand...
Click to collapse
drivers qualcomm installed, after erase aboot it appears a port 9006 but efs and qpst not found the phone
and it appears on my pc 7 local disk
Squagghy said:
drivers qualcomm installed, after erase aboot it appears a port 9006 but efs and qpst not found the phone
and it appears on my pc 7 local disk
Click to expand...
Click to collapse
firstly i suggest you to backup ur efs man
hey it would be easy if u contact somewhere else
Like telegram or phone cal
Or follow this
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I have followed the instruction but nothing good news ...phone don't work ...local disk doesn't appear on PC , only port appear but qfil failed ...i thinks that the phone cannot be restored
i've read better ..so i'm in old Qualcomm HS-USB QDLoader 9008 mode ....but there is one little problem to resolve this brick....qfil : after i choise the necessary file it fail ..sahara fail..
what's wrong ?
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
in QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
in QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Squagghy said:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
in QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
in QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
it will surely work
Just contact me on phone if
I am also making guide for this but that will take time
Unfortunately time is the only thing I do not have .... if you can post a guide to solve it would be great
Squagghy said:
Unfortunately time is the only thing I do not have .... if you can post a guide to solve it would be great
Click to expand...
Click to collapse
u are almost at the end of guide
Just try usung qfil it will work
Use different version if qpst
addy692 said:
u are almost at the end of guide
Just try usung qfil it will work
Use different version if qpst
Click to expand...
Click to collapse
used different version but nothing...i wrong something i'm sure...xD
13: C:\lui\prog_emmc_firehose_8936.mbn
01:46:17: Requested ID 13, file: "C:\lui\prog_emmc_firehose_8936.mbn"
01:46:17: ERROR: function: rx_data:247 Error occurred while reading from COM port
01:46:17: ERROR: function: sahara_main:854 Sahara protocol error
01:46:17: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Squagghy said:
used different version but nothing...i wrong something i'm sure...xD
13: C:\lui\prog_emmc_firehose_8936.mbn
01:46:17: Requested ID 13, file: "C:\lui\prog_emmc_firehose_8936.mbn"
01:46:17: ERROR: function: rx_data:247 Error occurred while reading from COM port
01:46:17: ERROR: function: sahara_main:854 Sahara protocol error
01:46:17: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
which files u r using
U should use programmef file in raw firmware folder
The link which i given to you there is firmware folder where u will find programmer file xml file and other
Specific to ur device use that
I have a simular problem. On my device gpt was erased by fault.
When I flash the firmware from subfolder "firmware/8939" with qfil (with "emmc_appsboot_8939.mbn" renamed to "emmc_appsboot.mbn"), I end up with the device booting in fastboot. But from there I can do nothing else, because the bootloader is locked. Tryed it with "flashall_AFT.cmd", but it cannot unlock bootloader ("fastboot oem unlock" gives "unkown command" error).
How can I flash partiton "gpt_both0.bin" without unlocking the bootloader? I think I need a modified "rawprogram0.xml" and "patch0.xml" for complete gpt and firmware, but how to do it?
Thanks in advance.
Mikel
I wanted to get on the latest developer preview release, downloaded the system image, and flashed it to my phone, when done i tried to reboot it, but it stayed on the white google logo screen infinitely. Eventually rebooted, and now won't even attempt to boot. It just goes back to fastboot.
Any attempt to go to recovery, boot the system, or anything - gives an error "Your device is corrupt. It can't be trusted and may not work properly". It offers a link to g.co/ABH then an option to press the power to continue, when I do, it briefly flashes the google logo, then back to the bootloader. Where it has a reason shown as "error booting boot.img"
It doesn't respond to any adb or fastboot commands, but does show in the device manager as LeMobile Android Device (Android Bootloader Interface). And that's about it.
I seem to be stuck in a loop here, and would appreciate if anyone has any advice to offer.
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Ohiostyle said:
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Click to expand...
Click to collapse
Is it going from fastboot to fastbootd?
Yeah it was, it completed a lot of other read/write actions after moving over to fastbootd, before failing.
I was able to get it working by sideloading the ota file. Any system image (always factory images) that I would try to flash would fail at the same point. I have no idea why.
Ohiostyle said:
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Click to expand...
Click to collapse
you need to extract the other zip within the image and make sure you extract it where your adb tools are
tmoore3496 said:
you need to extract the other zip within the image and make sure you extract it where your adb tools are
Click to expand...
Click to collapse
Yes, I had that problem time ago (I think with the OG Pixel).
Doing what you described fixed it, now I always do it just in case.
Also updating to the latest platform tools.
Can you go into recovery? If so try sideloading an OTA file.
Dear mates,
2 days I am trying to find answer to my problem and finally decided to start new post on exact issue I faced.
device is MI A1 with android one and current version on it was according to picture attached from recovery was tissot_10.0.19. when I took this phone from my mate to fix it was not booting with first MIUI page stacked on the screen.
fastboot output were saying:
--------------------------------------------------
C:\WINDOWS\system32>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.058s]
Finished. Total time: 0.059s
------------------------------------------------
getvar is attached
i tried to flash using miflash ver 2020.3.14 in fastboot mode but it was not successful because of locked bootloader and "locked everything".
i tried to load OTA updates using embedded recovery, but not successful, screenshot attached.
i got the error " E:Error in sideload/package.zip (Status 1)
and all time repeating error : fail to clear BCB message fail to fsync /dev/block/bootdevice/by-name/misc: operation not permitted
any option from recovery meny does not provide any result. wipe data/factory reset were stucking with erasing data notification for hours without result.
at the end i cam to EDL mode by shorting hardware test point. quallcomm driver was ok at computer Device Manager, miflash and QFIL are identifying device on com port 20 but flashing does not finish successfully , it stop at 12 sec in Miflash, and at 1,46% in QFIL. verbose log for QFIL is also attached .
main concern in QFIL log file is "IGNORING UNRECOGNIZED Attribute" stats for attributes from TARGET. my impression is phone is asking to send data in rawmode <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data> and Qfil is ignoring this attribute. as the result file copy finish with error
23:37:45: INFO: TARGET SAID: 'Finished sector address 131072'
23:37:45: DEBUG: XML FILE (92 bytes): CharsInBuffer=92-92=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
and we have repeating replies from Target as this : <?xml version="1.0" encoding="UTF-8" ?><data><log value="0 bytes received, 1048576 sectors more to go" /></data>
sorry for long explanation, the goal is to share as clear picture of the situation as possible.
i tried the same procedure with QFIL on other computer and had the same result.
now phone is in all time EDL mode. i suppose it is because i checked "erase all before configuration" option in QFIL firehose configurations.
Thanks to everyone in advance for your time and help if you could provide your suggestions how to solve the issue.
I can't solve this problem for more than 4 days and I have android 8.1 and it gives the same problem, you can do the easiest thing, as they say, edl test point, you can try but I don't recommend how you can mess up something if you were able to solve the problem, please tell me how to solve it
Try to flash stock rom via MiFlash Tool. Make sure to see COM port on MiFlash tool (press refresh to detect com port). Then after you see COM port. Flash it with "clean all" option(on the bottom). If you connect to EDL mode properly, process will be finished succesfully. But if you get some "Invalid argument, unknown error" errors, you are not connected to edl mode.
try to enter edl mode with this code in fastboot
Code:
fastboot oem edl
If it give OKAY, then you are ready to flash with Miflash tool.
There is another way to flash img files with fastboot mode. If you dont success, write here.
atc mode is not worked and I don't want to enter the testpoint, how can I tell you and the loader is not open, so this is also not a small problem as you look at it, so if there are other ideas, please send them to me
PLEASEEEEE
Testpoint is a final way. even if you cant enter testpoint, you cant do more
ivomin said:
It's ALIVE!.
Just to update that after debugging the whole windows com stack I struck on a wall and it seems that windows 7 and 10 block something there (I manage to get out of the driver to win kernel on debug but then it fails and didn't had any more nerves to deal with and I'm not a windows guy myself).
So the only solution for low lvl writing is to use linux with point boot to EDL. It seems that for mi A1 even if Qualcomm's boot chain is broken (https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html) it should fall to EDL in most cases but in our phone (global version at least) it goes to diagnostic mode (not to be confused with Download mode) regardless of drivers in windows - this is hardwired in the chip. So under linux you should fall in to download mode with hardware short of motherboard points to fall in to the correct mode. You should forget about windows as it depends too much on the selected driver (yes you can manually change driver and fu** the whole chain of communication). You need to hardwarely go to Download mode. Don't believe what windows reports.
From there you can use QDL (check documentation on how to install (you'll also need to install gcc (ubuntu - apt get install gcc) https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md).
Then download a full firmware flash from xiaomi (that's for MiFlash) and use the files in the images folder for the command ( for instance to be more easy copy images folder to qdl folder and:
./qdl --debug --storage emmc --include 'images' 'images/prog_emmc_firehose_8953_ddr.mbn' 'images/rawprogram0.xml' 'images/patch0.xml')
This will fix the first part of the qualcomm bootchain from there you will have access to fastboot and then use all other tutorials concerning fixes from fastboot.
If enough ppl want it I'll write extended tutorial in the other section.
Click to expand...
Click to collapse
Try this. It should bring you to mostly original state and from there you can fastboot unlock and proceed with installing shrp or twrp.
I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Did you try this? https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
nike1 said:
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
Click to expand...
Click to collapse
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
itsTarec said:
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
Click to expand...
Click to collapse
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
nike1 said:
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
Click to expand...
Click to collapse
Is your device rooted now? Or did you just fixed the issue?
nike1 said:
I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Click to expand...
Click to collapse
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
lucy1983 said:
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
Click to expand...
Click to collapse
Aha, I see. That wasn't clear to me. I thought i needed a full package and not just an incremental one, that's why I went for 1.1.7. I did patch it with Magisk though, just the wrong version i guess. But all is well now, the phone's fully working afaict. Thank you for clarifying what went wrong!