Post to factory reset Micromax a1 has hard bricked. Its not turning on. not boot logo. Never rooted. Current OS Marshmallow. But whenever I connect it with laptop, Laptop is detecting and giving back a sound.
Can someone help here.
Give this a try
Install it on your pc
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Unlock the bootloader
Root your device
Flash a custom rom(e.g. cm12.1 nightlies)
captain_nemo said:
Post to factory reset Micromax a1 has hard bricked. Its not turning on. not boot logo. Never rooted. Current OS Marshmallow. But whenever I connect it with laptop, Laptop is detecting and giving back a sound.
Can someone help here.
Click to expand...
Click to collapse
Seems like you posted this nine days ago.
Is your phone fixed?
If it isn't, then i have a solution.
Just revert back to me.
---------- Post added at 01:17 PM ---------- Previous post was at 01:09 PM ----------
captain_nemo said:
Post to factory reset Micromax a1 has hard bricked. Its not turning on. not boot logo. Never rooted. Current OS Marshmallow. But whenever I connect it with laptop, Laptop is detecting and giving back a sound.
Can someone help here.
Click to expand...
Click to collapse
just flash lollipop and everything will be fine.
Just follow the steps here
IN SP TOOLS DO NOT SELECT "DOWNLOAD ONLY" OR "FORMAT"
ONLY SELECT FIRMWARE UPGRADE.
Raizen12465 said:
Seems like you posted this nine days ago.
Is your phone fixed?
If it isn't, then i have a solution.
Just revert back to me.
---------- Post added at 01:17 PM ---------- Previous post was at 01:09 PM ----------
just flash lollipop and everything will be fine.
Just follow the steps here
IN SP TOOLS DO NOT SELECT "DOWNLOAD ONLY" OR "FORMAT"
ONLY SELECT FIRMWARE UPGRADE.
Click to expand...
Click to collapse
Bro Ive Tried All Possible Ways My Phone Not Booting Up
I Cant Even Start My Phone So No Question Of Booting In FastBoot Mode,
its Good As Dead…!
Power Button Is OK As Was Flashing A Sprout 8GB Version Rom Unknowingly (Afterwards I Realised And Regretted)
I'm Out Of Warranty 1 Month Before (1year+1Month Passed)
I Tried Every Option & Combination On Sp Flash Tool Tried Manual Format Yesterday
But Of No Use…!
1) Tried "Download Only"
2) Gone To Format Section "Format Everything Except Bootloader" Then "Download Only"
3) Formated all + Download
ALL THESE SAYS DOWNLOAD SUCCESSFUL AND THAT "" Popups
Now,
4) Tried Firmware Upgrade (After Going To Format Tab And Format All Except Bootloader)
A Strange ERROR Pops Up "PMT Info"
I Researched That ERROR "PMT Info"
Its When Partition Value Storer File Has Been Altered By Chanhe In Partition Value
So The Solution Online Was Given To "Format All" -> Download Only Preloader -> Then Flash All The Files
So… In The End I Know
1)My Preloader Is Currupt
2)Power Button Is As Good As On A New Device
3)i Dont Have Knowledge About How To I Format "Preloader" By Manual Format Option In The Sp Flash Tool, To Remove That Currupt Preloader From The Phone And Insert A New One Using Sp Flash Tool
THANK YOU If You Guys Read so Far… Now You Know What I Know, And what I Dont Know So… Waiting Eagerly For Your Reply! Please Help Me Get Out Of This Situation!
Bro, you look like you're in deep ****!
Don't worry, we'll fix this.
If you read my previous post in this thread, i said not to use download only.
USE UPGRADE FIRMWARE.
don't go to format tab or anything. do not edit anything.
JUST GIVE THE SCATTER FILE, SELECT FIRMWARE UPGRADE AND HIT DOWNLOAD. DON'T CHANGE ANY SETTING
do that and if still not working try kitkat flash file here
try it and revert back
Raizen12465 said:
Bro, you look like you're in deep ****!
Don't worry, we'll fix this.
If you read my previous post in this thread, i said not to use download only.
USE UPGRADE FIRMWARE.
don't go to format tab or anything. do not edit anything.
JUST GIVE THE SCATTER FILE, SELECT FIRMWARE UPGRADE AND HIT DOWNLOAD. DON'T CHANGE ANY SETTING
do that and if still not working try kitkat flash file here
try it and revert back
Click to expand...
Click to collapse
So i Tried What You've Said (First With Lollipop And Then With KitKat)
When I Select Filmware Upgrade It Shows "PMT Info" (Something Like PMT Currupted)
So Is There Any Way Of Solving PMT Other Than Just "Firmware Upgrade" Cause Its Not Working…(Cause PMT Is Currupt)
BTW ThankYou For The Reply…
Sagar Kapasi said:
So i Tried What You've Said (First With Lollipop And Then With KitKat)
When I Select Filmware Upgrade It Shows "PMT Info" (Something Like PMT Currupted)
So Is There Any Way Of Solving PMT Other Than Just "Firmware Upgrade" Cause Its Not Working…(Cause PMT Is Currupt)
BTW ThankYou For The Reply…
Click to expand...
Click to collapse
OK so I understood you'r problem, and luckily I have a solution.
I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash).
What is a PMT? A partition table that holds the addresses to all the other partitions.
Stepwise, What you have to do:
STEP 1 :
In SP tools, on the top you have tabs like welcome, format, download, readback and memoryTest.
Step 2 :
In download tab select scatter file. ONLY SELECT. Then go to Format tab.
(Use only stock kitkat scatter file or lollipop doesn't matter. Only, it should be stock.)
Step 3 :
Here check the validation check box, and select auto format flash. Now click on START.
Step 4 :
Once completed, go to download tab and select Upgrade Firmware and hit download.
This should probably get your phone up and running.
Revert back if not.
Guys, I am almost having the same problem. My Canvas A1 worked fine for 11 months and now it is malfunctioning. The phone stops giving audio output sometimes and then I have to restart it to make it work. It even started to restart on its own. Last day, I tried to wipe the dalvik cache and did a factory reset and now my phone is stuck on the "Google animation". I have less time left for my warranty, so please reply fast. Do I need to flash stock 6.0 via stock recovery ?? I don't want to unlock bootloader or to root the device for as long as possible. Thanks for reading, waiting for your reply. :crying:
Raizen12465 said:
OK so I understood you'r problem, and luckily I have a solution.
I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash).
What is a PMT? A partition table that holds the addresses to all the other partitions.
Stepwise, What you have to do:
STEP 1 :
In SP tools, on the top you have tabs like welcome, format, download, readback and memoryTest.
Step 2 :
In download tab select scatter file. ONLY SELECT. Then go to Format tab.
(Use only stock kitkat scatter file or lollipop doesn't matter. Only, it should be stock.)
Step 3 :
Here check the validation check box, and select auto format flash. Now click on START.
Step 4 :
Once completed, go to download tab and select Upgrade Firmware and hit download.
This should probably get your phone up and running.
Revert back if not.
Click to expand...
Click to collapse
I am also having the same problem, i tried steps that you said but every time i get error in Firmware Upgrade that "failed to get pmt info"
see my THREAD suggest me to unbrick my android one: http://forum.xda-developers.com/canvas-a1/help/help-android-one-hard-bricked-unable-to-t3273603
Please Help Me Get Out Of This Situation in any way easy way, hard way i will try.
have you tried this..??
http://forum.xda-developers.com/android/general/how-to-install-stock-rom-bricked-t3126834
harkirat singhh said:
have you tried this..??
http://forum.xda-developers.com/android/general/how-to-install-stock-rom-bricked-t3126834
Click to expand...
Click to collapse
how can I
Fastboot method requires at least get into bootloader menu,
but my android one has hard bricked not any buttons working.:crying:
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Have you tried to re flash fastboot (fastboot flash droidboot.img)?
About the serial number, I think 0123..DEF is normal because I mine is like yours, too. But everything is fine.
fanfan54 said:
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Click to expand...
Click to collapse
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Serial number restored by Asus Flash Tool, now I can flash with fastboot
Hakataben said:
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Click to expand...
Click to collapse
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
fanfan54 said:
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
Click to expand...
Click to collapse
If you want to use Marshmallow, I recommend to flash pre-rooted lollipop first, then to flash marshmallow. In your situation, you should unbrick your Z008 at first. After that, you can change system to Marshmallow easily.
Pre-rooted Z008 systems are here. http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
In my case, I needed to have rooted and bootloader-unlocked again to enter in recovery.
Yay!
ASUS Flash Tool flashed the 2.20.40.149 successfully
It's saying "Optimizing app 45 of 119", but I think I had 179 when upgrading to Marshmallow...
And my Android was in french before. But I think I'll be able to fix this
I'll check soon if I've still all my data and apps...
(also, I tried to film everything, if it works I could eventually upload a video tutorial )
Thanks
Another problem... Edit 1
Android boots, I haven't any installation "Welcome" popup because I did not reset it, but as a consequence it crashes at start :
"Unfortunately, android.process.media stopped"
"Unfortunately, android.process.acore stopped"
And it reboots
Maybe it's because these are Marshmallow apps... Will I have to reset it?
Or where can I find system.img for Marshmallow?
Edit 2 Just managed to access to recovery menu
Definitely solved
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
ZF2/ZE550ML/Z008/Android 6.0.1/WW-4.21.40.54 ~ download --> here.
ZF2/ZE551ML/Z00A/Android 6.0.1/WW-4.21.40.61 ~ download --> here.
Click to expand...
Click to collapse
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
fanfan54 said:
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
Click to expand...
Click to collapse
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
muhammed cy said:
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
Click to expand...
Click to collapse
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
help me
fanfan54 said:
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
Click to expand...
Click to collapse
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
iwakpauz said:
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
Click to expand...
Click to collapse
Hello, I already sent it to you by email. Here is the link : https://yadi.sk/d/XAUyR8eRtuKdA
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
ayuinaba said:
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
Click to expand...
Click to collapse
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
timbernot said:
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
Click to expand...
Click to collapse
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
ayuinaba said:
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
Click to expand...
Click to collapse
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
timbernot said:
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
Click to expand...
Click to collapse
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
ayuinaba said:
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
Click to expand...
Click to collapse
Marvelous stuff. ,its been a pleasure helping you
Happy flashing
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
PS, should see the lengths some people go to restore serial
Why ? Lol When it
Only takes 3 mins max this way
This method works for both variants (16 GB and 32 GB). I just whant to make an thread because 2 days ago i just bricked my nexus 5x 16 GB by lock bootloader with Resurection
Remix installed and with an custom recovery (TWRP). After 1 day of searching i give it up. Yestarday i just start again and i did it .
THIS WAS TESTED WITH AN NEXUS 6P ORIGINAL CABLE. DO NOT USE AFTERMARKET CABLES BECAUSE DON`T HAVE THE SERIALS PINS AND THE LGUP AND PC WILL NOT SEE YOUR PHONE IN DOWNLOAD MODE
thanks to : bitdomo gee one JaCh0o sniperIT
support threads
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/post66318089#post66318089
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://developer.android.com/preview/download-ota.html
Steps
1. Download TOT file for your device
2. Download LG usb drivers
3. Download LGUP tool
4. Download 8994 dll for LGUP
5. Install LG usb drivers
6. Install LGUP tool
7. Install 8994 dll for LGUP
8. Turn off your phone
9. Press and hold the volume_up key while you connect the phone to the PC with usb cable.
10. Wait for Windows to install the new drivers
11. Start LGUP
12. Put the TOT file like in the screenshot.
13. Push start and wait
14. Let the progress to 100 %.
15. The phone will boot and will recive and message about your internal memory problem (16 GB variant) because the TOT file is for 32 GB model.
ignore that message
16.Now unlock bootloader (enter in develop mode tick that button enter on bootloader and just use fastboot oem unlock press yes . The phone will factory reset and enter
again on the android)
17. Reboot to bootloader and move the arrows till see recovery mode ! Keep press the power button when the recovery animation apear and press twice vol + and wipe data/cache
like a factory reset, and then just use ADB SIDELOAD from recovery
18. Copy on the adb folder the Android N 7 OTA and use on the pc on cmd adb sideload name.zip , after finish reboot
19. The phone will enter on Android N 7 . BECARFULL BECAUSE AFTER BOOT YOUR BOOTLOADER IS LOCKED AUTOMATICALY AFTER ANDROID 7 N WAS INSTALLED.
20. Unlock the bootloader and now can be write the official android 6.0.1 (don`t try to write only after the android n 7 was installed because you will recive an error about system and internal memory
again the TOT file is for 32 gb)
I followed the steps, however at step 15 my phone just froze at the Google logo, but I have the 32 GB variant so that may be expected (Note that I enabled OEM/bootloader locking like an idiot when trying to solve this a few hours ago). I waited ten minutes and it remained stuck at that logo, so I rebooted into the bootloader, went into recovery, and ran "adb sideload bullhead-ota-nrd90m-fdb8250a.zip". It seems like it installed without any problems, except when I booted back to system, I got stuck at the four dots again...
Could any LG experts provide insight? I'm about to just have the phone replaced, but I'm flying across the country in less than a week, so I'll need a phone...
jabarel said:
This method works for both variants (16 GB and 32 GB). I just whant to make an thread because 2 days ago i just bricked my nexus 5x 16 GB by lock bootloader with Resurection
Remix installed and with an custom recovery (TWRP). After 1 day of searching i give it up. Yestarday i just start again and i did it .
THIS WAS TESTED WITH AN NEXUS 6P ORIGINAL CABLE. DO NOT USE AFTERMARKET CABLES BECAUSE DON`T HAVE THE SERIALS PINS AND THE LGUP AND PC WILL NOT SEE YOUR PHONE IN DOWNLOAD MODE
thanks to : bitdomo gee one JaCh0o sniperIT
support threads
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/post66318089#post66318089
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://developer.android.com/preview/download-ota.html
Steps
1. Download TOT file for your device
2. Download LG usb drivers
3. Download LGUP tool
4. Download 8994 dll for LGUP
5. Install LG usb drivers
6. Install LGUP tool
7. Install 8994 dll for LGUP
8. Turn off your phone
9. Press and hold the volume_up key while you connect the phone to the PC with usb cable.
10. Wait for Windows to install the new drivers
11. Start LGUP
12. Put the TOT file like in the screenshot.
13. Push start and wait
14. Let the progress to 100 %.
15. The phone will boot and will recive and message about your internal memory problem (16 GB variant) because the TOT file is for 32 GB model.
ignore that message
16.Now unlock bootloader (enter in develop mode tick that button enter on bootloader and just use fastboot oem unlock press yes . The phone will factory reset and enter
again on the android)
17. Reboot to bootloader and move the arrows till see recovery mode ! Keep press the power button when the recovery animation apear and press twice vol + and wipe data/cache
like a factory reset, and then just use ADB SIDELOAD from recovery
18. Copy on the adb folder the Android N 7 OTA and use on the pc on cmd adb sideload name.zip , after finish reboot
19. The phone will enter on Android N 7 . BECARFULL BECAUSE AFTER BOOT YOUR BOOTLOADER IS LOCKED AUTOMATICALY AFTER ANDROID 7 N WAS INSTALLED.
20. Unlock the bootloader and now can be write the official android 6.0.1 (don`t try to write only after the android n 7 was installed because you will recive an error about system and internal memory
again the TOT file is for 32 gb)
Click to expand...
Click to collapse
hi. i did this but my phone was international version and with flashing this rom
my Boot loader locked and never unlock with nexus root toolkit
what can i do now?
mgtbmgtb said:
hi. i did this but my phone was international version and with flashing this rom
my Boot loader locked and never unlock with nexus root toolkit
what can i do now?
Click to expand...
Click to collapse
i have international too ! let me know what you did !
jabarel said:
i have international too ! let me know what you did !
Click to expand...
Click to collapse
my bootloader was locked too ! let me know all details but if your phone boots in bootloader will work even your bootloader is locked ! so you need to have and original cable or compatible one because if you boot on download mode your pc don`t reconigze the phone ! aftermarket cables don`t have serials pins !
1. boot on download mode
2.write that TOT file (maybe you will remain stuck on google logo after you write the TOT file)
3.Enter on recovery mode wipe/cache and then use adb sideload to write the ota zip file (this will repair your partiton )
let me know if you figure it out ! I`m on USA on vacation but tomorow i will fly home and i will try to help you more !
Huskehn said:
I followed the steps, however at step 15 my phone just froze at the Google logo, but I have the 32 GB variant so that may be expected (Note that I enabled OEM/bootloader locking like an idiot when trying to solve this a few hours ago). I waited ten minutes and it remained stuck at that logo, so I rebooted into the bootloader, went into recovery, and ran "adb sideload bullhead-ota-nrd90m-fdb8250a.zip". It seems like it installed without any problems, except when I booted back to system, I got stuck at the four dots again...
Could any LG experts provide insight? I'm about to just have the phone replaced, but I'm flying across the country in less than a week, so I'll need a phone...
Click to expand...
Click to collapse
reboot in recovery wipe/cache factory reset sorry for delay i was in vacation
plz 16gb tot
tuningsea said:
plz 16gb tot
Click to expand...
Click to collapse
it`s working with 32 gb too ! mine is 16gb i unbrick my phone with 32 gb TOT file.... thats the reason why i send via adb sideload the android n ota file to repair the partition table...
jabarel said:
i have international too ! let me know what you did !
Click to expand...
Click to collapse
hi again. i flash the tot. after that i wiped cache partition on recovery. and i flash the bullhead-ota-nrd90m-fdb8250a.zip with sideload on recovery. process completed successfully but in middle of flashing This message appears:
E: unknown command [log]
i checked log and This is what was written:
E:faild to mount /cache (invalid argument)
E:cant mount /cache/recovery/last_locale
locale is [(null)]
then i reboot and my phone stuck in boot and reboting again
my phone is locked so i cant flash cache.img with nexus root toolkit
what can i do body?
mgtbmgtb said:
hi again. i flash the tot. after that i wiped cache partition on recovery. and i flash the bullhead-ota-nrd90m-fdb8250a.zip with sideload on recovery. process completed successfully but in middle of flashing This message appears:
E: unknown command [log]
i checked log and This is what was written:
E:faild to mount /cache (invalid argument)
E:cant mount /cache/recovery/last_locale
locale is [(null)]
then i reboot and my phone stuck in boot and reboting again
my phone is locked so i cant flash cache.img with nexus root toolkit
what can i do body?
Click to expand...
Click to collapse
after you flash the tot file your phone starts? Try after you write TOT file to enter on recovery and use wipe/cache factory reset and see if boot ! Don`t write the ota file only after you check if starts after you write TOT file. I will upload for you another OTA file to try with this. i will send you the link, it`s a beta one because when you use this OTA will erase everything and will repair the partitions and will lock the bootloader. Try with this OTA file. Try to boot after you write the TOT file. I was destroy 2 days when i bricked my nexus, i know how it is......! Let me know if you will win this time. I hope you will unbrick your phone
https://drive.google.com/file/d/0B03qc7cQ-LeDSUFuMmYxOVZ2ZjA/view?usp=sharing
got to step 10 my phone was stuck at zero percent on the firmware update screen and the windows computer was not doing anything related to driver install
---------- Post added at 10:57 PM ---------- Previous post was at 10:24 PM ----------
my phone got stuck on the google logo after step 15 and i tried to do what yo said and go into recovery but when i boot itto recovery there is a Android man with a red triangle and an exclamation mark. plz help!! also twrp got erased when i use the lg tool
There is a combination of up and power button. Google how to get into stock recovery. This is what you see.
http://forum.xda-developers.com/showthread.php?p=69092591
Hello,
I was wondering how to create a TOT file by myself.
Is there any guide somewhere?
Sorry for raising this thread from the dead but what can I do if my device isn't recognized on my computer in mode 9008?
I connect it to my computer but it's not doing a thing and after a few seconds boot up with this error.