Related
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
Hi, I have LG D405N with hard brick (bad recovery.img flashed). From this moment phone doesn't give any signals.
Trying to solve this problem, by copy aboot.img to partition on linux system.
Not work. I think i have a bad aboot.img.
Anyone can help me?
Are you able to get to download mode? If so flash the KDZ.
same problem no download mode i need aboot file please
k01vu said:
Hi, I have LG D405N with hard brick (bad recovery.img flashed). From this moment phone doesn't give any signals.
Trying to solve this problem, by copy aboot.img to partition on linux system.
Not work. I think i have a bad aboot.img.
Anyone can help me?
Click to expand...
Click to collapse
see my guide here: http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
Hello
Can anyome help me please? I bricked my Lg L90 P405n after choose bad recovery.img file. Phone is dead, when i connect it to the computer, i see Android USB serial device and one drive with etc 60MB capacity.
I tried some advices from forum, but nothing was succesful.
Now i see phone as QUALCOM USB .... device , but when i set boardiag and click on Start button a see message Failed during loading flash programmer, Test aborted when i choose G2MLTE (MSM8926) and Device was not found in dload trying flash programmer when i choose W7 (MSM8226).
Attempts over LG Flash tool ended after 4% with error communication with the phone.
Have anyone correct method for D405n and correct MBM files with partition.txt?
Thank you
Martin
mcambel said:
Hello
Can anyome help me please? I bricked my Lg L90 P405n after choose bad recovery.img file. Phone is dead, when i connect it to the computer, i see Android USB serial device and one drive with etc 60MB capacity.
I tried some advices from forum, but nothing was succesful.
Now i see phone as QUALCOM USB .... device , but when i set boardiag and click on Start button a see message Failed during loading flash programmer, Test aborted when i choose G2MLTE (MSM8926) and Device was not found in dload trying flash programmer when i choose W7 (MSM8226).
Attempts over LG Flash tool ended after 4% with error communication with the phone.
Have anyone correct method for D405n and correct MBM files with partition.txt?
Thank you
Martin
Click to expand...
Click to collapse
Did you choose the right Com Port in b2b?
Yes i choose correct one. Today i make some other things and now is phone functional, but after restore phone lost IMEI information.
I use advice in this post http://forum.xda-developers.com/showpost.php?p=61636749&postcount=34.
Next question - is some way to restore/fill IMEI ?
Guys i have got my self into a serious help any help will be much appreciated.
I Was running a resurrection Remix Port by @uncomment from here: http://forum.xda-developers.com/xpe...m-dogolollipop-resurrection-remix-lp-t3044032 but the thing is it wasn't having any recoveries in it so i found this thread by @hagar006 http://forum.xda-developers.com/xpe...resurrection-remix-v5-5-5-unofficial-t3207914, as it is a another new build for RR rom So i flashed the boot.img from this thread which is having a recovery in it.. so i downloaded the recovery and flashed it via terminal emulator for android and the time i reeboted my phone its gone. i mean the phn ain't working at all its not even charging i tried to flash it flashtool but its unable to connect it to the computer as its not being detected, not even sony pc companion working. no led lights blinking nothing i am afraid if the device is working or not.. is there any way to revive the device and could anyone please explain what happened to the device and is there any chance that it can be repaired in service center.. please anyone who could help please put some light in this thread.
@uncomment @hagar006 @xenius9 @airlessproject @Alx31TLse @vaisakh7
anyone Please.
StyleAJ said:
Guys i have got my self into a serious help any help will be much appreciated.
I Was running a resurrection Remix Port by @uncomment from here: http://forum.xda-developers.com/xpe...m-dogolollipop-resurrection-remix-lp-t3044032 but the thing is it wasn't having any recoveries in it so i found this thread by @hagar006 http://forum.xda-developers.com/xpe...resurrection-remix-v5-5-5-unofficial-t3207914, as it is a another new build for RR rom So i flashed the boot.img from this thread which is having a recovery in it.. so i downloaded the recovery and flashed it via terminal emulator for android and the time i reeboted my phone its gone. i mean the phn ain't working at all its not even charging i tried to flash it flashtool but its unable to connect it to the computer as its not being detected, not even sony pc companion working. no led lights blinking nothing i am afraid if the device is working or not.. is there any way to revive the device and could anyone please explain what happened to the device and is there any chance that it can be repaired in service center.. please anyone who could help please put some light in this thread.
@uncomment @hagar006 @xenius9 @airlessproject @Alx31TLse @vaisakh7
anyone Please.
Click to expand...
Click to collapse
What command did you use to flash the kernel?
Can you access fastboot?
Tapped from my ❶+❷
What command did you use? Did you flash it to the kernel partition or the fotakernel partition? Either way, your flashmode and fastboot should still work; unless you accidentally flashed over the TA partition, I don't see how any of what you did would hard brick the device.
vaisakh7 said:
What command did you use to flash the kernel?
Can you access fastboot?
Tapped from my ❶+❷
Click to expand...
Click to collapse
SirVer said:
What command did you use? Did you flash it to the kernel partition or the fotakernel partition? Either way, your flashmode and fastboot should still work; unless you accidentally flashed over the TA partition, I don't see how any of what you did would hard brick the device.
Click to expand...
Click to collapse
this is the command i used to : dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
but hte thing is i flashe dthe whole boot.img which was also having as kernal and not just the recovery
SirVer said:
What command did you use? Did you flash it to the kernel partition or the fotakernel partition? Either way, your flashmode and fastboot should still work; unless you accidentally flashed over the TA partition, I don't see how any of what you did would hard brick the device.
Click to expand...
Click to collapse
i also have the orignal ta partion backed up , so it could help if i have flashed it into ta partion
Dude... mmcblk0p6 shows up on my device as the aboot partition on my device. Aboot as in "Android Bootloader", the thing that (IIRC) loads the download mode in Samsung devices, and I think the flash mode in others. No wonder you couldn't use flashmode. Who told you to flash it there?
In any case, this could indeed cause a hard brick. If you're lucky, fastboot might still work; if it does, you could ask someone for an aboot image (don't know if an FTF might contain it) and flash it that way. If not... Sorry bro, only thing you can try is the service center, if you're lucky they might be able to help you out.
Good luck. ?
SirVer said:
Dude... mmcblk0p6 shows up on my device as the aboot partition on my device. Aboot as in "Android Bootloader", the thing that (IIRC) loads the download mode in Samsung devices, and I think the flash mode in others. No wonder you couldn't use flashmode. Who told you to flash it there?
In any case, this could indeed cause a hard brick. If you're lucky, fastboot might still work; if it does, you could ask someone for an aboot image (don't know if an FTF might contain it) and flash it that way. If not... Sorry bro, only thing you can try is the service center, if you're lucky they might be able to help you out.
Good luck.
Click to expand...
Click to collapse
thanx man thanx for the help i will try my luck..
SirVer said:
Dude... mmcblk0p6 shows up on my device as the aboot partition on my device. Aboot as in "Android Bootloader", the thing that (IIRC) loads the download mode in Samsung devices, and I think the flash mode in others. No wonder you couldn't use flashmode. Who told you to flash it there?
In any case, this could indeed cause a hard brick. If you're lucky, fastboot might still work; if it does, you could ask someone for an aboot image (don't know if an FTF might contain it) and flash it that way. If not... Sorry bro, only thing you can try is the service center, if you're lucky they might be able to help you out.
Good luck.
Click to expand...
Click to collapse
can you please ellaborate the procedure i am unable to find a guide.. just tell me what to do
and how to flash through fastboot
I'm sorry, I don't know where you could get one online; I don't really have time to try and make an image of the partition and send it to you. Hell, I don't even know how you'd flash it if you got it (I'm not that experienced with fastboot). What I suggest is making a new thread requesting an image of the partition, and help with flashing it. Hopefully I'll have some free time in a few days (or a week), and if you're still stuck by that point, I'll do my best to find a way.
My N8(TA1012) is hard bricked. I tried OST 6.0.4 and 6.1.2 and got error. I enter only Twrp and download mode. In Twrp, my files are corrupt. How to I fix without service?
the easy guide is use ntool.
If can use flash system and boot.img
komisermurat said:
My N8(TA1012) is hard bricked. I tried OST 6.0.4 and 6.1.2 and got error. I enter only Twrp and download mode. In Twrp, my files are corrupt. How to I fix without service?
Click to expand...
Click to collapse
Looks like you have the unlocked bootloader. Do fastboot flash unlock "your unlock.key" than fastboot oem unlock_critical and confirm unlocking on your device. Critical area restricts booting of service boots so OST can`t flash it. When the critical area is unlocked you can flash anything you want. I have TA-1004 and it works for me. I have rolled back to Nougat from Oreo this method. Hope it helps you.
komisermurat said:
My N8(TA1012) is hard bricked. I tried OST 6.0.4 and 6.1.2 and got error. I enter only Twrp and download mode. In Twrp, my files are corrupt. How to I fix without service?
Click to expand...
Click to collapse
What error you get?
But if you you have really hard-bricked (broken or drowned) nothing will help. The chips may be broken permanently and only service-center can repair it. Flashing the device in this state may kill it! But if its just result of unseccessful software experiments - try to do as I said above.
Hello everyone today i flash an incompatible rom with twrp and my screen turn completely black After reboot twrp in recovery .
Do you have solution ?
Sorry for my bad English
Hi if you can open bootloader, flash stock rom
The easy solution is press power+volume down. Phone should boot into fastboot mode. Then flash fastboot ROM without relocking the bootloader.
The other way is taking phone to service center. They'll flash stock in edl mode.
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Doesn't EDL need authorized mi account these days? It'd better to visit service center because installing EDL driver & all the fuss will be useless
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
RAMBO29 said:
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Click to expand...
Click to collapse
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Andrologic said:
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
Click to expand...
Click to collapse
I see it's super interesting as information I did not know that we could flash only a partition with QFIL.
Unfortunately I could not find the firehose files for the phone as the phone is probably very recent.
I had to pay someone to unlock my phone with an edl account of course .
My work now
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Miui 13 said:
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Click to expand...
Click to collapse
RAMBO29 said:
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Click to expand...
Click to collapse
yes it was done online I unlocked it with TeamViewer thanks to an edl account