yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52 4G] MobAndro:
Hello,

You can install Phone INFO ★SAM★ 3.8.5 to see the result ;)

Phone INFO ★SAM★ 3.8.5 APK Download by vndnguyen - APKMirror

Phone INFO ★SAM★ 3.8.5 APK Download by vndnguyen - APKMirror Free and safe Android APK downloads

www.apkmirror.com

Phone INFO pour Android - Téléchargez l'APK

Téléchargez l'APK 3.8.5 de Phone INFO pour Android. All-in-One Info et outils pour les appareils Samsung.

apkpure.com
[Samsung Galaxy A52 4G] ralanar:
Ok, did a bit more testing, pretty sure this is a problem with the LineageOS rom.

Re-flashed the latest stock firmware for an SM-A525M from sammobile.com (used the brazil firmware), and Settings->About Phone now reports the model as SM-A525M/DS, which is correct. Baseband firmware version did not change, nor did I expect it to.

Tested each sim individually in each slot, then both slots together, then swapped sims between slots. Audio worked in every voice call, regardless of which sim was used for the call or which sim was where.

Then I re-flashed LineageOS as per the instructions.

Starting with the VBMeta_Disabled image, then a recovery image (Used the LineageOS recovery from that thread this time, used TWRP from the TWRP website on the previous attempt), then LineageOS, MindTheGApps, and Magisk.

After re-booting Lineage, the phone once again reports it's model as SM-A525F under Settings->About Phone, and neither sim has working in-call audio when in slot 2, regardless of whether the other slot has a sim in it.

I'll add a post to the thread linked above to report the problem, and crosslink to this thread for reference.

For the moment, I've put the sim cards back in the phones I pulled them from and shelved this A52. I'll try again when a new release is available, and see what happens.

Thank you Flyos and Ryzen5950 for your assistance!
[Samsung Galaxy A52 4G] zeromant:
Do you happen to know the exact build BEFORE you flashed a custom firmware?
[Samsung Galaxy A52 4G] embryo1:
https://xdaforums.com/t/unofficial-rom-12-1-encryption-lineageos-19-1-for-a52-4g-and-a72.4364519/

Bugs

Fingerprint sensor on A72

No audio in calls with second SIM card
[Android Q&A, Help & Troubleshooting] jackbalo:
How can i root my xiaomi redmi note 114g
[Android Q&A, Help & Troubleshooting] Terrence5:
Did you find ?
[Android Q&A, Help & Troubleshooting] 4jean:
Please can someone help out. Need the root guide for RN11 Android 11 - 2201117TG
[Android Q&A, Help & Troubleshooting] joke19:
Why you don't look and or ask here

Redmi Note 11 (spes/spesn)

The Redmi Note 11 is a 6.43" phone with a 1080x2400 resolution display. The Qualcomm SM6225 Snapdragon 680 4G chipset is paired with 4/6GB of RAM and 64/128GB of storage. The main camera is 50+8+2+2MP and the selfie camera is 13MP. The battery has a 5000mAh capacity.

xdaforums.com
[Android Q&A, Help & Troubleshooting] Terrence5:
Because it's RN114G which is not really a Redmi note 11, but more like a Redmi 10.
[Android Q&A, Help & Troubleshooting] 4jean:
Which is the real RN11 is it the 5g pro
[Android Q&A, Help & Troubleshooting] 4jean:
OK I will
[Android Q&A, Help & Troubleshooting] zuhaibsarwar:
Anyone need rooting guide ?
[Android Q&A, Help & Troubleshooting] 4jean:
Yes I need rooting guide magisk preferred for RN11 spes
[Android Q&A, Help & Troubleshooting] zuhaibsarwar:
Follow this guide

https://xdaforums.com/t/root-redmi-note-11-pro-viva-vida.4470727/
[Android Q&A, Help & Troubleshooting] 4jean:
OK thanks
[Android Q&A, Help & Troubleshooting] zuhaibsarwar:
Welcome
[Android Q&A, Help & Troubleshooting] greenlight093:
Please share download links or update links.
[Android Q&A, Help & Troubleshooting] superuserblackview:
I got bootloader unlocked... But tried with different adb commands aswell as shell commands and fastboot commands...

No luck... How do i get it rooted and how can i find TWRP?
[Android Q&A, Help & Troubleshooting] Denverfan9:
ever figure it out?
[Android Q&A, Help & Troubleshooting] Khaledosman:
I also need a way to root this model, although I searched a lot for the software for this phone and did not find anything for it
[Android Q&A, Help & Troubleshooting] Khaledosman:
How did you unlock the bootloader can you give me the method please
[Android Q&A, Help & Troubleshooting] RASTAVIPER:
I got it also recently and trying to find ways to root it

Another annoying thing is that after every sleep the tablet wakes up and changes my selected keyboard to the stock one.

So I need to go manually each time and select it from settings.
[Android Q&A, Help & Troubleshooting] dixiewebmail@gmail.com:
There is little or no information on the BV Tab 11 tablet, too new perhaps? What I have realised having just bought one here in the UK is that there is only a very small community - niche in fact. The specs are high and build seems good, but early days perhaps for modders with rooting and new ROMs in mind. With the likelihood of no Android upgrades or Security updates ever, having the ability to install different ROMs would be the only way to go in the future. Fingers crossed.
[Android Q&A, Help & Troubleshooting] RASTAVIPER:
This tablet won't get any updates from the official company and I think the same will happen with the mod community: no-one will deal with it.

So I wouldn't expect any custom roms or root options any time soon.
[Android Q&A, Help & Troubleshooting] Steve98124:
Any luck on this?

I don't have this tablet but have been looking to buy one if I can verify that root is possible.

I've not found any reports of Blackview Tab 11 getting root but it should be possible.

Others have rooted Teclast T40 and AlldoCube 40 which are nearly identical.

This link provides a guide that might work.

How to patch boot image and root any Spreadtrum device using Magisk Manager

www.getdroidtips.com

It uses SPD Flash tool which is for Spreadtrum (aka Unisoc) processors.

You can get the stock ROM and SPD Flash Tool here:

Download Blackview Stock ROM for all models (Latest Firmware)

Download the latest Blackview Stock ROM Firmware (Flash File) for all the available Blackview smartphones, feature phones, and tablets.

androidmtk.com

As for TWRP you might be able to find some clues in the Alldocube 40 forum.

https://xdaforums.com/t/alldocube-i...d-tablet-with-some-minor-compromises.4212541/
[Android Q&A, Help & Troubleshooting] Steve98124:
Global Rom!!

DK_Tab11_NEU_M60_T618_New_SDK_ID3434_20220705_V1.0.rar

Link

Background:

I have done extensive web searching and initially was only able to find the Russian Rom which I have loaded onto my Tab 11 using the SPD tools referenced in my previous post.

The Russian ROM Tab11_RUU_M60_V1.0_22070702V01 is currently linked on a few sites. Here are two for referece naijarom and {Mod edit: Link to paid services website removed. Oswald Boelcke, Senior Moderator}

I also ran across a P30 version but I assume M60 is more recent.

The Russian ROM can be set up to use English but that's probably not a real solution for some of us.

I believe that it (the RUU Russian Rom) could be rooted but I have not tried yet.

The SPD Tool requires that you have the base firmware on your device and that you also have a .pac file that you can load into the SPD tool. I tried to make a backup using the SPD Research Tool of the firmware that came with my device (which of coarse did not match the RUU firmware) and it bricked. I got a bootloop that would start very briefly, buzz then start over and I couldn't turn it off.

To get it out of the bootloop I was able to use the research tool to get the device to a powered off state and from there I could load another firmware with the SPD Upgrade Tool. But I only had the RUU version so that's what I did.

I reached out on the sites that had the RUU firmware and asked for the Global version NEU. So, the NEU version may appear on some of those sites at some point but I haven't seen it out there yet .

I also reached out to the ebay seller where I got my tab 11 "blackview_global_store" and got a reply with a link to the NEU firmware that is linked above. 5 stars for vendor support for them!

So far I can verify that the file when extracted is a .pac file which the SPD tool needs. I'll be loading it onto my tab in a day or two.

It's a 2gb file that unpacks to a 5gb file.

I think this is the last missing piece that I needed to root the Tab 11.

With the correct frimware, SPD tool and Magisk we should be able to get this thing rooted.
[Android Q&A, Help & Troubleshooting] Steve98124:
Root successful!!

This tablet can be rooted with the Magisk method but the patched boot image and vbmeta image must be modified and signed. The links below are a collection of the information I used.

Bootloader unlocked using Hovatek guide

Extracting firmware guide with spd provided by droidwin

Guide to SPD tools provided by Romprovider and spdflashtool

extracting and creating keys provided by Hovatek

Simple tool to extract public keys from vbmeta.imag by ProKn1fe

Guide to create a custom signed vbmeta.img provided by Hovatek

Guide to avbtool to sign image with private key provided by Hovatek

Root method was Magisk based on guide provided by getdroidtips using signed boot.img and custom signed vbmeta.img

The root process is very similar to the one discussed on the Teclast T40 forum.

Aldocube iPlay 40 is also very similar with some useful information.

There is no TWRP for any of the Unisoc T618 tablets as far as I can tell.

If anyone has any additional info on TWRP for Blackview Tab 11 or other T618 tabs please share.
[Android Q&A, Help & Troubleshooting] loresa8979:
Wow, this is GREAT work what you managed to achieve there, congrats. Do you think this would also work for Blackview Tab13 - it looks to have quite similar specs.
[Android Q&A, Help & Troubleshooting] Steve98124:
Tab 13 does have some significant differences. It comes with Android 12 and it has a Mediatek processor vs. the Tab 11 which comes with Android 11 and a Unisoc processor. So there could be some differences to the process. I think that Mediatek uses a different tool for flashing firmware than Unisoc and android 12 may drive some differences also.

From what I've read it seems that most Mediatek devices can be rooted. I've also seen no evidence that the Chinese devices are locked down in any way like Samsung or some other. It seems that it's just a matter of figuring out how to do it.

Tab 11 with the Unisoc processor uses the SPD tools for flashing. Mediatek has something similar and I assume you have to use that one.

Using the Unisoc SPD tools I had to have the stock firmware (.pac file) to use the flash tool. I was able to get that from Blackview_global_store (ebay). They might be able to help you out as well. I was very surprised that they were able to provide the stock firmware file but happy they did.
[Android Q&A, Help & Troubleshooting] Steve98124:
Edit;

Tab 13 Rom seems to be available.

It is the NEU version which I believe is the global version of the ROM.

Blackview Tab 13 Stock ROM Firmware (Flash File)

Download Blackview Tab 13 Stock ROM Firmware (Flash File) without any password for Free. We also provide Stock ROM for other Blackview devices.

naijarom.com
[Android Q&A, Help & Troubleshooting] theSUGARHILLlover:
@Steve98124 where did you find the boot.img file? I'm not able to find in the pac file ...View attachment 5887545
[Android Q&A, Help & Troubleshooting] theSUGARHILLlover:
I used the "ResearchDownload.exe" binary that I got from Blackview's Support. With an updated application, I then got the boot.img file.
[Android Q&A, Help & Troubleshooting] fezza:
Hi mate,

I need some help. My tab 11 had stock build: ROW_P30_V1.0_20220223 and I decided to ResearchDownload RUU_M60_T618_NEW_SDK_ID3611_20221027_V1.0 and got stuck in a boot loop. Pulled battery and tried using UpgradeDownload to flash RUU_M60_T618_NEW_SDK_ID3611_20221027_V1.0 and NEU_M60_T618_NEW_SDK_ID3434_20220705_V1.0 but they both give me a "lte cali in phone is not calibrated" error. Looking at YT videos people suggest using spd ver 17.0 but that gives me a "bin packet version is invalid" error.

So how did you restore your boot looped Blackview Tab 11 and which versions of UpgradeDownload and ResearchDownload work for you? Also was your stock and original rom a P30 or M60?

Edit: problem solved, all I had to do was to use my original ResearchDownload tool and flash NUU with userdata selected, I had it unselected before so was boot looping. All good now

Also got a newer firmware DK_Tab11_NEU_M60_T618_NEW_SDK_ID3434_20221107_V1.0 from blackview: https://mega.nz/file/mDhmVIiK#jMvHzY2pSfQAeOQhkKX3b3vJEkWXup6RyKPcoFcCrhU (copy and paste the link, don't click)

Thanks!
[Android Q&A, Help & Troubleshooting] fezza:
I've found that I can no longer get 4G on my tablet when on the NEU firmware can only get 3g, I could get 4g when I was on my original ROW firmware but can't find that firmware anywhere. I reached out to blackview but they gave me a ROW build from 2021 and the touchscreen didn't work with that version.
[Android Q&A, Help & Troubleshooting] RASTAVIPER:
What is the changelog of the new Rom?

Which android version does it have?
[Android Q&A, Help & Troubleshooting] fezza:
No changelog, same android 11 but with a 2022/11/07 build date
[Android Q&A, Help & Troubleshooting] svgyula:
Greetings! Supplement for ROM installation. The tablet is turned off. Start writing in the PC Flash program. The tablet is connected while pressing the volume minus button. If we do not do this, the charging process will start and the installation will be broken. Good old days...

Blackview Why is there no normal installation system? I do not understand! From Android 6, there is already a regular update. Why do everything need to all data be rewritten?
[Android Q&A, Help & Troubleshooting] Shapry:
Conviently enough, the BV tab 11 fully supports project treble, doing some experimentation with DSU, I have gotten android 12L CorvusOS running on my device. Once blackview support gives me updated stock firmware files I will try to flash the ROM permanently, and gain root access. If I'm succesful ill detail it here if anybody else wants to do the same.
[Android Q&A, Help & Troubleshooting] svgyula:
Hello! If you have successful testing. I would like to use it too. Please put it on a available place or share it here. Thanks!
[Android Q&A, Help & Troubleshooting] Shapry:
If I get it working I'll share everything here, so far in my testing using DSU everything seems to be working well, the only issues I've seen so far are:

Netflix and such are stuck at widevine L3(I assume because DSU completely kills safteynet, so this should be fixable through root/actually flashing the rim)

And the lockscreen is stuck in portrait mode, face unlock is working though, so it's not a huge problem. Having the android 12L tablet ui optimizations is really nice.
[Android Q&A, Help & Troubleshooting] Shapry:
Update:

I decided to try rooting following STEVE98124's guide in this thread, which didn't go well. I guess I didn't sign/flash the custom vbmeta properely as it triggered android verified boot and prevented the device from booting, turns out that it also prevents the device from entering fastboot or the recovery, luckily the spd flash tool was still able to recover the device to stock firmware, with this convinient undo option in hand, I will continue to try rooting, and once I do that, I will try actually flashing the GSI.

I did end up switching from corvus os to Crdroid as my candidate for custom rom.
[Android Q&A, Help & Troubleshooting] Shapry:
Alright. Some good news!

I haven't been able to get around AVB and root, but it turns out you can flash a GSI without having to sign it.

Prerequisites:

Unlocked bootloader

PC with adb/fastboot tools installed(Grab them here if you haven't already)

A GSI ROM you wish to flash, I got mine from here, make sure to get the correct type of ROM(see notes)

A backup would also be good, since the default OS is being overwritten.

Instructions:

First boot into recovery however you wish

Then use the volume/power keys and select "fastboot" in the recovery, this should bring you to fastbootd

Once in fastboot run "fastboot devices" to verify your device is connected properely.

Then to install:

Run "fastboot delete-logical-partition product_a" to free up space for your GSI

Run "fastboot flash system_a yourGSI.img"

Finally run "fastboot -w" to clear userdata(it's fine if there is an error clearing the cache)

Reboot and you should be good to go.

Notes:

GSI ROMS on the site I linked with either have the -ab type, or -bgN/bvN, all of these will work, but bvN doesnt include google apps. Make sure the ROM you download isn't the slim or vndklite versions, we need the base ones.

I was only able to get up to Android 12/12L working, 13+ all got stuck on the boot animation.

If you wish to test a few different GSI's to figure out which you like before flashing, you can use the DSU sideloader and shizuku to do so, but I won't provide detailed instructions for that here(it's pretty simple)

I ended up using crDroid as it has the option for homescreen auto-rotate, while Corvus does not.

All of the base android 12 builds I've tried have had the 12L large screen optimizations included.

You must disable "a2dp hardware offloading" in developer options to get Bluetooth audio working on any of the GSI's

Issues:

Streaming services show widevine L3, DRM info still shows L1 so this is a whitelist problem. Should be fixable via root.... if I can actually figure out how to do it ;-;

Good luck, have fun...

(I am not responsible for bricked devices or thermonuclear war)
[Android Q&A, Help & Troubleshooting] Shapry:
Root Successful!

After flashing my GSI, I redid all of the steps for creating a modified vbmeta and signing the magisk boot.img on another computer(also taking a moment to generate my own private key), flashed in fastbootd. and rebooted without AVB ruining my day.

Generating the signed/modified vbmeta and boot.img is a pain, i'll upload mine here if anybody wants to try them(stock keys should be the same across devices), if flashing my files breaks anything just use the upgradedownload tool to restore stock firmware.

Flashing:

reboot to fastbootd, then run "fastboot flash vbmeta \path\to\modified\vbmeta"

then run "fastboot flash boot \path\'to\signedmagiskboot"

then reboot, find magisk icon and finalize installation.

My magisk image: <https://drive.google.com/file/d/16ZqywnXk1uQb5U6WUVkARoNWfZFwBlNq/view?usp=sharing>

Edit: don't try to install the magisk bootloop protector with the option to patch the boot image, it doesn't sign it or something and causes a horrible AVB induced bootloop, now I get to flash everything again ;-;

Edit 2: I'm still trying to use the upgraddownload tool to flash stock, so far it's just giving me a "Check baud time out" error. I believe caused by windows connecting to the device, then disconnecting before reconnecting again. I'm beginning to get worried...

Edit 3: Managed to get it working, for future reference if you get a "SW2276:Check baud time out" error on the ResearchDownload tool, try powering on your device(which in my case just makes AVB angy and instantly turns it back off) and plug in your usb cable to the computer while it's on the powered by android splash screen, also hold down the volume -/+ buttons.
[Android Q&A, Help & Troubleshooting] ejrv:
I recommend building from the source. Then you can flash it using Azerokit
[Android Q&A, Help & Troubleshooting] blackpowder1818:
hello, use that for unlock all unisoc bootloader work fine for me. and use magisk for patch boot.img

GitHub - patrislav1/unisoc-unlock: Python tool to (un)lock a Unisoc/Spreadtrum Android bootloader

Python tool to (un)lock a Unisoc/Spreadtrum Android bootloader - patrislav1/unisoc-unlock

github.com
[Android Q&A, Help & Troubleshooting] ch3mn3y:
So how it is when fishing M60 firmware on P30 device? Does You loose LTE? Only one person's word about it, but would still prefer to know if it's the result of changing EEA firmware to global one.
[Android Q&A, Help & Troubleshooting] GJJBEGamingGeorge:
you can bug out the keyboard selection with microsoft swiftkey then it lets you turn off the default and you can still turn off switkey
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] winsloweric:
So I tried to add a proxy on MiUnlock's fastboot.exe, here is the behavior I observed.

[MiUnlock checking the phone's lock status]

-s [serial number] oem lks

if lks = 1 // Means it's locked.

[Input]

oem get_token -s [serial number]

[Output]

(bootloader) token: VQECOgEQqNzRiT9Tkv/P1o1QGQ4fWQMIcGlzc2Fy

(bootloader) token: cm8CHNBr99W4fTqr+jL/CZKGOcTV+i1nZKwnS8Im

(bootloader) token: tOg=

Don't mind with the serial number, those parameters' will still work without it, it is for fastboot.exe targeting the phone, you will receive exactly same output without it.

My inference is that, this Base64 encoded information included Account Add Date and Phone Serial Number, for MiUnlock to check.

in the middle of data, cGlzc2Fycm (=) is Phone's Code, in Redmi 11's case, Pissarro.

We can infer that this divided the data into two parts.

VQECOgEQqNzRiT9Tkv/P1o1QGQ4fWQMI (Don't know if this "MI" at the end is for locating, haven't generate a second token(Rebind Account, which will reset your 168 hours.))

8CHNBr99W4fTqr+jL/CZKGOcTV+i1nZKwnS8ImtOg=

I haven't gained any progress on decoding them, it is highly likely that they are encoded with different Base64 rules.

I guess I'll try to remove Account Binding and bind it one more time to observe the Data alternation as for locating where is the date information encoded.

idk i don't think i can hack it anyway.

If you have any idea decoding it, welcome to share!
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] winsloweric:
ok, after 4 hour I rebinding and this is new output

(bootloader) token: VQECOgEQIhLuo5o7ujbwTgaaRoFNBwMIcGlzc2Fy

(bootloader) token: cm8CHNBr99W4fTqr+jL/CZKGOcTV+i1nZKwnS8Im

(bootloader) token: tOg=

we are now completely sure that "MI" is for locating, and where does the date got encoded.

View attachment 5602367
[8125, K-JAM, P4300, MDA Vario ROM Development] Tambuyeye:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.

my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.

i am frustreated man and really need help.
[8125, K-JAM, P4300, MDA Vario ROM Development] cornelha:
When creating packages with Package tool it creates the following folders:

SYS

OEM

Missing <-- Thats what you are looking for.

I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily
[8125, K-JAM, P4300, MDA Vario ROM Development] Nandaly:
When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.

If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.

This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.

If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.

Good Luck!