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
Is it possible to flash a (stock) rom on ascend p7 if I format the system?
Backround: I want a complete fresh system.
My problems:
If I do a factory reset, I´m nor enanbled to start fastboot mode.
Also it isn't possible to connect my phone to the pc and use adb.
So I cant flash TWRP to use my nandroid.
I'm on stock-recovery to install a stock update.zip
So I didn't do anything for now, because I'm not shure that it is possible to get my system back.
Any solutions?
To enter to download mode plug usb cable and restart device with Power and Vol(-) keys holding.
Sent from my HUAWEI P7-L10
Ziolek67 said:
To enter to download mode plug usb cable and restart device with Power and Vol(-) keys holding.
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
thanks for answering - but what happens then?
jangofritz said:
thanks for answering - but what happens then?
Click to expand...
Click to collapse
You will enter fastboot mode.
Sent from my HUAWEI P7-L10
if you can access the fastboot mode Might:
Download the firmaware you had installed and remove syste.img with extractor Huawei Firmware
Then turn the P7 in fastboot mode and put the system with the command
fastboot flash system system.img if all goes well you should get out of trouble.
Try and comet that you just did.
Hi
I see someone here have problems with bricked phone. It just keeps restarting and you cant even turn it off.
The problem is here that UPDATE never ended to 100% and software successfully changed boot.img to the new one
but with old system on the phone.
Its even worse if you have TWRP recovery installed before update then it will brick the phone too.
Allways install stock recovery on current rom before update firmware.
Ok i will start now with this guide because i had same problem and fixed it by myself.
I will not put any links to downloads find them self GOOGLE is your friend
First of all if you were on B200 5.0.1 version of android then you need B170 firmware to extract boot.img and recovery.img from
the UPDATE.APP file
For that you need a software called Huawei Firmware Extractor
Download it and install
Now you need even ADB/FASTBOOT on the computer. If you dont have download and install. Install even drivers for the phone
Now Open the Huawei Extractor and add the UPDATE.APP file.
Now you will see alot of files below
Now mark the boot.img system.img and recovery.img and extract them to the desktop of your PC
Now copy those files to the ADB/FASTBOOT folder.
You phone i still under the bootloop and you need to get it into FASTBOOT mode. Only way to do it is to plug in USB cable to the phone.
Now as soon the phone reboots by itself hold Power and Vol down button until you see white screen and fastboot mode
Now go to the ADB/FASTBOOT folder where you copyed files and hold shift and press right mouse button to get "Open command window here"
So you will be in fastboot and you will see C:/ADB that is right directory
Now start with fastboot erase cache
Then write fastboot flash boot boot.img and hit enter
When done do following fastboot flash recovery recovery.img and hit enter
You can if you want even try to flash system.img by writing fastboot flash system system.img or fastboot flash system.img dont remember that combination
but try and see wich works.
Now write fastboot rebootand phone will reboot . If you still have bootloop then as soon phone goes black then Hold Vol+up and Power until you see recovery.
Over there make factory reset and cache and then reboot.
If you still cant boot into recovery then you need to get Firmware B170 and put it on you SD card in DLOAD folder
to flash it from scratch. Same here is that you need to have USB plugged in in order to get to EMUI flash mode or it will wont work.
Remember that you only need UPDATE.APP in the DLOAD folder from B170 firmware.
I know my English sucks but im trying to help...
hello, i tried bouth solutions and i cant get my phone to boot up i dont now maybe i am doing something wrong i was on b200 rooted and twrp instaled an i updated to android 6 and i m stuck in bootloop you can help me with something i am out of ideas. thanks in advance
noraru said:
hello, i tried bouth solutions and i cant get my phone to boot up i dont now maybe i am doing something wrong i was on b200 rooted and twrp instaled an i updated to android 6 and i m stuck in bootloop you can help me with something i am out of ideas. thanks in advance
Click to expand...
Click to collapse
Yes, this is the your mistake
Never update firmware with instaled TWRP. First you need to flash to factory recovery then install the original firmware like B170(B200), then update to Marshmallow
Nevermind, fixed it.
sokkoban said:
Yes, this is the your mistake
Never update firmware with instaled TWRP. First you need to flash to factory recovery then install the original firmware like B170(B200), then update to Marshmallow
Click to expand...
Click to collapse
i know is my mistake , i flash recovery img from b170 but i cant get in to recovery mode anymore hao much i have to push the vol up+power buton? i only can boot in to fastboot
rndll said:
Nevermind, fixed it.
Click to expand...
Click to collapse
How please ?
TopperBG said:
How please ?
Click to expand...
Click to collapse
You don't flash img files through the recovery. Flash recovery.img, boot.img, system.img and cust.img manually through the fastboot screen (vol down + power) using either the windows command or mac terminal.
Thank you, at the moment I'm trying the same.
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
rndll said:
You don't flash img files through the recovery. Flash recovery.img, boot.img, system.img and cust.img manually through the fastboot screen (vol down + power) using either the windows command or mac terminal.
Click to expand...
Click to collapse
Which firmware, I've tried with full B200 and extracted images, but no success. B170 ?
Don't have success, please give advices ?
1. I Download the B313 update and extract the boot.img and recovery.img from update.app using Huawei Firmware Extractor.
2. Connect your P8 to your PC/Mac. Hold down volume down + power just before you feel the vibration and the Huawei logo shows up. This will boot you to the Fastboot/Rescue screen.
3. Using the windows command prompt or mac terminal, flash the B313 recovery and boot images using Fastboot:
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
After flashing these, if you reboot normally, the bootloop should be gone but you will get stuck at the Huawei logo. However, you'll now be able to access recovery (volume up + power) and the 3 button update (vol up + vol down + power) modes.
You can now reboot either holding the power down or issue a fastboot command:
Code:
fastboot reboot
4. This may be optional and may not have any bearing but at this point I was ok with losing data just to get the phone booting again. Boot to the recovery (volume up + power) Yes, it's not that easy using the buttons. Just try it until you get the recovery to boot.
In recovery select Wipe data/factory reset and Wipe cache partition.
5. Download the B170 Full ROM and extract the dload and custom folder to your microSD. Use a card adapter/card reader.
6. IMPORTANT: Disconnect your P8 from your computer if it is still connected. Doing the next step while you're connected through USB will cause the update to get stuck at 90% and if you force a reboot, your device will bootloop again.
7. Reboot from the recovery and boot into the EMUI Updater using the 3-button method (volume up + volume down + power). Let the phone update and voila! You're back in business!
Confirm, it works!
@rndll bold and make red color B313
TopperBG said:
Confirm, it works!
@rndll bold and make red color B313
Click to expand...
Click to collapse
so it works , i have to gflash boot,cache and recovery img from b313?
I've interrupted update (B313), write to SD /dload full B200 and started Recovery. Update gone just fine and phone started with brand new B200. Even don't reset or wipe !
noraru said:
so it works , i have to gflash boot,cache and recovery img from b313?
Click to expand...
Click to collapse
You only need the boot and recovery images.
rndll said:
You only need the boot and recovery images.
Click to expand...
Click to collapse
thanks my friend it woooorks, my phone booted up at last, thank you very much you saved me i allready packed my phone to take it to the service you are great thanks again for your help.
noraru said:
thanks my friend it woooorks, my phone booted up at last, thank you very much you saved me i allready packed my phone to take it to the service you are great thanks again for your help.
Click to expand...
Click to collapse
You're welcome.
:good:
Hey TopperBG,
i'm in the same Bootloop as you described.
I tried every ROM I found on the internet but the combo with Vol Up + Vol Down + Power won't work. There ist always a fail after 1 % loading.
The second I tried was on fast boot. Problem im my boot loader is locked. So there is no chance for me to get something flashed.
Last option was your comment. I've loaded the B200 Rom on my SD-Card in /dload and tried (the second time) the Vol Up+Vol Down+ Power combo. No success. Then I tried just Vol Up+Power to get the Recovery mode as you described. But I have no chance to boot to recovery mode.
Do I forgot a step ??
Please help
Thanks
Flo
Tell me first what you've done when become to bloop ?
With boot and recovery from that ROM you must flash.
If you can forcibly start update (vol+ vol- power) you have a chance to update properly with update.app in /dload folder
I tried to update through local update on the Phone. But not with .zip. I tried the .app directly. Now i know it was the wrong Choice.
Flash with fastboot is no option for me because of the locked bootloader.
If I do the Force start with the new marshmallow rom (update.app) there is a warning that i'm using the wrong version for my phone.
Good evening gents,
Since I broke my BIOS on my m5c5 by flashing the wrong one with Tecknights Tutorial, I was desperately trying to get back to the working BIOS.
Thanks to ionioni we have a way to unbrick our devices (as long as they still boot into dnx).
I accidentally flashed the wrong BIOS on to my X98 Air iii (m5c5) and thought i bricked it beyond repair (except opening it up and flashing it with EEPROM Clip).
Now we have a solution to flash the DUAL BOOT - BIOS to the m5c5 through dnx mode:
WARNING: EVERYTHING YOU DO, YOU DO AT YOUR OWN RISK! Only tested on m5c5! Using it on other devices can HARDBRICK!!!
IMPORTANT: DO NOT CUT THE USB OR POWER AND WATCH OUT THAT THERE IS ENOUGH POWER IN THE ACCU.
1. Copy the following files into your fastboot directory on your pc:
https://anonfiles.com/file/28e5e4990eee25d74ff4d6cc99fdb548
2. Boot the device into dnx/fastboot (pressing power and Vol+/Vol- at the same time)
3. Plug the device in via usb, open up a command prompt in your fastboot directory and type the following:
fastboot devices #Check if device is recognized
fastboot flash osloader efilinux.efi #Push Efiloader onto device
fastboot boot bios_restore_m5c5.img #restores the dual boot bios
4. Wait for reboot. There is now a 100 second timer in case of second guesses and afterwards update notifications during the flash. It takes between 3-5 Minutes. DO NOT FORCE REBOOT it WILL HARDBRICK
Be happy to have unbricked your BIOS. And thank ionioni !! PM him if you have any questions!
Fastboot boot --> that instruction not flashing anyting only booting partition to ram .
What is doing that img ? I'm curious .
mirek190 said:
Fastboot boot --> that instruction not flashing anyting only booting partition to ram .
What is doing that img ? I'm curious .
Click to expand...
Click to collapse
it flashes the bios @mirco446 gave me (also asked him and sent me the droidboot.img from the stock)
i used the droidboot.img sent as a base and modified it (included in it the bios sent together with the intel FPT binary for writing a bios file) and it just boots and runs when boot is completed the binary to flash the bios file (this is why one should NOT reset or power off the device after it enters the fastboot boot command as this could result in a partially written bios and this translates to HARD-BRICK). at the end it reboots to load the new bios
normally should also output some messages but for some reason it doesnt capture the framebuffer device and since i don't own the device i cannot 'debug' to check on why... but this is only a minor issue (not having status messages), so one just needs to wait a few minutes until the device reboots confirming that the bios was wrote.
nothing fancy
Interesting ... thanks for explanation .
And he did it for C5J8 too, mine is alive too.
hello i have the same problem with my m5c5 but it don't work for me.
i have this message:
entering dnx mode.
waiting for fastboot command.... efilinux [ 0.000449] ERROR[get_parth:334] couldn't find boot device handle.
Good drivers?
i use driver from TecKnight's Teclast Tutorials series.
i try under linux and same problem.
[email protected] ~/Téléchargements $ sudo fastboot devices
Baytrail02D31E57 fastboot
[email protected] ~/Téléchargements $ sudo fastboot flash osloader efilinux.efi
sending 'osloader' (2463 KB)...
OKAY [ 0.109s]
writing 'osloader'...
OKAY [ 0.008s]
finished. total time: 0.117s
[email protected] ~/Téléchargements $ sudo fastboot boot restore_bios_m5c5.img
downloading 'boot.img'...
OKAY [ 0.791s]
booting...
OKAY [ 0.003s]
finished. total time: 0.794s
tablet wait ~30s and restart on red logo and bootloop.
i upload my original bios but not dual boot:
https://drive.google.com/open?id=0B_A8FEPnUL61WHQ4RzAxOXpzZGM
edit: problem solved for me thank you ionioni!!!!!
bosondehiggs said:
i upload my original bios but not dual boot:
https://drive.google.com/open?id=0B_A8FEPnUL61WHQ4RzAxOXpzZGM
Click to expand...
Click to collapse
i won't invest anymore time in this. already tried this below stuff... not working
seems that it doesn't boot the image at all, this could be due to an existing IA32 bios (post a link to the bios you flashed so i can check)
until then...
you can try again and skip the first 'fastboot flash osloader efilinux.efi' if it still doesn't work replace the efilinux.efi file with one from a x86 older rom
no matter what wait until the tab reboots by itself after you enter the 'fastboot boot' command(~30-40 seconds if it cannot boot, at most 5 minutes if it does, in this case it will also flash your bios)
ionioni said:
i cannot access the share you posted (make it public)
seems that it doesn't boot the image at all, this could be due to an existing IA32 bios (post a link to the bios you flashed so i can check)
until then...
you can try again and skip the first 'fastboot flash osloader efilinux.efi' if it still doesn't work replace the efilinux.efi file with one from a x86 older rom
no matter what wait until the tab reboots by itself after you enter the 'fastboot boot' command(~30-40 seconds if it cannot boot, at most 5 minutes if it does, in this case it will also flash your bios)
Click to expand...
Click to collapse
Hi, can you make one for c6j7?
Hi,
I have exact same problem as bosondehiggs. "couldn't find boot device handle." when I try to flash the restore bios.img. I used the file with the link at top of thread.
Any idea?
Thanks for your help
Hi,
the same problem to me on my Teclast Air III !!
I hope anyone who solved the problem can help us ...
Thx a lot
Alex
Try my idea, maybe help you: http://forum.xda-developers.com/showpost.php?p=64725703&postcount=26
Hi,
thank you Blackbile. Now its working... :good:
Alex
those who cannot restore, see here http://forum.xda-developers.com/showpost.php?p=64736792&postcount=36
acnic said:
Hi,
thank you Blackbile. Now its working... :good:
Alex
Click to expand...
Click to collapse
But what was the solution?????
I booted into BIOS and did what you have written and press restore defaults. Then i flashed again the efilinux and the restore bios. I had the same error and no reboot from the tablet! After waiting 10 minutes i decided to press the Power Button and bling there it is...
Now i have dual boot, but only Mireks Rom installed.
The next days i will try to install Windows, too.
I hope there are no problems again.
Thx for your help...
Alex
I flashed my M5C6 softbricked with the BIOS for C5J8 (2.05c) from the other post and it works now my tablet. The only problem I had me too is that the system doesn't reboot automatically after flashing process like @acnic so after 7 minutes I rebooted manually (with all my fingers crossed), finally the tablet has started like usual (I did the restore default settings into BIOS).
Now the only "problem" I had is that when I shutdown the system from Android or W10, I can't restart with power button so I need to press 10s before to can start the system again, Someone have an idea of this behaviour?
Many thanks again for your incredible work and support!!
Santi
Enviado desde mi SM-G900FD
Gitantos: http://forum.xda-developers.com/x98-air/help/x98-air-3g-doest-power-t3287417
*****************
How did you bricked?
While the restoring happened, did you see messages on the screen as I posted in my thread?
blackbile said:
Gitantos: http://forum.xda-developers.com/x98-air/help/x98-air-3g-doest-power-t3287417
*****************
How did you bricked?
While the restoring happened, did you see messages on the screen as I posted in my thread?
Click to expand...
Click to collapse
Hello blackbile, I bricked using the flashing method from Techknight's. I have unbricked with your guide (BIOS from C5J8)
Enviado desde mi SM-G900FD
Hi everyone
Some days ago, xiaomi sent me the approve for unlocking the bootloader
so i followed the procedure
Here yet the first strange thing:
the xiaomi programm for bootloader unlock says that after unlock my device will be formatted at all
But after my mi5 rebooted it was all as before
no data loss
And fingerprint is working
Then i wanted to flash the TWRP following this thread: http://en.miui.com/thread-245756-1-1.html (In the very last post there is an update for fix the touch problem)
I downloaded Mi Pc Suite, adb driver and fastboot driver (In fact both adb and fastboot recognize my device)
And then i flashed the TWRP as mentioned
But if i disconnect my phone, it wont reboot autmatically, i need to press power button for like 8 seconds
If i press power button for 8s it will reboot normally into android
If i connect the phone and through adb i write adb reboot recovery it will reboot into a black screen with a phone and a cable (that i think mean that the recovery isnt installed first, and second it's like bootloader mode)
How to guys? I need TWRP to flash the new weekly
Thanks a lot to all
Federico
Download cofface fastboot tool here attached and the twrp recovery image below.
http://www.mediafire.com/download/bx0ru3cfgk1kv01/cofface_twrp_recovery_gemini.img
Boot the fastboot by maintaining power + volume down button, connect your phone to the computer.
Extract this .zip to your desktop.
Open Command Window and direct it to the extracted folder.
Note : If you use Windows 7 and above, maintain Shift key and right click to extracted folder., and choose "Open Command Window here."
Type "fastboot devices" to see if your Mi 5 is detected.
Type "fastboot flash recovery cofface_twrp_recovery_gemini.img"
When it's all done, type "fastboot boot cofface_twrp_recovery_gemini.img".
There will be a bug where the screen will be unreactive. Just click power button and let screen off during 3 minutes, when you turn the screen on again, the screen will function again.
I have instaled the wrong twrp3.0.0.0 having a bug now I have with the new adb twrp3.0.2.0 instaliert that would work.
only when I stabel who wants to install the new and I'm going in again into TWRP is the old version 3.0.0.0 TWRP back where the touch is not working! how can I fix this? and remove them from Completely mobile
elien100 said:
I have instaled the wrong twrp3.0.0.0 having a bug now I have with the new adb twrp3.0.2.0 instaliert that would work.
only when I stabel who wants to install the new and I'm going in again into TWRP is the old version 3.0.0.0 TWRP back where the touch is not working! how can I fix this? and remove them from Completely mobile
Click to expand...
Click to collapse
The same thing happened to me. I want to know too. (How to uninstall the old TRWP 3.0.0.0 completely.)
TWRP for MI5
The problem seems to be that the MI5 use two different kinds of LCD (JDI or LGD); you can know your kind in settings - about phone - tap 5 times on kernel version - 2. check version info - lcm information.
You can download the appropriate twrp from the section download of miui italia
Thanks to miui italia for the solution
The solution is taken from original post in this forum, not miui.it...
Inviato dal mio PLK-L01 utilizzando Tapatalk
Try format your phone completely , this will make TWRP overwrite the stock recovery
Command ; http://forum.xda-developers.com/nexus-6p/general/fix-twrp-hangs-splash-screen-android-t3438262