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
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
Hey there, so I was playing a game PubG in which in the middle of a match the screen got stuck. I waited for 10 mins for it to go back and tried locking the screen with power button but nothing happened. When I long pressed it closed for a second then restarted and got stuck on bootscreen with only mi logo and no animation. Now it isn't switching off it gets rebooted to the same screen again. Only fastboot is opening. I don't want to lose my personal data there photos, videos that includes all my college life. If I try to flash it I think I will lose all data. Also I didnt backup all the data on mi cloud or anywhere. Please help me.
Also in flashing if I select the option 'save user data' will my data be saved?
same issue
same issue
happened to me just now
should be common software/update issue
Is your bootloader unlocked?
If you only want to back up your music, photos,videos,documents etc. , flash twrp recovery then boot into it (power+vol up about 11s). Connect your phone to PC. Then copy all data you need to save. Then reboot to fastboot and do a clean flash (clean all).
If you either want to back up the application data, do the previous operation without flashing first, and then do a "dirty" flash (save user data). At this time, your phone should be able to boot, use the BACKUP app to back up all your application data and copy it to your computer. The backup file seems to be stored in /storage/emulated/ 0/MIUI/backup, I don't remember it well.
After backing up all data you needed to save, you'd better do a clean flash using fastboot method. Make sure you choose "clean all".
Yuki1001 said:
Is your bootloader unlocked?
If you only want to back up your music, photos,videos,documents etc. , flash twrp recovery then boot into it (power+vol up about 11s). Connect your phone to PC. Then copy all data you need to save. Then reboot to fastboot and do a clean flash (clean all).
If you either want to back up the application data, do the previous operation without flashing first, and then do a "dirty" flash (save user data). At this time, your phone should be able to boot, use the BACKUP app to back up all your application data and copy it to your computer. The backup file seems to be stored in /storage/emulated/ 0/MIUI/backup, I don't remember it well.
After backing up all data you needed to save, you'd better do a clean flash using fastboot method. Make sure you choose "clean all".
Click to expand...
Click to collapse
Thanks for replyling. I think my bootloader is not unlocked. Also power+vol up is not working, only power+vol down is working. Can I flash twrp with bootloader locked?
Arun pm said:
same issue
happened to me just now
should be common software/update issue
Click to expand...
Click to collapse
So what did you do? Please tell me the method if you were able to solve it.
Re: Prakharpathak
I'm sorry because I can't save a phone that have a locked bootloader. If you wish to try Qualcomm QDLoader9008, maybe it will not work. Xiaomi has locked the 9008 port for their phones. Unless you have an authorized Mi account to get the verify token and send the authentitation tag to your phone, or the phone will reject all flashing commands. QPST is not working. The only difference is that the bootloader can be unlocked, but the 9008 requires authorization every time.
If you want to try the force unlock bootloader tool, once the force unlock is successful, you will lose all your data. Unless you can erase the recovery partition before the bootloader send a wipe command to Mi-recovery. In other words, if the recovery partition is erased or the recovery is not stock recovery (like twrp, etc) , unlocking the bootoader will not lose any data. Twrp does not accept the wipe command from the bootloader.
[edit]Now we have working firehose programmer could be used. Use QFIL to dump your userdata.
Yuki1001 said:
Re: Prakharpathak
I'm sorry because I can't save a phone that have a locked bootloader. If you wish to try Qualcomm QDLoader9008, maybe it will not work. Xiaomi has locked the 9008 port for their phones. Unless you have an authorized Mi account to get the verify token and send the authentitation tag to your phone, or the phone will reject all flashing commands. QPST is not working. The only difference is that the bootloader can be unlocked, but the 9008 requires authorization every time.
If you want to try the force unlock bootloader tool, once the force unlock is successful, you will lose all your data. Unless you can erase the recovery partition before the bootloader send a wipe command to Mi-recovery. In other words, if the recovery partition is erased or the recovery is not stock recovery (like twrp, etc) , unlocking the bootoader will not lose any data. Twrp does not accept the wipe command from the bootloader.
Click to expand...
Click to collapse
my bootloader is locked but i am ready to lose all my data , can you please tell me how can i boot my device
Re: @jagannath287
If this is also useful for you @Prakharpathak , you can also try.
If you are ready to lose all your data, you can try to use Mi PC Suite. Offical link of MI PC SUITE:
http://pcsuite.mi.com
You must be able to boot into Mi-Recovery, otherwise my solution will not help you.
Download the recovery ROM for your phone. Note that you can't upgrade or downgrade the OS version using this method.
After downloading and installing the Mi PC Assistant application on your computer, run it and login to your MI account. Then select FLASH ROM section and connect your device to your PC. Make sure your device is booted into Mi-recovery and selected “Connect with MiAssistant”.
Warning: you can't downgrade/change ROM region (you can only install the same area version to your phone, like MI-MI, RU-RU, EEA-EEA, etc) using this method.
Make a full wipe for your phone and select the RECOVERY ROM package: fast update and agree with full wipe. Then wait for the data erasing is fully done. After you see “Checking zip file update” and if all ok, the flashing progress will start and you will see the flashing is in progress. At last, you will see the window with successfully flashing. In theory, the phone will reboot to system automatically. The first start will take about 10 minutes. Be patient and wait the welcome screen.
There is another MI PC SUITE version that I found and I attach with my post. There is also a XiaomiADB flashing program.
Alternative method:
Download the adb driver and install it on your computer. Use the XiaomiADB full-auto flash program to flash your phone.
Select “Connect with MIAssistant” in the recovery and connect the phone to PC.
Make sure the recovery ROM zip file and XiaomiADB flashing program that in same folder. For start flashing just HOLD zip ROM AND DRUG IT TO THE XiaomiADB. After this command your DATA will be reset! You lost all files and Settings on your device.
At last, I suggest you to unlock the bootloader for your phone as soon as possible and flash your phone using MiFlash in fastboot mode in order to avoid facing mysterious bugs. A phone that have an unlocked bootloader is easy to save (unbrick) or backup all data from the phone without booting into system.
Attachment:
1.XiaomiADB:
https://drive.google.com/open?id=1BIlCd5wFFFlU2ObIQ-AtBNp3jlSj_5L1
2.MI PC SUITE 4.0 Beta:
https://drive.google.com/open?id=1_QoNlQFVj7lPo5iqM8jdrNmRwPztHQbV
If you find it useful, please click thanks.
I have an unlocked bootloader with latest stock rom
Stuck at MI logo
>No stock recovery loading
>Unfortunately the usb debugging is off (Automatically by MI security app :crying
>Tried Mi flash, Fastboot, Qualcomm Qflash with test point connection
>Is there anything left to try
Thanks
Re: @Arun pm
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
Can your phone boots into fastboot?
Did you try to flash every partition manually?
Did you try to flash the oldest version--V9.5.19?
More information needed. It can save time and guesswork.
Yuki1001 said:
Re: @Arun pm
Thanks for the reply bro
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
>> tried failed; stuck at the twrp logo(tried multiple versions and built)
Can your phone boots into fastboot? :
>>yes, but cant flash, permission error (usb debugging is off)
Did you try to flash every partition manually?
>>yes, even tried it with qualcomm tools but failed
Did you try to flash the oldest version--V9.5.19?
>>yes : same
More information needed. It can save time and guesswork.
Click to expand...
Click to collapse
Thanks for the reply bro
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
>> tried failed; stuck at the twrp logo(tried multiple versions and built)
Can your phone boots into fastboot? :
>>yes, but cant flash, permission error (usb debugging is off)
Did you try to flash every partition manually?
>>yes, even tried it with qualcomm tools but failed
Did you try to flash the oldest version--V9.5.19?
>>yes : same
More information needed. It can save time and guesswork.
Re: @Arun pm
You'd better create a new thread otherwise we will disturb the original author of this thread (Prakharpathak).
Did you mean the returned message from your phone is like this:
Sending "recovery"...
OKAY. Total time: 4.016s
Writing "recovery"...
FAILED<remote: Permission Error>
finished. Total time: 4.016s
In theory, the fastboot won't return this message and the USB debugging switch has no relation with fastboot flashing.
All partitions can't be flashed and return the "permission error" message?
Can you take a photo of the flashing error message?
[edit] Now we have working programmer and you could do all you want via EDL.
Yuki1001 said:
Re: @Arun pm
You'd better create a new thread otherwise we will disturb the original author of this thread (Prakharpathak).
Did you mean the returned message from your phone is like this:
Sending "recovery"...
OKAY. Total time: 4.016s
Writing "recovery"...
FAILED<remote: Permission Error>
finished. Total time: 4.016s
In theory, the fastboot won't return this message and the USB debugging switch has no relation with fastboot flashing.
All partitions can't be flashed and return the "permission error" message?
Can you take a photo of the flashing error message?
Click to expand...
Click to collapse
I am currently facing a similar situation.
My device redmi note 5 pro was running on miui 11 and suddenly its screen froze and then it got restarted and stuck at mi logo. It has locked bootloader and I can't access the stock recovery but I can access fastboot mode. I tried flashing different miui versions with different flash tools and everytime the process starts then after 9 seconds I get the error "ack count doesn't match". I tried flashing with edl point method as well and with a patched firehose file to bypass mi authentication but still got the same error. Can you please help me? I searched around the net and I can't find anything related to this particular error I am getting. I would really appreciate if you can help.
oh god same issue its not booting, checked with service centre not able to update software, one of the mobile shop guy told that mobile mother board working fine but unable to locate software so that it can boot, now i am blank and helpless can you guys help me out please.. if people in chennai here let me know guys.. its been 5 th day without my mobile...
Hi,
I got similar issue. I had installed GFX tool for cod on redmi note 5 pro and got hang on call of duty mobile. After long press power button, got stuck at mi boot logo. Only able to do connect phone in fastboot to PC. Anybody found solution? I want to back up all data excluding apps. Kindly suggest working solutions.
Deep3004 said:
Hi,
I got similar issue. I had installed GFX tool for cod on redmi note 5 pro and got hang on call of duty mobile. After long press power button, got stuck at mi boot logo. Only able to do connect phone in fastboot to PC. Anybody found solution? I want to back up all data excluding apps. Kindly suggest working solutions.
Click to expand...
Click to collapse
Flash orangefox recovery, then boot to recovery and there you can disable all the apps you want
kadyt said:
Flash orangefox recovery, then boot to recovery and there you can disable all the apps you want
Click to expand...
Click to collapse
Thanks for reply.
I tried to flash orange fox recovery but bootloader is locked and no fastboot commands working. I have tried mi unlock flash tool to unlock bootloader but error is comming "couldn't unlock more devices by this account this month" on official tool and on unofficial tool error is "current account is not bounded to this device". I cannot add device to this account since phone is into bootloop and wanted to save data. Is there any way to unlock bootloader and get access to storage data?
Deep3004 said:
Thanks for reply.
I tried to flash orange fox recovery but bootloader is locked and no fastboot commands working. I have tried mi unlock flash tool to unlock bootloader but error is comming "couldn't unlock more devices by this account this month" on official tool and on unofficial tool error is "current account is not bounded to this device". I cannot add device to this account since phone is into bootloop and wanted to save data. Is there any way to unlock bootloader and get access to storage data?
Click to expand...
Click to collapse
Sorry I took for granted that you had the bootloader unlocked. Then I don't know. Hope someone else can help you
Anyway, if somehow you could unlock the bootloader now, as far as I know, you will lose your data when doing it
any development in the above event i am in the same stage