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.
Hey everyone, so I saw that there was a new update for MIUI Developer ROM (9.3.28) and I decided to download it. After I downloaded it, i opened twrp and flashed it with lazyflasher as I always do. After the phone boots normally, i realised that the phone had been upgraded to android pie, so I went to check google camera to see if it was working still, but it didnt. So I went back to TWRP to try to enable HAL3 via adb shell, but when i opened TWRP i saw a strange message. It asked for a password in order to decrypt my data. this was the first time i saw it and after searching a bit I tried to use my phones password, but it didnt work. I decided to ignore the message and just open adb shell and enable HAL3. The thing is that when I tried to open it said device not found, which is really strange ( im using the same computer as i was before, adb is installed of course ). I had no choice but to downgrade to stable, so I tried to downgrade to stable rom. Downloaded the rom, but when i chose "choose package" it wouldnt let me install the stable one because it was an older version of android....
So long story short, Android Pie has left me with a non-working Google Camera, TWRP and no ability to downgrade or flash and ROMs.
Any help would be appreciated
https://www.youtube.com/watch?v=bsbZ3kG88Dw
Same problem with me. I tried everything but no luck and now I am unable to use camera2api. So i thought to root my phone and edit build prop manually but when I flashed magisk my phone stuck at boot logo. I lost all my data and I had to flash with mi flash tool. Luckily my bootloader was unlocked.
After flashing Pie, you have to flash a TWRP recover for MIUI Pie. This will allow to decrypt your device (data will be erased).
If you want to rollback to stable (as I did), download fastboot ROM via MIUI official site, boot to bootloader and flash it via flash_all.bat file included in the ROM (assuming you have fastboot on your PC).
Hi, I have Moto G7 Power xt1955-4 with Android 10 Q, unlocked for any GSM carrier, used on T-Mobile network. I unlocked the bootloader and i'm trying to install TWRP recovery image into it. Mostly I follow this guide https://www.androidinfotech.com/root-moto-g7-power-ocean-android-10 . I got the latest available for my phone TWRP -3.5.2-10-ocean from https://dl.twrp.me/ocean/twrp-3.5.2_10-0-ocean.img.html, switched my phone into fastboot mode so it's visible to 'fastboot devices" command, then i run "fastboot boot twrp-3.5.2_10-0-ocean.img" Phone reboots to temporary TWRP now, shows "Enter password for User [0] - ... Data successfully decrypted".
Now, when I try to permanently install TWRP, I got a problem, even though everything looks ok, no error messages: first I installed Disable_Dm-Verity_ForceEncrypt.zip file, with Success. Then I installed twrp-installer-3.5.2_10-0-ocean.zip via TWRP itself: it shows "######## TWRP installer for A/B devices ######## Running image patcher on boot_a... Running image patcher on boot_b... Image patcher complete! Done installing TWRP ***Note: You are now unrooted!*** Updating partition details... Success!" - note no errors here.
BUT when I reboot into recovery mode again, I see only TWRP logo, then phone beeps for 1 sec, and nothing happens after that, no menu shows up, no prompt to "Enter password for user" as before. No response from screen touches. Only reboot helps.
So I understand that TWRP was not installed correctly. What did I do wrong?
Any suggestions will be appreciated.
You should join and follow the G7P (Ocean) telegram group if you haven't already done so. Any questions can be asked there or are already answered in the #notes section. As far as twrp goes because the device is a/b type I never install the zip. I connect to pc and fast boot twrp image to flash ROMs.
Skippy12359 said:
You should join and follow the G7P (Ocean) telegram group if you haven't already done so. Any questions can be asked there or are already answered in the #notes section. As far as twrp goes because the device is a/b type I never install the zip. I connect to pc and fast boot twrp image to flash ROMs.
Click to expand...
Click to collapse
Thank you Skippy12359, I found just "Moto G7 Power Ocean/River Channel" on Telegram, with 10 subscribers - is it the one you mentioned?
My goal is to install Magisk-v23 on my phone, to complete rooting procedure. I was going to use TWRP for this, and install it via zip file. But if I use temporary TWRP and just install Magisk-v23.0_renamed_apk.zip, after reboot Magisk app shows "Installed" status as N/A! Apparently it doesn't work as intended... So I thought that permanently installed TWRP would give better result.
UPD: Also I see "Moto G⁷ Power | Builds™" channel with 445 subscribers, and "Moto G⁷ Power | Discussion™" with 379 members. Signed up for those!
There's a Moto g7 power discussion group and a Moto g7 power builds group. If you're new to flashing ROMs put all your ROMs, magisk, gapp files on your sdcard. Then fastboot twrp and flash ROMs, magisk from there. You can install the twrp zip if you want just found it easier not to because it gets overwritten anyway because the device has no separate partition for recovery like an A- only has for example.
Actually this method (fastboot to temporary TWRP, then install magisk.zip file from sd card) works! I was able to install Magisk this way, and first time it boots normally, Magisk shows Install status v23, CheckRoot app shows that everything is ok. But on second reboot i'm getting into bootloop After Warning message and 5 sec wait my phone beeps and reboots.
Magisk has an uninstall zip file if you have boot problems. Once magisk is uninstalled from recovery it should boot up fine. There is also a magisk canary version on github which should fix any boot issues after flashing. You need both the magisk zip and the magisk app installed to have full root
I try Magisk-Canary (after uninstalling Magisk v23 by renaming zip file to uninstall.zip and run it via TWRP) from https://github.com/topjohnwu/Magisk, the result is the same- first boot is Ok, Magisk app shows that it's installed (Magisk status 5d6d2417 (23015) version installed), but second boot gives me bootloop...
What ROM are you using?
I use Original stock ROM, that comes with the phone. XT1955-4_OCEAN_RETEU_10_QPOS30.52-29-7-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip file from ttps://mirrors.lolinet.com/firmware/moto/ocean/official/RETEU ( i just found it to get boot.img and patch it with Magisk, I didn't change original firmware , just unlocked bootloader.
I haven't used stock for over a year and I don't recall having any problems rooting or ever had a boot loop on rooted stock Q. Also I've never needed to patch a boot image to get root. I just reflashed stock firmware, installed all the apps I wanted and fast boot to recovery. Flash copy partitions zip and then flash Magisk. After reboot to system I install Magisk app and I'm done. Always worked for me. Rooted and no reboots.
I assume that you have Moto xt1955-4, correct? Which ROM you have installed then? At the time of Magisk installation , was it custom ROM or original stock ROM on your phone?
I have the usa model of the same phone xt1955-5 and have always had it rooted whatever custom ROM or stock firmware used at the time. I'm currently on AICP 11 official custom ROM but switch frequently from Arrow, Colt and other ROMs.
Skippy12359 said:
I have the usa model of the same phone xt1955-5 and have always had it rooted whatever custom ROM or stock firmware used at the time. I'm currently on AICP 11 official custom ROM but switch frequently from Arrow, Colt and other ROMs.
Click to expand...
Click to collapse
Hey Skippy, When I originally got the phone, I bought it outright from Cricket. A Supra, but still the same as G7 Power.. No payments. No years agreements. Now that it is no longer supported, I want to unlock the bootloader and install a custom rom. Setup ADB and went to Motorola's website for the unlock code. I get "Does not qualify for unlocking." For the above two reasons, I'm a bit miffed. Has anyone found a work-a-round for this? I got up at 6 AM. All day studying and learning how to do this. Only to get the message. "No you can't. Sorry. Notta". And with Motorola's piss poor support policy, it grinds my gears.
Danny3568 said:
Hey Skippy, When I originally got the phone, I bought it outright from Cricket. A Supra, but still the same as G7 Power.. No payments. No years agreements. Now that it is no longer supported, I want to unlock the bootloader and install a custom rom. Setup ADB and went to Motorola's website for the unlock code. I get "Does not qualify for unlocking." For the above two reasons, I'm a bit miffed. Has anyone found a work-a-round for this? I got up at 6 AM. All day studying and learning how to do this. Only to get the message. "No you can't. Sorry. Notta". And with Motorola's piss poor support policy, it grinds my gears.
Click to expand...
Click to collapse
I have the TMobile variant codenamed Ocean, so I'm not going to be much help on your question. I suggest you ask in the Moto g7 power discussion group on telegram. I'm sure someone there can let you know if the cricket variant is unlockable or not. Good luck
Skippy12359 said:
I have the TMobile variant codenamed Ocean, so I'm not going to be much help on your question. I suggest you ask in the Moto g7 power discussion group on telegram. I'm sure someone there can let you know if the cricket variant is unlockable or not. Good luck
Click to expand...
Click to collapse
Thanks for the quick response! I don't use Telegram, but I guess I better get signed up. I wish there was a repository of, an HCL of sorts, where people can refer to before buying phones to avoid these issues.