Develop Bugs

[Q] Help! - Rooted Zenfone 2 (ZE551ML) bricked after OTA accidently

followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?

Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?

If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.

joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...

I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps

Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse

xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.

This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse

xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.

actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.

dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.

5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?

How to downgrade ZE551ML Z00AD from 2.20.40.97 to 2.19.40.22?

Hey guys,
Do you know how to downgrade the firmware from 2.20.40.97 to 2.19.40.22? I'm just going to try out game performance on the previous firmware. I've read somewhere that the lag on 3D games began on 2.20.xx.xx.
I was thinking of doing the same procedure of how to convert CN to WW using the older WW instead of CN, but I'm not sure if that's the right way. I might end up bricking my phone if I proceed without consultation.
I'm using 4/64gb ZE551ML

miki117 said:
Hey guys,
Do you know how to downgrade the firmware from 2.20.40.97 to 2.19.40.22? I'm just going to try out game performance on the previous firmware. I've read somewhere that the lag on 3D games began on 2.20.xx.xx.
I was thinking of doing the same procedure of how to convert CN to WW using the older WW instead of CN, but I'm not sure if that's the right way. I might end up bricking my phone if I proceed without consultation.
I'm using 4/64gb ZE551ML
Click to expand...
Click to collapse
If you are downgrading the firmware with the same *SKU*, then simply ADB sideload the firmware via the recovery mode. Done it once, no problem surfaced.
Converting your phones SKU though requires some additional flashing of the recovery, droidboot, and boot images from fastboot. A simple Google search should give you a very well-detailed page containing loads of information for each step. Good Luck!

Rizzed said:
If you are downgrading the firmware with the same *SKU*, then simply ADB sideload the firmware via the recovery mode. Done it once, no problem surfaced.
Converting your phones SKU though requires some additional flashing of the recovery, droidboot, and boot images from fastboot. A simple Google search should give you a very well-detailed page containing loads of information for each step. Good Luck!
Click to expand...
Click to collapse
Already tried that though, just got an error message saying that it cannot install the lower version firmware, or something like that.

miki117 said:
Already tried that though, just got an error message saying that it cannot install the lower version firmware, or something like that.
Click to expand...
Click to collapse
Oh no! I just remembered something! To flash to a firmware version lower than your current one, you would have to flash the downgraded recovery.img first, or else it would not succeed due to security checks.
To do so, download the appropriate recovery.img (link below -choose the one pertaining to the firmware version you want to downgrade to, e.g. if you are downgrading to version XXX, download the XXX version recovery), and place it into your ADB folder. Then, simply boot your phone into fastboot mode (Power Button + Volume Up Button - the screen just before you enter the recovery mode), and type "fastboot flash recovery recovery.img" into the command prompt (without quotes)
Download: (add h t t p : / / w w w. here)mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
Then, power off your phone, and reboot back to the recovery mode. No issues should pop up upon attempting to ADB sideload the firmware anymore.
If the command prompt says *error:device not found* upon entering the command, please install the drivers at (add h t t p s : / / here)software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Instructions for installation is at (add h t t p s : / / here)software.intel.com/en-us/android/articles/installation-instructions-for-intel-android-usb-driver
Do tell me if the links do not work, i will PM it to you. I do not have 10 posts yet, so I currently do not have the privileges of posting the full link.

Rizzed said:
Oh no! I just remembered something! To flash to a firmware version lower than your current one, you would have to flash the downgraded recovery.img first, or else it would not succeed due to security checks.
To do so, download the appropriate recovery.img (link below -choose the one pertaining to the firmware version you want to downgrade to, e.g. if you are downgrading to version XXX, download the XXX version recovery), and place it into your ADB folder. Then, simply boot your phone into fastboot mode (Power Button + Volume Up Button - the screen just before you enter the recovery mode), and type "fastboot flash recovery recovery.img" into the command prompt (without quotes)
Download: (add h t t p : / / w w w. here)mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
Then, power off your phone, and reboot back to the recovery mode. No issues should pop up upon attempting to ADB sideload the firmware anymore.
If the command prompt says *error:device not found* upon entering the command, please install the drivers at (add h t t p s : / / here)software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Instructions for installation is at (add h t t p s : / / here)software.intel.com/en-us/android/articles/installation-instructions-for-intel-android-usb-driver
Do tell me if the links do not work, i will PM it to you. I do not have 10 posts yet, so I currently do not have the privileges of posting the full link.
Click to expand...
Click to collapse
Thanks! I'll be testing it out. The link for the recovery is working fine. Didn't try out the one for the intel drivers though, I already have them. I'll go ahead and flash and see what comes up.
By the way, how do you guys get the recovery.img files? When I check the insides of the firmware zip, I only see the recover folder.

Worked like a dream! Went through the process flawlessly! Thanks a lot! Time to test out some games.

Please let us know the results, I'm quite disappointed with the current gaming performance as well,half of the reason why I bought this phone was for the good reviews that it had @ gaming. Curious if the firmware is the culprit or not.

zapz said:
Please let us know the results, I'm quite disappointed with the current gaming performance as well,half of the reason why I bought this phone was for the good reviews that it had @ gaming. Curious if the firmware is the culprit or not.
Click to expand...
Click to collapse
Right now, I think the culprit may be Asus' firmware. Not sure though. I've tested Eternity Warriors 4 on both my ZE551ML and a Selfie, both with the latest update. I was expecting the Selfie to have better performance when I thought that the lag could be some x86 issue. But to my surprise, both performed exactly the same. Laggy. Even my colleague's Xperia T2 (I think) and a Note 2 performed better. I haven't tested much though. Interface response feels faster, not sure if it's just me or if it's really faster. I'm unable to test out other firmware due to my awesome internet connection. But a tip on where to start would help. I started on 2.19.40.22 since I read somewhere that the lag started on 2.20 series.
I was able to test Contract Killer: Sniper, sadly, pretty much the same performance. Will test other games.

zapz said:
Please let us know the results, I'm quite disappointed with the current gaming performance as well,half of the reason why I bought this phone was for the good reviews that it had @ gaming. Curious if the firmware is the culprit or not.
Click to expand...
Click to collapse
Reverted back to the latest 2.20.40.97 since I pretty much have the same performance. There was a slight improvement on gameplay on the older firmware, but basically still the same. Games I've tested is Contract Killer: Sniper and Sniper X. Eternity Warriors 4 won't start for some reason.
I'm not able to test out all firmware due to my internet connection. 1gb would take the whole day to download on my end. :/

Rizzed said:
Oh no! I just remembered something! To flash to a firmware version lower than your current one, you would have to flash the downgraded recovery.img first, or else it would not succeed due to security checks.
To do so, download the appropriate recovery.img (link below -choose the one pertaining to the firmware version you want to downgrade to, e.g. if you are downgrading to version XXX, download the XXX version recovery), and place it into your ADB folder. Then, simply boot your phone into fastboot mode (Power Button + Volume Up Button - the screen just before you enter the recovery mode), and type "fastboot flash recovery recovery.img" into the command prompt (without quotes)
Download: (add h t t p : / / w w w. here)mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
Then, power off your phone, and reboot back to the recovery mode. No issues should pop up upon attempting to ADB sideload the firmware anymore.
If the command prompt says *error:device not found* upon entering the command, please install the drivers at (add h t t p s : / / here)software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Instructions for installation is at (add h t t p s : / / here)software.intel.com/en-us/android/articles/installation-instructions-for-intel-android-usb-driver
Do tell me if the links do not work, i will PM it to you. I do not have 10 posts yet, so I currently do not have the privileges of posting the full link.
Click to expand...
Click to collapse
oh sht thank you so much i had the same issue and now its installing the ota cause im gonna be unlocking the boot loader unofficially

some questions as i am a newbie
i have rooted my zenfone 2(z00ad), will this method work for me cause i have rooted my phone, unlocked the bootloader and flashed twrp ?? and if not plzzz help me....

[RECOVERY][UNOFFICIAL][TWRP] For Sony Xperia T3 D5103 (seagull)

Hi guys, I decided to start modding this smartphone, now that I have a computer capable of compiling in a few hours.
I ported TWRP 3.0, based on Omni 6.0 source to this device. There are a few things not working and I need other people's help and feedback.
READ FULL GUIDE AND NOTES BEFORE FLASHING!!!
-Necessary steps:
Unlock bootloader. Here's a guide from Sony
-How to install:
1)From computer, open a terminal (Linux and MacOS) or command prompt (Windows) where you saved the file (download below). (Linux And MacOS. On Linux you'll need to flash with sudo) or where you have the platform-tools (Windows)
2)Poweroff your phone.
3)Boot into bootloader by pressing Volume+ button while connecting the usb cable into the usb port (the usb cable has to be inserted into the computer's port too, to successfully boot into fastboot)
4)With unlocked bootloader, type fastboot flash recovery twrp_3.0.2-0-seagull-UNOFFICIAL.img, if you renamed the files, substitube "twrp_3.0.2-0-seagull-UNOFFICIAL.img" with your file name or the directory where you saved the file.
5)When you see the OK message from fastboot, disconnect your phone.
6)Press Power, Volume+ and Volume- untile the phone vibrates.
7)Release Volume+ key. When you see the Sony logo appear, wait 3-4 seconds and then release Power button.
8)You should see TWRP bootscreen after a few seconds
-What's working:
Almost all. I could succesfully flash GApps and Root packages from this recovery, Backup, Restore and Wipe partitions. Settings work fine. Terminal and File manager work.
-What's NOT working:
Can't read files MicroSD or USB-OTG, can't browse in them and can't wipe. Investigating about it.
-Download:
(GDrive) Version 3.0.2-1
(AFH) Version 3.0.2-1
-Source and guide to build:
https://github.com/EmaMaker/device-sony-seagull/tree/twrp-3.0
Changelog:
30/04/2018: I think I fixed the screen problem by using the Lollipop kernel instead of the Marshmellow one
Thanks Everyone

Cool, although upon booting into recovery the screen isn't operating normally, similar to what happens when flashing the fxp lollipop. Might be because I'm on stock ROM/kernel though.

What do you mean with "isn't operating normally"? The screen only displays coloured bands? If so, it should have be fixed, maybe only the download link is wrong. Tell me, I'll fix in a minute

EmaMaker said:
What do you mean with "isn't operating normally"? The screen only displays coloured bands? If so, it should have be fixed, maybe only the download link is wrong. Tell me, I'll fix in a minute
Click to expand...
Click to collapse
Yes, sorry for not being more specific xD, I'm indeed getting the white-grey bands on screen.
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
It's possible it's the lollipop kernel that's to blame, since I've had the same problem with other lollipop builds.

Fixed
Download link fixed with working version

EmaMaker said:
Download link fixed with working version
Click to expand...
Click to collapse
Will try it and report back ?

Tried the updated one, still no luck. It could be just my device though.

Try the one from AFH. I really don't know why. The 3.0.2-1 version works on both my two seagulls

EmaMaker said:
Try the one from AFH. I really don't know why. The 3.0.2-1 version works on both my two seagulls
Click to expand...
Click to collapse
Tried both versions, so it's probably my device.
(However, if it is it's fine, since I do have working twrp.)

Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,

Don't know
goosnarrggh said:
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Click to expand...
Click to collapse
One of my two seagulls came back from assistance and I tried to flash TWRP on it without any problems. I don't know if it had an updated bootloader or what, but the firmware was stock

goosnarrggh said:
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Click to expand...
Click to collapse
In order to flash recovery, you first need to download and install the Emma flashtool and restore your phone through it. That will add a recovery partition so you can flash twrp. (The Emma flash tool supports only the D5103 model of the T3 as far as I know)

I tink you will have the same as the eagle (m2) device, you need to update your bootloader and then flash recovery...

EmaMaker said:
Hi guys, I decided to start modding this smartphone, now that I have a computer capable of compiling in a few hours.
I ported TWRP 3.0, based on Omni 6.0 source to this device. There are a few things not working and I need other people's help and feedback.
READ FULL GUIDE AND NOTES BEFORE FLASHING!!!
-Necessary steps:
Unlock bootloader. Here's a guide from Sony
-How to install:
1)From computer, open a terminal (Linux and MacOS) or command prompt (Windows) where you saved the file (download below). (Linux And MacOS. On Linux you'll need to flash with sudo) or where you have the platform-tools (Windows)
2)Poweroff your phone.
3)Boot into bootloader by pressing Volume+ button while connecting the usb cable into the usb port (the usb cable has to be inserted into the computer's port too, to successfully boot into fastboot)
4)With unlocked bootloader, type fastboot flash recovery twrp_3.0.2-0-seagull-UNOFFICIAL.img, if you renamed the files, substitube "twrp_3.0.2-0-seagull-UNOFFICIAL.img" with your file name or the directory where you saved the file.
5)When you see the OK message from fastboot, disconnect your phone.
6)Press Power, Volume+ and Volume- untile the phone vibrates.
7)Release Volume+ key. When you see the Sony logo appear, wait 3-4 seconds and then release Power button.
8)You should see TWRP bootscreen after a few seconds
-What's working:
Almost all. I could succesfully flash GApps and Root packages from this recovery, Backup, Restore and Wipe partitions. Settings work fine. Terminal and File manager work.
-What's NOT working:
Can't read files MicroSD or USB-OTG, can't browse in them and can't wipe. Investigating about it.
-Download:
(GDrive) Version 3.0.2-1
(AFH) Version 3.0.2-1
-Source and guide to build:
https://github.com/EmaMaker/device-sony-seagull/tree/twrp-3.0
Changelog:
30/04/2018: I think I fixed the screen problem by using the Lollipop kernel instead of the Marshmellow one
Thanks Everyone
Click to expand...
Click to collapse
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers

Lord Sithek said:
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Click to expand...
Click to collapse
Maybe you can try by holding down the volume down button when rebooting, it may work.
In other case, I think the only option is fixing the button
Best regards

EmaMaker said:
Maybe you can try by holding down the volume down button when rebooting, it may work.
In other case, I think the only option is fixing the button
Best regards
Click to expand...
Click to collapse
Oh, thx for your reply, I didn't expect it really after so many days This method doesn't work, unfortunately. But I won't bother fixing the power button, actually Ive just being using my old Xperia for testing purposes only. But thank you anyway :good:
Regards
Sent from my mido using XDA Labs

Boot loop
Lord Sithek said:
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Click to expand...
Click to collapse
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:

sushil lad said:
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
Click to expand...
Click to collapse
Sorry bro, I don't own this device anymore and I truly don't remember the procedure...
Sent from my SM-T720 using XDA Labs

sushil lad said:
Boot loop
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
Click to expand...
Click to collapse
same me too

TWRP recovery not working on Blackview BV9500

Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?

I, too, am trying to do this. I have not yet flashed it... I was going to use the fastboot boot command to boot the recovery kernel before permanently flashing it, to make sure it would work, and in my googling I stumbled across this post. Serendipity! [Edit 3: Although, reading your post again, I see you tried that as well and it didn't succeed for you. For me, it simply tells me remote: command not found, so how were you able to even get that to work?]
All that said... I have the BV9500 Pro, specifically for the two-way radio, so I'm going to try to keep that little tidbit of hardware working in the process. I mainly just want to tweak the menus a bit, tweak the quick settings, get root, delete the Google crapps I won't be using...
On to your problem, though, I can't help much but maybe if we post back and forth our successes and failures we might be able to stumble through it together?
First, I assume you already have unlocked your bootloader? [Edit: Honestly, I'm not sure flashing the recovery would be allowed without first unlocking the bootloader]
[Edit 2: Perhaps this thread might be of help. Different model, but often the hardwares used by manufacturers are similar enough that the same steps generally work. ]

Thank you for the link, maybe i need to flash the complete rom with the twrp recovery with spflash tools, and it will work.
I will try and let you know, but i will make a backup of my rom before flashing it!
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
To flash recovery with fastboot, you need first to enable the developer mode on your phone (go to "Settings > About phone" and make 7th tap on the build number, the Developer options will be unlocked and available), and unlock the bootloader of course.
here what is the process i made to flash the recovery :
- i use the command "adb devices" to check if the phone is well connected. (response is like "BV9500S320001179 device")
- then i enter in fastboot mode with "adb reboot bootloader" (phone reboot and ask confirmation for fastboot mode)
- check with command "fastboot devices"
- unlock the bootloader with the command "fastboot oem unlock" or "fastboot flashing unlock".
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.

I am too facing this problem. In case you got any solutions please let me know too.

Yves596 said:
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
Click to expand...
Click to collapse
Yup. Already had fastboot installed for the LG G5 this phone replaced, the Galaxy Note 4 the LG replaced, the MyTouch 4G Slide the Galaxy replaced, my wife's old Galaxy S5 I used in the interims... LOL, I've got a working install. No, the "Remote: command not found" was returned from within.... Whether fastboot or adb, I forget now, but I was able to get the file to flash eventually, after reading your first post, but unfortunately the phone would not boot to it (nor Android). I thought I'd bricked it. Twice this happened. Each time, after about 5 minutes, it eventually booted to Android.
I flashed the recovery from the ROM in the link Blackview sent me and was able to boot their recovery just fine, so there's something in the TWRP that my particular phone doesn't like.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
Click to expand...
Click to collapse
Thanks, I keep forgetting which keys to hold for recovery versus bootloader, so I use the adb command to be sure without having to keep a notepad nearby.
Clearly I don't do this as often as I used to.
(snip)
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
Click to expand...
Click to collapse
Now that was something I haven't done since the T-Mobile G1 days. My understanding was that you CAN boot a recovery without flashing it first if you"fastboot boot {image filename}" but that didn't work for me either. I'm also assuming that the filename to flash can be anything because the device stores it to a partition, so it shouldn't have to be specifically "recovery-verified.img".
The recovery you have... Were you ever able to boot to it? If so, would you be willing to share a link to its download source, please?
I've got to run for a prior engagement, I'll check back later.
Thanks!

veronicadavis said:
I am too facing this problem. In case you got any solutions please let me know too.
Click to expand...
Click to collapse
I guess i find the reason why the modified recovery image won't boot.
I find an interesting information in a post of osm0sis (https://forum.xda-developers.com/showthread.php?t=2073775) were he say : "some newer MediaTek (MTK) devices use special image signing that adds a "BFBF" pre-header signature, so images will unpack/repack but most likely won't boot unless run through their internal signing tool."
After more search, i find an interesting publication (http://www.lieberbiber.de/2015/07/04/mediatek-details-partitions-and-preloader/) witch confirm that.
They say in conclusion of the publication :
"Yes, I can confirm that SignTool is able to add digital signature information to firmware images. Signed images have an additional header “BFBF” and some fluff which SP Flash Tool checks on a secure device. Apparently some manufacturers merely used the default MTK key for signing the images, making them no better off than a typical insecure MTK device."
So we have to find another way to install magisk to root it.

Root 9500/pro
Mine rooted already....you guys can check on 4pda russian forum
Note : do not use the 17.1 version of magisk there because after reboot the device will freeze if you resboot after twrp 1st install...instead flash 17.3+ or 18+ right after first install of twrp...
EDIT : dont mind the russian language in TWRP as you can change it to english once there

Yves596 said:
Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
Click to expand...
Click to collapse
Hello I have same problem... Do you have that original recovery file? I don't have and I would like to get that back. Thanks.

DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru

kanadali said:
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
Click to expand...
Click to collapse
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.

Yves596 said:
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Click to expand...
Click to collapse
you can just download latest firmware and simply backup NVRAM etc with sp flash tool also flash with sp tool, you will have then working twrp with disabled encryption. there are tons of post regarding using sp flash tool on this forum
im using same phone and did these actions on first day and did not have any problem with twrp or magisk

Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards

nr0000000 said:
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
Click to expand...
Click to collapse
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?

kanadali said:
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
Click to expand...
Click to collapse
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.

Everything restored & updated.
Using SPFlashTool I flashed all files included in 2018092919_s32v63c2k_jk_pro.rar (including original recovery instead of TWRP).
After that, Android booted and then, using OTA, I updated to latest version.

Reflected_God said:
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Click to expand...
Click to collapse
Could you please send me the link? Can't find it on blackview forum

kanadali said:
Could you please send me the link? Can't find it on blackview forum
Click to expand...
Click to collapse
The latest version is not on the forum. I installed via OTA.
But if you mean the previous firmware, there is one link on the blackview forum: http://bbs.blackview.hk/viewtopic.php?t=480235#p795494
SP Flash tools are well documented here: https://forum.xda-developers.com/showthread.php?t=1982587
And a complete list of blackview bv9500 / bv9500 pro files and instructions (in russian): https://4pda.ru/forum/index.php?showtopic=931296
Hope you find what you are looking for.

@kanadali,
for the moment I'm not facing battery drain because there is not simcard in it at this state of my modifications, sorry.
@Reflected_God,
I think this is the link I used, I use the 2018092919_s32v63c2k_jk_pro.rar rom for base.
For all others who faces big problems like me (facial recognition not working then reboot on twrp only, I could reflash my phone with SPFlashTool, the rom and twrp from Jemmini/4PDA in russian only (others don't work for me). I used Format + Download in root mode on Linux. Then format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally. Do other things. To remove gapps I disabled/force stop it before remove with TWRP. Others apps I can't disable simply remove with TWRP. I test if I encounter bugs but none for the moment. If someone wants to know what I do I've made a LibreOffice Calc sheet log, which evolve when I have time
Hope this helps
Bests Regards

Need Files or a GOOD guide. bv9500 NOT PRO.
If someone could upload the exact files that they used, and the exact same steps, that would be great. Please mention what stock version you have and a link to the image if possible as well. I've followed numerous different guides, with multiple different rom versions, multiple different recovery imgs, used sp flash tool and adb/fastboot multiple times, tried making sure everything was unlocked before each try, have all the necessary drivers, and the closest I get to a functional twrp recovery is a green line that appears at the top of the boot screen before it reboots. Ive tried going to the source, the russian site, but all of the links are 404ed. if not for me, then it would be great to just have this all in one place. Thank you please future hero.
Please include exact program versions (ex SP Flash) as well if not zips of them. I am sorry to be asking so much in one post however I truly didn't know what else to do. And I am typically very good with my google fu xD
I currently have build number BV_BV9500_V1.0_20181026. That seems to matter I believe.

I second the notion.
I have the pro model. I have considered rooting it, but honestly, the phone works well enough as-is without root (for me). However, I'd LOVE to be able to play with different ROMs on this device **AS LONG AS I CAN MAINTAIN THE TWO-WAY UHF TRANSCEIVER FUNCTIONALITY** (i.e. not some "needs-a-network-of-some-kind" "walkie talkie app" like Zello but the real UHF two-way), and I'd LOVE the ability to play with the files associated with the radio to really explore the hardware's capabilities.
Unfortunately, this phone seems more popular in [North]eastern Asia than anywhere else so I don't think we're likely to get much on this forum regarding it unless and until BV become a popular name in the western hemisphere.

Question [SOLVED] Can't return back to stock ROM.

Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
EDIT: I have solved this issue.

NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
Click to expand...
Click to collapse
Try flashing miui via batch scripts is what I would do...
When you extract firmware there should be flash_all.bat file inside, run it via cmd - just type the name of it with cmd directed at the folder where the firmware is unpacked. ( For this you need adb tools installed properly so that the whole system has access to it , if you don't know how then download platform tools from google , unpack it and copy everything inside platform tools folder then paste into firmware folder , then you should be able to run the scripts inside firmware folder )
It will start regular process that mi flash does but if it fails then I guess you can see where it fails exactly and update here .
Idk...

You know, this would've been much easier to read if you put some effort into your grammar.
What error did you get in Mi Flash? Did you download the correct Fastboot Stock ROM for your specific region?

NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
Click to expand...
Click to collapse
try to download again the firmware, maybe the file you have been trying to flash is corrupted.
Most and foremost, try to be specific what it was you encountered. Feels like I was reading in a wattpad.

How did you do it?

Please share with how you solve it
NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
EDIT: I have solved this issue.
Click to expand...
Click to collapse
Please share with us how you solve it

miku1024 said:
Please share with how you solve it
Please share with us how you solve it
Click to expand...
Click to collapse
Basically , I managed to flash it successfully after many attempts. I was getting different errors every time when I was trying to flash the EU version in my PC , so I thought of switching to my laptop and trying with the GLOBAL version this time. I succeed the 2nd time . I also used a different usb cable. So it was just miflash being miflash... nothing to worry about.