Hello all..
I've struggled almost a week to unbrick my yureka AO5510. I can able get into bootloader mode by using sd boot method. Also i can able to get into Qualcomm HS USB QDLOADER 9008 by shorting board pins.
But in but in bootloader mode after flash_all.bat done successfully device remains same. No boot. In 9008 mode Sahara protocol error. Couldn't flash.
Finally Here is the solution and cause..
Cause : Corrupted radio modem in bootloader (or something related to boot)
Solution:
Get into bootloader mode using this method https://www.youtube.com/watch?v=TooHuDpKyzA ...
(If you can't get into bootloader mode using this method then nothing helps, i've tried even flashing my device using JTAG boxes)
As per video instructions even after flash_all.bat done if yureka remains bricked here comes the solution.
Download flash_radio.bat(zipped) from link below. Place it in stock firmware folder and run. After everything done successfully Run fastboot -i 0x1ebf reboot
Voila.. you got your device back
This is my first thread. Forgive me if anything uncompleted.
Shiva
View attachment flash-radio.zip
Someone please revert back with results.. i've spent many hours in this.. i can really help you i believe to bring your bricked device back...
yureka hardbrick
I did use your solution and results are very good.but I have a problem Touch not working properly after locking screen. If u tell me how to format bootloader of yureka and flash a very fresh ROM in it.
himan1995 said:
I did use your solution and results are very good.but I have a problem Touch not working properly after locking screen. If u tell me how to format bootloader of yureka and flash a very fresh ROM in it.
Click to expand...
Click to collapse
You dont have to format whole eMMc bootloader. just flash the rom either using fastboot mode or custom recoveries.
xboxxtech said:
You dont have to format whole eMMc bootloader. just flash the rom either using fastboot mode or custom recoveries.
Click to expand...
Click to collapse
I flash yureka plus ROM in yureka via fastboot and causes of that when I get back to my stock.my mobile touch screen work perfectly until I lock mobile screen.
himan1995 said:
I flash yureka plus ROM in yureka via fastboot and causes of that when I get back to my stock.my mobile touch screen work perfectly until I lock mobile screen.
Click to expand...
Click to collapse
Try [Tool] [OFFICIAL] UN-brick yureka device using Annabathina tool V1.0 avilable in XDA.
xboxxtech said:
Try [Tool] [OFFICIAL] UN-brick yureka device using Annabathina tool V1.0 avilable in XDA.
Click to expand...
Click to collapse
I will try it . thanks for reply. Hope its works for me
Related
i'm not experienced with such things
i gained some knowledge from googling the last few days
i have access to Fastboot ADB and CWM recovery
it started when i tried to flash the rom but it stopped on 35% on the yellow bar on SP Flash
i tried more than 2 cables , 5 different SP flash tools versions
also tried to
adb push
fastboot flash
but always failure
the device was not rooted and i think this is the dead end point :crying:
is there a way to root it using ADB -CWM-Fastboot ?!
is there any more tries i take ?!
BTW also IMEI Shows nothing on MT Droid Tool
thanks in advance
same issue to me
first make a backup from your IMEI then try to format your device (except bl) using flahtool format whole flash feature
Red-code said:
first make a backup from your IMEI then try to format your device (except bl) using flahtool format whole flash feature
Click to expand...
Click to collapse
How to backup from imei? Just try many pc and cable still cant flash. Brom error. Any solution?
Please help, I need proffessional help.
Android Phone: ASUS Zenfone 2 Laser 5.0 (ROOTED)
Android Firmware: 5.0.2 Lollipop
Aim: To enter into Fastboot mode and Recovery Mode without problems
Situation: Recently installed TWRP Recovery in-app and through software, but when I try to enter in Fastboot Mode (HOLD POWER & VOLUMEUP) or even Recovery Mode (HOLD POWER & VOLUMEDOWN), I just end up in a hanged out ASUS Logo. I can't do anything except pulling out the battery myself and putting it back then booting the device through power button to boot it normally. I don't know if it's the problem with the model, or the phone's system itself, or it's just a bug, or a problem when I rooted my device through ADB.
(Note: When I rooted the device, I wasn't even able to see the blue "FASTBOOT MODE" when I tried it, I only saw the ASUS logo as well.)
For anyone who has any idea on what's going on with my device, please reply and help me. I really want to have the benefits of a rooted phone completly and I'm a new root user so I need assistance.
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
CrimsonShade09 said:
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
Click to expand...
Click to collapse
Do you can acesse to twrp recovery on your device
Same problem.....waiting for helping, please
mohamedelkholy said:
Do you can acesse to twrp recovery on your device
Click to expand...
Click to collapse
I think I have "access" to TWRP recovery. However, I can only access it through booting it up from ADB. I used the command "adb reboot bootloader" to boot it to fastboot mode, however only the ASUS screen appears but I treated it as the fastboot mode itself. Then I checked if it was really on fastboot mode through "fastboot devices" and it showed my serial number. I can only enter into TWRP using "fastboot boot twrp.img" . I don't know if I already installed it because although I opened it, I can't do it from the phone (POWER+VOLUMEDOWN)
Ok now boot twrp and then flashamodified zip or cm13 and your phone should eork you dhould to have unlockrd bootloader
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
...anybody?
Up.....
sh4d3_ said:
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
Click to expand...
Click to collapse
Up...
QFIL or AFT can be the solution.
I have a similar problem, a hard bricked Z00ED (ZE500KL) not able to get into fastboot or recovery.
after reading some thread here an there. that are Processor / Chipset specific flash tools that help flash bootloaders and repartition hard bricked device.
For mobiles with MediaTec devices, there is a tool called SP Flash Tool. I wasted a whole day with it. then understood that Z00ED (ZE500KL) has a Qualcomm Processor MSM8916
Therefore we need a Qualcomm Flasher here (QFIL )
But nos I am stuck with getting firmware for ZE500KL that can be used by QFIL tool, It should have a firehouse*.mbr file that is the programmer (dependent on CPU of the phone) and a rawprogram*.hex file that I don't know where to get from.
Thanks... It seems a bit less wild, but in any case no solving, yet
Up! ...anyone?
Up!
(URGENT) HARDBRICK ... Please help me. I installed a custom kernel in the AICP rom, but I installed it on the recovery partition. The phone now turns on but does not leave the leeco screen. It does not go into recovery or fastboot mode. I've downloaded the Qualcom QPST tool but I do not know how to use it or the files I need ... Does anyone have a solution?
Try this
https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
ajegile said:
Try this
https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
Click to expand...
Click to collapse
As said, the device does not leave the screen of the leeco, does not start in recovery and fastboot mode. So there is no way I can restore using TWRP. The device is recognized only by the qualcom tool. I need a guide on how to use it. Anyway, thank you for your time.
zapinho said:
As said, the device does not leave the screen of the leeco, does not start in recovery and fastboot mode. So there is no way I can restore using TWRP. The device is recognized only by the qualcom tool. I need a guide on how to use it. Anyway, thank you for your time.
Click to expand...
Click to collapse
Try to boot into fastboot from ADB and install a new twrp
My phone is LeEco Le 2 x620.
It has been bricked after fastboot reboot command. The phone shows red light only and still connecting/disconnecting every time I connect it to my PC.
After searching, I found that there is a way to unbrick it using SP Flash Tool.
I downloaded everything needed such as the SP Flash Tool, the firmware, the MediaTec Driver installer....
The problem is that I am facing problems that SP Flash Tool is not recognising my device. Showing errors such as ERROR: STATUS_BROM_CMD_STARTCMD_FAIL, and BROM_ERROR: STATUS_ERR.
Please help me, am about to lose everything!!
a7madhazim said:
My phone is LeEco Le 2 x620.
It has been bricked after fastboot reboot command. The phone shows red light only and still connecting/disconnecting every time I connect it to my PC.
After searching, I found that there is a way to unbrick it using SP Flash Tool.
I downloaded everything needed such as the SP Flash Tool, the firmware, the MediaTec Driver installer....
The problem is that I am facing problems that SP Flash Tool is not recognising my device. Showing errors such as ERROR: STATUS_BROM_CMD_STARTCMD_FAIL, and BROM_ERROR: STATUS_ERR.
Please help me, am about to lose everything!!
Click to expand...
Click to collapse
you need choose secureboot /DA_PL_HIGH.bin at download Agent. when flash at sp tools.
tony770101 said:
you need choose secureboot /DA_PL_HIGH.bin at download Agent. when flash at sp tools.
Click to expand...
Click to collapse
Try the firmware, it will help you unbrick your phone.
https://www.needrom.com/download/le...ulitilanguages-rom-unbrick-firmware-sp-tools/
hi, i have flash this firmware
ZE520KL_V13_13_1_36_M2_6_7_P7_Factory_raw
fastboot modded but now i can t do anything and my notebook not see my phone can anyone help me? thx
Putting the phone into EDL and using QFIL to load the stock rom is probably your best bet
what is EDL and i never used QFIL there is a guide for this? thx
sgjk86 said:
what is EDL and i never used QFIL there is a guide for this? thx
Click to expand...
Click to collapse
EDL is basically a state built in to Qualcomm chips that allows it to load firmware to unbrick when it can't load Android. QFIL can be found at https://qfiltool.com/qfil-tool-v2-0-3-5 and a stock rom can be found here https://firmwarefile.com/asus-zenfone-3-z017d-ze520kl. The QFIL tool link has its own instructions link by the download button but in short you'll want to install Qualcomm's QFIL USB drivers, open QFIL's .exe, select the .mbn from the stock rom, and hit download. It'll start flashing.
need deep flash cable for enter in EDL mode?
sgjk86 said:
need deep flash cable for enter in EDL mode?
Click to expand...
Click to collapse
No, you can use the standard microUSB cable you were using. All you need are the USB drivers (link is in QFIL's tutorial), QFIL itself, and the stock rom for the .mbn file to flash.
EDL mode will automatically be handled by QFIL itself as long as the device is on as shown in the tutorial.
i have install driver but NOTEBOOK not see smartphone in fastboot mode... ( must try the cable? ) and where i find .mbn file for firmware?
The driver from the QFIL tutorial doesn't allow platform tools to see it, it allows QFIL to see it. You need to download QFIL and follow its tutorial. The .mbn file is with the firmware download I also linked.
n00bl3x said:
The driver from the QFIL tutorial doesn't allow platform tools to see it, it allows QFIL to see it. You need to download QFIL and follow its tutorial. The .mbn file is with the firmware download I also linked.
Click to expand...
Click to collapse
That firmware only supports fastboot commands with a .bat file.
sgjk86 said:
i have install driver but NOTEBOOK not see smartphone in fastboot mode... ( must try the cable? ) and where i find .mbn file for firmware?
Click to expand...
Click to collapse
Try this guide here.This should explain everything to get it working again.Best of luck!
Unbrick a Bricked ZenFone 3 (ZE520KL/ZE552KL) (Full Guide) - Techtrickz
In this guide, we show you how to unbrick a bricked ZenFone 3 ZE520KL and ZE552KL by restoring bootloader and latest version of stock firmware. Installing custom recovery like TWRP, custom ROM, custom kernel and getting root are fine, but sometimes these will brick your device leaving it a...
techtrickz.com
Surgemanxx said:
That firmware only supports fastboot commands with a .bat file.
Click to expand...
Click to collapse
Ah, downloaded it and I see what you mean. Thanks!
n00bl3x said:
Ah, downloaded it and I see what you mean. Thanks!
Click to expand...
Click to collapse
No problem!That guide should get it back factory for them at least!
Surgemanxx said:
Try this guide here.This should explain everything to get it working again.Best of luck!
Unbrick a Bricked ZenFone 3 (ZE520KL/ZE552KL) (Full Guide) - Techtrickz
In this guide, we show you how to unbrick a bricked ZenFone 3 ZE520KL and ZE552KL by restoring bootloader and latest version of stock firmware. Installing custom recovery like TWRP, custom ROM, custom kernel and getting root are fine, but sometimes these will brick your device leaving it a...
techtrickz.com
Click to expand...
Click to collapse
so, i put original last firmware in a micro sd and run it from recovery and i replace all?
sgjk86 said:
so, i put original last firmware in a micro sd and run it from recovery and i replace all?
Click to expand...
Click to collapse
You can do it both ways from what that guide says.Personally,I would try to restore via fastboot
Surgemanxx said:
You can do it both ways from what that guide says.Personally,I would try to restore via fastboot
Click to expand...
Click to collapse
i can t run on fastboot the phone stay on screen at first post and notebook not see nothing so i think my last hope is to put firmware in micro sd and try to install from original recovery the firmware i have now.is.the same of this topic
UNLOCK/LOCK Bootloader For ZenFone 3 ZE520KL/ZE552KL
Mod info: Method doesn't work anymore and will result in a hard brick. Make sure you’ve backed up all of your IMPORTANT DATA before unlocking/relocking bootloader I am not responsible for bricked devices and dead SD cards. YOU are choosing to...
forum.xda-developers.com
sgjk86 said:
i can t run on fastboot the phone stay on screen at first post and notebook not see nothing so i think my last hope is to put firmware in micro sd and try to install from original recovery the firmware i have now.is.the same of this topic
UNLOCK/LOCK Bootloader For ZenFone 3 ZE520KL/ZE552KL
Mod info: Method doesn't work anymore and will result in a hard brick. Make sure you’ve backed up all of your IMPORTANT DATA before unlocking/relocking bootloader I am not responsible for bricked devices and dead SD cards. YOU are choosing to...
forum.xda-developers.com
Click to expand...
Click to collapse
Give it a try!You have all the information to get it working again!Here's the direct link for the firmware straight from Asus.Just pick the one that matches your device and rename it update.zip.
ZenFone 3 (ZE520KL) - Support
www.asus.com