yashsingh1/xdaforums huggingface dataset:
[Android Auto General] spyderboyant:
Any joy here to report? I can confirm stesps above are correct and I have done the same recovery but the tablet sits on the pre-screen without the Audi rings starting on my desk. It took ages to do the factory reset/ wiping /data and cache... I tried to "root" the tablet so hopefully not fully dead. The eMMC is a BGA so really painful to try and recover the old way with a complete image flash. Maybe JTAG ports on the Pegatron board?

Looking at a firmware update there is a referenced in the build.prop a reference to the factory reset partition:

#factory reset protection partition

ro.frp.pst=/dev/block/mmcblk0p13

which isnt mounted during normal operations so no way should have a root attempt damaged this. I would assume that this would just recover all the necessary files and overwrite them durin the normal recovery operation. Question is, is there an issue with build.prop so factory reset doesnt get to find this location?

When I run the recovery procedure it finishes correctly and provides the option to reboot as per the Audi instruction.

All I can do from a PC now is use sideload as the tablet doesn't get to the Audi rings so true ADB isnt running :-(

Did the tablet need to go into the car to fully recover?

Does anyone know with the Android recovery main menu "forced recovery" does?
[Android Auto General] spyderboyant:
Update... I re-flashed the APP partition I had from another tablet that has root and then re-run the update via recovery so tablet is back.

The issue is the rooting process I used (kingoroot) only half did the job. Tablet looks to be rooted when booted into fastboot:: fastboot getvar secure & getvar unlocked

(bootloader) secure: no
(bootloader) unlocked: yes

BUT, I can only boot the correct BOOT.IMG found on the update SD cards. If I change one byte in the update image I receive on the screen of the tablet

???.img verififcation failed twice in BootAndroid!! Contact care!

To me, this means the bootloader flag for unlocked is set but not being read and hence the SELINUX secureboot check is still being used :-( Hence you cannot load any "adjusted" bootloader images :-(

The only "oem" switch I can find for the tablet that loads is "fastboot oem lock" to lock the bootloader. When I try and lock the bootloader again, nothing happens, the flag stays set at (bootloader) unlocked : yes. There isnt any "fastboot oem unlock" command. Analysis of the bootloader image I have from another rooted tablet doesnt show many obvious commands for the oem switch..

Very strange.

When also in fastboot mode the bootloader image shows as 6Meg?? whereas its based on Tegra which has the boot loader split across two partitions of 4Meg each on the eMMC: mmcblk0boot0 and mmcblkboot1

Without a truly unlocked bootloader I think I am stuffed.

Any ideas?

APX mode is available from the bootloader "forced recovery". Maybe this is the only way by re-flashing known "virgin" bootloader partitions?
[Android Auto General] Roguyt:
Hi @spyderboyant, how did you manage to get into the recovery ? I have 2 of those tablets with forgotten password and I can't get into the recovery to factory wipe them...
[Android Auto General] spyderboyant:
Power off tablet, then while pressing and holding the power button down to power on the tablet constantly press the left volume button quickly. Keep pressing this volume button with power button depressed and it will bring you to the "fastboot" menu (the bootloader image). Then release the power button and stop pressing the volume button when you see this menu. Then select via the volume buttons the "Recovery Kernel" and press the power button. The tablet will look like it reboots but will show an android image. Depending on the firmware on the tablet you can either press the "power" button to get to the recovery menu or "hold power + press right volume button" to proceed to the recovery menu... You should now be in the "Android System Recovery <3e> menu..." Scroll down to "wipe data/factory reset" and press enter and there you go....

**IMPORTANT** This wipe can take anywhere from 10minutes - 45 minutes+ ****

BE PATIENT.. LET IT FINISH

If above doesnt work. Install Android Debug Bridge (ADB) and connect to the tablet from a PC with a micro USB cable. You need to enable Android Debugging (settings/about tablet/press "build number" seven times). Then under developer make sure "USB Debugging" is enabled and connect tablet to PC and "trust" your PC. Then from a command prompt in the folder with adb tools installed issue the with "adb devices" command to make sure you can connect to the tablet.

PC>adb devices

List of devices attached

2ps53qtnDvxxJPx1K device

If you can see the tablet then you are good to go... Issue "adb reboot recovery" and you get to the screen with the android image... Again either press power button OR hold power button and press "right" volume button to proceed.

Make sure you use a decent micro USB cable as some are only power and you wont be able to connect to the tablet.

good luck
[Android Auto General] 21spyder:
hello i have a porsche with a rear entertainment system which the same as audi's the device is the sdis1 and one of the tablets are just showing error codes as seen in the image and gives me this menu after i tried each choice and nothing works it keeps repeating the same error codes can anyone help me with a fix?View attachment 5974453
[Android Auto General] deckardd:
hey dude! did you find any solutions for this?
[Android Auto General] 21spyder:
Not yet unfortunately
[Android Auto General] rodken:
This error message clearly indicates that there is a problem with the firmware on your device.

There are a few things you can try to fix this problem:

-- Try reflashing the firmware. This will update the firmware on your device to the latest version. To do this, you will need to download the firmware file from the manufacturer's website. Once you have downloaded the firmware file, you can use a tool such as Odin to flash the firmware to your device.

-- Try wiping the cache and Dalvik cache. This will clear the temporary files that are stored on your device. To do this, you will need to boot your device into recovery mode. Once you are in recovery mode, you can select the option to wipe the cache and Dalvik cache.

Both methods might require a trip to the dealer.
[Android Auto General] 21spyder:
i went to the dealer they have no solution unfortunately as my car is out of warranty but this appears to be a software issue i can reflash the rom from the other tablet that is running perfectly but i'm unexperienced and i don't want to brick my device. the device is stuck on fastboot menu and i tried connecting it to my laptop after installing adb and fastboot drivers and my laptop can recognize it with fastboot devices but i don't what to do next
[Android Auto General] rodken:
Due to the lack of experience, your odds of rendering the device useless are very high.

If you feel adventurous,

-- Reset the audio entertainment system to factory defaults. This will erase all of the data on the system, so be sure to back up any important files before doing this. In order to achieve a reset, you might have to contact Porsche directly [not your local dealer] and lay the foundation for your dilemma in order to persuade them to assist.

Usually, to reset the Porsche Entertainment System (PCM), you can follow these steps:

-- Press and hold the PCM info button for approximately 10 seconds until the PCM reboots.

-- Immediately select the following from the PCM CAR > OPTION > Set PCM System > Reset PCM > Vehicle Handover > Yes > Yes.

This will reset the PCM to its factory default settings.

Spoiler content hidden.
[Android Auto General] peuuu_s:
Hi ,

I have the same problem, after a factory reset my tablet is stuck in pre-screen with Audi rings. I tried wipe data/cache but without any success. Do you know if I can clone rom from another tablet fully working tablet? It is 4M0919606A version.

Thanks a lot
[Android Auto General] spyderboyant:
Those errors relate to one of the partitions on the tablet being corrupted. The "Audi" rings etc.. are part of the bootloader image which then loads the main image which in your case is corrupted.

So factory resetting doesn't work as that clears the app partition. You need to get into Recovery and get the same firmware you had on the device or a newer one (the upgrade script does a version check and you can't downgrade). You can also flash individual partitions but only if you have an unlocked bootloader (rooted tablet).

Also note, as well as the batteries dying (you can buy replacements from Bentley... believe it or not).. the micro USB ports can die as well...
[Android Auto General] spyderboyant:
As your tablet is stuck at this point, you need to go to the Recovery Image from the bootloader and use ADB with "sideload" View attachment 6043775

When you select "Recovery Kernel" you may get stuck on the "android screen" with "no command" message:

View attachment 6043776

Now press Power and volume “+”. Play around a bit as I think sometimes you press power (don’t hold) then vol +. Maybe you hold power and press vol “+”. When successful you get off the android update screen and get into the recovery screen! Also dont have the tablet connected to your laptop with a micro USB cable at this stage.

View attachment 6043777

Select "apply update from ADB. USE ota ZIP file".

***Note: SDIS images on MIB2 update media ARE OTA.ZIP files and are stored in certain Audi Q7 updates in the TD_SDIS folder. The image is called SDIS.IMG. For a 606a tablet you must have the MHI2Q MIB so you need an update MHI2Q (Qualcom) update image. The image needs to be for a 606a as the 607 iimages will fail during the upgrade as the upgrade script checks for versions etc... and no downgrades possible. *** as you were most probably updating via your MHI2Q you will have the correct SDIS image to use.

View attachment 6043778

Now you need to have ADB toolkit installed on your laptop and you need to connect your laptop to the tablet with the micro USB cable. You will see via the "adb devices" your tablet with the "sideload" description next to it. This means ADB can see the tablet and its in sideload mode which is what you need. **Note, you will need a version of adb that is compatible with your tablet androice recovery image.. so if the version you try doesnt work, try another one... Try adb (not sideloader) on your working tablet. You will need to have the tablet in "developer mode" to do this.

View attachment 6043779

Now have your SDIS.IMG file somewhere handy and "push" it to the tablet. This is from a 607 update:

View attachment 6043780

On the tablet you will see the scripts checking the updates. It takes a while and as you can see, updates the "system" android image.

View attachment 6043781

Once the sideload is finished, you select "reboot system now" and you should see the tablet start updating...

You should be good now. You might need to wipe the user cache again... All the version information is in a partition that doesn't get touched as part of the update. View attachment 6043782

Hopefully this is helpful and good luck.

Note: Fastboot is your friend if the tablet is rooted... or else its useless to you
[Android Auto General] peuuu_s:
Thanks a lot for this update. I manage to connect to ADB and I can see the tablet in devices/sideloaded.

Can you please share SDIS image file? Or tell me where can I find it? I'm new in 'audi's world'.
[Android Auto General] spyderboyant:
Do you have root access to your MIB2 head unit? If so, it is in a folder on the MIB2 its about 800meg. there werrent many update medias for the MHI2Q and I think they removed SDIS image because there was issue with google maps... The SDIS,IMG is an android OTA which is a large zip file. You can open them up with 7zip to see what version they are... you dont want to install a 607a image as this kills DVB-T if you have it. They run different versions of the DVB-T app between 606a and 607a tablets
[Android Auto General] Leo SAMSUNG:
Hi, My tablet(audi rearseat entertainment) has lost the Audi desktop launcher, but I can access the native Android system desktop. Can you extract an Audi desktop launcher? Thank you
[Android Auto General] Leo SAMSUNG:
Hi, I have the same tab as you and my tablet(audi rearseat entertainment) has lost the Audi desktop launcher, but I can access the native Android system desktop. Can you extract an Audi desktop launcher? Thank you
[Samsung Galaxy A10 ROMs, Kernels, Recoveries, & Ot] Gabriel260BR:
ArrowOS

​

ABOUT

ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.

Website: https://arrowos.net

Telegram: Channel | TG Portal/Links

Github: https://github.com/ArrowOS

Code Review: review.arrowos.net

E-mail: arrowos.contact

PayPal: Donate to us

Blog: blog.arrowos.net

Checkout more documentation at (maintainership/contributing): Check this out

WHAT WORKS?

Almost everything

WHAT DOESN'T WORK?

VoLTE

Bluetooth calls

Be sure to include a log : check how to

DOWNLOADS

Download arm32 rom

Download arm64 rom

Read our blog article/post about:

* HOW-TO report a bug

* GAPPS and VANILLA variants

* Checking build integrity

ROM Source: https://github.com/ArrowOS

Kernel Source: https://github.com/Chatur27/Eureka-kernel-for-SM-A105-Q
[Samsung Galaxy A10 ROMs, Kernels, Recoveries, & Ot] BrotherBoard:
Keep posting awesome ROMs...
[Tilt, TyTN II, MDA Vario III General] nufsaid:
Here is a vid of my bluetooth headset, video captured w/ kaiser cam so sorry for ****ty quality again.

WEP500
[General Questions and Answers] Bushcat:
Device tree: https://github.com/Bush-cat/android_device_samsung_gts7xlwifi

Kernel tree: https://github.com/Bush-cat/android_kernel_samsung_gts7xl

Vendor tree: WIP

Common tree: https://github.com/Bush-cat/android_device_samsung_gts7xl-common

Rom source: https://github.com/LineageOS/android/tree/lineage-18.1

Build Error: https://del.dog/motuxyrevi

Problem: hiddenapi.cc:58] No boot DEX files specified. I checked the hiddenapi.cc code and it shouldn't need dex files because it's only needed for encode. All stubs files were created successfully.

(don't look at my messy commits, I will clean them when I get a good build)
[General Questions and Answers] Bushcat:
steps I tried: remove the boot dex if from hiddenapi; compile los 17.1; differrent Linux Systems (ubuntu 20.04 running in wsl2, native ubuntu 20.04, Linux mint 20.1), lots of try and error in the board config
[General Questions and Answers] Bushcat:
I feel so stupid rn, the fix was changing the base makefiles, I probably removed one sometime to fix another error but now it's working
[General Questions and Answers] edward0181:
What makefile did you replace (I have same issue)
[General Questions and Answers] Bushcat:
Idk anymore, I think boardconfig
[OnePlus 5T  Questions & Answers] Techie Android:
I have been having some problems with LineageOS 18.1 on my OnePlus 5T. My bluetooth OnePlus bullets have this constant stuttering whenever I listen to music, and that never happened on the stock rom. I also can't get the original camera and gallery apps to work when I systemize them.

I have tried with multiple versions of the stock apps from apkmirror and every single one does the same thing, it starts to open and then closes instantly.

I already have magisk with systemize which is what I installed them with, I have also tried both installation dirs.

As for the gallery app, it has weird problems such as not displaying photos or information after you click on them.​
[General Questions and Answers] nishat islam:
I have set some stuff in /system/etc/init.d/

Now, how do I know, if those feature are doing their jobs or not?
[General Questions and Answers] Deleted member 1890170:
You can't generically tell whether an init script was executed: Make your init script emit a log message.
[Samsung Galaxy S10+ Questions & Answers] Hitti2:
SM-G975U

I just paid my device off which is a Verizon Samsung S10+ on Android 11 UI one.

I rebooted My device and OEM unlocking is missing.

I tried the manual time and date trick and it did not work to make OEM unlocking show and developer options.

anybody have a suggestion? if you need any more info let me know.
[Samsung Galaxy S10+ Questions & Answers] It_ler:
Maybe best to ask Verizon.

Some users reported that they really had to wait for about 10 days, as the date/time trick did not work.
[Samsung Galaxy S10+ Questions & Answers] Hitti2:
Yea, verizon is a bunch Aholes, after 45min on the phone they transferred me to samsung without asking or notifying me. Waste if time.
[OnePlus 8T Guides, News, & Discussion] craznazn:
NOT FOR OOS, If you do this on TMO OOS you will lose connectivity.

So Lineage and all other AOSP based ROMs does not enable dual SIM for kebabt due to the T-Mobile modem having a hissy fit. However, you can flash the US/Global modem, retain all your 5G goodness, and enable dual-SIM as follows:

Download the Global modem: https://www.androidfilehost.com/?fid=2188818919693783632

Download the dsds magisk module: https://www.androidfilehost.com/?fid=2188818919693783509

Flash the Global modem:

fastboot flash modem modem.img

Install the dsds magisk module

Make sure you follow all instructions in the lineage installation https://wiki.lineageos.org/devices/kebab, that will be my first question if you have any issues.

As always, thanks @LuK1337 and LineageOS Team
[OnePlus 8T Guides, News, & Discussion] craznazn:
Well... I did say it's for Lineage/AOSP... But I'll make it clear in the OP
[OnePlus 8T Guides, News, & Discussion] David Ortega:
hello can you help me I have my umidigi 2020 bison that does not detect the SIM 2 by accident I moved that option and I can not activate again to the same opinionView attachment 5415687
[OnePlus 8T Guides, News, & Discussion] Crescendo Xenomorph:
by: Santosh Yadav

-Using ADB + root-

su

setprop persist.vendor.radio.multisim_switch_support true

setprop persist.radio.multisim.config dsds

REBOOT
[OnePlus 8T Guides, News, & Discussion] Diangucmau:
Hello friend ! I use 8T TMO, after upgrading to CBT 12, my device only accepts 1 sim, because the imei is duplicated, sim 2 can't be used, is there any way to fix it?
[OnePlus 8T Guides, News, & Discussion] craznazn:
Not sure, I haven’t upgraded to 12 yet to test
[OnePlus 8T Guides, News, & Discussion] Diangucmau:
i am using TMO carrier version , now i think on ColorOS android 11 will get enough signal , because i have experienced CBT OOS 12 on 8T , it also has the same error with COS , i flash colorOS 11 ROM with msmtool but since my device is TMO , can you make a conversion?
[OnePlus 8T Guides, News, & Discussion] leting130:
我也处于这种情况。你解决了吗
[OnePlus 8T Guides, News, & Discussion] Olaxodic:
Someone please give a reply on this
[OnePlus 8T Guides, News, & Discussion] mofinheim:
THANK YOU VERY MUCH 😍

This worked on my OnePlus 8t kb2007 using nameless 13
[OnePlus 8T Guides, News, & Discussion] raven911:
My 8T bootloader is locked, and unrooted. Is there any way to do this without needed to unlock bootloader (and therefore wipe my device)?

Thanks!
[OnePlus 8T Guides, News, & Discussion] Rootk1t:
I think no. To flash abl.img from beta OOS you need unlocked bootloader, and for changing props you need root permissions.

But i read that you can lock bootloader straight after flashing one from OOS beta, though i didn't test it myself.
[OnePlus 8T Guides, News, & Discussion] urover:
Are these commands to enable DSDS without flashing modem and installing magisk module?
[OnePlus 8T Guides, News, & Discussion] just4sc:
Can you detail how that's done? I tried pulling the build.prop and the command says it's successful I can't seem to find the file in my windows laptop. Thanks!
[OnePlus 8T Guides, News, & Discussion] just4sc:
NM. I was able to do it via ADB shell and it looks like it's working. Just wondering if it sticks or do I have to it every time. If so, I'll need to find out how to edit build.prop. Try doing so via ADB but can't seem to pull the file to local. Says it's sent but I don't see the file locally.
[OnePlus 8T Guides, News, & Discussion] urover:
I'm on LineageOS20.

I just ran these command and didn't run steps in the first post.

I can see both SIMs but the 2nd SIM slot does not accept/send any sms. Both slots share the same IMEI.

What's the possible issue here?
[OnePlus 8T Guides, News, & Discussion] Rootk1t:
It depens on what base OOS ROM you have installed.

If OOS13, try to flash abl.img from OOS F.10 beta.
[OnePlus 8T Guides, News, & Discussion] urover:
Thanks. Base ROM was OOS13-EU.

I just went back to OOS13-EU since I didn't like Lineage and Evolution-X. Got dual-SIM working by flashing the firmware flasher from another thread.. which flashes abl.img like you said.
[OnePlus 8T Guides, News, & Discussion] Speedwagon98:
Disregard. Flashing the abl.img worked wonderfully on LOS20
[OnePlus 8T Guides, News, & Discussion] sunmast:
I'm running LInageOS 20 on my T-Mobile 8T (KB2007) phone and trying to enable dual SIM functionality following the instructions here. But it's not working. I've tried all the things mentioned in this thread so far:

Download/install the Global modem: https://www.androidfilehost.com/?fid=2188818919693783632

Download/install the dsds magisk module: https://www.androidfilehost.com/?fid=2188818919693783509

setprop persist.vendor.radio.multisim_switch_support true

setprop persist.radio.multisim.config dsds

The phone can recognize the 2nd SIM, but can't send/receive SMS.

I don't know where to get the abl.img mentioned above. I've tried to use the one extracted from a global rom, but it doesn't change anything. Any anyone help? Thanks!
[Touch Diamond, MDA Compact IV General] aidanbree:
I have recently upgraded to Dutty's 1.8 ROM and have reinstalled all my usual applications but for some reason the phone keeps dialing up an internet connection. When I terminate the connection it starts again after a few seconds.

I have set my mail receive to manual and checked around the other apps I use (Funambol etc) but I cannot discover which application is requesting a network connection.

Has anyone got any ideas how to resolve? My battery life is shocking due to the connection always being on.

Cheers

Aidan
[Samsung Galaxy Note 10+ Questions & Answers] SiqrCarnbon:
Hi All,

I've got a Note 10+ 5G and was wondering how would one go about rooting this device on the latest Samsung firmware

N976BXXU6FUBD​

The guides that I have seen such as Dr.Ketans thread, instruct to flash a boot loader image that on his media fire page. does not match the firmware I'm running.

As I wouldn't want to flash anything that would break the phone, I'm wondering if someone can give me a method on how to root the stock rom.

thanks
[Samsung Galaxy Note 10+ Questions & Answers] hengybengy:
Hi, I am in exactly the same boat, did you solve it and get your sm-n976b rooted and if so how, Please and thanks/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Hussainbukhari:
Is there any estimate, when will the custom roms arrive?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] dirtytwo:
On Monday, 4:12 AM
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] osemoka:
Real time is like 3 months ig for first stable ones.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Jinzuken:
Is this even a question? Sir, you'll need to wait for the devs to release here or go to their respective website as you probably know it and ask there on their telegram channel about your question. From there, you'll get your answer not here
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
Soon™️
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ineedroot69:
i can compile TWRP for poco f3 but i don't want to use my device as guinea pig also i'm scared of bootloop also not confident enough on my skill compiling TWRP <: i guess ill wait for official twrp release for it
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Hussainbukhari:
This is a question because I am not asking about a particular ROM or anything. I am just asking generally that how much time is taken after the device is released to the public for the CUSTOM ROMs to come out.😊