yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Justadudeinspace:
So I'm not very familiar with the device but I believe the UI may be locked. I believe it is moddable but I am not sure it will be easy.

However, here are some threads on the device that may assist you in your task.

V-Tech Kidibuzz XDA Thread

V-Tech Tablet Innotab Max XDA Thread (Similar Issues)

Another Innotab Conversion XDA Thread

Sometimes content is transferable between devices with similar issues. I could be wrong and these links may lead to a dead end, but they are the best place to start. Unfortunately, I didn't find a whole lot on the V-Tech Kidibuzz, so that's not to say that what you are wanting to do isn't doable, but you may have to figure it out and be one of the first to do such.
[General Questions and Answers] devicemodder:
I was able to sideload nova launcher and get past the locked UI with that, just can't set it as default, so I have to launch it from the tech UI. What I care most about at the moment is root access, debug settings and ADB.
[General Questions and Answers] Justadudeinspace:
I wonder what chipset is the V-Tech Kidibuzz?? Do you know?
[General Questions and Answers] devicemodder:
Same as the leapfrog epic...

CPU 1.3GHz Quad-Core MT8127

GPU Mali-450MP
[General Questions and Answers] Justadudeinspace:
Yes, it's Mediatek.. If you can figure out how to access Dev Mode to toggle OEM Unlock, you can easily use MTKClient (my favorite flash tool) by bkerler to unlock the bootloader and install a GSI. Granted you can do this with fastboot, but BRom mode is for flashing the device when it bricks. It's how the manufacturer accesses and fixes the device. So I'm curious if the MTKClient bootloader unlock code would work without the Dev Mode access? I've never tried it before, so it may be worth a shot.

My other idea was to access Dev Mode settings by means of apps such as System UI Tuner but that requires Shizuku, which requires Dev Mode access. So that won't work.

I'm sure there is a way. Unfortunately I'm not even a novice developer, but I'm an advanced user. I will do some research and see what I can come up with.
[General Questions and Answers] Justadudeinspace:
So the problem isn't accessing developer options because if I'm understanding this correctly, developer options was removed from the device. Essentially, there's nothing there to access.

So this begs the question, is the OEM lock enabled?

The second question is, how to trick the device into BRom Mode? As it is Mediatek, it surely has BRom Mode.

Dude, unless you have mad android programming skills and understand code, I think your best shot is to use MTKClient to try and unlock the bootloader from BRom mode. Are you familiar enough to figure it out or would you like me to post a guide?
[General Questions and Answers] devicemodder:
As for oem unlock, not sure. But I can try the MTKClient when I get home. I'll let you know if I get stuck and need assistance l.

Thanks for the help so far.
[General Questions and Answers] devicemodder:
Getting somewhere... MTKClient sees the device, but hangs up at stage 2: Didn't recieve Stage2 DRAM info.

Tried multiple times, always hangs up here.
[General Questions and Answers] Justadudeinspace:
So I'm old-school I guess. I run MTKClient through the shell without the GUI. I installed MTKClient directly into the platform-tools folder, and then open MTKClient by typing cmd into the search bar.

For me it looks like this in the shell:

C:/platform-tools/mtkclient>

The first code I typically run is to wipe user data:

python mtk e metadata,userdata

Then I run the bootloader unlock code. Which there are two, typically only one will work:

python mtk xflash seccfg unlock

or

python mtk da seccfg unlock

I'm assuming you got the device to enter BRom Mode. Understand that you will have to unplug the device and plug it back into BRom Mode after each individual code is ran. Let me know if you have any further complications.
[General Questions and Answers] devicemodder:
I am running MTKClient from the linux live iso provided in the github, as i've been having python issues with windows 11...
[General Questions and Answers] Justadudeinspace:
Ah, I gotcha.. Well, I don't know. I'm confused as to why it's hanging up in stage 2. Did you successfully enter BRom Mode?
[General Questions and Answers] devicemodder:
Don't think i did. oh, got python running correctly on my windows box. gonna give the command line a try.
[General Questions and Answers] Justadudeinspace:
On smartphones, the typical way to enter BRom Mode is by powering off the device. Run the code into the shell, then press and hold all volume and power buttons before plugging the device into the computer. Sometimes, the code doesn't catch up on plug-in and I immediately unplug and then plug it back in again and it catches.
[General Questions and Answers] devicemodder:
well, getting further:

Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.

.........Port - Device detected :)
Preloader - CPU: MT8127/MT3367()
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x8127
Preloader - Target config: 0x0
Preloader - SBC enabled: False
Preloader - SLA enabled: False
Preloader - DAA enabled: False
Preloader - SWJTAG enabled: False
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca04
Preloader - SW Ver: 0x0
Preloader - ME_ID: 0022E35405461806829E18669745E22B
DA_handler - Device is unprotected.
DA_handler - Device is in BROM-Mode. Bypassing security.
PLTools - Loading payload from mt8127_payload.bin, 0x258 bytes
Exploitation - Kamakiri Run
Exploitation - Done sending payload...
PLTools - Successfully sent payload: C:\Users\eric\mtkclient\mtkclient\payloads\mt8127_payload.bin
Port - Device detected :)
DA_handler
DA_handler - [LIB]: Device is in BROM mode. No preloader given, trying to dump preloader from ram.
DALegacy - Uploading legacy da...
DALegacy - Uploading legacy stage 1 from MTK_DA_V5.bin
legacyext
legacyext - [LIB]: Legacy address check not patched.
legacyext
legacyext - [LIB]: Legacy DA2 CMD F0 not patched.
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DALegacy - Got loader sync !
DALegacy - Reading nand info
DALegacy - Reading emmc info
DALegacy - ACK: 04028d
DALegacy - Setting stage 2 config ...
DALegacy - DRAM config needed for : 15010038475446345206323e5ad2864f
DALegacy - Reading dram nand info ...
DALegacy - Sending dram info ...
DALegacy - RAM-Length: 0xbc
DALegacy - Checksum: 15AA
DALegacy - M_EXT_RAM_RET : 0
DALegacy - M_EXT_RAM_TYPE : 0x2
DALegacy - M_EXT_RAM_CHIP_SELECT : 0x0
DALegacy - M_EXT_RAM_SIZE : 0x20000000
DALegacy - Uploading stage 2...
DALegacy - Successfully uploaded stage 2
DALegacy - Connected to stage2
DALegacy - Reconnecting to stage2 with higher speed

\

but whben i try to get it back into BROM mode to run the unlock command, the device won't go back into brom and i just get a black screen. but that is resolved by pulling the battery, but then i have to start all over.
[General Questions and Answers] Justadudeinspace:
BRom Mode always has a black screen, but you should still hear a successful connection from the computer. The phone screen should remain blank showing nothing. It's like a backdoor often referred to as an exploit.

Also, you don't have to take out the battery to reset the phone. I believe it's hold the Volume Down and Power buttons for 10 seconds, or hold the Volume Up and Power buttons for 10 seconds. I can't remember which one it is at the moment.

Sent from DE2117 using ReLabs
[General Questions and Answers] devicemodder:
Gonna try again later tonight, and report back. Seems like the program stops though and doesn't continue after reconnecting the phone.

But it does try to reconnect, and all I hear is the usb disconnect/reconnect noises with the MTKClient saying it cant find the phone.
[General Questions and Answers] Justadudeinspace:
If the "waiting for device connection" freezes, then it's trying to read the phone. I have this error often. That's when I'll continue to hold all the HW buttons, disconnect the USB cable, and immediately reconnect the USB cable. Typically, this will achieve a connection and the code on the shell will take off.

*Do Not Release The HW Buttons Until A Successful Connection Is Achieved*
[General Questions and Answers] devicemodder:
I should have been more clear, my apologies. When I say the software freezes, I mean it stops whatever it's doing and drops me back to the C:\> prompt in cmd. Ie, the software exits sometimes
[General Questions and Answers] Justadudeinspace:
OK, it errors mid-way through. This happens to me sometimes, especially when flashing an entire firmware package at once. Sometimes, starting the phone by powering on and then navigating to recovery mode to power it back off will reset the device. Sometimes it just glitches. This is no perfect science, and each device varies in quirks, but I'm sure together we can figure it out.

Also, remember I said after performing one task in BRom Mode, you'll have to repeat the process for each individual task. So starting over is typical, because with BRom Mode, leaving the device connected doesn't work.

Sent from DE2117 using ReLabs
[Google Pixel 8] Pritster5:
Hi All,

Google in typical google fashion made a dumb change a while back that regresses on UX by attempting to show an estimate of the time remaining rather than just showing the user the battery percentage in the Quick Settings panel.

This is a bad idea for a number of reasons, with the main one being that the estimate is almost always wrong and doesn't update fast enough to changes in the usage of the device.

Is there anyway to replace the estimate with the percentage when swiping down on the quick settings panel?

And no, this isn't the same as enabling the percentage in the battery options menu, that just shows the percentage next to the icon and takes up unnecessary space on the status bar.
[Google Pixel 8] blackhawk:
I use Battery Guru now. Accubattery is always trying to send data. Battery Guru less so and can be firewall blocked without going nutz. Doesn't consume much battery.

Nice pull down notification info too...

View attachment 6096785
[Google Pixel Fold] wolfaas12345:
So after trying out Android 15 on Pixel fold i decided to take Lineage OS 21 for a spin and here's what i found

What works well

System is super speedy definitely feels more responsive than stock pixel OS

USB/Data/Wifi/NFC/Folding and Unfolding/Camera all those work

Gapps installed and work effortlessly

Esim seems to work as well (at least with gapps installed didn't test without gapps)

View attachment 6096721

Battery seems to have improved i don't have any benchmark evidence but it definitely seems to last longer

Google camera also works as camera services are present in the build so you can just download google camera from play store and it mostly works ( for some reason internal selfie camera is rotated 90 degrees on pixel cam (not a problem on LOS cam or other apps)

View attachment 6096722

Now playing also kidna works it listens to songs but it doesn't display on lockscreen to see the results you need to go to settings/now playing to see music history other than lockscreen notification works flawlessly

I love the bigger grid options in LOS launcher definitely something stock pixel launcher needs

View attachment 6096723

Split screen works fine however there is no option to force app to stretch to full size of the internal display so if app cant stretch it won't fill the screen also the app dock is present (can be turned off its on by default)

View attachment 6096724

What don't work

Despite NFC working and 6 of my banks not complaining (neither does netflix and other safetynet apps i use) google pay is a no go out of the box despite it saying (OH YEAH U PASS ALL SECURITY MY GUY NO PROBLEM) (can probs be fixed with magisk but im talking stock experience here)

However surprisingly (japan only) Osaifu Keitai does work out of the box (i did not expect that to work honestly)

View attachment 6096725

Pixel exclusive garbage doesn't fully work so circle to search is not present (can it be fixed with magisk? probably Do i know how ? no)

This review is based on latest April build from LOS directly

View attachment 6096727

Other than NFC and some pixelOS stuff build seems crazy stable no crashes works great and overall a decent daily driver

What would i add personally ?

Circle to search ( i got used to it surprisingly useful)

SafetyNet out of the box (not gonna happen on official LOS build)

App resizing option to force them to stretch to internal screen (like on stock os)
[Google Pixel Fold] XDM inc:
mines updated to the latest version, broke my custom launcher ortus launcher, i tried to downgrade my system and now softbricked, gotta nuke the device...

moral of the story, if it works DONT UPDATE.
[Google Pixel Fold] bs3pro:
LOL, I had a real early build working great, and like an idiot upgraded to a later version, and broke some magisk mods. They just wont work anymore unfortunately. Might downgrade to older build, and start over.
[Touch Pro, Fuze General] LaMpiR:
I am thinking of ordering AT&T unlocked version of htc touch pro. I am little confused. There are so many version of htc touch pro? I am looking for cheapest version and I think it's unlocked HTC fuze. Now, is there a way to remove all those AT&T shortcuts and get a normal(original) HTC touch pro phone?
[Touch Pro, Fuze General] hidden_hunter:
The ATT version has a slightly different keyboard on it to the other varients (numbers along the top are removed and are accessed by a FN key - replaced by symbols)

I'm looking at doing a similar thing to get a Touch Pro, ATT seems the cheapest way of getting one but from memory it's about $50 more with other carriers that use the normal keyboard.
[Touch Pro, Fuze General] LaMpiR:
Yes, that is the case with keyboard but I don't mind really. I've found that I can latter install other rom and get original HTC touch pro, something like this http://xdaforums.com/showthread.php?t=444784

@hidden_hunter, is there any other version that will work with GSM providers worldwide and has original HTC touch pro keyboard?
[Touch Pro, Fuze General] PUNiZZLE:
You will want to get the HTC Touch Pro T7272 (European Version) over the AT&T Fuze because there is a descrepency inbetween the US (Fuze) 3G Bands and the European (Touch Pro T7272) 3G Bands.

I am thinking about selling mt Touch Pro as mentioned in these thread replies: http://xdaforums.com/showthread.php?t=466685
[Touch Pro, Fuze General] hidden_hunter:
If you're in Australia I think ATT's 3G bands are the same as Telstra's so it should work no issues, others might know more (I'm with Virgin mobile who since being totally bought out by optus seem to be becoming worse and worse value) So you would need to check if the frequencies are compatabile (make sure you don't buy a CDMA version for instance)
[Touch Pro, Fuze General] LaMpiR:
I live in Bosnia. Would Fuze work here?
[Touch Pro, Fuze General] PUNiZZLE:
Check your PM. I sent you details.
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] Arun0A:
My Tablet is locked by Samsung Knox Account Manager, I cannot sign in to the account either, since it is not connected to internet neither I can switch it on, it is just blocked to change screen to anywhere else.

I tried to reset the device from the system recovery, but failed to do so (there isn't any option).

Tried to recover using 'adb shell', but error: closed

Tried using fastboot, but 'fastboot devices', error: closed

Cannot install TWRP (not sure if that would help)

I am out of options, any other ideas, suggestions, or correction to my current trials.

PFA, the recovery menu and logs.
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] parrots_:
If you flash the stock firmware with the normal CSC file (not HOME_CSC) it should reset.
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] Arun0A:
Yup, had to flash it. Thanks @parrots_
[Xiaomi Redmi Note 8 (2021)] ovywankenobi:
Can I flash ginkgo rom in biloba redmi note 8?

I have redmi note 8 2021 global rom, and for some reason I want a India or Indonesia rom. But I couldn't find any for Redmi Note 8 2021 version. Only Europe and Russia is available for biloba. Indian and Indonesia rom is available for ginkgo version only. Hence, any way can I install ginkgo rom instead biloba?

I already tried many ways, but always getting error in Mi flash tool while installing ginkgo rom.
[Xiaomi Redmi Note 8 (2021)] NOSS8:
Nope,different socs, Mediatek and Qualcomm.
[Android Q&A, Help & Troubleshooting] ABuilderProbably?:
Hello guys I was trying to flash my self-made TWRP from hovatek.com auto TWRP builder. When suddenly this error came for approximately 0.106 seconds after booting into recovery (it would just boot loop 2 times and go back to system) Device is Samsung Galaxy A24 4G
[Android Q&A, Help & Troubleshooting] Justadudeinspace:
So the TWRP porting programs on the Hovatek forums are pretty outdated if I remember correctly, and they are for I think Android 9 and below. I haven't seen a current TWRP porting program personally, and I tested all that I could find. I realized that it's about that time where I just learn how to compile TWRP. I'm not there yet, but it's probably not too far off.

With that being said, I would flash the stock recovery.img over the ported TWRP recovery.img to fix your error. If that doesn't work then you will probably need to perform a clean flash with the entire stock firmware to bring the device back to full functionality. I hope you made a backup.
[Android Q&A, Help & Troubleshooting] ABuilderProbably?:
Yeah but I selected the android 12 option bc I think it's also for 14, plus when I got TWRP from my GitHub it still didn't work.

Could you make a custom recovery from this stock recovery? I tried some Ubuntu commands that were in the auto TWRP builder but they just wouldn't work
[Android Q&A, Help & Troubleshooting] Justadudeinspace:
I believe the process is a bit more complicated than that. However, at this current moment I do not know how to compile TWRP.

Porting is essentially just making a copy of TWRP, but in a way that it will work for a similar device. Sorry..

Sent from DE2117 using ReLabs
[Android Q&A, Help & Troubleshooting] ABuilderProbably?:
hey hey, i found out you can patch fastbootd to any stock recovery img from samsung

but its only meant to flash gsi's and i would like twrp for obvious reasons
[Android Q&A, Help & Troubleshooting] Justadudeinspace:
Are you talking about this:

GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd.

CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd. - Johx22/Patch-Recovery

github.com

Yeah, it's for activating fastbootd on Samsung devices because they don't come with it. I have yet to use it personally because I don't actually like Samsung. Don't get me wrong, Samsung has a nice UI, but they implement too many restrictions for me. I think Samsung is trying to monopolize and maintain complete control over their devices. Which I disagree with considering how much money I shell out for smartphones. I buy them, this isn't a lease.

Anyway, if you really want TWRP for your device and it hasn't been compiled yet, then your only option is to learn to put in work. Here is what you need to learn to create TWRP for your device:

[DEV]How to compile TWRP touch recovery

All of TWRP 3.x source is public. You can compile it on your own. This guide isn't going to be a step-by-step, word-for-word type of guide. If you're not familiar with basic Linux commands and/or building in AOSP then you probably won't be...

xdaforums.com

Its an old thread that's still current and active. Good luck..

Sent from DE2117 using ReLabs
[Android Q&A, Help & Troubleshooting] ABuilderProbably?:
i compiled twrp from this website (i forked it and made some changes to target device a24) using github actions but no error shows up and it bootloops times after flashing: https://github.com/NoNameBuilder/Custom-Recovery-Builder

referring to the fastboot patcher thing, no i used wsl (linux commands but for windows) commands from this website that were on the bottom of page (similar script):

GitHub - ratcoded/fastboot-patcher: A bash script that utilizes avbtool & magiskboot to patch recovery images of dynamic samsung devices with android 10 and above to enable fastbootd.

A bash script that utilizes avbtool & magiskboot to patch recovery images of dynamic samsung devices with android 10 and above to enable fastbootd. - ratcoded/fastboot-patcher

github.com

because i got errors when using github actions

and i was wondering if you are using the samsung galaxy a24 too
[Android Q&A, Help & Troubleshooting] Justadudeinspace:
No, I have the A14 collecting dust somewhere. I'm currently all about my Pixel 8 Pro, I'm calling it the current Pimp of the Android world, lol.

But look, finding an easy quick fix to magically create TWRP for your device when it has yet to be compiled properly the developer way, well let's just say the odds are slim.

I've gone through the exact same process you're going through right now, and every lead just lead me to a dead end. Except for the link I posted for you in my previous post. I just haven't had time to sit down and read through it thoroughly.

However, I can tell you that the developers have presented us with all the information we need and they do not like repeating themselves. Their number one complaint is why won't us noobs just read. Especially, the long posts, because that's where the answers are.

Sent from DE2117 using ReLabs
[Android Q&A, Help & Troubleshooting] ABuilderProbably?:
I tried researching and no one has this problem, also after rooting it seems that after 6 hours or smth it shows "No sim detected - Emergency calls only" even on the stock rom and custom rom. I used fastbootd method to install evolution x 8.3 Android 14 gsi and i need to quick change custom roms without pc in necessary cases or additional devices (dad is lucky cos he has samsung galaxy a54)

I could read the error and it may be the problem with the keys needed to boot into recovery (it could do tricking to think its a phone with home buttons built in the hardware and not the screen)

I know i can use DSU Sideloader, but i just hate that i have insufficient storage many times

I use my moms laptop bc i dont have one and here are the specs:

Device name DESKTOP-UJGTRK7

Processor Intel(R) Pentium(R) CPU N4200 @ 1.10GHz 1.10 GHz

Installed RAM 4.00 GB (3.83 GB usable)

Device ID E1CC7EC1-953D-4C33-A816-5EBD7E178CE0

Product ID 00328-90000-00000-AAOEM

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display
[Android Q&A, Help & Troubleshooting] Justadudeinspace:
I don't know what you are talking about, no one is just creating TWRP out of thin air and it working.

Check to see if your IMEI is missing or null. If so, you're going to have to flash the device with the original stock firmware to get it back.

Sent from DE2117 using ReLabs
[Android Q&A, Help & Troubleshooting] ABuilderProbably?:
IMEI is unknown

additional: Should i try using dsu sideloader to flash a gsi from samsung