yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro Questions & Answers] Ju5t3nC4s3:
All the testing has led me down many roads. Is the process I have found a faster bootloader unlock. Just need to be carefull and back up your efs first. And also have lots of new info how the tmobile simlock operates. To start out the bootloader unlock took way to many steps.so I found a moded msm ,that if you back up your modemst1 and modemst2 first eather with edl.py or with qfil and the proper firehose. All you need to do is erase them after u back up and then the oem-unlock will work. PLEASE BACK UP EFS FIRST. Then u can restore by twrp. And one of the major things I found with the sim lock is, a esim or they call it a virtual sim. (REDTEAMOBILE) this is OnePlus Roaming. It has been in sense android 9 tested with OnePlus 6. But for tmobile how they are using it ,only makes sense the reason they can only have one sim slot active.With the esim active it changes the sim profile I'd and blocks any others . Making it look like there is already a sim. And they are hiding all this behind a VM called India. A dialer code can switch u to this.All the GSM core is still all there with the binder.plus they are hiding the Field in the bottom battery states. And a big part of it all is the HW test in the engineering app. But least to say they have thaught about this lock.it is the reason it has not been broken.like all the others.I have found many vulnerabilitys, plus a new way to inject code or hook the methods in the apps. That I don't know if anyone has even seen or tried. I'm gonna stop here for now. For my head don't explode. If there's anyone that would like to help and is truly interested in reversing.and not just looking for a unlock, please hit me up.
[Android Head-Units] Mr.Armaani:
Hello,

This is my Honda Android Navigation Unit which stuck boot logo as you see picture below. Also I am uploading its software and hardware version etc details.

Anyone who can help me to get out of this boot loop. This unit have no physical button instead of touch buttons and small reset pin button.

Stuck on Boot Logo as seen below after factory reset

Software and hardware versions

Model: CA9001-WL

MCU Version: V1.0_CA9032-WL__K7D0945

OS Version: t3_Javelin=eng 6.0.1 MMB29M 20190723 test-keys 20190723

U-Boot 2014.07

KERNEL version: 3.10.65 liul@hwjst #1
[Touch Diamond, MDA Compact IV ROM Development] H3PO:
Hey Developers! Why don't you put your latest cooked ROMs into the wiki page so that one can easily get an overview of what's available?
[Xiaomi Redmi 8A Dual] sdm439 olivewood:
View attachment 5296879

Pixel Experience Android 11 for olivewood

* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.

What is this ?

PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation). Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device

Based on Android 11

Whats working?

Wifi

RIL

Mobile data

GPS

Camera

Flashlight

Camcorder

FMradio

Face unlock

NFC

Lights

Sound / vibration

volte

Known issues

You tell me

NO NEED OF FLASHING GAPPS.IT HAS PREBUILT GAPPS

Follow Instructions Carefully otherwise you will get bugs in the rom

• Boot into any custom recovery

• Go to advanced wipe

• Wipe all leaving internal storage,otg,sdcard

• Flash Q vendor

• Flash rom.zip

• Flash cherry kernel and incall speaker phone bug fixer zips [ Given in downloads ]

• Flash custom rom volte (Given in my telegram group)

• Format data yes

• Reboot to system

• Enjoy

Downloads

Rom link ;- click this [ Sign in to gdrive ]

Cherry kernel :- click me

Call Audio speaker fix :- click this [mount vendor paste these files to vendor/etc in recovery reboot to system ]

Join my group for latest updates and for help :- https://t.me/olivewood_devs and our updates https://t.me/olivewood_updates

Sources

Kernel source :- https://github.com/SimplyJoel-LTSC/android_kernel_xiaomi_sdm439/tree/a11/master

Device tree :- https://github.com/Aghora7/device_xiaomi_olivewood-1.git

Common tree :- https://github.com/Aghora7/device_xiaomi_sdm439-common-1.git

Vendor tree :- https://github.com/Aghora7/vendor_xiaomi_olivewood_32.git

Credits

@Aghora7 for his device,vendor,common trees

@simplyjoel for kernel source
[Motorola Moto G100 / Edge S] PEACH-PIT:
My native language is not English.

I am sorry, but I do not understand native English.

This operation is very dangerous.

Enables writing to "/".

All at your own risk.

Devices preinstalled with android 10 or later are

Even if you root the device, it will still be r/o and you will not be able to edit it at all.

By running this script, you can r/w the system itself.

We will use makeSystemRW and makesysrw_repair created by lebigmac.

You will need a linux system to run makesysrw_repair.

[SCRIPT][Android 10+] Universal Mount System read write R/W

I would like to thank lebigmac for creating this script.

1. After unlocking the boot loader and becoming root, disable all vbmeta.

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

2. Copy makeSystemRW to /data/local/tmp of edge s.

3. Run makeSystemRW.

adb shell
su
chmod +x /data/local/tmp/makesysrw_1.31/makesysrw.sh
setenforce 0
./data/local/tmp/makesysrw_1.31/makesysrw.sh size=20

An error will occur here and it will fail.

You need to use makesysrw_repair.

4. Run makesysrw_repair.

Copy makesysrw_repair, open a terminal at the location where you copied it, and run the code.

sudo bash makesysrw_repair.sh

We have confirmed that this command is executable on Ubuntu.

5. Finish.

You are now done.

You can mount it with r/w using the root explorer.

Make sure that you can create new files and folders.
[Motorola Moto G100 / Edge S] nexus7lte:
Would like to do this but why hasn't anyone else posted on this thread regarding success or fails?
[Motorola Moto G100 / Edge S] Beetle84:
I guess no one tried it, or they did and never commented 🤷
[Motorola Moto G100 / Edge S] lebigmac:
Thank you for your interest in my SystemRW/SuperRW feat. MakeRW project. ;)(y)

Yes I got the project thread closed while I was enjoying the summer holidays. Everyone needs a well deserved break every once in a while. I'll have it reopened as soon as I'm ready to publish the new version of my script. Hopefully soon ;)(y)

It's looking like a fall release rather than a summer release though... Time flies... 🕗

The old version 1.32 works in A10, A11 and some folks even got it to work in A12 simply by disabling the sdkCheck() function :)

The new version should have A13 support straight out of the box if everything goes according to plan. Wish me luck!🍀 Thanks! (y)

Cheers 🍻
[Motorola Moto G100 / Edge S] nexus7lte:
i would like to try this just to get rid of the annoying Android 12 update message.

Evan after disabling google play services notifications and freezing the OTAs, I still cant stop

com.motorola.ccc.ota and I assume thats because its on a read only portion, right? ADB commands didnt work.
[Motorola Moto G100 / Edge S] nexus7lte:
My error in adb or terminal is_

u

:/ # pm disable com.motorola.ccc.ota

Exception occurred while executing 'disable':

java.lang.SecurityException: Cannot disable a protected package: com.motorola.ccc.ota
[Motorola Moto G100 / Edge S] lebigmac:
Hi @nexus7lte

Did you get my SystemRW/SuperRW feat. MakeRW script to work on your Android 12 device?

Is it the Motorola Moto G100 ? How do you like it?

Yeah disabling those protected system packages can be tricky sometimes. I'm sure it's possible somehow.

On Xiaomi devices we also got this Xiaomi security app and I can't disable it even as root with full rw access but I'm sure a true expert could do it ;)(y)
[Motorola Moto G100 / Edge S] Vipxpert:
Well... I tried your script on my new Realme GT Neo 3T android 12. It booted but seems like nothing changed. Mounting system still says "mount: '/system' not in /proc/mounts"
[Motorola Moto G100 / Edge S] lebigmac:
Hi. That's a nice device you've got! :D(y)

Are you sure you're calling the command as root?

Usually you get this error message if you try to remount something as shell user...

Or you're trying to remount the wrong path. Try mount -o remount,rw /

Without seeing any screenshots or at least your log it's very difficult to tell what's wrong on your device from here. Did you check if my script successfully removed the infamous shared_blocks read-only feature from your phone? :unsure:

adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done
[Motorola Moto G100 / Edge S] Vipxpert:
Here I have flashed it through EX kernel manager since there's no TWRP for Neo 3T or even a forum yet. Do u need a full log somewhere though?
[Motorola Moto G100 / Edge S] Vipxpert:
Ah here I found
[Motorola Moto G100 / Edge S] Vipxpert:
Also I tried copy-paste your code. It gives a bunch of nonsenses hmm...
[Motorola Moto G100 / Edge S] Mr Hassan:
Same this result for me even with your command

adb shell

su

for a in /dev/block/dm-*; do tune2fs -l $ etc

Or if i flashed rw fixed_super.bin

Device not able to boot anymore
[Motorola Moto G100 / Edge S] lebigmac:
Hi @Vipxpert thanks for your log and for the screenshots! (y)

I don't understand why the script didn't detect your shared_blocks read-only feature... :unsure:

Are you saying the script didn't do anything and you flashed the resulting super_fixed.bin to your super partition and phone still boots in read-only mode?:unsure:

Oh yeah right I forgot that OnePlus devices usually have dozens of useless pseudo (cow) partitions in its partition table...

To find out if your device has got the infamous shared_blocks read-only feature please try this updated code. Good luck! (y)

adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol" -e "mounted on"; done

Or like this:

adb shell
su
for a in `seq 0 5`; do tune2fs -l /dev/block/dm-$a | grep -e "feat" -e "vol" -e "mounted on"; done

@Mr Hassan bootloops are always very sad :(. Do you have any idea why it happened? :unsure:

Try to boot into TWRP and pull any log files to find out reason for error and then reflash original stock super.img and phone should boot again ;) Good luck! (y)
[Motorola Moto G100 / Edge S] Mr Hassan:
I even try stock super but device wont boot until flash back stock

And hes oneplus have somekinda cow partitions etc

I see when i try flash its asked to delete all cow parts

Don't know what's this
[Motorola Moto G100 / Edge S] Vipxpert:
Yeh I did flash it with "fastboot flash super super-fixed.bin" and that took no effect ://

Anyways here're the results of your 2 commands. They seem not to end up well
[Motorola Moto G100 / Edge S] Vipxpert:
@lebigmac mention mention 👀
[Motorola Moto G100 / Edge S] lebigmac:
Well it looks like your /product partition does indeed have the infamous shared_blocks read-only feature.

I know that's a stupid feature but this is actually good news. This means new upcoming version of my script should be able to do the job ;)(y)
[Motorola Moto G100 / Edge S] Vipxpert:
Yess!! U're the hero thanks so much now I can debloat, fake Google daydream service, add AR supports, edit mixer_path.xml for volume and tons of stuffs. Oh I miss those time a lot ^^^
[Motorola Moto G100 / Edge S] Mr Hassan:
any any estimate of days or release date
[Motorola Moto G100 / Edge S] Mr Hassan:
heres the result form me

OnePlus8:/ # OnePlus8:/ # OnePlus8:/ # for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol" -e "mounted on"; done
Filesystem volume name: /
Last mounted on: /
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
Filesystem volume name: system_ext
Last mounted on: /system_ext
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-10
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-11
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-12
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-13
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-14
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-15
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-16
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-17
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-18
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-19
Filesystem volume name: product
Last mounted on: /product
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-20
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-21
Filesystem volume name: product
Last mounted on: /product
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-23
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-24
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-25
Filesystem volume name: vendor
Last mounted on: /vendor
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
Filesystem volume name: odm
Last mounted on: /odm
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-5
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-6
Filesystem volume name: product
Last mounted on: /product
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-8
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-9
1|OnePlus8:/ # The directory name is invalid.

@

lebigmac​
[Motorola Moto G100 / Edge S] Mr Hassan:
another command

Spoiler content hidden.

@

lebigmac​
[Motorola Moto G100 / Edge S] Vipxpert:
He doesn't need it anymore since he knows there's shared-block and he's going to include it in the next update anyways. Just telling guys in case people spam him with logs lol
[Motorola Moto G100 / Edge S] lebigmac:
Wait @Mr Hassan are you seriously trying to tell me that your OnePlus 8 device got both shared_blocks AND erofs read-only features? :unsure: Now that would be double read-only protection now wouldn't it... Or u got 2 different devices one with shared_blocks and the other one with erofs problem?!⁉️

And please post here your mount output and the cat /vendor/etc/*fstab* of the same OnePlus 8 device. Just put the output into [QU0TE] or [C0DE] tags or make screenshot (or upload it as .txt file here). Thanks! (y)
[Xiaomi Redmi 8A Dual] sdm439 olivewood:
View attachment 5296881

Project Sakura android 11 for Olivewood

* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.

What is this ?

Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.

Whats working?

Wifi

RIL

Mobile data

GPS

Camera

Flashlight

Camcorder

FMradio

Face unlock

NFC

Lights

Sound / vibration

volte

Known issues

Nothing

Follow Instructions Carefully otherwise you will get bugs in the rom

• Boot into any custom recovery

• Go to advanced wipe

• Wipe all partitions

• Flash rom.zip

• Flash Gapps (recommended)

• Format data yes

• Reboot to system

• Enjoy

Downloads

Rom link ;- click this

Gapps :- click this

Gapps-addon :- click this (recommended to flash before rebooting to system )

Join my group for latest updates and for help :- https://t.me/olivewood_devs and our updates https://t.me/olivewood_updates

Sources

Kernel source :- https://github.com/SimplyJoel-LTSC/android_kernel_xiaomi_sdm439/tree/a11/master

Device tree :- https://github.com/shield44/device_xiaomi_olivewood.git

Vendor tree :- https://github.com/shield44/vendor_xiaomi_olives.git

Credits

@Aghora7 and @sdm439dev for fixing trees and making them stable trees

@simplyjoel for kernel source
[Touch Diamond, MDA Compact IV General] lazerin:
Just a question for tomtom users. Is it possible to disable the gps and make it so it doesn't try to access it?

I know it's possible to just browse the map, but it still gets a lock on. I want to just browse the map without it trying to use the gps to maximise battery life if I can.

Thanks in advance!
[Touch Diamond, MDA Compact IV General] shtewps:
Sure, chose the wrong hardware or wrong com port in under the gps settings and the software wont use your gps because it wont know where to find it.
[Touch Diamond, MDA Compact IV General] lazerin:
Ah yes, but will it still keep trying to find the gps and thus continue draining the power further?
[Touch Diamond, MDA Compact IV General] MarcLandis:
most of the power is actually drained when GPS is active and not when TT is searching for the hardware.
[Touch Diamond, MDA Compact IV General] shtewps:
No it wont try to find the GPS and it will read "No GPS device".
[Introductions] Billkoa:
Hi. I'm a newbie when it comes to custom roms fpr phones. I decided to take the plunge with CRdroid on my Mi A1 since support ended more than a year ago. I'm hoping to learn more on this topic as I enjoy tinkering with all type of electronics including phones. I hope I can contribute to this forum in the future to help future newbies as well.
[Introductions] orb3000:
Welcome to XDA!

Here your devices section

https://xdaforums.com/c/xiaomi-mi-a1.7044/

Enjoy!
[Xiaomi Redmi 8A Dual] sdm439 olivewood:
" #DroidOnTime "

ROM Version: 5.2

Device: olivewood

Maintainer: shield44

Build Status: OFFICIAL

* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.

"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration.."

dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....

CLEAN FLASH/First Time Installation :

Download the latest build (Both Vanilla [Non-gapps] and Gapps builds are available)

First Make sure recovery is installed. (LineageOS recovery works fine as of now)

Reboot to recovery

Make nandroid backup (Not Necessary, but just in case if you lost somewhere)

Wipe Data, dalvik cache, cache, system, vendor, internal storage​

Format data --> yes

Reboot to system

DIRTY FLASH :

Download the latest build

Reboot to recovery

Flash the latest build

Wipe Cache

Reboot

Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.

Website - https://www.droidontime.com/devices

Complete Changelogs: https://changelogs.droidontime.com/

AOSP

Lineage OS

Pixel Experience

Dirty Unicorns

And all other open-source Devs/Teams.

Mohan CM - Founder/Core Developer

Iacob Ionut - UI, UX Developer/ Core Developer

Sipun Kumar - Developer/Maintainer

Special thanks:

Manish Bajpai - Web Developer

Important Links

If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM

dot OS source

dotOS-Device Sources

Telegram Group

Telegram Channel

Website

Downloads page

REPORTING BUGS !

As soon as the problem occurs, take a LOGCAT!

for more READ THIS

and do not forget to send it to us 😜

Contributors:

@sdm439dev

Source Code: https://github.com/DotOS

Kernel Source: - https://github.com/dotOS-Devices/kernel_xiaomi_olivewood

ROM OS Version: 11.x Android R

Version Information

Status: STABLE

Current Stable Version: v5.2

Stable Release Date: 11-10-2021​
[Xiaomi Redmi 8A Dual] sdm439 olivewood:
OFFICIAL Release!
[Xiaomi Redmi 8A Dual] callmebutcher101:
Safetynet failing. Thermal profiles not working.
[Xiaomi Redmi 8A Dual] hxudsh:
While trying to get it installed I'm getting a "Updater process ended with ERROR:255. Error installing ZIP file '/sdcard1/dotOS-R-v5.1.3-olivewood-GAPPS-202108111-0729.zip'" error, could anyone tell me what I'm doing wrong and how can I fix it?
[Xiaomi Redmi 8A Dual] bhavik0077:
How to flash this 5.2 rom, which recovery to use and while formatting data which format to choose ext4, sdcard, f2fs while format data?
[Xiaomi Redmi 8A Dual] sdm439 olivewood:
Join our telegram group https://t.me/redmi8aofficial
[Xiaomi Redmi 8A Dual] azmibey:
Location (GPS) doesnt working any fix ? (i cant add logcat.txt in here)
[OnePlus 7T Questions & Answers] j4g3rb0mb3d:
My mobile data no longer seems to work after updating to 11.0.0.2. Phone calls and texts still work - issue seems to be isolated to just mobile data. I'm using an international version of the 7T, on AT&T here in the states. If I downgrade back to OOS10 using the MSM tool, mobile data works again. I'm able to use a Google Fi sim with data on both OOS10 and OOS11. I tried wiping bluetooth, wireless, and mobile data with no joy. If I upgrade again from OOS10 to OOS11, mobile data breaks. Any ideas or troubleshooting tips?
[OnePlus 7T Questions & Answers] HueyT:
APN?
[Moto G10] xdaman-2021:
This thread has been merged into the moto-g10 info thread...

Admin, Please delete this thread.
[Moto G10] xanthrax:
thread closed
[Touch Cruise ROM Development] Serdce:
http://www.htc.com/www/supportdownloadlist.aspx?p_id=59&cat=all

It work on cooked roms?

Not working on my Polaris.ASerg.4.WM61.WWE rom
[General Questions and Answers] Vivek_9963:
I want to build Custom Kernel for My Lenovo Zuk z1 Device . For That I've Downloaded Kernel Source Code from Manufacture . But Problem is I can't find devicecode_defconfig like ham_defconfig file ham is my device code . Also I don't know further steps to compile Kernel , I'm just following One Youtube video . Can Anybody help me ?? Please