yashsingh1/xdaforums huggingface dataset:
[Magisk] DaviidCou:
I have this app added to Magisk Hide, blacklisted with Hide My App List and have installed PLAY INTEGRITY FIX from chiteroman.

I can even open Google Wallet with no message and TB Checker shows everything OK except "Strong Integrity" and "Virtual Integrity"

BUT my banking app has these 2 services

com.bbva.bbvacontigo/com.bbva.ethermobilesdk.devicechecker.root.service.RootService

com.bbva.bbvacontigo/com.bbva.ethermobilesdk.devicechecker.magisk.service.MagiskService

I can use App Manager and disable both but if I try to start the app I get

11-22 16:46:12.241 19320 19462 E AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { cmp=com.bbva.bbvacontigo/com.bbva.ethermobilesdk.devicechecker.root.service.RootService }
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:2040)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at android.app.ContextImpl.bindService(ContextImpl.java:1951)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at android.content.ContextWrapper.bindService(ContextWrapper.java:853)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at android.content.ContextWrapper.bindService(ContextWrapper.java:853)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at i57.c(RootUtils.kt:92)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at i57.a(RootUtils.kt:101)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at h57.invokeSuspend(RootUtils.kt:13)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at iy.resumeWith(ContinuationImpl.kt:12)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at yz1.run(DispatchedTask.kt:125)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: at kotlinx.coroutines.scheduling.a$a.run(CoroutineScheduler.kt:79)
11-22 16:46:12.241 19320 19462 E AndroidRuntime: Suppressed: gy1: [w58{Cancelling}@bd626a7, Dispatchers.Default]
11-22 16:46:12.245 1721 19730 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
11-22 16:46:12.246 1721 7741 W ActivityTaskManager: Force finishing activity com.bbva.bbvacontigo/com.bbva.woody.app.modules.initial.splash.view.SplashActivity
11-22 16:46:12.313 1721 2536 I ActivityManager: Process com.bbva.bbvacontigo (pid 19320) has died: fg TOP
11-22 16:46:12.315 1721 8521 I WindowManager: WIN DEATH: Window{86d8d3f u0 com.bbva.bbvacontigo/com.bbva.woody.app.modules.initial.splash.view.SplashActivity}

The app just crashes when it's not able to use com.bbva.ethermobilesdk.devicechecker.root.service.RootService, just enabling it again and leaving com.bbva.ethermobilesdk.devicechecker.magisk.service.MagiskService disabled allows me to open the app and login, but even if I disable it again and still login it's already detected root.

Any idea of what I could do?
[Magisk] xcl1pse:
Working fine here but I can't go further tho...
[Magisk] DaviidCou:
Same setup? Did you disable com.bbva.ethermobilesdk.devicechecker.root.service.RootService on App Manager?
[Magisk] mustaph12:
I suggest you install

1. magisk delta

2. On the dree dots you get "disable magisk".

3. Wait for phone to reboot.

4. It should work.

If not.

Install "island" app to create a work profile.
[Oukitel (All phone models)] SwedishForenger:
View attachment 6035816

Oukitel WP23 Pro 6.5-inch 10600mAh Outdoor Smartphone (8+128GB NFC)

The Oukitel WP23 Pro is a rugged outdoor smartphone with a 6.5-inch display, a powerful 10600mAh battery for extended usage, a convenient rear fingerprint sensor for security, and NFC support for contactless payments. Boasting 8GB of RAM and 128GB of storage, this device is ideal for those...

oukitel.com

​

I bought myself another Oukitel, this time a WP23 pro with a Unisoc T606 processor and 10600mAh battery. The idea is to create a phone I only need to charge once every two months. So right now my first goals are to, open the bootloader, flash a tiny GSI with 4 apps on it, a Phone app to make calls, a Contact app to save my contacts, a SMS app for messages and a small webbrowser, the Via browser for surfing the web if I need it. Let's get started.

I starting out of the box with firmware version:

OUKITEL_WP23_Pro_EEA_V06_20230912

and Android 13

​
[Oukitel (All phone models)] SwedishForenger:
Well, that went to fa**k FAST....

None of the usual fastboot unlock bootloader commands work, as they do on the usual MTK Oukitel processors. After some research on the internet, apparently the Unisoc processors need a signature.bin file to unlock the boot loader.

So let's create one:

Download the rar file and extract it to your desktop. I use linux, but you can open a CMD window in the folder in Windows to. Just type cmd in the address bar and hit enter.

View attachment 6035855
​

Now put your phone in fastboot mode.

adb reboot bootloader

Now go and get your key from your phone:

fastboot oem get_identifier_token

View attachment 6035856
​

Copy your key and replace it with X in the code below:

./signidentifier_unlockbootloader.sh XXX rsa4096_vbmeta.pem signature.bin

Copy the hole code with your key and past it in to the SMD promt:

View attachment 6035857

View attachment 6035858​

Press Enter. And the script will now create your flashable signature.bin file in the folder.

Now, let's flash the bin file to unlock the bootloader.

Copy the code:

fastboot flashing unlock_bootloader signature.bin

View attachment 6035859
​

Hmm? FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first.

The "Flashing Lock Flag" you get because the bootloader is locked. So we can't unlock the bootloader by flashing, because the locked bootloader doesn't allow flashing.

Anyone have any good ideas here?.

.
[Oukitel (All phone models)] SwedishForenger:
I found a way using Python. But for me, this didn't work either.

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

View attachment 6036060​
[Oukitel (All phone models)] SwedishForenger:
Someone got it working on the Cubot Pocket

Cubot Pocket: unlock bootloader and flashing GSI/lineageOS

I finally got my cubot pocket. I like my devices without GAPPS so I unlocked the bootloader and finally managed to flash a GSI. This post contains: observations and general hints for this level of development, a guide to unlock the bootloader...

xdaforums.com
[Oukitel (All phone models)] SwedishForenger:
I found this: CVE-2022-38694 by NCC Group. I think it's worth looking into.

Releases · TomKing062/CVE-2022-38694_unlock_bootloader

This is a one-time signature verification bypass. For persistent signature verification bypass, check https://github.com/TomKing062/CVE-2022-38691_38692 - TomKing062/CVE-2022-38694_unlock_bootloader

github.com
[Oukitel (All phone models)] SwedishForenger:
This is a Unlock hack for iPlay 50 mini tablet on Unisoc Tiger T606, which is the same processor we have in our phone.
​

I have 2 WP23 pro, and ran this hack on both phones, one it worked on and now has an Unlocke bootloader. The other one for some reason froze in the middle of the script and died. And is now permanently stuck in BROM mode. And nothing works, no buttons or screen that lights up. However, if I hold down -volume and run the script again, the script runs as before, but stops at the same place. and is still in permanent BROM mode with no option to reboot it or shut it down.

at least we are one step closer to a reliable bootloader unlocker. So I guess we are on the right track.

I am adding the link to the Stock firmware. So if you want to try to unlock your bootloader and fail, like I just did, you can just reflash the phone and try again.

828.35 GB folder on MEGA

636 files and 305 subfolders

mega.nz
[Oukitel (All phone models)] SwedishForenger:
During my time using the SPD flashing tools, I come a cross a lot of strange ERROR messages.

View attachment 6037567​

''Bin packet’s size is too small, maybe it has been destructed''​

"data packet with type(0x96) returned was misformatted"​

"Failed: Wait input time out) error"​

" type(0x96) returned was misformatted"​

Etc. Etc.Etc. Etc.Etc. Etc.Etc. Etc.Etc. Etc.Etc. Etc.Etc. Etc.Etc. Etc.

I don't know if it is the programs themselves that are unstable, or if it is something in the phones that is unstable and gives all these error messages. but I solved all of them just by flashing the firmware to the phone wiyh SPD_Factory_Tool_R27.23.1902.

Just something to keep in mind, should you experience problems while slashing.
[Oukitel (All phone models)] SwedishForenger:
Rooting stock firmware OUKITEL WP23 pro​

OUKITEL_WP23_Pro_EEA_V07_20231103
​

If you don't want to flash GSI roms and are happy with the stock Android, you can "partl" control by rooting it. Download the boot.img and Magisk app. Unlock the bootloader, activate Developer Option "see previous post", insert your cable.

This will DELETE EVERYTHING on your phone. BACK UP !

adb reboot bootloader
fastboot -w
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot

.
[Oukitel (All phone models)] SwedishForenger:
I discovered that NFC doesn't work with GSI roms.

I'll will try to find a solution for this. today many use NFC payments and will soon be a must in all phones, for all scanning, tag related circumstances in our daily lives.
[Oukitel (All phone models)] SwedishForenger:
Restoring IMEI
​

Unisoc have gone out of there way to prevent people playing around in their system.

So when you have flashed GSI and things have gone wrong, Here's how to reset your IMEI.

We need to Relocking the bootloader before we can reset IMEI....

1. Download Stock firmware WP23 pro and extract the firmware from the downloaded

OUKITEL_WP23_Pro_EEA_V07_20231103.rar file

825.56 GB folder on MEGA

635 files and 304 subfolders

mega.nz

2. Download the two files in this post and extract to the desktop.

Install the drivers in the SPD Driver R4.20.4201 folder. Reboot the computer.

Open the SPD_Factory_Tool folder and launch FactoryDownload.exe

Guide ----

Hold down Volume- and insert the cable. You are now flashing back stock firmware to the phone. When the flashing is finished, restart the phone and activate the Developer option and usb debugging.

Now reboot the phone in to fastboot mode.

adb reboot bootloader

Lets relock the bootloader:

fastboot flashing lock

Look at your phone and follow the instructions.

Phone vill reboot and reset. When you finish the welcom guide. turn the phone OFF.

Open the SPD_IMEI_Tool folder an start the program. Enter your IMEI number.

If you don't know what it is or have access to it. It doesn't matter. You can choose an IMEI number from any other phone you have. Do you have a old mobile phone from the 90s lying around in a box?.... Ore do you have a friend who has a cell phone nearby?. Phone Company don't care about your IMEI number anymore, as long as you don't edit the phone ID number. The phone ID mixed with its SIM card number is what registers you on the phone company's network and forwards your calls and texts and all the other services you have with your operator.

You get a green text in the program saying that the IMEI is ready.

Reboot your phone and call and text away.

.
[Oukitel (All phone models)] SwedishForenger:
Remov "TEE Not Write" -

adb shell pm uninstall -k --user 0 com.unisoc.keyboxchecker

.​
[Oukitel (All phone models)] SwedishForenger:
If you are tired of the phone killing all the apps you need to run in the background, and not getting your messages from telegram etc etc etc. then you can turn off "idle mode"

Check if your phone has Deep Sleep mode active:

adb shell dumpsys deviceidle get deep

To deactivate deep sleep mode, run this code:

adb shell dumpsys deviceidle disable

View attachment 6043460
​

If you are not rooted and can use Tasker to start this process for you during phone boot, you have to manually do this through the computer every time you start your phone.

If you don't want ALL the apps on your phone having full blast battery draining mode, you can instead implement a "whitelist" of necessary apps only, like telegram ore whatsapp and E-mail etc.

example:

adb shell dumpsys deviceidle whitelist +com.telegram
adb shell dumpsys deviceidle whitelist +com.app.whatsapp
adb shell dumpsys deviceidle whitelist +com.app.email

to check which apps are in your whitelist:

adb shell dumpsys deviceidle

View attachment 6043743
​

To remove apps from the whitelist:

adb shell dumpsys deviceidle sys-whitelist -com.app.whatsapp
[Oukitel (All phone models)] SwedishForenger:
NO incoming calls!​

I have received several questions about why incoming calls don't work on different GSI roms. And the answer to that is complicated, and has to do with the UNISOC processor and chipset. Unisoc is running its own drivers and code separate framework from Android standard network code, and makes the phone incompatible with GSI roms missing the Unisoc 4G and 5G drivers.

So running GSI roms on phone with Unisoc, will restrict your call to 3G. But apart from incoming calls, are the Outgoing calls, surfing the internet and making calls with other apps, like Telegram, Facebook etc in 4G and 5G, no problem.

-- FIX incoming calls --

Go to "Settings" and change to 3G, to fix the incoming call problems.

This is GSI Evolution-X slim / Blazing fast and stabel Amdroid 14.

View attachment 6048318 View attachment 6048319 View attachment 6048320

View attachment 6048321 View attachment 6048322 View attachment 6048323

​

For future reference.

These files must be replaced from stock firmware, in to all GSI roms, to fix 4G / 5G networks.

com.android.unisoc.telephony.server

com.unisoc.networksliceserver

com.unisoc.phone

Unpack the GSI.img file, replace the android original files with stock unisoc files:

GitHub - Heliwrenaid/android-tool: SAT - the unpack/repack tool for Android system images

SAT - the unpack/repack tool for Android system images - Heliwrenaid/android-tool

github.com
[Oukitel (All phone models)] zerosava:
I think your code should have been

./fastboot flashing unlock_bootloader signature.bin

to take advantage of the modified fastboot file you downloaded. At least, that worked on my G5 Mecha. Unfortunately, it was unsuccessful overall:

[zerosava@moya Create_signature]$ ./fastboot flashing unlock_bootloader signature.bin
2downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.054s

Didn't like my sig file, I guess. I really wish I had read about Unisoc chips before I bought this phone. Damn, miss those MTKs!
[Oukitel (All phone models)] SwedishForenger:
Stock WP23 firmware for this phone:

828.35 GB folder on MEGA

636 files and 305 subfolders

mega.nz
[Oukitel (All phone models)] PYCON:
It's not so common to find someone with an Oukitel phone, right man ? But nice description and work, appreciated. I've had several Oukitel, C19, C21, WP12 Pro.

No so bad for the money. I'm using the WP12 to take some pics to my children when we're in the swimming pool.

Of course, root, magisk, lucky and some GSIs tried A13 based ( Pixel Experience and CR Droid ) using DSU SideLoader.

:cowboy:

PS I'm interested to WP27 but the there's 2 issues for the moment, the reasons for which I'm continuing to use my Poco X3 NFC:

* WideVine ==> only L3

* Google Camera ==> only last Burial and 6.x / 7.x are working ( and not all so fine ), no way to make working 8.2 / 8.3 / 9.x Gcam releases
[Oukitel (All phone models)] SwedishForenger:
I'm sorry, but I didn't understand much of your text.

Was it a question between the lines I missed or didn't understand?

.
[Oukitel (All phone models)] SwedishForenger:
-- NFC fix on GSI roms --
​

in some GSI rom's the NFC does not work. The NFC Magisk module fix has proven to be able to solve that problem at least in 3 of the rom's I tested this on. Might be worth a try anyway.

Download it from github or the zip file below if the github version is no longer available.

Releases · Jon8RFC/NfcScreenOff

Read NFC tags when screen is off. Disable NFC tagging sound. - Jon8RFC/NfcScreenOff

github.com
[Oukitel (All phone models)] cnxphysics:
Hi,

In your first post you mentioned that you wanted to have only a few apps and wondering if you have achieved it. I still use the wp5 pro with Lineage 19. However, close-up photos are blurry and self photos are red (wife's moto g9 with Lineage 20 does not have this issue).

I am considering wp23 or wp17 as you have achieved root unlike the wp5 and camera behaving better,

Thank you
[Oukitel (All phone models)] Infinexkwie:
Does this work with other phones like infinix? My phone has the same processor
[Oukitel (All phone models)] PYCON:
I've read that it's possible to use correctly the GCAM 8.X on Unisoc phone. Have you tried on WP23 ? If I'm not wrong, this could enhance the poor quality of the stock camera of this phone.
[Oukitel (All phone models)] JokanderX:
I love your tries, did you get success on that ?

I have infinix Smart 8 with unisoct606

no way to unlock the oem untill now ?
[Oukitel (All phone models)] JeremyBorja:
is it possible to unlock the Infinix hot 40i with the same processor? Unisoc T606
[Samsung Galaxy Watch 5] nikita@:
I would like to ask, has anyone ever encountered such a problem? If so, what is the solution to reset its size to normal?

Sorry
[Samsung Galaxy Watch 5] Clark Joseph Kent:
4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ , https://www.babelfish.com/ or https://fanyi.baidu.com/#auto/en or use one of your choice.
[Samsung Galaxy Note 20 Ultra Questions & Answers] kingfa:
HI guys i got an note 20 ultra 5g 1 sim (Korea ) and cant find sim manager at settings and no e sim option any way to fix thats maybe in specific rom cz as samsung forum told that all note 20 ultra has e sim inside but it seems thats need to be activate or something any help plz ty all
[Samsung Galaxy Note 20 Ultra Questions & Answers] matti88:
If it's running a very old software version, that could explain it
[Samsung Galaxy Note 20 Ultra Questions & Answers] kingfa:
Thats the system information dont know if it helps
[Samsung Galaxy Note 20 Ultra Questions & Answers] matti88:
No, it's not running old software. So contact Samsung for support
[Redmi 9A Questions & Answers] trueuser:
I just wanted to flash LineageOS on my Redmi (failed), I may or may not have accidentally flashed an incompatible twrp image, too. It bricked after the reboot. It shows the Redmi logo (that reboots every 5 seconds or so) and just vibrates when I hold down button combinations.

Please never rush your image flashing guys :(

I followed this (https://xdaforums.com/t/guide-how-to-fix-a-hard-bricked-redmi-note-9-merlin-hard-brick.4347025/) guide (with dandelion latest global scatters), but failed at step 18 of flashing because of DA 100% (most likely because I did this step wrong) and I unplugged for I had to go. When I plugged it back, it did not detect again. Not even libUSB nor the bypass ultility. How am I going to unbrick this now?
[Redmi 9A Questions & Answers] mvikrant97:
[How to guide] Redmi 9A [Dandelion] - Flashing with SP Flash Tool in BROM mode.

[How to guide] Redmi 9A [Dandelion] - Flashing with SP Flash Tool in BROM mode. 1.Please don't use Format all + Download in any circumstances in the SP Flash Tool. You have been warned! If you get any error while flashing or have any doubts...

xdaforums.com

Press and hold all 3 keys together to boot into BROM mode.
[Redmi 9A Questions & Answers] trueuser:
@mvikrant97

got another problem here

(link to my reply which i put more detail on the problem)

[How to guide] Redmi 9A [Dandelion] - Flashing with SP Flash Tool in BROM mode.

[How to guide] Redmi 9A [Dandelion] - Flashing with SP Flash Tool in BROM mode. 1.Please don't use Format all + Download in any circumstances in the SP Flash Tool. You have been warned! If you get any error while flashing or have any doubts...

xdaforums.com
[General Questions and Answers] peoro:
I have an Android smartphone without a display and I wish to use it via `adb` and `scrcpy`. The bootloader is unlocked and I should be able to enter fastboot and recovery mode and flash stuff from there without using the screen.

However I'm afraid that if I need to do a factory reset, I'll be locked out: the first time it boots, USB debugging would be disabled and my computer's ADB key wouldn't be authorized on the device.

Is it possible to patch an existing ROM so that when I flash it on the device and boot it, USB debugging is on from the very beginning and my computer's ADB key is already authorized?

Can I do that on the stock ROM? How can I do it?

If it matters, the phone is a Google Pixel 6 Pro: it has got its own recovery (there's no TWRP/OrangeFox for it) and it means that I can't `adb shell` into the recovery to mount and modify the /system partition after it's flashed. I can just flash partitions with `fastboot` and wipe system and data from the recovery using the volume and power buttons.
[General Questions and Answers] Sparklingtube2:
Do you know how to do it?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kudos1uk:
I came here to find out more, the web is awash with news the F5 is about to get HyperOS (Android 14) in mid December.

HyperOS 1.0 Spotted for Poco F5; Coming very soon - Chroma tech

Xiaomi has already prepared the HyperOS stable updates for 5 Xiaomi devices and these updates can be rolled out any time. Now, another HyperOS 1.0 stable

techroma.in

POCO F5 will receive HyperOS 1.0 update soon - GSMChina

POCO F5 is POCO's latest F series model. The smartphone is known for its high performance and impressive AMOLED panel. All users were surprised by Xiaomi's

gsmchina.com
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] muppetz:
As far as I know HyperOS was released in Europe , for now , Global variant it's on the way so ...

I was Global , locked bootloader , unrooted , no TWRP . Then unlock , flashed EEA , not instantly received HyperOS then flashed HyperOS and locked again . I used it for 1 week .

There are NO significant/major upgrades , new HyperOS is slightly the same MIUI . If they didn't put a new boot-logo screen with HyperOS I shouldn't believe it's an " upgrade " .

There are no bugs , same fluid ROM but some annoying inconsistencies like notification icons , it is shown just one icon , the rest of them are only dots , big futile wifi calls icons on Control Center , maybe an improved camera , wifi 6 is faster then previous , didn't test 5G but 4G+ is fat enough , though a major downgrade is battery . Also I experienced a new Video Editor and a personalized look of locked screen ( Iphone style ) but no "wow" on those .

Same fine connectivity , no issues for calls or gsm signal , maybe a better fast fingerprint , same Poco Launcher with his gestures limitations , no gaming experience for me, same fast charging with no heating issues . I think or it's an personal impression the booting time is a little bit longer .

Security patch is November . GPS working fine , I don't use yet NFC or banking apps payment , bluetooth neither . Music player sound in ear buds is a little bit distorsioned in my opinion compared with A13 version with the same player apk .

Also I've tested in the near past ( Android 13 ) and the Antutu score was 1141086 (quite fabulous ) and now with the firmware , Antutu is 1120280 which is not bad at all .
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] muppetz:
Stock EU ROM , just received OTA

1.0.5.0 UMREUXM , 1,2 GB , security updateView attachment 6075879
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] muppetz:
Stock EU ROM , just received OTA ,

1.0.7.0 UMREUXM - Security patch = 251 MB

View attachment 6104162
[Introductions] perspective091:
I'm an enthusiastic person an android geek

A gamer and one who has passion for technology