yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Peet13:
Hi all... i am not sure where to post this, because i am not sure what kind of head unit it is. All in know is that it is a Kunfine 10.1 android.

When I bought the unit, there use to be an option (when pushing the menu button on the steering wheel controls) to switch between navigation, music, video, radio or what ever i want to open whithout taking my hands off the steering wheel. But then all of a sudden it stopped doing it. Now if i press the menu button it goes to google. In fact the speech button, and both phone buttons on the steering wheel revert to the same (google). It is only the volume + and volume - and skip (Forward)(back) buttons that are working normally. i informed Kunfine and they said i have to configure the canbus.... I have tried it 100000000 of times. IT DOES NOT WORK. I have a Hiworld canbus and i drive a Toyota Hilux 2.4 GD6 2017model. There are no Hilux option when configuring... Please help if possible and if there is no option for the hilux in the configuration, what must i choose. I tried the Prado/Rav4 option.
[Android Head-Units] marchnz:
Not Android Auto, requested moderator move to Android Head-Units forum.

Op, take time and enjoy xda.
[Android Head-Units] Peet13:
Does anyone know what is going on? Why does this happen and what can i do to try and fix it.
[Android Head-Units] y2imm:
I think the steering wheel app is in the factory menu, 8888 or 123456 to access. Once you find it you can set your steering button functions.
[General Topics] hunkstar:
How do I enable USB debugging and OEM unlocking in order to install a custom ROM in the phone?
[P3300, MDA Compact III General] misi91:
Hello... My Artemis (O2 XDA Orbit) cannot recognize SIM Card :( I had original factory version of WM5 (O2 CZ) and I flashed to WM6 (O2 UK). Everything was great but about two weeks later: "SIM Card is missing".

I tried newest ROM, newest radio, original factory ROM but always the same problem. I start the phone, all is right and then (several minutes later) the same error again.

SIM Card is OK but only a few minutes after start or a i have to restart the phone module in commanager -> then few minutes and error again.

I tried everything help me please :-(
[OnePlus 9 Pro] grpeo32:
Title.

Is there any (preferably somewhat privacy focused) custom ROM that passes full SafetyNet checks and where Google Wallet & Pokemon Go still fully work?

I understand I might have to sacrifice some privacy to get google products to work but I am okay with that.

Preferably if it's relatively efficient and drains my battery less then stock.

I still want to be rooted btw.

Thanks in advance <3
[OnePlus 9 Pro] JordyEGNL:
Im using the latest crDroid with nikgapps core, passes safetynet and google wallet still works
[OnePlus 9 Pro] grpeo32:
Any chance there is a guide for this setup? Sounds good :)
[OnePlus 9 Pro] TheGhost1951:
Google search "crDroid rom XDA"
[OnePlus 9 Pro] JordyEGNL:
https://xdaforums.com/t/rom-13-oos-cam-op9pro-crdroid-v9-5-09-06-2023.4511627/

(My advice is to use the firmware updater script, it automatically updates the firmware and flashes the correct recovery :))
[OnePlus 9 Pro] cave.man1908:
To get Pogo to work you gotta check both Pogo & Google Play Services in Magisk, under denylist. Reboot and should work after that.
[OnePlus 9RT] Encapsulator:
How do i force my game(bgmi) to use gpu instead of cpu.

I am trying to unlock 90 fps. Somehow unlocked using adb shell to force game to use min refresh rate of 90 but its reverting back to below 60 frames when i start a match.

Also i noticed game uses my CPU upto 100% and GPU only 7-8% ?

why?

What is the use of adreno 660 then?

can anyone help or explain me this?
[OnePlus 9RT] nidheeshv:
thats not how it works. The gpu comes in picture when there is something to render.CPU will be handling logics.

Here your devcie and game is CPU extensive there is nothing u can do
[Google Pixel 7 Pro] geo91:
Hi everyone,

Tried getting some help via other sites but no luck, decided to come here to the experts.

My Pixel 7 pro had an issue where if you would push harder on the screen it would restart, it's a HW issue from what I understand.

Pushing the screen in multiple locations trying to find out exactly where is the point it triggers the restart lead to multiple restarts which bricked the phone.

Now my phone goes into fastboot and whenever i try to go into recovery mode or rescue mode it just cycles back into the fastboot.

I have tried multiple suggestions via connecting the phone to PC in order to fix it or rewrite the rom but I always get the error that my bootloader is locked (it's true i never unlocked it from Dev mode, not even sure i have USB debugging on).

Sending the phone to warranty is not an option, i bought it while on vacation and i live in a unsupported country.

If anyone has any idea how to fix this I would greatly appreciate it. I'm adding here a photo of the screen.

Also things that i have tried until now:

-Draining the phone completely and charging it back

-Sideload rom via ADB (Errors out with : Setting current slot to 'a' FAILED (remote: 'command (set_active:) is not allowed when locked')

fastboot: error: Command failed)

-Chrome flash utility/pixel rescue

Multiple people have pointed out that i don't need the bootloader unlocked to flash OEM ROM but the errors im getting about the bootloader being locked says otherwise.

Thanks again to anyone taking their time to read this post!
[Google Pixel 7 Pro] Lughnasadh:
Are you trying to sideload the full OTA? You can do that with a locked bootloader. Maybe you were trying to sideload the factory image instead?
[Google Pixel 7 Pro] geo91:
Hi there! Yes i remember downloading a file from the link you provided. Got it under ""cheetah" for Pixel 7 Pro " file 13.0.0 (TQ2A.230405.003.E1, Apr 2023).

Issue is, following the instructions, it says i should go into recovery mode but recovery mode does not open for me it just goes back to fastboot screen (the pic i provided). It also mentions there that i shouldhave USB debugging turned on and i don't think it's on...
[Google Pixel 7 Pro] Lughnasadh:
Did you double check to make sure it was the OTA file and not the Factory Image file?

You don't need USB Debugging enabled to sideload a Full OTA. Recovery mode allows for a couple of commands without having that enabled, including sideloading an OTA.

Do you see the Android robot when you try to get into recovery mode? If so, do you then press Power + Volume Up and then release Volume Up?
[Google Pixel 7 Pro] WoKoschekk:
Forget USB-Debugging! You don't need that. Neither in fastboot mode nor in recovery. It's only mentioned to boot from system to recovery via ADB. So, it doesn't effect you. In fastboot mode USB-Debugging isn't recognized by your device/USB port.

If you can't boot into recovery the device must be send to a repair station. Are you really sure that recovery isn't accessible?
[Google Pixel 7 Pro] simplepinoi177:
If volume button selection isn't working to get into recovery mode, I wonder if executing the fastboot reboot recovery command to get into it might work...

*you shouldn't need to have an unlocked bootloader to run that fastboot command, right?

also, OP confused me at the outset; he mentioned "Sideload rom via ADB" but also "fastboot: error: Command failed)" -- I've only sideloaded an OTA years ago without issue so I can't recall, but as the selection/name implies, isn't it supposed to be an ADB command,

not

a fastboot command (therefore, why is it a fastboot error?)?
[Google Pixel 7 Pro] 5.1:
adb sideload ota_name.zip

that is 👍

Sébastien.
[Google Pixel 7 Pro] simplepinoi177:
right?

so would that output "fastboot: error: Command failed" in any instance?

I doubt it, but for all I know, when running the "adb sideload" command, it also calls a fastboot command when applying it (sort of how "fastboot update" executes a bunch of command protocols like to automatically reboot after applying)...?
[Google Pixel 7 Pro] WoKoschekk:
but OP is stuck in fastboot mode.
[Google Pixel 7 Pro] simplepinoi177:
thoughts?
[Google Pixel 7 Pro] WoKoschekk:
the problem seems to be kernel related since he can't access recovery and/or system. A/B devices only use 1 Kernel for both. The recovery is merged into the boot.img and has no own partition with an own kernel.

Full firmware can't get flashed with a locked bootloader.

Full OTAs need the recovery due to payload.bin which depends on update-engine. So, OTAs need a shell environment.

The mentioned error output "set_active:) is not allowed when locked" shows that OP tried to flash an OTA. A full firmware won't change the slot by executing fastboot update UPDATE.ZIP. In this case fastboot uses the active slot to flash the firmware.

It's not possible to flash anything in fastboot mode + locked bootloader => device must be send to a repair station.

fastboot reboot recovery: If it's possible to execute this command (not all devices support that) it will do the same as hardware keys do. But it's worth a try.
[Google Pixel 7 Pro] simplepinoi177:
Trying to understand better (don't mean to hijack the thread, but also I'm sure this will be helpful info to OP)...but is "set_active" called when sideloading OTA? I wouldn't think it would from an adb command ("apply OTA via adb")...

You mention "flash an ota" vs. sideload that's why; unless i'm getting confused by semantics...

If so, can it be concluded that the OP was mistakenly trying to flash the OTA instead of "sideloading" like he claimed (which is only done in recovery mode, correct? unless, again, semantics) as fastboot commands were executed instead of adb?

@geo91, looks like if you can figure this, this might we worth a try....
[Google Pixel 7 Pro] WoKoschekk:
My question: Do you find such a command in the flash-all.sh script inside a full firmware? It's not clear what update-engine really does. It doesn't follow any shell script.
[Google Pixel 7 Pro] WoKoschekk:
Here are the corresponding lines in the AOSP from the master branch of update-engine:

if (!result.success) {
LOG(ERROR) << "Unable to set the active slot to slot " << SlotName(slot)
<< ": " << result.errMsg.c_str();
}
return result.success;

source: https://android.googlesource.com/pl...heads/master/aosp/boot_control_android.cc#127
[Google Pixel 7 Pro] omar qaissy:
MOD TRANSLATION

"How can it be solved? I'm having the same problem with Google Pixel 7 Pro"

********************************************

كيف يمكن حلها؟ أواجه نفس المشكلة مع Google Pixel 7 Pro

omar qaissy, Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by Forum Rule 4 (quoted below) -- that you just agreed to when you first registered your account. Please consider this when you are creating a post in the future. Feel free to include your original message under the English message if you wish. If you do not know English, I encourage you to use any of the resources in the quote below. Your post has been translated as a one-time courtesy.

Thank you for your cooperation, and have a good one!

simplepinoi177 FSM (Forum Specific Moderator)

View attachment 5934311View attachment 5934347
[Android Stick & Console AMLogic based Computers] boylklk9515:
I'm currently using this device: https://www.androidtv-guide.com/pay-tv-provider/myrepublic-stb/

Now I'm using Android 11 and wanna flash to latest firmware. But I'.stucking at step that need booloader unlocked, they showed the error like that:

Moreover, the USB Burning Tool for Amlogic chip did not detect my device before, I've tried connect many times but not success.
[Android Stick & Console AMLogic based Computers] Functioner:
Note that a device running a newer SoC like the Amlogic S905Y4 will not have worldcup burn mode, so such a connection is not possible in any case.

What firmware do you intend to flash? You could easily brick the device by flashing incompatible firmware.

Your image above does not show what commands you are typing, and in what context.

There are multiple types of fastboot connections. Such as a userspace fastbootd connection, and a bootloader fastboot connection. There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.

The image you posted is insufficient to determine what type of connection you had, and which commands you entered.
[Android Stick & Console AMLogic based Computers] boylklk9515:
thanks for your reply.

thanks for your reply.

But what is "worldcup burn mode".

I've tried connect my device to the UBT, but unsuccessful, then I tried to connect to 'fastbootd' mode and used the adb command to unlock bootloader, and the result shown above.
[Android Stick & Console AMLogic based Computers] Functioner:
When you said: "the USB Burning Tool for Amlogic chip did not detect my device before".

The type of connection that would have been used to connect to v2 of the "USB Burning Tool for Amlogic chip" would have been a worldcup burn mode connection. The Amlogic S905Y4 chip used in the SDMC DV9135 does not have the ability to make this type of connection.

I'll assume that "UBT" means "USB".

The bootloader cannot be unlocked in fastbootd mode.

It only can be unlocked in bootloader fastboot mode. This mode can be accessed by selecting the "reboot to bootloader" option in the recovery menu. Or, by typing "adb reboot bootloader" from a booted system with adb shell access.

Again, be careful in what firmware you choose to flash to this device. You can easily brick the device if you flash third party firmware. Only versions of the original factory firmware should be used.
[Android Stick & Console AMLogic based Computers] boylklk9515:
Thanks, let me try later and feedback you soon.

Do you use whatapps/telegram, can I have your number?
[Android Stick & Console AMLogic based Computers] Functioner:
No, I don't use either of those. I'd rather go down in a plane crash than use those apps.
[Android Stick & Console AMLogic based Computers] v7676uy:
Do you know any way to enter adnl mode?
[Android Stick & Console AMLogic based Computers] boylklk9515:
Here are some commands that I used on adb to unlock the bootloader

Spoiler content hidden.

The are two FAILED (in bold lines), said that my device is not accepted to unlock bootloader

My I try unlock bootloader by flashing other "boot.img" ?
[Android Stick & Console AMLogic based Computers] Functioner:
Enter the fastboot command:

fastboot getvar all

and report what it shows

No. If you somehow manage to install a modified boot partition with the bootloader still locked, the device won't boot at all, and might be more difficult to recover.
[Android Stick & Console AMLogic based Computers] boylklk9515:
Here are the result
[Android Stick & Console AMLogic based Computers] Functioner:
It looks like you are in fastbootD, not the bootloader version of fastboot.

to check, enter the fastboot command:

fastboot reboot bootloader

wait for the device to reboot and connect to fastboot again, and then enter the fastboot command:

fastboot getvar all

(again), and report if the output is any different than what you posted before
[Android Stick & Console AMLogic based Computers] boylklk9515:
here is the result like this
[Android Stick & Console AMLogic based Computers] boylklk9515:
further result which the following commands

fastboot oem unlock
fastboot flashing unlock

View attachment 5937145
[Android Stick & Console AMLogic based Computers] Functioner:
The commands you tried usually work.

SDMC must have changed their bootloader some for this particular DV9135 model, since it is an operator tier model.

It's interesting that you have the folder structure:

\DV9135\DV9135_ATV11_RELEASE

on your windows pc.

Do you have the firmware extracted in the "DV9135_ATV11_RELEASE" folder?
[Android Stick & Console AMLogic based Computers] boylklk9515:
Shared by my friend, but what exactly happened with my device?

What can I do next to unlock the bootloader?
[Android Stick & Console AMLogic based Computers] Functioner:
Exactly what was shared by your friend. Be precise.

If you have a copy of the firmware, it would go a long way in understanding what is going on.

Based on what you've posted, the bootloader restricts "oem" commands in fastboot based on the secureboot fuse setting.

And the unlock ability flag is 0, which is why "flashing unlock" doesn't work in fastboot.

You can check the value of the unlock ability setting:

fastboot flashing get_unlock_ability

(be sure to run this fastboot command in the bootloader version of fastboot, not fastbootD)

The result might be something like this:

(bootloader) get_unlock_ability: 0
[Android Stick & Console AMLogic based Computers] boylklk9515:
I've tried and the result was:

View attachment 5937359

so, my device was locked on fastboot mode and can not do anything

I've read something about ARM by this article: https://review.trustedfirmware.org/...329cabdd6e75c78e81f4e/docs/firmware-design.md

and it said :

The cold boot path in this implementation of the ARM Trusted Firmware is divided into five steps (in order of execution):

Boot Loader stage 1 (BL1) AP Trusted ROM
Boot Loader stage 2 (BL2) Trusted Boot Firmware
Boot Loader stage 3-1 (BL3-1) EL3 Runtime Firmware
Boot Loader stage 3-2 (BL3-2) Secure-EL1 Payload (optional)
Boot Loader stage 3-3 (BL3-3) Non-trusted Firmware

So, may it have anyway to replace thee "boot.img" and "bootloader.img" on the device to unlock the bootloader?

Do you use telegram?
[Android Stick & Console AMLogic based Computers] Functioner:
You've ignored my question about exactly what was shared by "your friend" and whether or not you (or your friend) have a copy of the firmware in that "DV9135_ATV11_RELEASE" folder. I won't reply to this thread anymore if you don't answer these questions.

As I said before, 'android verified boot' (avb) checks the contents of the partition that contains "boot.img".

If you do what you describe as "replace thee "boot.img" with a copy that fails verification (while the device is still locked), it won't boot.

The bootloader is most certainly encrypted. It is unlikely that you could ever find what you describe as "bootloader.img" that could ever even boot on this device.

Flashing a bootloader that won't start results in a bricked device.
[Android Stick & Console AMLogic based Computers] boylklk9515:
that is the folder has the firmware tool of dv9135, but nothing can be done if the bootloader in not unlocked. And exactly its mine.

Yes, I have

View attachment 5937475
[Android Stick & Console AMLogic based Computers] Functioner:
What is the firmware tool? Is it the amlogic burn tool (windows gui interface), or perhaps the adnl tool (command line)? Both of those are burn mode tools. Burn mode can still write to this device with the bootloader locked, but usually just for a verified firmware update.

Even if the firmware you have in this folder is for the dv9135, just flashing bootloader and boot from it would not unlock the device. Unlocking is a process distinct from flashing any partitions to the device.

If the firmware you have in these folders is a generic version, and not a version that is customized for some OTT provider, then perhaps the operating system would run with less customizations, but it wouldn't unlock the device.
[Android Stick & Console AMLogic based Computers] boylklk9515:
many thanks for your replies, I've tried some way and finally success.
[Android Stick & Console AMLogic based Computers] v7676uy:
Can you share the method? I am trying to unlock my device.
[Android Stick & Console AMLogic based Computers] Functioner:
"some way" works almost every time! No matter the problem, "some way" provides the solution!
[Android Stick & Console AMLogic based Computers] v7676uy:
I have a device which have the same problem with his device. Could you possibly help me to find the solution for this thread? I have device but my knowledge is limited so I can't find a way to unlock it. I will provide any information that I can access on my device If you need it.
[Android Stick & Console AMLogic based Computers] v7676uy:
I have tried command

fastboot oem 'setenv lock 10101000;save'

on both fastbootd and bootloader but did not work. I am thinking about boot device to adnl then use command:

adnl cmd "setenv lock 10101000"
adnl cmd "saveenv"

Do you think that is the right direction? The problem is I can not enter adnl mode on this device. It has a reset button. I tried hold it and turn on device but the tv box enter recovery mode instead.
[Android Stick & Console AMLogic based Computers] Functioner:
It could only possibly work on bootloader, not fastbootd.

But it appears that all "fastboot oem" commands are blocked by secureboot setting. What response did you get from bootloader fastboot when you sent the command quoted above?

It could possibly work. The value to use is 10000000, not 10101000. However, the "adnl cmd" could also be blocked by secureboot whitelist setting.

Only one of the usb ports can work for an adnl connection. The same one that works with fastboot.

If you can't get an adnl connection using the button, but can access adb on a booted system, try this adb command:

adb reboot update

I don't have a dv9135. You'll have to ask boylklk9515 the "some way" he used that resulted in "finally success". Without a device, I'm just guessing with my suggestions.
[Android Stick & Console AMLogic based Computers] v7676uy:
I also tried both 2 usb port. None of them work so I guess the problem is the method to enter adnl.

I tried and that command brought me to recovery mode instead of adnl.

I will provide as much information as that I can.

Afaik, he is selling unlocking bootloader and custom ROM services. And that kind of service will only unlock your device but still keep the method secret. So, I guess I have to do it myself instead of trying to ask him.
[Android Stick & Console AMLogic based Computers] v7676uy:
what did you mean by "verified firmware update"? Let's assume I have a modified super.img, can I flash it use adnl without unlocking bootloader?
[Android Stick & Console AMLogic based Computers] Functioner:
Flashing partitions with adnl is a whitelisted command on secureboot devices. It probably is intended to install or repair a device using unmodifed/factory firmware.

The device won't boot if modified partitions have been flashed without unlocking the bootloader. For a modified super.img, not only does the bootloader need to be unlocked in order for the device to be able to boot, but vbmeta needs to be patched/disabled.

So, while it may be possible to flash a super.img file to the super partition, if it is modified and the bootloader is locked, the device won't boot. And if you can't easily get into adnl mode to flash back the original unmodified super.img, you may not be able to repair the device.
[Android Stick & Console AMLogic based Computers] v7676uy:
How about flash a bootloader.img from generic version of device? Will it also make device not bootable? If it work, it will possibly make it easier to unlock bootloader.

However, I have to enter adnl first. Do you have any recommendations?
[Android Stick & Console AMLogic based Computers] Functioner:
Are you able to open the device and connect a ttl serial cable in order to access the uart? Doing this might involve soldering a header or wires to the uart connection points.

Historically, sdmc devices don't have any restrictions on the use of uart commands. If such is the case with this device, more options will be available.
[Android Stick & Console AMLogic based Computers] v7676uy:
I planned on doing that if all other solutions failed, because I don't have experience doing that. I will order the tools, try to do it, and report if I make any progress.
[Android Stick & Console AMLogic based Computers] v7676uy:
@Functioner Finally, I found the solution. The reason is my device firmware version old. After update to lastest version. I can unlock it easily with command:

fastboot flashing unlock

If anyone have device https://www.androidtv-guide.com/pay-tv-provider/viettel-tv-dv9135/ then you can use this ota https://drive.google.com/uc?id=1cjKWoTJSOT-wK5iF_1At3QvhhGe5nS3v&export=download

to update to the unlockable version.