Database Develop

[Bricked][Asus Zenfone/Zenforce 4] Boot loop on Asus logo

Hey,
Since multiple flashing operation (fastboot), the phone was turned into 'brick' and seems now looping on Asus logo at start..
After pressing power button + vol up the phone is well entering into droidboot but with this log message : 'E:Unable to open debricking'.
The phone stills open with USB cable (fastboot/adb) but I've already experienced some 'signature mismatching' during flash?
Any idea to recover ?
Thanks!
Product : TW_ZENFON (not WW)
Droidboot ver : 4.3.10.0

[Bricked][Asus Zenfone/Zenforce 4] fastboot flash fastboot fastboot.img
W4sh said:
Hey,
Since multiple flashing operation (fastboot), the phone was turned into 'brick' and seems now looping on Asus logo at start..
After pressing power button + vol up the phone is well entering into droidboot but with this log message : 'E:Unable to open debricking'.
The phone stills open with USB cable (fastboot/adb) but I've already experienced some 'signature mismatching' during flash?
Any idea to recover ?
Thanks!
Product : TW_ZENFON (not WW)
Droidboot ver : 4.3.10.0
Click to expand...
Click to collapse
After flashing the device with fastboot flash fastboot fastboot.img the output log are now : E:flash_fastboot_kernel : check_sign_key fail no allow to update kernel
Well, it seems that a specific firmware is needed and droidboot is checking for a key signature? If no match, it cannot allow an overwritting or something.

hi
Please forgive me English is not very good. You determine your own model, the Asus machine has some need to correct the file name, for example, k012, the file name is k012_sdupdate.zip. Then look at your card is correct brush pack

The device has been flashed once again with fastboot -> fastboot flash fastboot fastboot.img
The fastboot.img file was included from the official firmware zip archive UL_ASUS_T00Q_TW_4_3_2.zip
The operation was done succesfully without any error... meanwhile the boot is now going to blank (Android robot is fading to blank) and loop continuously...
If I restart the phone, the boot stuck as well on the Asus logo... So no more droidboot menu available..
@Chinaxiao4 : do you mean to rename the firmware (ie : UL_ASUS_T00Q_TW_4_3_2.zip) with the device model number ? Afterwards do we need to play with adb/fastboot ?

hi
You try, some machines need to change the name ASUS, please forgive me English is very bad, can not help you get more information

Chinaxiao4 said:
You try, some machines need to change the name ASUS, please forgive me English is very bad, can not help you get more information
Click to expand...
Click to collapse
No worries for your English, well.. my machine/device is an 'Asus T00i'

W4sh said:
No worries for your English, well.. my machine/device is an 'Asus T00i'
Click to expand...
Click to collapse
..so far it might be a firmware like this UL_ASUS_T00I_TW_4_X_X.zip

To resume, the Asus Zenforce/Zenfone 4 (T00I) TW model has been bricked since some flashing operation with firmware.
- used firmware : UL_ASUS_T00Q_TW_4_3_2.zip
- command line : fastboot flash fastboot fastboot.img
- result : No more boot menu... the droidboot is fading to blank, boot loop on model logo (bricked)
- Looking for (maybe) : UL_ASUS_T00I_TW_4_x_x.zip and droidboot with recovering mode
Linux to help by mounting the device and doing some repartionning job? Let's go further!!

When plug on USB the device is now unrecognized due of his previous flashing... (no matched Drivers)
Any help so far?

Boot Loop and no more driver to recognize the phone
https://www.youtube.com/watch?v=eUOTnIkXMvY&feature=youtu.be

RE
W4sh said:
https://www.youtube.com/watch?v=eUOTnIkXMvY&feature=youtu.be
Click to expand...
Click to collapse
As said from the vid, "better to replace the initial droidboot by another recovery mod before doing anything "

A bit darky but the idea seems ok, hoping for a next further release of Clockworkmod recovery
https://www.youtube.com/watch?v=OQ1gE9TpZ60
Meanwhile no idea to get outta my bootLoop locking screen...

Hi,
Is there any update solution, hint? My zenfone 4 also in brick bootloop intel logo status, can't enter to fastboot mode using key combination Power and Volume. It also cannot be detected using USB in PC.

coffeelover said:
Hi,
Is there any update solution, hint? My zenfone 4 also in brick bootloop intel logo status, can't enter to fastboot mode using key combination Power and Volume. It also cannot be detected using USB in PC.
Click to expand...
Click to collapse
me 2 same prblm dude got any solution
pls reply us

Flash image failure(FAILED (remote: ERROR: Image-SKU: 'TW_Zenfone' Device-SKU: 'WW_Zenfone'))
I get this error message while flashing using AFT

Moto X 1st Gen x1049 Bricked after Root Attempt

Hello XDAers,
So a couple of days ago I tried to root my Republic Wireless 1st gen Moto X (x1049) using the Suicide Flash method made by NiceneNerd for lollipop. What ended up happening is that the phone entered Qualcomm Emergency Mode, and stayed there since the script glitched when I tried running it. I tried many ways to get out of it - CrashXXL's method, s5610's method, and a few other methods to try and get out of this state. I can't even access bootloader at this point either - all there is is a black screen. And yes, i have tried every button combo possible to get out of this black screen. I dont have any phone for now - so if anybody has the solution or can contribute please help.
Thank you.

Heronicola said:
Hello XDAers,
So a couple of days ago I tried to root my Republic Wireless 1st gen Moto X (x1049) using the Suicide Flash method made by NiceneNerd for lollipop. What ended up happening is that the phone entered Qualcomm Emergency Mode, and stayed there since the script glitched when I tried running it. I tried many ways to get out of it - CrashXXL's method, s5610's method, and a few other methods to try and get out of this state. I can't even access bootloader at this point either - all there is is a black screen. And yes, i have tried every button combo possible to get out of this black screen. I dont have any phone for now - so if anybody has the solution or can contribute please help.
Thank you.
Click to expand...
Click to collapse
Did u make any progress sir?

hbenz2008 said:
Did u make any progress sir?
Click to expand...
Click to collapse
Unfortunately i did not. It still is in Qualcomm Emergency Mode, and Device Manager shows it as Qualcomm HS-USB QDLoader 9008

Heronicola said:
Unfortunately i did not. It still is in Qualcomm Emergency Mode, and Device Manager shows it as Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
There is a thread that will get you back up hopefully, look for "how to unbrick..." I will link you if needed

hbenz2008 said:
There is a thread that will get you back up hopefully, look for "how to unbrick..." I will link you if needed
Click to expand...
Click to collapse
Well, I have tried any links that are related to bricking and unbricking. For example - blankflash returns this -
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
sdl_hello() - Failed to receive ACK
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has been reset back to blank flash mode. Usually this is caused by power supply issues. Please try again with battery eliminator if it persists

Welp, i also just tried to pop off the back and i broke of the connector that connected the volume rocker. Im guessing then the volume button doesnt work anymore and i cant access fastboot anyways/

Heronicola said:
Welp, i also just tried to pop off the back and i broke of the connector that connected the volume rocker. Im guessing then the volume button doesnt work anymore and i cant access fastboot anyways/
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2629057

hbenz2008 said:
http://forum.xda-developers.com/showthread.php?t=2629057
Click to expand...
Click to collapse
i tried that too

502SO Failed Flashing & Can NOT enter Flash Mode

The device is Softbank version of X Performance, which is 502SO.
I tried to flash International ROM for the X Performance, ended up failing.
Then when I try to boot the device, the message says "Your device as been unlocked and the boot image is not working"
However as we know Japanese version cannot have bootloader unlocked (which i did not).
Tried entering flashmode pressing volume down and connecting it to the laptop.
The green light blinks, but nothing detected on laptop.
It is true that I can enter fastboot mode (Blue light mode), but no use as the bootloader is locked. Access to flash image is denied.
Already tried on two laptops, one Win10, one Win7, both no hope.
Any solutions for this?
It seems like I am not the only one with this problem.
(https://forum.xda-developers.com/xperia-x-performance/help/how-to-fix-boot-image-t3542326)

Tomoya2001 said:
The device is Softbank version of X Performance, which is 502SO.
I tried to flash International ROM for the X Performance, ended up failing.
Then when I try to boot the device, the message says "Your device as been unlocked and the boot image is not working"
However as we know Japanese version cannot have bootloader unlocked (which i did not).
Tried entering flashmode pressing volume down and connecting it to the laptop.
The green light blinks, but nothing detected on laptop.
It is true that I can enter fastboot mode (Blue light mode), but no use as the bootloader is locked. Access to flash image is denied.
Already tried on two laptops, one Win10, one Win7, both no hope.
Any solutions for this?
It seems like I am not the only one with this problem.
(https://forum.xda-developers.com/xperia-x-performance/help/how-to-fix-boot-image-t3542326)
Click to expand...
Click to collapse
issue solution : you need emmc file system dump and try flash via jtag method, but i dont have system dump 502SO

any solution??

gungsye said:
any solution??
Click to expand...
Click to collapse
sampean duwe ora ISP sama file dump nya, yen ra duwe rinio nangis bareng:crying::crying::crying:

juliotomad said:
sampean duwe ora ISP sama file dump nya, yen ra duwe rinio nangis bareng:crying::crying::crying:
Click to expand...
Click to collapse
waduh ga punya tuh, situ ada file dump nya?

gungsye said:
issue solution : you need emmc file system dump and try flash via jtag method, but i dont have system dump 502SO
Click to expand...
Click to collapse
did u solve the problem？

not yet

Bricked! Help me please.

Hello everyone
My brother's Mi A2 is bricked for no reason. I tried to solve this problem and searched a lot but didn't manage to solve it. I hope you can help.
* before telling my story here is some stuff to know:
- The phone was running official firmware and bootloader is locked, I've never played with it's software before.
- Oem unlocking option isn't turned on.
- The phone doesn't go to recovery mode, only fastboot or regular boot.
- I used EDL mode in every flashing attempt.
- I don't remember that there is a mi account assigned to the device.
* Here is what happened:
- The phone suddenly shut down during a call and never passed the AndroidOne logo after that.
- Tried EDL mode and miflash to flash the latest firmware. Flashing completed successfully but the phone still stuck on the androidone logo.
- Did it again and again but the result was constant.
- Tried flashing older firmware "Oreo 8.1" but during flashing system.img the process stopped with an error. (I don't remeber what the error was).
- I tried to turn on the phone but after showing AndroidOne logo This message appeared:
"Your device is corrupt. It can't be trusted and will not boot.
Visit this link on another device: g.co/ABH"
and the device shuts down in a minute.
Hint: Sometimes when I try to turn one the phone the above message appears after androidone logo and sometimes the device just keep showing the logo.
- Trying to flash any firmware version by using Miflash Beta gives an error message "Can not found programmer file" immediately. when I try again it gives: "can't read from port COM4", Changing the port gives the same error with different port number.
-When I use any other version of "Portable miflash", The flashing process starts normally but fails when trying to flash "dsp.img", giving an error of "writing time out".
- I tried reinstalling all drivers needed with no change at all.
I hope that you guys can help me solving this problem.
Thank you so much!

Try EDL mode opening your phone...

Badotti said:
Try EDL mode opening your phone...
Click to expand...
Click to collapse
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.

Ahmed A. Mohsen said:
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...

Badotti said:
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Click to expand...
Click to collapse
I opened the phone and used edl mode already but the problem is still present.

up

Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x

HTCDevil said:
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
Click to expand...
Click to collapse
This needs bootloader to be unlocked and my device's bootloader is locked.
Any solutions?

Go to service center this is last option you save RIP mi a2 ?

As I can see from picture you have posted, your bootloader is unlocked.

SkullSatan88 said:
Go to service center this is last option you save RIP mi a2
Click to expand...
Click to collapse
They refused to receive my device because I bought it from another country.

bomil said:
As I can see from picture you have posted, your bootloader is unlocked.
Click to expand...
Click to collapse
when I checked bootloader status in the beginning it was locked.
Are you sure that it's now unlocked?

Text me on telegram. @dejavutr

Question The current image (boot/recovery) have been destroyed

Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!

Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me

Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon

Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing

hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha

KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware

DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware

KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files

I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.

KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?

yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials

KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.

yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot

Damn!! I hope you find some way to fix your device. Good luck.

关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安

I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate

GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.

hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?

yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.

hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)