FORUMS
Remove All Ads from XDA

Xiaomi Black Shark Support/MEGATHREAD

238 posts
Thanks Meter: 81
 
Post Reply Email Thread
23rd April 2019, 03:12 AM |#11  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by JengaMasterG

Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?

Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.

first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2019-04-23-09-08-42-314_lockscreen.jpg
Views:	188
Size:	164.6 KB
ID:	4747529   Click image for larger version

Name:	Screenshot_2019-04-23-09-09-01-637_com.blackshark.ota.png
Views:	190
Size:	75.9 KB
ID:	4747530  
 
 
23rd April 2019, 06:06 AM |#12  
JengaMasterG's Avatar
OP Senior Member
Flag Devon
Thanks Meter: 81
 
Donate to Me
More
Quote:
Originally Posted by khususgw

first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks

Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.
23rd April 2019, 08:40 AM |#13  
Junior Member
Thanks Meter: 0
 
More
Reply:
Xiaomi Black Shark support are the thing which people need to know now a days world is evolving and things are changing rapidly.
23rd April 2019, 10:18 AM |#14  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by JengaMasterG

Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.

thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist

but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update

thanks
23rd April 2019, 10:56 AM |#15  
JengaMasterG's Avatar
OP Senior Member
Flag Devon
Thanks Meter: 81
 
Donate to Me
More
Quote:
Originally Posted by khususgw

thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist

but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update

thanks

Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.
23rd April 2019, 11:19 AM |#16  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by JengaMasterG

Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.

okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a
23rd April 2019, 10:24 PM |#17  
JengaMasterG's Avatar
OP Senior Member
Flag Devon
Thanks Meter: 81
 
Donate to Me
More
Quote:
Originally Posted by khususgw

okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a

Yeah you can do it that way!
24th April 2019, 04:46 PM |#18  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by JengaMasterG

Yeah you can do it that way!

hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.
24th April 2019, 05:01 PM |#19  
JengaMasterG's Avatar
OP Senior Member
Flag Devon
Thanks Meter: 81
 
Donate to Me
More
Quote:
Originally Posted by khususgw

hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.

Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.
24th April 2019, 10:13 PM |#20  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by JengaMasterG

Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.

after i try flash from scratch
and using old vendor b
still i cant do the OTA update
25th April 2019, 05:53 AM |#21  
JengaMasterG's Avatar
OP Senior Member
Flag Devon
Thanks Meter: 81
 
Donate to Me
More
Quote:
Originally Posted by khususgw

after i try flash from scratch
and using old vendor b
still i cant do the OTA update

Please try using the slot a files provided by me. They are in the first post in the thread here.
Post Reply Subscribe to Thread

Tags
xiaomi-black-shark

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes