yashsingh1/xdaforums huggingface dataset:
[Android General] hobs0n:
Im really thinking of buying this phone. My main worry is that the UBS-C port on works with the cable that comes with it and that regular headphones wont work with the headphone output on this phone. Can anyone make any of this clear?
[Android General] Alberto96:
Not that easy, you need to modify the SystemUI.apk.

As regards the USB-C port, you can find compatible cables that fit (as long as the connector isn't too short, it works. For example, AUKEY ones are not compatible but iVoler ones yes), unfortunately though you are right for the headphone jack. As far as i know, there are no other headphones/earphones with a long plug.
[Android General] Alberto96:
20170814 Stock ROM added to first post.

Changelog:

- Minor bug fixes (Camera Blur issue)
[Android General] Pappmann:
Does anyonehere have Experience to change the SystemUI.apk to stock android Statusbar/Quicksettings?
[Android General] Alberto96:
20170822 Stock ROM added to first post. Fixes all issues with Waze and Google Play. (for users being impacted by these issues)
[Android General] danielesr82:
Ciao [MENTION=2386505]Alberto96[/MENTION] , ho da pochissimo acquistato questo grandissimo telefono dopo aver avuto il bv6000. Non mi dilungo... Ho seguito alla lettera la tua guida per il root, appena ho terminato il flash al primo avvio tenendo premuto v+ mi parte la recovery TWRP ma al riavvio successivo premendo sempre v+ mi si avvia la recovery originale.

In più riprovando e rimettendo TWRP ho seguito la procedura per installare supersu che sembra andare a buon fine ma al riavvio successivo non è tra le app e rimane sempre non rootato.

La versione di rom che ha è la V0.1_20170803_20170829-1811 è ho usato la tua versione di TWRP e di SP Flash Tool.

Cosa posso fare? Ti servono altre info? Grazie in anticipo per l'aiuto.
[Android General] Alberto96:
Solo Inglese su XDA-Developers.

I'll summarize your question to let others who don't understand Italian know it. He is asking why the device keeps losing TWRP after a reboot, as well as SuperSU.

I guess the system partition gets mounted as read-only, thus, all changes won't get applied.

To be sure, after installing SuperSU, go to the TWRP's File Manager, browse to /system, and delete the "recovery-from-boot.p" file. Please make sure that the system partition is mounted before doing this, otherwise you will get a blank folder.

If you get an error, then it means that the system partition has been mounted as read-only. You will find the RW flag in the Settings menu.

Keep me informed :)
[Android General] Alberto96:
20170829 ROM added to first post, should fix all issues with camera focus.
[Android General] danielesr82:
I'm sorry to all for my bad English. Thanks for the help Alberto, it was mounted read-only.

Enabling it I managed to get on /system and delete the "recovery-from-boot.bak" file (I did not see any other names).

I tried again to install SuperSU and restart, to reflash TWRP and check that the file was always deleted, the memory enabled RW .... but at first I do not find SuperSU and I reboot the original recovery as well.

Now I'm trying again with another Windows but it does not change the situation.

PS: Looking at the log better when installing Super SU writes: Boot image patcher - Finding Boot Image - Boot image: / dev / block / mmcblk0p21 - extracting ramdisk - failure, aborting.
[Android General] Alberto96:
It sounds like a LZMA ramdisk then.

Could you try Magisk instead? https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Android General] danielesr82:
I tried to install Magisk-v13.3.zip with TWRP just installed but:

Mounting /data/magisk.img to /magisk - Magisk image mount failed...
[Android General] 82ghost82:
thank you serg, downloading right now it's very slow, I think I will flash it tomorrow and report if some of the major bugs are solved, expecially the deep sleep one.
[Android General] 82ghost82:
About the "6th december" rom:

- stock camera "red is pink" is solved

- stock camera has hdr button in the top bar (I didn't have hdr button in previous official rom)

- deep sleep problem not solved, at least on my device

I noticed the mtk logger running at the first startup, after stopping it and following reboots it didn't start again.

Developer options already activated.

About the firmware:

patch level: 5th july 2017

GSM version base band: MOLY.LR11.W1630.MD.MP.V14.P21, 2017/11/08 16:10

CDMA version base band: SIXTH.CBP.MD.MP5.V19_P8, 2017/09/27 09:54

Kernel version: 4.4.15 root@onesmile-All-Series #1 Wed Dec 6 17:09 CST 2017

Build number: BV8000Pro-Blackview-V0.1_20170803

Actual rom: BV8000Pro-Blackview-V0.1_20170803_20171206-1558
[Android General] allincheung:
for those who interested in buying a new Bv 8000 pro, dont ever buy from gearbest, they claimed this phone in stock but they didnt. Ordered/Paid for my Items on the 31st of August. As of Today 11th of December Items have still not arrived. Almost 4 months and no movement. I contacted DHL to enquire about an update. They revealed no item has been delivered to them for shipping and it was just an shipping order placed. and BAD CUSTOMER SERVICES EVER!!!
[Android General] jman0:
Hi, how did you flash it? Did you use MTK SP Multi Port Download Tool or SP Flash Tool? I used the latter and flashed everything but recovery and userdata, to keep TWRP, my apps and setup. The result was that my phone booted to a white screen, with no startup sound. I waited for a while, and it didn't seem to boot, but it was detected by adb. I finally flashed previous firmware again, then flashed TWRP, and finally restored a TWRP backup.

I think it may be because I didn't flash recovery, but I'm not sure. I may try again today.
[Android General] 82ghost82:
SP flash tool (firmware upgrade), I flashed everything with no problems.
[Android General] jman0:
Ok, I'll try again. I used download only instead of firmware upgrade and did not flash everything. I think I might be able to restore data from my TWRP backup later, or at least restore my apps using Titanium Backup. Thanks
[Android General] jman0:
This is definitely not suitable for all BV8000 Pro phones, so I guess there must be some subtle difference between them, or the firmware is still work in progress. I just tried on mine again, using firmware upgrade and flashing everything, and got the same result: a white screen and no sign of booting. Got it to work by flashing the latest firmware again. At least, since it was now unrooted again, I was able to receive the latest OTA upgrade, which I'm now downloading.
[Android General] jman0:
I finally noticed there was a new official firmware available on the Blackview forum and flashed it. It's based on the 1114 version, just modified to fix the red/pink issue on the camera and the lack of HDR mode on the back camera. It's noted on the site that once you flash it you can't flash older firmwares or your phone will be bricked (never heard of that on other Mediatek based phones) but I don't care, since I just wanted to have the latest version and this one works fine for me. Also, fingerprint scanner looks quite faster and more accurate than before, but that could just be my first impression or me wanting it to work better.

The 1206 firmware might be flashable, unchecking something, but I don't know what and I really don't care, since its changelog seems to be the same as this new 1114 official version from Blackview.
[Android General] serg2327:
all because you downloaded the firmware from another resource ... the firmware on my link works! "
[Android General] xJ$:
Link not working.

I couldn't download the file.
[Android General] jman0:
I downloaded it from the link on Needrom. Anyway, I'll wait for an official release. Thanks for sharing.

BTW, as I said previously, the changes look the same as the modified 1114 version from Blackview: red/pink issue and lack of hdr on the back camera. Everything else looks the same, or at least no one reported otherwise
[Android General] jman0:
One thing I noticed after running the phone on the updated 1114 revision: I installed Magisk 14.5 and the phone passed the SafetyNet check, although Magisk still fails to mount properly and modules don't work. Superuser keeps working. Google Play Store keeps saying my phone is not certified.
[Android General] Matioupi:
Rom update after rooting

Hello,

I rooted my BV8000 a while ago (it's on build 1_20170803) . Thank a lot to people making that possible.

I saw on blackview forum ther eis a new ROM 20171219_s21v57c2k_jk_tee.zip that is supposed to solve some battery drain issues (amongst other corrections)

How should I handle upgrading on a rooted device ? Are there any special stuff to do, will it loose root ?

Sorry if this aleady been asked before, I looked at a few of the 20 pages of this thread but not all of them...

Regards, and merry christmas !
[Android General] poganytamas:
Rooted device can not be updated via OTA, only via Flashtool. I usually (but please read my note below) download the Flashtool firmware, select everything in Flashtool except recovery and userdata (to keep my applications / settings / internal storage). After flashing, I immediately boot into recovery, and re-root the device. And yes, you will loose root during the process, and the first thing you must do is to gain it back.

But note this: 20171114 rom, and all the roms after, are incompatible with the previous roms (they even have a red warning on their download site). That means you can not keep userdata (your internal storage of files, and your settings / applications). So for the first time, you must select userdata in Flashtool too. And you have to reinstall your applications / settings with another tool than TWRP, for example Titanium Backup.
[Android General] Matioupi:
Thank you for all the details.

I managed to upgrade ROM and reroot successfully.

In the process, I lost IMEI number that when to 1111... for slot 1 and 2222.... for slot 2.

I saw another user facing it on blackview forum.

I solved this with this tool :

sn-write-tool-v1-1728

together with regular Mediatek VCOM USB drivers used for flashing (and of course original IMEI numbers from the phone box that I hopfully kept !)

You also need 2 files from the stock ROM : MDDB_InfoCustomAppSrcP_MT6757P_S00_MOLY_LR11_W1630_MD_MP_V14_P14.EDB and APDB_MT6757_S01_alps-mp-n0.mp5_W17.32, you have to enter them in some option box of the sn-write-tool-v1-1728

Regards
[Android General] Matioupi:
was in experiment mood... tryed magick 15 that just went out, but this does not seem to work (out of the box) on the BV8000. I'm stuck at boot logo... will probably have to reflash everything again...
[Android General] Matioupi:
I did not had to reflash everything...

I unistalled magisk from TWRP with uninstaller. That allowed booting correctly.

then I reinstalled version 14 (from TWRP) (so back to starting point)

then upgraded magisk manager to 5.5.1 (sideloading apk from github)

then upgraded magisk from magisk manager. I checked both box (force ciphering and the other one). Also, at the end of the process, I did not choose to reboot from Magisk manager. I just exited. Then I switch the phone off on the regular way, on turned it back on.

One nice thing is that now Netflix is showing off from playstore and running correctly !
[Android General] Matioupi:
Is the logcat activity level normal ?

on my BV8000, I find it very high compared to other devices.
[Android General] 82ghost82:
Anybody knows how to export/import the blocked number list?

I found a database in /data/user_de/0/com_android.providers.blockednumber/databases/blockednumbers.db

By opening it on a pc with a sqlite database reader I can see all my blocked numbers (in the "blocked" table), but copying it back on a fresh official rom doesn't work: if I enter the settings of the dialer of blocked calls it crashes.
[Android General] Sebastl:
Reason for the magisk module failure seems to be that their kernel doesnt support loop devices

Long story is linked here

Edit: Not correct. Read https://xdaforums.com/showpost.php?p=75151458&postcount=4936
[Android General] Dilip66:
I have seen a Blackview branded audio jack extender that allows you to use standard. earphones on Amazon UK, so they are now available
[Android General] jman0:
I've ordered a pair of those. I'll report back when I get them.
[Android General] jman0:
I just got the adapters. They are indeed Blaqckview branded and the quality is very good. Still a bit expensive, but they work like a charm.
[Android General] agreo:
Can you post the link, I can't find them.

Thanks.
[Android General] jman0:
https://www.amazon.es/gp/product/B078MN2GMS

That's a link from Amazon Spain, but they are available at least all over Europe. I couldn't find them on amazon.com, but you can find them at least in Frace, Italy, Germany and the UK. The link is the same, you just have to remove ".es" and use ".fr", ".it", ".de" or ".co.uk" instead
[Android General] khaqanson2018:
Can we root 20171227 Rom?

hi there,

can we root bv 8000 pro 20171227 rom with the same rooting method explained here????
[Android General] jman0:
There's now also a similar adapter on Aliexpress:

https://www.aliexpress.com/store/pr...re-4-7-Inch-1280x720/1049542_32808403757.html

It's labeled as an adapter for Ulefone Armor, but a user on 4pda already tested it on a BV8000 Pro and it works. Also, the description is quite misleading, but it looks like it's the adapter you'll need. Anyway, judging just from the photos, the adapters on Amazon look quite better in terms of build quality.

---------- Post added at 01:55 PM ---------- Previous post was at 01:49 PM ----------

The easiest way to root it is flashing the latest Magisk version from TWRP. There's still a bug that prevents Magisk from completely mounting (this just means that the modules won't work) but superuser and Magisk hide functions work well, and you won't have trouble with an outdated su binary, like when you root using SuperUser zip.

The Magisk mounting bug has already been reported and identified, and is supposed to be fixed on the next version.
[Android General] Nexmar:
Hi

I bought the phone in the thinking I could flash a stock android rom, which doesn't seem to exist for this phone, or I can't find it. So as a "try what you can" guy i have started to try to compile my own lineageos for it, with no real success as of yet. I somehow got to compile a recovery, which doesn't boot and I am generally stuck with the build environment. After a lot of trying and figuring out the basics I got to unlock the boot loader with fastboot, flashed TWRP by Jemmini, was able to export the Build.prop for the proprietary blobs and to read out the blockbased partitiontable with fdisk. I also got the lineageos repo for cm14.1 synced on as of yet 3 PCs/VMs but still haven't figured out how to compile it.

My problems start with the missing mkvendor.sh, which I would need to create the vendor strukture. make otatools also doesnt work, I got it to run by changing the make file to set the variable to true anyways but something goes wrong I think, as its more of a hack than a solution. It seems I had it in the first try but now I am also missing the unpackbootimg file.

Has anyone an idea on how to get the build environemnt setup correctly so that I can make my own lineage? I figured it would be easy as long as I manage to get the needed information and files from the phones, which I am capable of, as I can figure out ways with the shell and/or TWRP backups. it just seams that the whole build process is somewhat badly documented, as no guid I found as of yet tells how to get those missing files.

The guides i was using mainly are /2017/01/how-to-build-lineageos-rom-for-any.html on "lineageosrom com" for the how and then /works/GUIDES/AndrodDeviceTree/ on "developerswork github io" to get vendor specific stuff. (sorry seams I am not allowed to post links yet)

What i have now is on Ubuntu 16.04 and Linux Mint 17.3, I followed the first link until "Prepare the device-specific code" where I then tried to get the device-specific stuff with the second guide, with no real success.
[Android General] Bzero333:
Can't Use VPN

I'M Wondering Why I Can't Press Accept Button But Can Press Cancel Button When I Want To Use VPN App
[Android General] H4MM3RD0WN:
Hey guys I'm currently running 20170803_20170829-1811 and I'm getting a notification to upgrade. Is it really worth it to unroot and everything to upgrade? If so what steps do I need to take?
[Android General] jman0:
You can do it without the OTA upgrade system, but you have to download the whole flash package and use SP Flash Tool. You must flash everything but recovery (to keep TWRP) and userdata (to keep your apps and settings). Then, after flashing, you must boot into TWRP to root again. Just that, and it's faster than unrooting and flashing the OTA file, even if it's smaller. The whole flashing process takes less than 2 minutes. It's the download that takes more time and space.

I've been doing it like this since I got the phone. It's worth it because during this time, Blackview have addressed many issues with the phone, and the battery life, for example, has greatly improved.

You have all the flash packages on this Blackview forum thread: http://bbs.blackview.hk/viewtopic.php?f=192&t=213272
[Android General] H4MM3RD0WN:
Do I just need to flash the latest firmware? And I've used sp tool before but if you could give me an abridged version of the process I'd appreciate it
[Android General] jman0:
Once your phone is running TWRP and rooted, every time a new update is published (it needs to be via Flash Tool) you have to do the following:

1) Boot intro TWRP and do a backup, so you can go back to it if anything goes wrong.

2) Flash the update using SP Flash Tool. You must select everything except recovery, so you can keep TWRP. You can also leave userdata unselected, so you keep all your apps and configurations. Be sure to NEVER select "Format all + download" as the flash method, since you'll loose your IMEI numbers if you do so. Use "Download only" mode. In the future, when Android 8 is out, you'll probably need to select "Firmware upgrade".

3) Reboot the phone. If you didn't flash userdata partition, you won't see the setup wizard, since all your data in still there.

4) Boot into TWRP.

5) From TWRP, if you had flashed userdata partition, you can (if you want) restore the data part of the previous TWRP backup and recover your apps and setup. This includes the Google account and even the finger prints you had registered before.

6) Flash Magisk or SuperSu zip from TWRP, in order to root the phone again. I suggest using Magisk, because it works better.

7) Reboot and you'll have the latest version installed

Before using this method, I tried to unroot the phone to get an OTA file flashed, but the upgrade system kept saying my phone was rooted, even after flashing the stock recovery again. So now I stick to the process above, which takes less than 5 minutes or so (except the download, which will obviously take more time, since the firmware file is way bigger).
[Android General] H4MM3RD0WN:
Ok I thought i read somewhere earlier in the thread that past a certain point in the updates userdata partition had to be flashed. I tried using magisk before but it just instructed me to download the manager from the playstore but it had been removed.
[Android General] jman0:
What you say about userdata is true, but you can always try first, and if you feel that the phone is not working as smoothly as you expect it to, you can always factory reset later.

Always get Magisk from the official link here on xda.

Download links are always on the official thread: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Android General] Azmal Huda:
Issue with Bluetooth

Hi, Got a bv8000 pro running on Android 7. It has been releasing the bluetooth connectivity frequently and my smartwatch fails to connect back. My other phones are working fine. Is this issue coming from bluetooth module or Android 7 ? Any suggestion around how to recover?
[Android General] jman0:
Just make sure you're using the latest firmware version. If not, you'll need to upgrade. You can find all the info on the official Blackview forums: http://bbs.blackview.hk/viewforum.php?f=189
[Android General] poganytamas:
Two versions came out since this issue has been identified (15.3 and 15.4), still not fixed :(
[Android General] Sebastl:
Feel free to contribute. Did you ask Blackview-Admin if he has has any hints from the developers for example ?

You could also tell me if you have got any AEE Errors in your magisk-debug.log
[Android General] jman0:
I remember that Magisk developers stated some time ago that the issue would be fixed on the next major release (I guess 16.0).
[Android General] Sebastl:
Nope. Because the real cause is still unknown
[Android General] H4MM3RD0WN:
After upgrading to the latest firmware I've been getting a lot of device lag most noticeably using the chrome internet browser but other times too, to the point where apps force close or my device restarts and sometimes it just randomly restarts. Anyone else getting this issue?
[Android General] poganytamas:
I experience random reboots. 1-2 / week
[Android General] serg2327:
firmware 20180124_Lite_ROM

description:cleared of many system applications,full deodex, integrated ROOT-magisk , several modifications have been integrated.

download and read the details here: {Mod edit: Link to 4pda removed! Oswald Boelcke, Senior Moderator}

on the forum I go very rarely on this all the questions ask in private messages or on the forum 4pda
[Android General] bakancs:
Yeah, but I can't read it. It is Russian.

Tapatalkkal küldve az én BV8000Pro eszközömről
[Android General] xJ$:
Hi Serg,

I have a serious pblm with my handset. I cdn't enter even recovery mode. The handset is stuck at "Blackview & powered by android " logo . The red led is blinking without any pause. I tried all methods (SP flash / SP Multiport). All completing successfully but the mobile is not switching ON. Whenever putting in charge ,just the logo appears & then disappears every few mins. Nothing else happens.

Will this ROM be able to solve the issue?

Pls help !!

---------- Post added at 03:28 PM ---------- Previous post was at 03:23 PM ----------

Hi Sir,

I have a serious pblm with my handset. I cdn't enter even recovery mode. The handset is stuck at "Blackview & powered by android " logo . The red led is blinking without any pause. I tried all methods (SP flash / SP Multiport). All completing successfully but the mobile is not switching ON. Whenever putting in charge ,just the logo appears & then disappears every few mins. Nothing else happens.

Will this ROM be able to solve the issue?

Pls help !!

---------- Post added at 03:29 PM ---------- Previous post was at 03:28 PM ----------

Hi Sir,

I have a serious pblm with my handset. I cdn't enter even recovery mode. The handset is stuck at "Blackview & powered by android " logo . The red led is blinking without any pause. I tried all methods (SP flash / SP Multiport). All completing successfully but the mobile is not switching ON. Whenever putting in charge ,just the logo appears & then disappears every few mins. Nothing else happens.

Pls help !!

---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------

what's the solution for that?
[Android General] poganytamas:
Just do a full rom flash. Turn off the phone : hold the power button for 10 seconds. Download full rom, select everything in SP flash tool, hit download. Connect the phone to PC while pressing the volume up button. Release volume up when you see the progressbar moving in SP flash tool. Start phone when flash complete.
[Android General] Alberto96:
[MENTION=6055362]xJ$[/MENTION] : Hardware Problem = physical damage. There is no solution for that.

Still, be sure that it isn't a software issue first.
[Android General] justjager:
Mine did the same thing.... Some apps work but most have to be installed 2x

Like you I get the same results and some do okay others like adAway (that I've loved for years) won't write to the system and won't work. Some have to be installed 2x and then may not work anyway...
[Android General] xJ$:
Pls share link for unofficial / custom ROM for Blackview BV 8000 Pro