yashsingh1/xdaforums huggingface dataset:
[LineageOS Questions & Answers] tomhanman:
alecxs, thanks for the suggestion. It wasn't that I wanted to hide the message, but to return my phone to a state where Google pay would work. Which I have done now thanks to Serge and his compatriots on pda4u. I am running 8.1 again, but I really don't care what number it says, what is important to me is that for the first time since I got this phone over two years ago everything is working (except maybe some battery stats but as I have no battery usage probs it doesn't concern me). Gpay works, autostart apps works, camera works well, Bluetooth also, and background apps work, so it's just like a real smartphone! I screwed up my nvram along the way, even though I backed it up (so I thought), and that has probably caused me most headaches, there may be Mac id problems hiding, but so far they're not troubling me.

I'll have to get on with my life now that I don't have to waste it flashing and reflashing a phone!

Regards to all.
[LineageOS Questions & Answers] serg2327:
BlackView BV9600 Pro + LineageOS?

I can’t understand why this topic has such a name??

For example, today I installed LineageOS_17.1 firmware on my bv9600Pro

Surprisingly, almost everything works ... but I honestly don't like LineageOS

Now there are a lot of lineageOS-based firmware updates that are much more interesting!

For example Havoc-OS 3.6 it’s much more interesting and also, without problems, it runs on bv9600Pro

PS/

Ссылка:
[LineageOS Questions & Answers] marcelodub:
Please.

how was it successful ???
[LineageOS Questions & Answers] joe tigercat:
Serge, I tried havoc is, and everything works well except video recording. Does this work for you?
[LineageOS Questions & Answers] fredbzh:
Hello i need help installing the rom on my BV9600 Pro. I am 8.1 I installed TWRP and the phone is rooted. Unable to install XXXX.IMG.XZ file; TRWP does not see the file. I checked out this file. I install the "System" folder. This is the only folder I can install. The phone restarts and gets stuck on the Blackwiev logo. I left it overnight. I did a fresh install and now it is stuck on "Fastboot". What is my mistake?

Bonjour

j'ai besoin d'aide pour installer la rom sur mon BV9600 Pro.

Je suis 8,1

J'ai installé TWRP et le téléphone est rooté.

Impossible d'installer le fichier XXXX.IMG.XZ;

TRWP ne voit pas le fichier.

J'ai extrait ce dossier.

J'installe le dossier "System".

C'est le seul dossier que je peux installer.

Le téléphone redémarre et reste bloqué sur le logo Blackwiev.

Je l'ai laissé pendant la nuit.

J'ai fait une nouvelle installation et maintenant elle est bloquée sur "Fastboot".

Quelle est mon erreur?
[LineageOS Questions & Answers] Rukkyakakporo:
Hello there please I'm having issues connecting my Blackview BV9600b pro to my laptop and have searched the internet for drivers but failed. Please can you share with me link to get actually drivers
[LineageOS Questions & Answers] Rukkyakakporo:
Hello please I need help, I followed this exact process with same files on same phone type and everything showed successful till I tried booting to recovery from fastboot and twice I tried it out showed

Orange State

Your devices has been unlocked and can't be trusted

Your devices will boot in 5 seconds

Then it boot normally but refusing me access to the custom recovery.

Please any help
[LineageOS Questions & Answers] alecxs:
boot straight into recovery right after flashing, otherwise twrp is overwritten with stock recovery and twrp must be flashed again
[LineageOS Questions & Answers] Rukkyakakporo:
Yes, at first after flashing custom recovery I fastboot to recovery and that was the first time it showed me the orange mode.

Please I need help, what can I do?
[LineageOS Questions & Answers] alecxs:
orange state is just a message about your bootloader is unlocked, which is desired. That message is absolutely fine and nothing to worry about.

On my phone that "5 seconds" is actually taken 2-3 minutes or so, after this my phone boots normal into android or recovery, depending on which mode i selected with Volume key.

after flashing recovery, press and keep holding Volume Up while rebooting your phone with fastboot reboot
[LineageOS Questions & Answers] Rukkyakakporo:
Though have tried that before, but at thy words I'll try reflashing the custom recovery and booting to recovery from the fastboot again now
[LineageOS Questions & Answers] Rukkyakakporo:
Trying the entire process again from flashing the recovery, but fastboot devices refuse to identify my device and when I tried WwR MTK (2.51 version) it saw the phone but showed

Device is in sleep mode

Need to wake it up!!!

Meanwhile my phone is on with me and not asleep
[LineageOS Questions & Answers] Rukkyakakporo:
Have been able to get my pc to see my phone, according to Hovatek I just needed to revoke usb debugging authorizations
[LineageOS Questions & Answers] Rukkyakakporo:
Hello pls is your phone same with mine?

Cause mine refuse to boot into recovery
[LineageOS Questions & Answers] Rukkyakakporo:
Hello, please i cant stil boot to the custom recovery, when i try it goes to Orange Mode then boot normally so I cant flash in the bo verity, supersu or magisk. Is there a way to get the files in img fastbbot to flash them on the device or any way to bypass the Orange Mode to allow the phone boot to recovery?
[LineageOS Questions & Answers] Rukkyakakporo:
Hello please I'm having TWRP loop issue.

Blackview bv9600pro Rooted with Magisk patched boot.img

I just wanted to factory reset before backing up and now phone's stuck, please help.

Can I copy the stock ROM which I had downloaded to SDcard and use TWRP to install it or any other custom ROM?

Please I'll still like to keep the root and TWRP as I have been striving to get these for works with my phone barely staying connected to PC with me not having one close by.
[LineageOS Questions & Answers] Sebalex2021:
Well thanks to this thread i was now able to install lineage os 17.1 on the first revision of bv9600pro.

Used ADB & fastboot tool via linux mint 20. first i tried it with the ADB & fastboot tools on windows 7 but failed to get a reaction on the smartphone after selecting fastboot mode...

Followd instructions and link on first page here up to installing magisk and the decrypt tool.. Will send a screenshot of the versions i used on request from the laptop screen.. Writting this now on the bv9600pro with lineage os 17.1 on it.

Tried the suggested havov os 3.6 from the quoted post of serg2327 ...after install i just got stuck in the dark screen on boot with the "fastboot mode..." On bottom left..

Then i when back to twrp and formated data, dalvic, cache and installed the lineage os 17.1 and afterwards after reboot into recovery agaon g apps nano ...

Now lineage os 17.1 is running. what i recognices is the following:

No loud speaker sound what so ever.... Without turning on loud i can speak with people on the phone..

Youtube does not work in the browser but the app works..

I made a backup before rooting of everything i could find and safed it on the laptop by copying it from the micro sd card.

Also the device info in nearly empty. If the reader of this needs more information just let me know..

Hope i can solve some of this.. I did not put a simcard yet in the bv9600pro since flashing if that has any effect on the about phone window..
[LineageOS Questions & Answers] Rukkyakakporo:
Guess it most be Linux PC then cause when tried mine fastboot said the partition size is different.
[LineageOS Questions & Answers] Sebalex2021:
Well i dont understand how that answers any of the questions i put in the room..

From my point of few it seems much easier to get such things done with for example linux mint (based on ubuntu) .. In the core both android and mint are based on linux ..i did not search for a driver this time but maybe laoded it in the past and just forgot..

Meanwhile i got whatsapp app, paypal app and my google account back to run on this bv9600pro

...some crashes in whatsapp but thats nothing new with the damn blackview bv9600pro.. That thing is tough in ruggednes but not fully developed in software.. The factory 8.1 android is a catastrophy when it comes to design and usebility ...and the app icons where nearly the main reason for me to switch..also functionality seems more on with android 9 or 10..

Still audio on loud speaker does not work at all. Any suggestions on how to get that running.. Maybe serg has an answer.. I have backed up all from the 8.1 android.. So i dont know how but i could overwrite some data of the custom rom to get audio running again or not.. I remember data in encrypted..dont know how to "repair" the functionality of the speaker.. I read somewhere that it needs to be overwritten to get some parts of the original software back..also regarding that parts that contain the original imei codes and other info that is black in my current state of the phone..

And skillful people around that can send me a guide..sure it may help others that have similar issues..

How about flashing havoc os 4.~ ...is a version out there that is fully compatible with the 8.1 android version of the bv9600pro?

Also in this threat i found that people describe a lot to flash magisk after flashing the custom rom.. I did that the other way around.. Like first i flashed magisk...the the decrypt zip and after that the rom and the gapps... So why to flash magisk after the rom?
[LineageOS Questions & Answers] joe tigercat:
can someone provide insight with a problem. i once had havoc is on my 9600 pro (p60 version), but could not hget 4g and volte to work with it, so went back to stock. i now have a second 9600 pro (p70 version), and am trying again.

so i flash stock rom with sp flash tools. boot to unlock the bootloader (have the red letter in right corner for some reason). go to fastboot unlock bootloader, unlock flashing, flash recovery, boot to recovery, flash havoc 3.8 arm 64 AB gapps. flash magisk. wipe, and reboot. every single time it boots back to fastboot (says factory on phone. ) i've tried a couple different roms. same result. after flashing, it boots to fastboot.

any ideas?
[LineageOS Questions & Answers] joe tigercat:
ok, so serge's 'fix start' patch might have done the trick
[LineageOS Questions & Answers] joe tigercat:
Serge, thanks for your hard work on this phone. I've enjoyed your 4pda.rom, as well as havoc os for the 9600. We're you able to get volte working for any GSI Rom? Seems almost impossible on MediaTek chips
[LineageOS Questions & Answers] 77777777777777:
hi

I have blackview A90 same os , but can't find Nvram folder in data ?

pleas help, thanks
[LineageOS Questions & Answers] amhossain:
Yes
[LineageOS Questions & Answers] naseera422:
I am install already all twrp and magisk work twrp fine but i need custom rom stable please link best custom rom who support bv9600pro
[LineageOS Questions & Answers] naseera422:
I need bv9600pro custom rom which is the best for bv9600oro.

i like miui rom if possible for bvp600pro
[Samsung Galaxy S9+ Questions & Answers] netengineer:
Does anyone have an idea when the unlocked US models will be getting the Pie update? I'm on Sprint if that makes a difference. Kind of sucks that everyone is getting the updates but unlocked phones are not.
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
Sprint has already rolled out the carrier locked update. The u1 should be rolling out in the next day or two.

---------- Post added at 03:17 AM ---------- Previous post was at 03:16 AM ----------

I'm in the same boat. I'm with an mnvo and I have to stay on u1 firmware to retain VoLTE as they block simultaneous calls and data on BYOP plans.
[Samsung Galaxy S9+ Questions & Answers] Hangoverr:
For some reason u1 stayed on ark5 for me with Nov 1 patch. I have att phone where I loaded u1 before. No further updates. I saw posts that u1 has dec patch. Am I missing something?

I'm also waiting for ota to see when it hits my phone. Not in a hurry.
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
That's because the AT&T devices are locked. You can flash u1 firmware all day long, but you can't change the locked CSC (where the device looks for software updates). The phone is looking for u1 firmware from a carrier that doesn't provide firmware for the U1. If the device is paid off, ask AT&T to remove the Sim lock on the phone. You maybe able to change CSC forcibly, but I think you may trip the Knox counter.
[Samsung Galaxy S9+ Questions & Answers] Hangoverr:
It was already unlocked which is how I was using it on T-Mobile. I did a weird thing in December. I updated to android pie beta and due to some issues with apps I tried reverting back to Oreo. But I did multiple tries using odin and didn't work. Then I read through online and found that to go from pie beta to Oreo we have to downgrade using samsung switch as bootloader is different. That's when things might have been messed up. Any suggestions or thoughts on how I can get it back to pure u1 with updates?

Attached my current software details
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
I've never hear of needing to use smart switch to jump bootloaders as I don't think that's even possible on a locked bootloader. Once the bootloader changes, there is no going back.

So was your phone originally a U1 device or a U? What firmware are you currently on?

---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------

I've never hear of needing to use smart switch to jump bootloaders as I don't think that's even possible on a locked bootloader. Once the bootloader changes, there is no going back.

So was your phone originally a U1 device or a U? What firmware are you currently on?

Edit: I see your screenshot. What is sticking out at me is your CSC. I see ATT/ATT/TMB. I'm not seeing XAA like an unlocked phone would have. If I'm not mistaken, once you attach your phone to ATT or TMB, you essentially lock your CSC to their network.

When you flashed back to u1 firmware from the pie beta, you didn't use Odin, correct? If you didn't use Odin. I don't think smart switch will reset your CSC to XAA.

My best advice would be to download the U1 ARL1 Odin firmware files and flash the CSC (Not HOME_CSC). You will have to wipe your phone, but that will put you to the latest U1 firmware and back to unlocked CSC and will point it in the right direction for future OTA updates.

---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------

Just an FYI, I flashed my phone from the pie beta to the U1 ARL1 odin file with no issues. Today I flashed my other s9 plus from brk2 (carrier) to u1 and had ODIN give me some fuss using the same method/firmware I used on my other phone. If Odin is failing, put the phone in download mode and connect it to ODIN, loaded and ready to flash... Hold power, volume down, and bixby until the phone reboots back into download mode, ODIN will connect again, unplug the phone and plug it back in, THEN flash. It's an odd sequence, but it works.
[Samsung Galaxy S9+ Questions & Answers] Hangoverr:
Thank you for detailed explanation and questions.

My phone is originally att which will be u device. If you remember or heard of it, back in April we had att phones in Samsung site for 650$ and that's where I bought it. I was never on att Network so I submitted for unlock and meanwhile installed u1 from xda

then I unlocked and used tmobile sim. It always got ota as expected. In November I signed up for Samsung pie beta and then did an ota to pie.

When I wanted to revert back, I downloaded latest u1 and installed through odin it didn't boot up. Then I tried multiple versions and didn't work. I again installed pie beta using odin from xda. Then I was able to boot it up again. That's when reading online and xda I think but don't recall exactly where I got suggestion to use smart switch to downgrade to Oreo. I think it took me to att version Oreo as my imei is for att phone. Then I again downloaded u1 from xda and installed.

Hopefully I was clear in explaining what I did. I can try arl1 and install csc. I'm ok with user data loss as I don't really have many apps or data. But can I install csc for my current ark5 and see if that gives me ota for arl1? I'm assuming arl1 is latest Oreo for s9 plus u1.

Thanks for your help.
[Samsung Galaxy S9+ Questions & Answers] netengineer:
Thanks for all the feedback. I am on Sprint ad I have the U1. Do I have to worry about not being able to get the Pie update? I am on the Dec security patch so it does update.
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
You should get the official unlocked pie update from Samsung once it's released. If you were to flash the g965u firnware with Sprint userdata, you would receive the pie official w/carrier bloat that is currently being pushed right now.
[Samsung Galaxy S9+ Questions & Answers] netengineer:
So... Should I just wait or flash g656u? I can wait, but getting a whole new build is like Christmas for me. Lol

Thanks for your reply.
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
I believe when the CSC is changed, it must be pushed with the bootloader, AP and everything else when using ODIN. It still wouldn't hurt to push the ARL1 firmware w/CSC to it and wait to hear when the official unlocked pie is available via OTA to make sure you're able to get the OTA push. And yes, ARL1 is the unlocked U1 final Oreo fw.

Also, when you flashed to the pie beta, were you using the official z builds or the leaked "c" carrier builds? That might explain why you had issues flashing back

---------- Post added at 04:22 PM ---------- Previous post was at 04:08 PM ----------

Personally, I would wait. The unlocked build will be pushed in the next day or two once the majority of the carriers have pushed it. The only benefit you would gain from going ahead and flashing it would be to get carrier specific features like WiFi calling, but that also comes with the carrier bloat. Most carrier specific apps can be had from the play store anyway.
[Samsung Galaxy S9+ Questions & Answers] Hangoverr:
First pie beta was ota. Second one I believe it is c but don't recall exactly. I will try flashing arl1 and will see how it goes. Any suggestions on where to get it?
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
Hangoverr,

You maybe right about smart switch reverting you back to the u firmware based on your imei as it was originally a carrier device. From that point forward, if you flashed over to the u1 firmware and used CSC_Home to preserve userdata, that would explain the lack of OTA pushes as it's still tied to ATT/TMB CSC. Did you happen to flash home instead of csc when switching back over to u1 firmware?
[Samsung Galaxy S9+ Questions & Answers] Hangoverr:
I might have flashed home. I will look over xda for arl1. Would you mind giving me the link if you already have it?
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
https://xdaforums.com/galaxy-s9-plus/how-to/sm-g965u-g965usqs3ari6-sm-g965u1-t3853429

Use the latest U1 file in that root folder of androidfilehost and use the patched odin mentioned in the original post to ignore the hash check. Remember if it fails to flash, hold power, volume down, and bixby until it resets into download mode again, Odin connects again, unplug, and replug the phone back in, once Odin confirms connection, flash.
[Samsung Galaxy S9+ Questions & Answers] Hangoverr:
thank you .. appreciate your help. i will try that out today.
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
Here is what I'm talking about
[Samsung Galaxy S9+ Questions & Answers] YrrchSebor:
Looking at your screenshot I think you might possibly be okay. Looks like you are on U1 ARK5 with a T-Mobile SIM? I have the exact same thing(except my phone was originally Verizon), and I was not getting the OTA for ARL1 either, so I Odin'd it. I later realized I don't think the OTA is even available for my phone configuration.... Check here on the phone info app, even though I am now on ARL1, the latest version is still showing as ARK5. I don't really understand how this all works, but also if you search U1 firmwares on SAMMOBILE labeled with product code TMO, it will also shown you ARK5 as the latest. If you select a different carrier in the drop-down menu, it will give ARL1 as the latest. I don't really understand how carriers are associated with U1 firmwares, but that is what I am seeing on SAMMOBILE.
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
The u1 firmware is still pushed OTA via your carrier. When you check for the latest update, your phone doesn't check Samsung's servers directly... Your phone queries your carrier. Whether your carrier is pushing Samsung's unlocked firmware updates or not is a different story. If your phone is saying you're up to date and you know that there is a more recent update, you will have to use smart switch or kies to directly contact Samsung's firmware servers, which may or may not be releasing to your time zone/region at that time.

Otherwise, you will have to wait for your carrier to push the OTA. Generally, carriers can release the unlocked firmware immediately as it doesn't require any additional modifications on their end before pushing it to Samsung's unlocked phones, but sometimes they get lazy or run into issues pushing it. After all, the carriers aren't making money off subsidizing unlocked phones, so why hurry to push firmware to them. Know what I mean?
[Samsung Galaxy S9+ Questions & Answers] YrrchSebor:
Thanks for the explanation ? That explains the behavior I have seen, and I guess that's what those carrier designations mean on SAMMOBILE when I look for U1 firmwares. T-Mobile seems to be the slow one! I find it convenient enough just to Odin the ones that come out with XAA code.
[Samsung Galaxy S9+ Questions & Answers] Hangoverr:
i have same CSC as yours. So if i follow the instructions by hyperblu and get to XAA csc then i might see OTA. I have to try that.

---------- Post added at 11:33 AM ---------- Previous post was at 11:29 AM ----------

do you mind posting your phone firmware info?
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
The XAA (US Region Unlocked) will just ensure your phone will query the carrier's server specifically for the unlocked OTA pushes. If your CSC is TMB,ATT,VZW or anything else it will ask specifically for "U" pushes instead of U1 and constantly be denied because you're on U1 firmware.

However, even XAA CSC will not guarantee timely updates, it will guarantee the right updates the server will actually push to your phone. Like I said, your OTA updates will only come as fast as your carrier will push them. If you want official updates as soon as they hit the servers, use smart switch or kies. Otherwise, it boils down to how fast your carrier pushes it... Obviously, TMO skipped an entire security patch for the u1 ARL1 update... Lol
[Samsung Galaxy S9+ Questions & Answers] Hangoverr:
aha.. makes sense thanks. so i guess if i use smart switch now to do the update instead of flashing arl1, it might work? that should update my csc too?

dumb question.. it doesn't work like that i guess.
[Samsung Galaxy S9+ Questions & Answers] YrrchSebor:
Yep, TMO skipped it lol. While we're at it here, do you know why XAA doesn't show up in the CSC. For example I have flashed only U1 XAA, but my CSC is TMO/TMO/VZW. I understand the last one just specifies the original code of the device. I assume the first two represent the U1 firmware adapting to my SIM card/carrier? No sign of XAA tho
[Samsung Galaxy S9+ Questions & Answers] hyperblu:
The XAA CSC, in and of itself, is before it ties to a carrier. If you were to remove the Sim and factory reset, it would revert back to XAA/XAA/VZW, but I would assume it's possible to somehow accidentally flash a non XAA CSC to U1 firmware, especially if using carrier leaked pie beta builds or not being familiar with the newer flashing methods.
[Samsung Galaxy S9+ Questions & Answers] YrrchSebor:
Gotcha, thanks for the lesson!
[Samsung Galaxy S9+ Questions & Answers] KewlRobD:
I purchased my S9+ unlocked directly from Samsung and use it with an AT&T sim card. My CSC reads ATT/ATT/XAA but I have not been able to get the update. Every time I check for update it tells me I have the latest updates installed.