Related
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
EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have
Congrats! Would it work on the BV9000 HD version?
Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash
hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F
Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><
hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected
Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone
I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q
Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?
Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889
TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)
Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers
Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...
Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.
Hello everyone, after struggling for a few hours I managed to finally disable force encryption in my phone (so that TWRP could backup the data partition).
I'd like to write a quick list of what I did in the form of a guide to unlocking the bootloader, installing TWRP and getting root with Magisk. I'm just a user, not a developer and this guide is brief, it's not a detailed tutorial and does not include trivial steps (like how to install drivers for your OS).
Warnings: Although small, there is always the chance this bricks your phone. I take no responsibilities.
This will factory reset your phone so back up everything before you start.
My phone is Lenovo S5 (K520) Global version (see screenshot) I don't know if this will work for other firmwares.
Prerequisites:
Install Phone, ADB and Fastboot drives. You can get ADB and Fastboot binaries from here:
https://forum.xda-developers.com/showthread.php?t=2588979
Download this archive:
http://www.mediafire.com/?4dcvzw1hdmzfn10
It contains all the files used in this guide.
Alternatively, download all the files used from their sources.
You will need an SD card or a USB flash drive with an OTG adapter.
Copy the following files to it:
A. "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3817389 )
B. "Magisk-v18.0.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3473445 )
C. (optional) "\stock\boot.img"
(Downloaded from the global firmware @ 4pda)
If you chose to use Micro SD card, you can insert it now.
Note: I know there is a way to push these files directly to TWRP from PC through USB instead of using SD Card/Flash drive but I've never tried it.
Lets start:
1. Go to 'Settings>About phone' and tap on "Lenovo version" several times until developer options are enabled.
2. Go to 'Settings>System>Developer options' and enable "OEM unlocking" (Note: for me this option was greyed out and I had to connect to wifi and wait for a minute or two).
Optional: Enable "USB debugging" if you wish to enter fastboot via ADB.
3. Turn off the phone and press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" on the phone screen (alternatively, don't turn off the phone and instead enter fastboot mode via ADB (adb.exe reboot bootloader)).
4. Connect the phone to the PC via USB and open a command prompt in the location that you installed fastboot binary to.
Type (after each command press enter):
Code:
fastboot devices
To verify that the phone is recognized. And if it is type:
Code:
fastboot oem unlock
Now on the phone LCD navigate to "Yes" with volume buttons and press power to select it.
Your phone will factory reset, this will take a few minutes. Let it finish.
5. Put the TWRP image in your fastboot path. I used "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" downloaded from this URL:
https://forum.xda-developers.com/android/development/lenovo-s5-k520-twrps-t3863860
But I included 2 more files that I found (I did not try them).
6. Enter fasboot mode again and type:
Code:
fastboot flash recovery recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img
(Substitute "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" with the recovery filename of you choice)
7. If successful, disconnect the USB cable and enter Recovery mode, do not turn off or reboot the phone because upon restart the phone will revert to stock recovery (I.E. delete TWRP).
To enter Recovery mode press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" and from there choose "Recovery mode" with the volume buttons and confirm with the power button.
(Alternatively, you can try holding 'Volume up'+'Power' to directly enter Recovery mode but I found it a little finicky)
8. In TWRP, swipe to allow changes. Press cancel when asked for a password to decrypt data.
If you chose to use a USB flash drive with an OTG adapter, connect it and mount it (Mount>usb-otg).
9. Go to Wipe>format data, type "yes" and confirm (if you have any data like installed apps, contacts etc., it will be deleted).
10. Go to Install and install "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
The files will be in (/external_sd/ or /usb-otg/).
11. Install "Magisk-v18.0.zip"
Important note: If you want to keep encryption (if you don't care if TWRP can't access /data/) and just obtain root, skip steps 9 and 10.
12. Reboot to system and wait for a few minutes for the initial setup.
If for some reason boot fails (nothing happens after 10 minutes) and you can still enter TWRP (hold 'Volume up'+'Power'), then you can revert the changes by restoring the stock boot image (TWRP>Install>Install image>boot.img - put a checkmark on "boot").
If this worked for you, please tell us by replying to this thread.
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
C4lculated said:
I also wanted to root but I didn't want to run a bunch of unknown programs (from XN Logos), so I managed to install TWRP and root with magisk. I wrote a guide on how to do it:
https://forum.xda-developers.com/ge...ide-lenovo-s5-k520-twrp-root-decrypt-t3882402
Click to expand...
Click to collapse
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
does anyone enable lte bands, 4 and 28?
just bought this phone, currently on shipping..
I'll first try with twrp + aosp 9 GSI
Hi man, have you upgrade to gsi
acost91 said:
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
Click to expand...
Click to collapse
Kindly drop the procedure am hitting brick with all the method i used .????????
Stock firmware lenovo k520
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Working on S5 Pro too?
Hi! Can it work on S5 Pro too? I really want to root this device and I don't find out a way to get this happening. Thanks!
Does this work for s5 pro l58041?
Thanks
B4ph0 said:
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Click to expand...
Click to collapse
Hi! Sorry for offtopic!
Could you please PM me the link on AOSP extended image which you installed. Thank you!
Hello! Did somebody managed to install GCAM to Lenovo S5? I'm trying and I can;t do this, magisk modules are not loading...
so far I've used 2 alternative rom and works fine, aosp & octopus os, especially octopus os
I need some help..
Did anyone had lenovo s5 persist.img..
I lost my persist afer flashing global rom.208st via qfil..
I check the rom has no persist.img
Please visit to https://youtu.be/wbpV59kutJM for tutorial flash and upgrade Lenovo S5 in YouTube
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
has anyone achieved unlocking bands in this phone?
Please port miui 11 9.10.30 mi-room pie 9.0 redmi note 4x SD625 to lenovo S5.
https://megaroms.net/miui-11-9-10-30-stable-port-for-redmi-note-4-4x/
https://sourceforge.net/projects/miui-ports.whats-new.p/files/mido/miroom/
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
Suryo75 said:
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
Click to expand...
Click to collapse
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
jychung93 said:
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
Click to expand...
Click to collapse
thank you i'll try
Could you plz make tutorial about getting back to stock unroot...thx
Twrp gone
Hello sir thank you for this wonderful tutorial,
But I have a problem , after booting to TWRP , then boot to system after that when I try to go back to recovery mode TWRP , twrp is gone , stock recovery back
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Preloader only works o Pie, and if you flashed miui Android 10 the preloader partition was over wrote...
Excuse my bad English
djzero86 said:
Preloader only works o Pie, and if you flashed miui Android 10 the preloader partition was over wrote...
Excuse my bad English
Click to expand...
Click to collapse
From what I understood, you have to be on android 9 when flashing preloader. After that one can flash other ROM versions. Or am I wrong?
avdo06 said:
From what I understood, you have to be on android 9 when flashing preloader. After that one can flash other ROM versions. Or am I wrong?
Click to expand...
Click to collapse
Nope, if you flash a rom that contain those partitions it will be over writed.
Read carefully the instructions, the dev remark this point clearly in the mega post
In the past, I would edit the updater script to remove whichever partition updates I didn't want, such as boot.
Does that work with MIUI 11? I guess I could try it out, only flash the system partition and see what happens. Anyone else try?
OP, did you flash both preloader, lk and lk2 before rebooting?
Try this:
I was in a similar situation. I unbricked my phone by downloading the SP flash tools with the DA file specifically for the MT6785 (The note 8 pro's chip). here's the link to download it: https[colon]//easyfirmwares[dot]com/index.php?a=downloads&b=file&id=603
Just extract and follow the directions to unbrick your device on the megathread. Hopefully this helps.
* Also, this won't work if you don't have the preloader and lk images flashed, as said in the megthread. *
edit: Replace [colon] with " : " and [dot] with " . "
I pulled my phone back from the dead. I read in a thread somewhere that this guy had the same situation as me. He downloaded miflash pro (black icon). So I did the same. There is a tab inside miflash for sp flash tool. When I connected my phone it immediately started flashing. The phone rebooted with the firmware I chose ( which is 11.0.3.0 PGGEUXM). Since this thread is from last year (when I have more time I'll post the link here), I think that it MIGHT work for bricked RN8P's that don't have the preloader/lk files flashed. But it's just a thought. Anyway, like I said, my phone was dead, wasn't reacting to anything, I had no fastboot and SP Flash Tool that I had downloaded from the official website kept giving me errors each time I connected with USB. It could be that particular versions of SP Flash had some misunderstandings with my PCs (tried two PCs and three versions of the SP tool). I was so desperate and I had already ordered a Redmi Note 8T from Amazon. But then I read this post and it worked! :silly: :laugh:
i need an auth. mi account to flash my firmware back. can anyone help me please?
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
I can access my fastboot but how do i flash stock rom ? Prior to this i was able to flash global version but got brick when i install twrp
If i flash a different rom it just says anti rollback
By the way my unit is china variant any response will be apperciated
I have eea 11.0.2.0 android 10 and the twrp is diferent than android 9...
Test with this version of twrp..... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
Brother i hace muy phone bricked now i downloaded mi pro Italian versión, i havent fastboot only blackscreen pc cant read phone only on edl, i disconnected battery and still not getting fastboot, so mmy question is where to find that miui android 10 tgz ROM ? For install and try ? I got same error Brome and auth permission , i payed 25$ and i got scamed, i cant find that android 10 ROM that you mentioned
I do as you say but it's not work
Sorry, I'm confused with Step 4:
Where do I find the scatter file? Is it in a subfolder of the firmware I downloaded ? I have a scatter file but each and everytime I get Error: Status_scatter_file_invalid (bC0030001). I have googled all over, change the path of my firmware to a real simple path (c:\firmware). I have the same problem with stand-alone sp flash tools. - For that I tried 5 different versions. Any advice appreciated
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
poster74 said:
Sorry, I'm confused with Step 4:
Where do I find the scatter file? Is it in a subfolder of the firmware I downloaded ? I have a scatter file but each and everytime I get Error: Status_scatter_file_invalid (bC0030001). I have googled all over, change the path of my firmware to a real simple path (c:\firmware). I have the same problem with stand-alone sp flash tools. - For that I tried 5 different versions. Any advice appreciated
Click to expand...
Click to collapse
The scatter file is inside the firmware. You need to extract the tar.gz image, then it should be in the 'images' folder.
Thanks, I managed to get abit further, but not much.
My phone is bricked I think. Can't go into recovery nor fastboot. powering it on, I just get the standard 'Redmi, by Xiaomi' splashscreen for about 3 seconds, in the bottom left, I get a small line 'se blown:sucess'. I think it should read efuse or qfuse but because of rounded corners, cant see full message. After 3 seconds it reboots, goes blank for 5 seconds and then back to Redmi Screen..
I have noticed, having it plugged into PC, when it reboots (i.e. goes blank) the meditek vcom driver pops up in Device Manager and I get the Windows sound of a device being connected. Then it disappears after a second or two
So I can now successfully load my firmware and scatter file. and if I hit the Download button in SPFT just as the its rebooting, detects the phone and the port comes up in bottom left of SPFT. But after 2 minutes it just times out with an error. Its like it detects it for a second and thats it.
Any ideas?
avdo06 said:
The scatter file is inside the firmware. You need to extract the tar.gz image, then it should be in the 'images' folder.
Click to expand...
Click to collapse
poster74 said:
Thanks, I managed to get abit further, but not much.
My phone is bricked I think. Can't go into recovery nor fastboot. powering it on, I just get the standard 'Redmi, by Xiaomi' splashscreen for about 3 seconds, in the bottom left, I get a small line 'se blown:sucess'. I think it should read efuse or qfuse but because of rounded corners, cant see full message. After 3 seconds it reboots, goes blank for 5 seconds and then back to Redmi Screen..
I have noticed, having it plugged into PC, when it reboots (i.e. goes blank) the meditek vcom driver pops up in Device Manager and I get the Windows sound of a device being connected. Then it disappears after a second or two
So I can now successfully load my firmware and scatter file. and if I hit the Download button in SPFT just as the its rebooting, detects the phone and the port comes up in bottom left of SPFT. But after 2 minutes it just times out with an error. Its like it detects it for a second and thats it.
Any ideas?
Click to expand...
Click to collapse
Looks like it's not hardbricked anymore, that's great. You should check out other threads on the RN8 Pro about what to do next.
It works flawlessly AND i had preventive loader (Android 9, Global 11.0.6)
However, note following points;
1. if you get your battery drained it wont charge in preloader mode. so you have to flash the original preloader/lk files as well else, you can uncheck preloader, lk1 and lk2.
2. For future, DONT EVER LET YOUR PHONE BATTERY EVER DRAIN TO ZERO, else possibly you might have to flash whole rom again. (you can try simply restoring preloader)
hi i have a redmi note 8 pro bricked, wrong twrp install, i tried this but it says i don't have any authorized account, what can i do?
dont work!for me
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
i do this step and when press volume + and connect my mi account authotised but after it take error such
STATUS_BROM_CMD_STARTCM_FAIL(0XC0060001) ...
...in devices manager in laptop(windows 10) when press and connect phone show mediatek usb port... but flash do not start!!!
tanx for you giud and response
hello
zumboy said:
hi i have a redmi note 8 pro bricked, wrong twrp install, i tried this but it says i don't have any authorized account, what can i do?
Click to expand...
Click to collapse
do you resolve that problem?? i got the same (same wrong twrp install) & i think our only chance to resolve this is with authorised account
Hi there,
though i'm not a newbie, i'm not an expert either. I usually go by trial and error.
And so I have done with my Poco F3: I've succeeded (with trial and error) to get a recent MIUI 13.eu rom on it and it runs real smooth. But the TWRP I am using, is not able to decrypt anymore with the password I've always used. And I think my fastboot-option is corrupt, since when I boot to this option my pc does not recognize my phone as a device anymore.
I am looking therefore for instructions / a tutorial on how to repair the fastboot option and how to go about with the encyption if I don't know what te password is. I would like to be able to upgadre to the latest .eu rom, but for this my twrp needs to decrypt and I can't get that to function anymore. So in present TWRP, i can not acces any rom-files, also not through the SD-storage function
Ofcourse there will probably by an option for clean install of everything, but where is it and how does this find the nescessary rom-file (as the file explorer had only acces to internal files and even then not to encrypted part).
Hope I explain it clearly enough?
Any help / tips / suggestions will be appreciated!!
Thanks in advance!
* download mi unlock tool and open its settings (at the top right corner)
* install phone drivers (connect your phone in fastboot mode)
also make sure you connect the phone on a usb 2.0 or 3.0 port
as for twrp, use the following twrp:
https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.3_A12/%5BBOOT%5D3.6.2_12-RedmiK40-POCOF3-Mi11X_v6.3_A12-alioth-skkk_a616ae6b.zip
3zozHashim said:
* download mi unlock tool and open its settings (at the top right corner)
* install phone drivers (connect your phone in fastboot mode)
also make sure you connect the phone on a usb 2.0 or 3.0 port
as for twrp, use the following twrp:
https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.3_A12/%5BBOOT%5D3.6.2_12-RedmiK40-POCOF3-Mi11X_v6.3_A12-alioth-skkk_a616ae6b.zip
Click to expand...
Click to collapse
Great tip on the correct installation of phone drivers, thank you. After re-installing them through the mi unlock tool, it looks like the device is recognised again.
As for the TWRP, I am using the official TWRP 3.7.0 for A12 now... wil downgrading to the 3.6.3 skk version be a step forward for the decryption problem?
Thanks very much for helping me out!
mnstr said:
Great tip on the correct installation of phone drivers, thank you. After re-installing them through the mi unlock tool, it looks like the device is recognised again.
As for the TWRP, I am using the official TWRP 3.7.0 for A12 now... wil downgrading to the 3.6.3 skk version be a step forward for the decryption problem?
Thanks very much for helping me out!
Click to expand...
Click to collapse
skkk twrp is pretty much the go to twrp for poco f3
Thanks for the help, but alas the problem isn't solved.... After reinstalling the USB drivers, my the driver-utility reports it sees a device after I connect my Poco F3. In ADB (through powershell with administrator rights) however, on the command ADB devices it shows no connected devices. And also the fastboot flash recovery command does not work... it looks like it is uploading the twrp-file, but notihing really happens.
I'm guessing the fastboot that the official TWRP 3.7.0 brought me, does not function well... But now I have no idea on how to get the correct TWP img version on to the device, since I cannot seem to get an ADB session, and since the present TWRP 3.7.0 does not recognise the normal filesystem, I also cannot load it through the TWRP interface.
Any ideas on how to get out of this mess are very welcome, I would very much like to be able to have a properly updateable Poco F3 once again, appearantly I messed up by installing the official TWRP 3.7.0...
Thank you for helping me out, any idea is appreciated!
Luckily this problem is solved now. Problem was that I was using the wrong TWRP, appearantly the proper one for alioth is the TWRP from skk. And after booting into that one (not flashing it yet), I could get in the new TWRP recovery, which did recognise my folders and file system, including my USB drive. So I was able to install the latest EU rom from that booted TWRP and before rebooting, I also opted in the new TWRP to have this new TWRP flashed into recovery.
After rebooting, all is well. I have the latest stable EU rom installed and my installed recovery is the latest skk one. Thanks for all the help, I am glad I called on the community!