yashsingh1/xdaforums huggingface dataset:
[Android General] changer86:
As I understood, the app is doing exactly the same like the Google Doc say. It seems like unlocking the Bootloader is enough to boot a custom-DSU.I have read something about signed Images that will boot without unlocking the Bootloader, but i didnt try it. I just want to get rid of all the Google-Stuff before using the Pocket :) Hope we can get it working.

btw: Gestures seem to work. swipe from right to middle closes Apps. from middle to up opens Menue
[Android General] changer86:
After a Weekend of fails i flashed Lineage 19 to my old KingKong mini and its working on the first try. Problem seems to be the Unisoc T310. The success-rate of flashing GSI to T310 seems to be really low. Does anybody know another Android 11 Device with Unisoc T310 that is working with GSI-Roms?
[Android General] badcodelab:
GSI on Unisoc device

My tablet is unisoc t310 T803 with oem android 11 here is were im stuck I reflashed oem super.img and the system booted fine so i can start fresh i erased product and system, and flashed lineage 17.1

www.hovatek.com

seems this guy has succeeded and his device looks pretty similar to pocket in treble info
[Android General] raary:
Hi, can you help me with this situation? I can't unlock bootloader on cubot pocket.

I tried to unlock on my ubuntu and windows devices.

FAILEN ( Flashing Lock Flag is locked. Please unlock it first)

I don't know that I will do for this problem

Spoiler content hidden.
[Android General] wori:
@raary did you enable OEM unlocking in the Android settings?
[Android General] raary:
Yes of course
[Android General] changer86:
Did you use the modified fastboot ? Under Ubuntu start a Terminal from the extracted Folder and use ./fastboot instead of fastboot. Ensure that fastboot in the folder is executable. Check this guide: How to unlock Unisoc

Be warned: Unlocking the Bootloader ist working but flashing vbmeta like you tried leads to bootloop. I think the cubot pocket needs signed Images for flashing. there is a guide for custom signed Images but i did not get it to work for now.
[Android General] raary:
Thank you, I will be try to unlock
[Android General] badcodelab:
@wori any updates on flashing gsi?
[Android General] wori:
@badcodelab not from my side. I got frustrated and also had some other things to do. Hopefully find some time + energy to continue working on this.
[Android General] raary:
I can't stay in stock OS, my GSI on cubot pocket have only 16 Gb via DSU sideload less for me, correct custom not exist for this, sad
[Android General] badcodelab:
@wori, @changer86 i didn't get clear from your posts if you tried to use signed vbmeta from the stock rom

also i haven't manage to make research tool to unpack boot.img nor super.img

by some reasons they stay listed as zero-sized .flag files in the target folder
[Android General] changer86:
Yes i tried, but mayxbe i did something wrong. Did you get a NVBackup vie Research-Tool? I dont get it to work
[Android General] badcodelab:
nope, haven't tried
[Android General] santosst:
Ok, I just booted Google's Android 13 GSI from here, version ARM64, no GMS. Steps on fastbootd (after unlocking bootloader):

fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img

fastboot --disable-verity --disable-verification flash vbmeta_product vbmeta_product.img

fastboot resize-logical-partition product_a 38000

fastboot flash system system.img

(on phone, go to recovery -> factory reset -> factory reset -> reboot)

I used both vbmeta-system and vbmeta-product from stock ROM.

I'll try to boot any phh-treble-based GSI now

EDIT 0: To enter fastbootd, run fastboot reboot fastboot before all the commands above.

EDIT 1: LOS 19.1 vndklite leads to bootloop

EDIT 2: Sooti's Android 13 booted 🥳 so I suppose LOS isn't able to boot because it is not a "secure" version i.e. it has su binary. Probably any A11, A12, or A13 GSI without inbuilt su will boot following this tutorial

EDIT 3: 4g calling isn't working, maybe we need to install the IMS apk from stock ROM in GSI. For now, I'll use only 3g

EDIT 4: Sooti's GSI doesn't pass SafetyNet test, so it's impossible to use GPay. Now I've installed PixelExperience and SafetyNet (and GPay) works well.
[Android General] santosst:
Some screenshots
[Android General] Md652:
I also managed to install gsi 13, but in no way root, which is the most important thing for me, when I burn boot it goes into bootloop
[Android General] santosst:
I wasn't able to install Magisk even in stock ROM. In fact, I couldn't flash any images, including the stock ones, through fastboot, only in fastbootd, and both the boot and the vbmeta partitions must be flashed through fastboot.

We need to learn how to flash these images using fastboot, or maybe through the Upgrade Download tool.
[Android General] raary:
Help, doest works, thank you
[Android General] santosst:
Not sure what's happening, but I have some suggestions:

- Do you have both images (vbmeta_system.img and vbmeta_product.img) in the same folder you're running the fastboot command?

- Are you running these commands in fastbootd? In other words, did you run fastboot reboot fastboot before running these commands? Your device should be on a screen where it's written "fastbootd".

- Which version is your fastboot binaries? Run fastboot --version to check it.
[Android General] raary:
I used windows adb tool instead linux version. It works ^)
[Android General] SpliFFdu95240:
Hi, How root the cubot pocket ?
[Android General] kkm6761:
You in France? I got contact in 93. Has KKM.
[Android General] SpliFFdu95240:
yes i m french.

I just want to have LED notifications ( for call missed , sms ... ) and light flow need root
[Android General] kkm6761:
I don't have Pocket. I guess root should be installed in recovery to boot in recovery to work, unless it is different. Don't know, sorry.
[Android General] LovinGSI's:
Thank you! This worked for me and I was able to get a prerooted Lineages 13 GSI to boot! It's AndyYan's lineage-20.0-20221111-UNOFFICIAL-arm64_bvS.img.xz. lineage-20.0-20221111-UNOFFICIAL-arm64_bvS.img.xz
[Android General] LovinGSI's:
FOUND A WORKING ROOTED LINEAGE GSI for the Cubot Pocket ! It's the lineage-20.0-20221111-UNOFFICIAL-arm64_bvS.img.xz on Andy Yan's github. It's under the Lineage-20-td builds here https://sourceforge.net/projects/an...20221111-UNOFFICIAL-arm64_bvS.img.xz/download to get it to work I had to follow santosst's post above EXACTLY and install the official google GSI first, then once it booted and was working:

adb reboot fastboot

fastboot erase system

fastboot flash system /yourfilepathonyourpc/blahblablah/lineage-20.0-20221111-UNOFFICIAL-arm64_bvS.img

then on phone, go to recovery -> factory reset -> factory reset -> reboot

and it worked.

One weird thing that I noticed after about 22 failed flashes is that I HAD TO COPY AND PASTE THE COMMANDS OUT OF santosst's POST specifically for it to work. I have a text file with command strings saved that have worked successfully on other fastboot devices (and still do) that appear identical and also return a successful result in terminal, but would still end up bootlooping. so if it your copying and pasting commands from some where else try copying it from santosst's post. there's no logic too it, but who cares as long as it works.
[Android General] LovinGSI's:
If you get caught in a bootloop (the phone powers on to the "lock flag is : unlock!!!" text over a white screen with the cubot logo and website address, then it powers down after 1 second and repeats) you can fix this by using the researchdownload tool and stock rom from the official cubot site https://www.cubot.net/Support/id/79/cid/19.html#hh . the trick is to hit the play button on the researchdownload tool so that it starts listening for the phone on all open ports, then hold down the volume up button as the phone is bootlooping then connect the usb cable to your phone. keep holding the volume up button until FDL2 fiinishes installing (~20 seconds) just in case I keep holding it until super.img starts installing (~40 secs). the tool seems a little finicky. sometimes you'll get a failed error on FDL2 and you just have to try again. if researchdownload tool just says waiting and never detects to phone, or if your phone is stuck on a black screen but the charging light is on, try holding down the Volume up button and power button a the same time. after ~10 seconds the blue charging light will shut off for a fraction of a second then come back on but the screen will stay black. when the charging light comes back release the power button but keep holding the volume button until researchdownload tools detects and flashes FDL2. it seems to come down to getting the timing right of holding down volume up, the power button and connecting the usb cable. I usually leave the usb cable connected the whole time but there were a few times i was able to get a successful flash to go thru by unplug/plugging it back in.
[Android General] LovinGSI's:
Getting closer to magisk working: I was able to get magisk to install on AndyYan's lineage 13 TD GSI above by installing the older 24.3 version in F-Droid (the newer 25.2 version just freezes). it will run successfully on directpatch mode, but the phone bootloops as soon as you reboot. you can fix this pretty quickly in the researchdownload tool by just flashing boot (and all the required stuff you cant uncheck like FDL1 and FDL2). just select the double gear button and uncheck everything except for boot and the required stuff.
[Android General] santosst:
It's very weird that any other command results in a bootloop... Maybe it's because of encoding. Anyway, as you said, it's working, so... 🙃

I believe the phone bootloops because we need to flash a patched (or blank) vbmeta. I wasn't able even to flash the stock vbmeta or the stock boot partitions through fastboot (not fastbootd); after that, the phone ever bootloops.

However, if you were able to flash the boot partition through researchdownload tool, maybe we also could flash the patched vbmeta through this tool.
[Android General] badcodelab:
some folks from 4pda managed to make root to work with stock and gsi by patching vbmenta-sign.img

Cubot Pocket - Обсуждение - 4PDA

Cubot Pocket - Обсуждение, Смартфон, 4,1"

4pda.to
[Android General] Md652:
I also succeeded with the signed file from PDA4 as soon as there is boot & vbmeta with the same signature it is very simple like normal rooting

I'm attaching the files here, it is necessary to burn this rooted BOOT that is signed with a signature compatible with vb
[Android General] wori:
with 4PDA's boot.img and vbmeta-sign.img, as well as AndyYan's LineageGSI 2022-11-11 build it works for me too. Great!

Does anyone use wired audio? When I attach a USB-C to headphone jack adapter (one without a DAC, I thinkg they're called USB-C audio gadgets), it continues to use the internal speaker. It does *something* with the adapter: it reacts to remote buttons on an attached headset.

I'd consider getting a USB-C headphone adapter with DAC if that works - can someone confirm that's working? I don't have one at hand currently.
[Android General] raary:
I'm having the same problem. No wired headphones do not work correctly (I tried 3 different models: complete with cubot, Xiaomi type-c, and using the type-c to jack 3.5 adapter). I had to switch to bluetoth headsets, everything works correctly for them
[Android General] wori:
USB devices (thumbdrive, audio device) don't work either.

So no wired Audio at the moment :(
[Android General] santosst:
Yeah, I also have this issue with the USB-C headphone. We will need to send logs to any dev who is working on the trebledroid project (maybe AndyYan or even phhusson).
[Android General] wori:
I filed issues for not working UAC (DAC) and USB-C audio gadget(mechanical adapter) to phhusson's repo
[Android General] raary:
n1
[Android General] santosst:
Does sound come out from the internal speaker and the USB-C headphone, or does it come out just from the speaker? For me, there's sound from both outputs.

I'm asking because there's a user of another device that just reported an issue with wired headphones on phh's telegram group (audio coming out from the speaker AND from the headphones).
[Android General] wori:
UAC DAC: only internal speaker (which makes sense: in the audio policy there's no additional output)

USB-C audio gadget: actually both - I didn't even notice that also the headphones do something...
[Android General] santosst:
Sadly phhusson will probably not help us, but he brought some light to the issue:
[Android General] atomphil:
How did you use the command?

fastboot resize-logical-partition product_a 38000

With my devices the return is always

fastboot: usage: unknown command resize-logical-partition

Both with the Windows and Debian platform tools and also with the version linked here. ROM is the latest official one from the Cubot support site (CUBOT_Pocket_C011C_V1-2_20221226), bootloader is unlocked.
[Android General] wori:
I used debian testing/unstable version 29.0.6. If you use the bullseye's i.e. stable's version 10.0.0 maybe that is the reason? In that case, it's probably easiest to use a live linux, but it's also possible to configure apt* to use some packages from a newer debian.
[Android General] santosst:
I'd say you check if the command fastboot --version returns anything above 29.

For example, in BigLinux, Arch-based, returns fastboot version 33.0.3p2-android-tools.

Furthermore, on which screen is your phone when you're running this command? Is it written "Fastbootd" on the screen?
[Android General] s_licciardello:
Hi, I am considering buying the Cubot pocket. I would like to install lineage 18.1, which version do you recommend? With gsi does the device work perfectly or does it have problems? I've read about problems with usb c headphones, not a problem for me, do you have other problems?
[Android General] wori:
I'd consider Andy Yan's Lineage 20 build to know to work reasonably well.

One minor annoyance: This Android version has a "take out of pocket" detection function, that turns on the display. However it doesn't work completely reliable, so sometimes you need to press the power button. If it did turn on the display before, it now powers off :/

There's a checkbox to turn it off but that doesn't work.

No Idea about any root detection things needed for certain apps
[Android General] s_licciardello:
Ok, everything else works?
[Android General] wori:
from my experience: yes
[Android General] s_licciardello:
Thanks. I find this lineage 18.1 GSI. Do you think it is ok for a/b treble device ? https://sourceforge.net/projects/meowice-gsi/files/LineageOS/
[Android General] wori:
no idea, why not just try it?
[Android General] s_licciardello:
I am afraid of a possible bootloop. I have read it is complicated to solve in this device.
[Android General] wori:
there's the possibility that it hangs on boot and it's not possible to restart it. In that case, you have to wait till the battery is empty, which can take a couple of days - or you disassemble it.

If you go with waiting, it's not complicated, but annoying.
[Android General] atomphil:
This hassle is not necessary, you can simply flash a stock image with the SPDUpgradeTool when the device is bootlooping.
[Android General] wori:
exactly, but just when it is bootlooping. When it hangs instead, you need to reset it somehow. When the power button doesn't do it's thing you have to either disconnect or drain the battery.
[Android General] s_licciardello:
Thanks, very useful
[Android General] GSI-Enjoyer:
Hi there, I bought this device and flashed Andy's Lineage 19 a while ago, the process is mostly hassle free, but I got into a boot problem when I tried to install magisk on it. After flashing 4pda's boot.img and vbmeta-signed.img via fastboot it just hangs at the boot screen, sometimes it boot loops after re-flashing. Has anyone encountered something similar? Would be even better if someone found the exact version of the rom that works with magisk. Thanks!
[Android General] GSI-Enjoyer:
Update: I tried again a few more times and had some partial success. The key is old firmware. I got the device in mid-Feb 2023, it might shipped with the newer firmware. I used the 20220611 version and 4pda's images, after flashing magisk recognizes the installation. But magisk also warns me the su binary is not from it, and if I allow the app to "Fix" the install the device would boot loop. I had to use the stock firmware tool to restore the original boot files and flash it with 4pda's images again.
[Android General] s_licciardello:
files: boot and vbmeta can i use them in any stock rom? does that also apply to the latest one? or do i have to extract them from the stock rom?
[Android General] wori:
not sure what you mean by stock rom here - you want to go to the cubot rom?

I'd do that the way cubot documents, that should work most robust.
[Android General] barenko:
I have a kkm3 and tried to root, but I made some mistakes and got the boot looping and the hardware buttons does not work anymore.

I already waited by the battery drain (enough to not power on the display anymore). Then I put the phone on PC usb with power+down pressed. It not worked. The phone continues with the boot looping as before.

Can you give me more details about your procedure to help me to unbrick my phone?
[Android General] wori:
sorry about that :/ as I wrote, I only managed to recover from that state with reflashing the complete vendor firmware following their instruction (there's also the link in the part you quoted). It's a bit too long ago for me to really remember the procedure, but at least from the instructions, you don't need to push power, but hold volume-up while inserting a USB cable while having the flashing software running on a PC you're connecting to.
[Android General] barenko:
I fixed the problem a couple days ago.

I had to access brom (vol up+vol down + USB) with the phone off and with mtk tool listening by phone connection on PC. I used chimera tool to access the Brom and reinstall all official ROM. The only trade off is that I yet don't know how to fix the dm verify and orange warning status. But the phone is operational, at least
[Android General] birdibird:
Orange state is very simple: hex edit lk.img and blank out the Orange state message.
[Android General] barenko:
No, it is not right. Change the hex can erase the message, but it will not remove the instruction to reboot in 5 seconds... In this way, the problem will be bigger...
[Android General] birdibird:
I have done it many times on many devices.

It is not about rebooting, it is a warning when booting the device into system.

The Orange state message is a cosmetic warning that the bootloader is unlocked.

You replace the whole message (Orange State Your device has been unlocked and can't be trusted Your device will boot in 5 seconds) with 00.

Then this message will not show up anymore. The boot will still take 5 sec longer than without the bootloader unlocked, but that is not a problem.
[Android General] s_licciardello:
Hello everyone, I would like to install LOS GSI on my CUBOT POCKET. I have read the entire thread and I am feeling a bit confused. I would like to understand if everything works with GSI, as I see some users have problems during the installation. Is there any other more comprehensive guide besides the main guide in this thread? I am also interested in the possibility of installing Magisk to solve SafetyNet. I thank in advance anyone who can help me.
[Android General] s_licciardello:
I was able to start several GSI android 13, but in none of it is bluetooth enabled, do you know how I can solve it?
[Android General] :
How to unlock bootloader? Every guide tells something else.
[Android General] santosst:
It seems that Bluetooth only works in Android 12 atm. It's not only for Cubot Pocket; other UNISOC devices have the same issue.
[Android General] santosst:
I updated the patched boot.img with the latest Magisk version. This boot.img is from the newest stock ROM provided by Cubot. I used the vbmeta-sign.img from here. Tested on stock ROM, but it'll probably work on GSIs too.
[Android General] santosst:
A great update about the Bluetooth issue: phhusson solved it, so the next Android 13 GSIs should have Bluetooth working on Cubot Pocket (and probably other Unisoc devices). Check this TD's release.
[Android General] tellko53:
Hello guys. I got my pocket and am trying to unlock bootloader, but having trouble with fastboot. I searched far and wide and installed every driver recommended, but still no luck working.

windows 11

cubot pocket firmware 1.2, usb debugging checked, oem unlocking checked

these are the steps i do:

1. connect phone to laptop

2. open cmd as admistrator in adb folder

3. run command adb devices, so far everything works, device listed

4. run command adb reboot fastboot, phone reboots to fastbootd

5. run command fastboot devices, and nothing. if i try running anything in fastboot i get "waiting for devices".

optional step: i even tried running it with 'disabled driver signature enforcement', still no luck

any idea what am missing? and how to make it work.
[Android General] santosst:
Hmmm, you'll need a modded fastboot, as cited in the first post. I used it in a Linux environment, but maybe you can use WSL2 inside win11. If it doesn't work, maybe you'll need a Live USB with any Linux distribution, like Ubuntu.
[Android General] tellko53:
EDIT: got it. will post results later. thank a lot for the help
[Android General] tellko53:
EDIT:

Info:Unlock bootloader success! OKAY [320.009s]

finished. total time: 320.010s

finally after 5 days of trying lol. am such a noob. now to get root...

thank you @santosst
[Android General] santosst:
Nice, congrats! :)

To get root, flash the magisk patched boot image and the modified vbmeta in fastbootd. You can ask if you have any doubts.
[Android General] tellko53:
Did that already. Cheers for that boot btw. Saved me more headaches.

Now looking for some bugless roms without gapps, probably android 11.

Quick question though. Once i erase system and flash new GSI, do I lose the patched boot and vbmeta?
[Android General] tellko53:
im omitting these two steps as i have no idea how to get these files. is there a nice, easy to follow steps to get them?

all my attempts so far at flashing gsi ended in a bootloop.
[Android General] santosst:
No problem!

To be honest, I did not try any Android 11 GSI, only A12 and A13. All of them have the issue with wired earphones. A13 GSIs had issues with Bluetooth, but they are now solved.

About boot and vbmeta, if you just flash the GSI, you won't lose them, but if you need to flash stock ROM, yeah, you'll need to flash them again.

Hmmm, I didn't tell before how to get them, right? The easiest way is loading the stock ROM's pac file in Upgrade Download, then the app will create a folder with all the images that compound the stock ROM (I don't remember if this folder is in the same directory of the Upgrade Download tool or the pac file). Just pick there both images, copy and paste them anywhere.
[Android General] s_licciardello:
Hi, in which gsi works bluetooth? I'm on los 18.1, i'm searching for an android 13 rom similar to los but with safetynet for gpay.
[Android General] tellko53:
Im happy to announce several successful GSI flashes. 🤘

The problem was in picking the wrong imgs.

I thought our phone was vndk positive, but all those ended in a bootloop. If anyone can share some light on this.

Thats a huge bummer. I bought an adapter for nothing 🤦
[Android General] santosst:
I believe all GSIs built in June will have Bluetooth working. On the other hand, I don't know if GSIs other than the Pixel ones will pass safetynet.