yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] mexamilian:
What model of phone and FW are u running. I know u posted " BV9100NEEA000" but do u have the right FW on it that came witht he phone? There are 2 versions of this phone also FW files on official site are not updated to latest OTA update. Official FW for eu and non eu can be found here, but its old.

https://bbs.blackview.hk/viewtopic.php?t=532355 You can flash the older FW back and try again. If u have the original hardware FW on ur EU model phone then it could be possible for you

Ive made a post asking for the files, my message needs to be approved as a new registered user. You can bookmark the link below and wait for my post to appear and the files when and if they provide em.

official firmware - Page 2 - bbs.blackview.com

bbs.blackview.hk

Currently i reverted back to latest OTA stock FW till i get those new files.

I am at a standstill on the proper order to root and get twrp on this non eu model phone.

Magist guide says i need to flash to recovery partition (u need original to patch which i cant have without TWRP on the phone in the 1st place) Then there is another issue of getting TWRP onto the device before rooting which again u need the original vbmeta.img, i can do with a blank one but the problem comes to TWRP then setting an encrypted password provided by bengris32 which his twrp is for EU model of the phone. Headache

I'm on non EU FW, BV9100_M860A_v1.0_20200722V3

You can get SP Flash Tool thats needed to flash this phones FW, here https://spflashtool.com/ which has the latest version shown as V5.1924. There is also v5.2044 which i dont know how and where it came out, can be found here https://forum.hovatek.com/thread-13970.html @Hovatek seems reputable after me digging around for the past 3-4 days https://xdaforums.com/m/hovatek.5636663/

Assuming you have MTK Drivers installed. if not https://forum.hovatek.com/thread-16640.html or find official site.

Open up SP Flash Tool,

Go to tab Download

Point Download Agent to where SP Flash Tool is installed to the file "MTK_AllInOne_DA.bin"

Load up you FWs scatter file in the 2nd box/line "Scatter-loading File.

***IMPORTANT! In the graph table below MAKE SURE U UNCHECK the preloader box. This will help getting TWRP as recovery later on.****

Klik box up top with green arrow that says "Download"

Phone is in off state.

Attach your USB cable to the phone, but NOT to the computer yet.

Hold VOLUME UP & DOWN at the same time then connect it to the PC.

On the SP Flash Tools you will see a long white bar on the bottom of the softwares window

It will turn RED then Yellow and will start flashing your phone.

You can RELEASE KEYS after you see the RED COLOR.

Once SP Flash Tools is done flashing a box will come up and say Done.

Close box, close SP Flash Tools.

Disconnect Phone from PC and Phone and u are on stock FW.

If u didnt uncheck the "preloader" box TWRP will not work on your phone
[Miscellaneous Android Development] neccowafer:
That's the same as mine: BV9100_M860A_V1.0_2020722V3, so I guess I'm waiting on BV to respond to your firmware update request.
[Miscellaneous Android Development] bengris32:
Hi, this is because android restores the original recovery when the device boots, you must not let your device boot into android until you boot TWRP for the first time, repeat all of your steps, but when you "fastboot reboot", hold the volume up button to access the boot menu, then select recovery mode. Once your device boots into TWRP, it will automatically patch the rom to prevent the original recovery from being restored on boot up.
[Miscellaneous Android Development] mexamilian:
I confirm on my non EU bv9100 M860A

kept holding like you said then typed fastboot reboot and still held a selection menu popped up with 3 option on black background, i released the key then selected recovery, pressed the vol down to accept then quickly release it and went back to holding volume up and son of the devil :devilish: it worked thanks, now i go back to messing with magisk installation.

Question though,

once booted into recovery following what u just said above, should vipe data factory be done like other (lineageOS) require or not? if it work it works just maybe thats where i had my issue with no mount for microsd and external

@neccowafer i can link you the official FW so u can flash what i have?

Latest stock rom link of BV9100 - bbs.blackview.com

bbs.blackview.hk

get the non-EEA version and flash it follow your own steps you mentioned

EDIT: Just did wipe data button bottom right on button [WIPE] then did factory wipe.

How access to internal and MTP on reboot into recovery with buttons, still can get micro sd mount
[Miscellaneous Android Development] mexamilian:
Got a reply from official blackview admin

official firmware - Page 2 - bbs.blackview.com

bbs.blackview.hk

looks like there wont be any updates to A10 and over. Gonna be trying out different CFW and see how it does, i managed to get unofficial lineage-17.1-20201215 unofficial with test keys flashed
[Miscellaneous Android Development] JeffJK:
I just got one of these phones today and I'm having a bear of a time getting into it with adb to install TWRP and hopefully flash a new ROM. I tried to follow the detailed instructions from neccowafer (thank you for those!) earlier in this thread, but adb returns the device as unauthorized when in recovery mode.

This phone seems to have two recovery modes. One is accessed by booting while holding vol-down and the other is loaded when you boot holding vol-up and choose recovery from the menu.

In either recovery mode, I run adb devices and get

List of devices attached
BV9100EEA00016800 unauthorized

While booted to Android, I run adb devices and get

List of devices attached
BV9100EEA00016800 device

I'm becoming a bit frustrated trying to figure it out on my own, and it's been a few years since I did any custom bootloader or custom ROM stuff with Android, so any help would be very much appreciated.
[Miscellaneous Android Development] mexamilian:
@JeffJK I have factory mode on my down key and recovery mode on up, you wanna do up. my model is NEEA
[Miscellaneous Android Development] JeffJK:
Oh good to know! I got the same error noted above in the up key mode, the unauthorized thing from adb. Any idea why?
[Miscellaneous Android Development] mexamilian:
did u enable dev mode then enabled usb debugging, boot loader unlocked?

when u got ur phone out of the box, skip everything and dont sim in, just skip things, make sure u dont set any pass and dont encrypt device, enable dev mode then enable debugging by tapping on ur build in settings all the way on bottom in about. make sure oem unlock is also enabled and greyed out if u done already so.
[Miscellaneous Android Development] JeffJK:
Ah, I did set the phone up. Should I wipe and start over?

EDIT: I did a factory reset and booted into Android to turn on debugging, and even without setting up anything on the phone, encryption was enabled in the security settings and adb still lists the device as unauthorized while in recovery mode.

EDIT 2: Also tried wiping /data from the recovery mode menu, which put out the below lines but still did not allow adb access even after a kill-server

Formatting /data. . .
Formatting /cache. . .
Formatting /mnt/vendor/nvdata. . .
Data wipe complete.
[Miscellaneous Android Development] mexamilian:
@JeffJK To remove encryption meaning you had twrp installed and made it work or stock os?

Boot into recovery Format data / factory reset This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).

*DONT set any passwords for lockscreen, dont login to google, pay attention to not encrypt device when setting up. just basic skip u dont even need wifi or sim in phone

Dont forget to unlock ur bootloader before flashing or doing anything. Follow post #7 thats exactly how you would do it then read up on post #10 and #11 and it will work.

Also did you install USB drivers?

Get android usb drivers https://developer.android.com/studio/run/win-usb

if that didnt work try the one below,

https://forum.hovatek.com/thread-16640.html (need to register) you want the " Auto Mediatek USB VCOM Drivers Signed"

If you messed up you just flash your legit FW back to stock and follow post #7 10 and 11
[Miscellaneous Android Development] JeffJK:
I couldn't get TWRP because adb still reads the device as unauthorized. I wiped the data while in recovery mode, booted to the"Welcome" screen, and when I skipped everything in the setup wizard, the settings still show encryption as enabled, and I had no option to enable or disable it at any point. Bootloader also still showed as unlocked. This seems like a very unusual problem! I have drivers but will try the vcom ones.
[Miscellaneous Android Development] JeffJK:
I did this, and reauthorized when it brought up the prompt, but the security menu says the phone is encrypted and adb says the device is unauthorized (only while in recovery mode; adb works booted into Android). Also, fastboot commands straight up do not send while in recovery or bootloader. It just says "waiting for device" and the phone displays "FASTBOOT MODE..."
[Miscellaneous Android Development] JeffJK:
Maybe relevant, I get the below message when trying to enter the adb shell

error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

I can, however, get the phone into adb sideload mode, but I don't now how to install TWRP that way.
[Miscellaneous Android Development] mexamilian:
ops didnt see 2nd page XD

What do you currently have on phone? bootloader unlocked, this threads TWRP installed, root?

Can you boot phone to home screen?

If for some reason something got messed up, you can boot into bootloader, select fastboot,

type

fastboot devices

enter

if device popped up

type

fastboot flash recovery stockROMsRecovery.img (place it where your Platform Tools folder is)

enter

Reboot to system and skip all setup and read post 20 to backup certain things because later you wont be able to do it and have to struggle like me for days figuring it out, only applies if u havent flashed any custom rom or fw not meant for your phone (big issues with headaches)

Otherwise u will have to flash your EU or NON EU firmware back.

Dont flash anything yet. Look at my post #20 on 1st page (last one) i got some

crucial

info there and a request since u still have a hopefully original stock image installed with all its hardware files (which i lost due to a bad flash). take a look at your phones original box BV9100 came in. on the back you will have some stickers (KEEP these) you will need em if u ever mess up your nvnand

sorry for repeating im copy pasting my own messages. ATM you need to have stock default original fw in original state your phone came in the box with.

From what im currently aware of u can only sideload ZIP files and not img(twrp)

you have to have the previous steps in place and flash via fastboot
[Miscellaneous Android Development] JeffJK:
EID: Unknown

Serial: BV9100EEA0001****

BT (*00:61) and Wi-Fi (*03:cb) do not match

I have MTK Droid Tool, but I can't produce a scatter file with it for some reason

I can boot into home screen, but DO NOT have TWRP installed as ADB won't give me access in recovery mode
[Miscellaneous Android Development] JeffJK:
UPDATE: Tried again on a new computer following all of your steps and the phone can still not be read by adb in recovery mode. It still shows up as unauthorized. MTK Droid Tools won't root it either.

UPDATE AGAIN: I managed to find more info. MTK Droid Tools doesn't work on this chipset, but SP Flash Tool does. I've been experimenting with using Magisk to patch img files and flash them using SPFT. Nothing seems to have worked so far, but I'm not very knowledgeable. Each attempt so far has put the phone into bootloop red state and requires me to reflash the untouched img.

UPDATE AGAIN AGAIN: It was an issue with Windows drivers all along, argh!! I think I've got it now.
[Miscellaneous Android Development] JeffJK:
Okay, got TWRP up and running, got everything adb and fastboot up. Now my new mission is to install Android 10 or 11 somehow, either custom ROM or GIS system image. No luck so far.
[Miscellaneous Android Development] mexamilian:
@JeffJK Awesome u got twrp. can you check if u can mount micro sd card or use a usb drive and its visible in TWRP?

I managed to flash a couple different roms but they run slugish aside from havoc os

Ive tried lineage 17.1 for 3 days and havoc for 2 with google apps pico, tried lineage 18.1 but no plays store for it yet went back to stock fw, it runs pretty well especially the long batt life is what im after. i slowly strip down original rom down so no crashes yet. im using official lucky patcher https://www.luckypatchers.com/ to uninstall apps as i have a pro key for titanium backup and its trash at uninstalling anything non user installed(used to be my number1)

for trusted roms that i tried work are these ones:

*Havoc-OS-v3.12-20201230-Official-GApps-arm64-ab.img (this one is stable, had default app crashes at 1st but after clearing caches for those apps works like a charm and my fav so far)

Havoc-OS - Browse /arm64-ab at SourceForge.net

sourceforge.net

*Stock BV9100 rom OTA updated is pretty stable and the one im gonna use, its easy on memory and i have striped it to bare android experience, prolly the best rom for this phone on android 9)

Latest stock rom link of BV9100 - bbs.blackview.com

bbs.blackview.hk

*lineage-17.1-20201215-UNOFFICIAL-treble_arm64_bvS.img (this one drains my batter way to fast than stock rom, play store works wish it was good on bv9100)

Andy Yan's personal builds // GSI - Browse /lineage-17.x at SourceForge.net

sourceforge.net

*lineage-18.1-20201219-UNOFFICIAL-treble_arm64_bvS-vndklite.img (this works but no official playstore, havent really messed with it to see its full potential)

Andy Yan's personal builds // GSI - Browse /lineage-18.x at SourceForge.net

sourceforge.net

****Evolution X rom. (IF You manage to get this one working with stability let me know, this is the one i actually want on bv9100, this one is supposed to run pretty cool temp wise under load)

Download Evolution X 4.1 Android 10 Rom

Download Evolution X 4.1 Android 10 Rom Download Evolution X 3.0 Android 10 Rom Pixel UI, Android Q vibes, Customization and more. We are Evolution X! Evolution X 4.1 Quick settings can be accessed by pulling the notification shade further down. Most Android skins allow you some basic quick...

tweakguy.com

Evolution X #KeepEvolving

#KeepEvolving!

evolution-x.org

Evolution X - Browse Files at SourceForge.net

Pixel UI, Customization & More. We Are Evolution X!

sourceforge.net

Reference for what to download, Our bv9100 are arm64 A/B systems, vndk28 supported and system as root supported, Still looking for what "flavor/codename our stock systems are, if u know holler with proof:

treble_arm_av*	ARM 32-bit, A-only	32A
treble_arm_bv*	ARM 32-bit, AB	32B
treble_a64_av*	ARM 32-bit with 64-bit binder, A-only	A64A
treble_a64_bv*	ARM 32-bit with 64-bit binder, AB	A64B
treble_arm64_av*	ARM 64-bit, A-only	64A
treble_arm64_bv*	ARM 64-bit, AB	64B
[Miscellaneous Android Development] JeffJK:
OH SNAP, I thought we were a-only, no wonder I've been struggling!!
[Miscellaneous Android Development] mexamilian:
u can install these apps to check info:

Treble Check - Apps on Google Play

Check your device for Project Treble support and more

play.google.com

Treble Info - Apps on Google Play

Helps you check Project Treble, A/B and Architecture for GSI installation

play.google.com

Were you able to check if u can mount micro sd cards or usb flash drives on your device inside TWRP recovery mode?
[Miscellaneous Android Development] JeffJK:
I was not able to mount sd or otg usb, unfortunately
[Miscellaneous Android Development] mexamilian:
@bengris32 would you please take a loot at this.

@JeffJK got a nice list for you to debloat https://www.olorin.me/2020/02/11/debloating-the-umidigi-f2/
[Miscellaneous Android Development] JeffJK:
So, I used Treble Check to see again, and it DOES say I have a-only. Would it be dangerous to try the AB img anyway?

UPDATE: HAVOC A/B WORKED!! FINALLY. No fingerprint sensor support tho, hmmmm.... Trying out AOSP 11 next, first boot is taking a WHILE.

UPDATE AGAIN: AOSP 11 gets stuck on the Android logo while booting, vndklite and non. Dang. Might have to settle for Android 10.

UPDATE AGAIN AGAIN: AOSP11 booted!! I had to unlock the bootloader in fastboot again. I've had to do that... an oddly high number of times.
[Miscellaneous Android Development] mexamilian:
@JeffJK yo, so i was messing around with other TWRP i manages to get micro sd card and usb flash drives to mount but its on a different recovery version 3.3.1 mehanik6 oukitel k9

331 BV9100

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

put device in fastboot check for fastboot devices,

then

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

then flash the recovery from the link.

when u flash it and boot into it it will ask you for a password since i didnt have it, what i did is press back till it let u in to twrp main menu. then i Format data / factory reset and reboot back into recovery flashed magisk 21.2 zip file and reboot into system

all working well.

when u flash the images flash to system

fastboot flash system nameofrom.img

havoc woks well with the name of image and link i provided for sure. i dont use any lock screen security. Ye lineage took a while to boot up, its normal i experience that as well
[Miscellaneous Android Development] JeffJK:
I was able to flash the system img from internal storage, thankfully. I'm currently using this version of Android and I'll let you know how it goes:

system-roar-arm64-ab-vndklite-gapps.img.xz
[Miscellaneous Android Development] JeffJK:
Interesting new problem: My device locks the bootloader upon reboot and unlocking it seems to reset my OS back to first launch

EDIT: I think I'm good rebooted once or twice with no issues...
[Miscellaneous Android Development] mexamilian:
ye u want stock or Havok, those are solid atm
[Miscellaneous Android Development] JeffJK:
I'm loving Android 11, but I want to pull some of the vendor apps out of the stock rom and install them, and I want to find out how to get my current rom to recognize the fingerprint sensor and the extra hardware button. Could someone point me toward a tutorial? I am usually good at fumbling my way through stuff like this, but I don't even know where to start. I could start pulling .so libraries out of the vendor img, but I'd like to go in a little less blind!
[Miscellaneous Android Development] DavaDino:
Hallo All,

Have tried to follow post #7

But i get stuck at rebooting in to fastboot.

My phone will boot in to fastboot, but on my computer it shows up in device manager under other devices with a yellow question mark, so a driver problem.

Have tried drivers but nothing works.

Can someone link the correct driver here for Win10.

Greeting

EDIT:

I followed this https://androidadbdriver.com/blackview-bv9100-usb-drivers/

But when i install the drivers in device manager the drivers are installed with error 10.

"cant start the device" and has a yellow question mark.

When i then connect my phone i shows up as a android device with a yellow question mark.

If i then click with right mouse on the android device and install the driver (can only install one) the android device then disappears and i have a "Android ADB Interface" without the yellow question mark.

But then i only have one working driver, cant install the other 2 drivers.

Please Help.

tryed both PC and laptop. When installing the drivers on my laptop it shows-up as SAMSUNG Android phone well on PC it shows-up as Android device.

Greetings
[Miscellaneous Android Development] DavaDino:
Okay have it working now.

I removed the drivers. Then followed post #7 til the point off " adb reboot bootloader "

Then in device manager it shos-up as Android device with a yellow question mark.

Then did right clik en select install drivers. I then only installed the bootloader driver end not the other two.

Then did " fastboot devices" and it showed up. So folloyed rest of post #7 en post #10, now it works.

Greeting
[Miscellaneous Android Development] bengris32:
Hi, please avoid off-topic discussion on this thread, the discussion of this thread should be about TWRP.

However, feel free to talk on my BV9100 Telegram group
[Miscellaneous Android Development] bengris32:
Hi, to avoid trouble next time, please try using Google USB Drivers, extract the zip. Now when you plug in the device, wait for it to appear in device manager, update device software, manually select driver, point it to android_winusb.inf and select "Android Composite Bootloader Interface", you may get a warning about incompatible drivers, simply continue anyway. Then device should be detected by fastboot
[Miscellaneous Android Development] DavaDino:
Hello,

i need some help.

I just updated magisk manager, got a message it needed to boor the phone for corect install.

Now my phone turned of but never turned on.

If i connect the usb-c cable i do see the red led light up, but phone will not start. i can press the power button as long as i want, but nothing happens.

greeting
[Miscellaneous Android Development] 95amberdaniels:
That's why I always use patchers!
[Miscellaneous Android Development] GroovyG:
Hi guys, big thanks for this thread and especially @bengris32 for the lovely TWRP, made setting up a BV9100 a breeze :love:

I'd also like to share some stuff I found while fiddling around with it:

- The GSI that runs best for me is LiR by @eremitein , check it out HERE . I used the vanilla (arm64 bvZ) build and added microg for FCM support and sefetynet

- I managed to pull the latest stock vendor.img from the OTA, it has vendor security patch dated April 1st 2020 and a kernel built April 30th 2020, see screenshot attached. If anyone needs it let me know

With this combo the device runs like a charm - blazingly fast, no bugs encountered and battery lasts forever.
[Miscellaneous Android Development] DavaDino:
Okay, i shiped the phone for warranty, and received it back today with a different IMEI nr.

But don't no what was broken on the phone, but it works again.
[Miscellaneous Android Development] DavaDino:
Hello, can you please post some link on how to use patchers for my phone ?

Greeting
[Miscellaneous Android Development] detlion1643:
I've got to say this: Thanks for this thread and everyone who provided information.

I received my BV9100 today, only bought it for the battery size, and all of these instructions are still working as of today (09/10/2021). I've successfully installed the TWRP recovery.

Next up is flashing the Magisk zip. I might even get into custom roms on this phone. The last time was using LineageOS and it was like 4 years ago. Is Lineage still the go to?

BTW, for anyone wondering, I'm using this phone on Cricket Wireless in the United States. Cricket told me they won't allow me to use since the IMEI number isn't supported. Popped my sim in anyways to try, and no issues yet!

Edit - Is there a way to remove the message about the "unlocked and can't be trusted" and "wait for 5 seconds"?
[Miscellaneous Android Development] denncath:
I'm about to give up trying to make fastboot driver to work. I've tried to disable driver signing and use Mediatek Driver Auto Installer v1.1352. Restarted pc. Device is unrecognised (exclamation mark in device manager). Tried to force-install every driver from that package, - fastboot didn't pick it up. I also tried a driver package from google and force-installed the supposed universal fastboot driver - did not work. If you have it working, could you at least check what the driver is called, what package you used etc., so I have al least something to grab on instead of blindly trying everything... Thanks in advance!

PS. ADB driver works properly