yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A50 Questions & Answers] home_is_where_the_csc_is:
Fudge. I thought it meant that the protection is enabled. Not that it's locked. I believe DrFone triggered it. I thought the flashing just failed but not that it triggered a lock. For the DrFone it did give an error or something.

I would have expected that flashing the normal firmware would also have failed if it was actually locked. So wrong assumption there? It didn't give an error for the normal firmware.

So it does allow the flash but at next boot detects it and locks? Wouldn't the WARRANTY_VOID be non-zero in that case?

Yeah I've seen the devices for about 300$. I was thinking worst case I could still sell it afterwards. But I didn't count on a license for the software as well :(

So this will get expensive quite quickly. Problem with the data is that I probably don't need it but in case there's some damage somewhere I have some picture proof (it usually never happens but you never know). And some personal pictures. So it's difficult to put a value on :)

Today I went to a shop just to test if the battery is at fault. He swapped the battery and it's still the same behavior (although I couldn't trigger a reboot at the boot screen).

I indeed never unlocked the OEM and USB debugging since I know with these data can be more easily recovered when loosing the phone (which of course now is a disadvantage). Anyway in hindsight I could have enabled it flashed drfone on it and recover all the data easily ^^

In regards to modded/patched odin and "engineer" firmware: isn't this risky in itself as these will not be official releases of course.

Once again I appreciate you taking the time to bring some more clarity on what paths I can follow. Seems for now buying the JTAG is of the list.

EDIT: what I see from engineering firmware is that it will also trigger factory reset?
[Samsung Galaxy A50 Questions & Answers] SubwayChamp:
No,you can flash almost any firmware always that the compatibility allows it, FRP doesn´t play a role in that early stage.

Yes, FRP (in case it is) doesn't allow booting normally to protect the data BUT if you somehow can format data you should be allowed to boot at least to the settings menu prompting you to identify your self with the Google account that is in the device.

No, by flashing wrong firmware always that they are stock/official this wouldn't break the Knox security, the warranty is a different thing, it comes from the policy of a certain company and can be ruled in this or that way I mean if you take the device in this state obviously they will diagnose it like an attempt from the user and not an issue from the device itself.

Sorry, this part is hard enough to predict completely, some ENG firmware could perform a factory reset BUT if you take a look on they, and it hasn't some other files than boot and system and if they are the same firmware release that was previously onto your device then it wouldn't factory reset it BUT to be honest you need some kind of luck on that, Why? ENG firmware are known to force a device to boot no matter what they have to do, and one of the first reason to not booting a device it is that the data is protected.
[Samsung Galaxy A50 Questions & Answers] home_is_where_the_csc_is:
I thought about this again and it seems kind of odd that the FRP lock would not allow the OS starting to the bit where it's actually asking to authenticate to your google account. And also that it wouldn't allow me to go to the recovery mode where I can factory reset the system after which FRP lock probably asks me for the details.
[Samsung Galaxy A50 Questions & Answers] SubwayChamp:
From what I followed your issue, this is what I think:

Your device did get a failed update by itself, of course, a failed update will take it to a boot loop, after that you flashed a firmware; at this point the better is formatting data, did you know if it was the same exactly firmware or newer? Because a downgrade is not allowed also as you couldn't enable previously the USB debugging and OEM unlock Samsung detected like an unofficial attempt to alter the firmware, at the time to flash through Odin you doesn't have to see in the download screen some warning message from RMM/KG prenormal state or similar, this is why Knox doesn't allow device to boot, the only way available in this condition will be download mode, not system, not safe mode, not recovery.

Formatting data, as I said to you previously, essentially is the main task assumed by Samsung/Google to protect the data, I don't think you can recover your device without get of rid of that. The better solution will be finding an engineer firmware and flash it.
[OnePlus Nord N200 5G] Devildog78965:
I have a Nord n200 5g I got from T-Mobile the day it came out. My system is taking up 44gbs of storage and I'm not sure how to solve this without factory resetting it. I've seen similar problems like this with other phones and the oem_log being an issue. I have already tried deleting all logs with the one plus log kit app and I wiped system cache aswell. If anyone has any ideas what could be causing this issues I would appreciate it alot.
[OnePlus Nord N200 5G] tmchan1962:
On my N200, the system only takes 11GB. Try to reset the phone to see if it goes back to 11 GB. If not, contact one plus for replacement. I
[OnePlus Nord N200 5G] jdramseur2:
I found the files that seem to be increasing the System storage under /data/vendor/ramdump/

Filenames are "ramdump_modem_YYYY-MM-DD_HH-MM-SS.elf" (269 MB each added at a 5 per day clip)

In order to find and delete these, I unlocked the bootloader, gained root access, installed SD Maid (Pro Version), and used the Storage Analyzer.

The question is for those with stock T-Mo ROM, can OnePlus identify the issue and provide a cleanup solution or stop producing the files?

I added this to Feedback > Suggestions under the OnePlus Community Forums here:

OnePlus Community

Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.

forums.oneplus.com
[OnePlus Nord N200 5G] inspron:
Life saver tip here. Worked great. I spent hours searching until I got to your comment. I was able to take 107GB of system usage down to 23GB.
[OnePlus Nord N200 5G] EnumC:
Once you have your bootloader unlocked (See edale1's post), you can get started!

Disclaimer:

* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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.
* Your warranty will be void if you tamper with any part of your device / software.

You first need to acquire a copy of your boot image. If you don't have the stock firmware package, you can extract it by following the steps in my previous post here: https://xdaforums.com/t/full-rom-du...n-gaining-root-access-without-magisk.4321559/

For reference, Here's the stock boot image for DE2118 on build 11.0.1.5.DE18CB, as well as the already Magisk patched version. This has only been tested using the T-Mobile variant of the device. You're welcome to give it a try, but please report your result in the comments section along with your device model number.

If you decide to attempt the patched version, skip to step 5.

1. Get the latest magisk apk from https://github.com/topjohnwu/Magisk/releases

2. Install the apk on your device.

3.

adb push boot_stock.img /storage/emulated/0/Download/

3. Open the magisk app on your phone, select the boot image from your Download folder, and patch the image.

4. Now run

adb pull /storage/emulated/0/Download/name_of_patched_boot

. This will store the new boot image to your PC's currentl directory.

5. Reboot to fastboot by running

adb reboot bootloader

6. Now temporarily boot from the patched boot image FIRST to ensure your device still boots by running

fastboot boot name_of_patched_boot

.

7. Once your device boots, open the Magisk app to check that magisk has been installed successfully.

8. Reboot to fastboot again by running

adb reboot bootloader

9. Run

fastboot getvar current-slot

to get your current active partition slot. If it's A, then run

fastboot flash boot_a name_of_patched_boot

. If it's B, run

fastboot flash boot_b name_of_patched_boot

10. Run

fastboot reboot

to get back to the system
[OnePlus Nord N200 5G] alarmdude9:
All I can say is wow.............
[OnePlus Nord N200 5G] SMcC2:
Thank you!
[OnePlus Nord N200 5G] ttar ttar:
Thank you! Have been waiting for it since June 25!
[OnePlus Nord N200 5G] edale1:
Nice!

So we pretty much just have to wait for a TWRP release and the stock ROM now, right?
[OnePlus Nord N200 5G] EnumC:
Stock ROM is uploading, and it should be up on the previous thread shortly (at least the T-Mobile ROM).
[OnePlus Nord N200 5G] PopCaps1996:
thank you so much! i was able to flash magisk patched boot.img after booting patched img trough fastboot to make sure it worked on my metropcs variant! i am now rooted on stock rom with latest updates!
[OnePlus Nord N200 5G] edale1:
You have TWRP working on the N200?
[OnePlus Nord N200 5G] PopCaps1996:
No! I'm sorry I have both OnePlus n200 an n10 metro. I'm getting confused between the 2 lol
[OnePlus Nord N200 5G] EnumC:
I'm working on this also, but still running into roadblocks. Got a majority of the core features working, including booting to TWRP and most of the mounting points. But userdata decryption is still not working. If anyone knows about the flags needed in BoardConfig and recovery.fstab to mount userdata with encryption, please PM.

[ 208.269528] [19700113_12:54:27.554867]@6 F2FS-fs (sda16): Magic Mismatch, valid(0xf2f52010) - read(0x6421a6eb)
[ 208.269535] [19700113_12:54:27.554876]@6 F2FS-fs (sda16): Can't find valid F2FS filesystem in 1th superblock
[ 208.269702] [19700113_12:54:27.555042]@6 F2FS-fs (sda16): Magic Mismatch, valid(0xf2f52010) - read(0x8dc24167)
[ 208.269705] [19700113_12:54:27.555046]@6 F2FS-fs (sda16): Can't find valid F2FS filesystem in 2th superblock
[ 208.269928] [19700113_12:54:27.555269]@6 F2FS-fs (sda16): Magic Mismatch, valid(0xf2f52010) - read(0x6421a6eb)
[ 208.269932] [19700113_12:54:27.555273]@6 F2FS-fs (sda16): Can't find valid F2FS filesystem in 1th superblock
[ 208.270096] [19700113_12:54:27.555437]@6 F2FS-fs (sda16): Magic Mismatch, valid(0xf2f52010) - read(0x8dc24167)
[ 208.270100] [19700113_12:54:27.555441]@6 F2FS-fs (sda16): Can't find valid F2FS filesystem in 2th superblock

recovery.fstab

/data f2fs /dev/block/bootdevice/by-name/userdata flags=display="Data";fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption

BoardConfig.mk

PLATFORM_SECURITY_PATCH := 2099-12-31
VENDOR_SECURITY_PATCH := 2099-12-31
TW_INCLUDE_CRYPTO := true
TW_INCLUDE_CRYPTO_FBE := true
TW_INCLUDE_FBE_METADATA_DECRYPT := true
BOARD_USES_METADATA_PARTITION := true
[OnePlus Nord N200 5G] xstahsie:
Thanks so much for the patched boot img file. It worked great. Flashed it on two phones and both phones are working great 👍
[OnePlus Nord N200 5G] Lossyx:
On step 6, just go to magisk manager and direct install. And there is no need to specify a slot when flashing with fastboot.
[OnePlus Nord N200 5G] Lossyx:
Seeing the same on 8/Pro, but haven't found a solution. Bigbiff tried spent some time trying to fix but no luck.

Honestly I don't know more than that. If you haven't already you can join twrp zulip and ask there
[OnePlus Nord N200 5G] AiM2LeaRn:
According to @theincognito as far as with how the Oneplus8 was released... the 8 and 8 pro uses ICE encryption and 8t and later use aes-256. Perhaps something similar with the OnePlus Nord N200 Tmobile Variant where the encryption algo was slightly changed? maybe you can MSG @theincognito and perhaps maybe he can shed some insight as to his findings with Oneplus encryption regarding helpful insights to recovery dev build for OnePlus device recovery
[OnePlus Nord N200 5G] EnumC:
The issue is even with the original config from stock recovery.fstab:

/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc

It still exhibits the same issue. And it looks like he also used the stock fstab entry. I'm looking through some of the chat history for OP 8T/9R and see if I can pick up anything atm.
[OnePlus Nord N200 5G] mingkee:
BOOM!

All we need is system dump and snatch boot.

I'll do it once I got home even I can do it with other rooted phone with adb host installed
[OnePlus Nord N200 5G] lzgmc:
For the FBE decryption issues, have you tried looking at the TWRP device tree for the Nord N10? I see a bunch of extra files related to decryption which could help.
[OnePlus Nord N200 5G] mingkee:
The way I flash patched boot is just

fastboot flash boot

Press space once, and drag and drop patched boot onto command window, and press enter
[OnePlus Nord N200 5G] EnumC:
Thanks for including a link. Yes, I'm currently attempting to integrate the same common device tree that repo also has. Got the scripts running without critical issues & made sure all the FBE binaries' dynamically linked libraries are included. TWRP still not decrypting properly and fails very early:

I:Unable to decrypt metadata encryption
I:FBE setup failed. Trying FDE...DEBUG:PrepDecrypt::Running PrepDecrypt script for TWRP...
E:fde::get_crypt_ftr_and_key::Unexpected value for crypto key location:
E:Error getting crypt footer and key
...
I:PrepDecrypt::File Based Encryption (FBE) is present.
DEBUG:PrepDecrypt::SDK version: 30
DEBUG:PrepDecrypt::DEFAULTPROP variable set to prop.default.
DEBUG:PrepDecrypt::A/B device detected! Finding current boot slot...
DEBUG:PrepDecrypt::Current boot slot: _b
DEBUG:PrepDecrypt::No recovery partition found.
I:PrepDecrypt::SETPATCH=true
DEBUG:PrepDecrypt::Build tree is Oreo or above. Proceed with setting props...
DEBUG:PrepDecrypt::Temporary vendor folder created at /v.
DEBUG:PrepDecrypt::vendor mounted at /v.
DEBUG:PrepDecrypt::Vendor Build.prop exists! Reading vendor properties from build.prop...
DEBUG:PrepDecrypt::Current vendor Android SDK version: 30
DEBUG:PrepDecrypt::Current vendor is Oreo or above. Proceed with setting vendor security patch level...
DEBUG:PrepDecrypt::Resetprop binary not found. Falling back to setprop.
DEBUG:PrepDecrypt::Current Vendor Security Patch Level:
E:PrepDecrypt::setprop failed. Vendor Security Patch Level unchanged.
DEBUG:PrepDecrypt::prop.default update successful! ro.vendor.build.security_patch=2021-07-01
DEBUG:PrepDecrypt::Temporary system folder created at /s.
DEBUG:PrepDecrypt::system mounted at /s.
I:Can't probe device /dev/block/sda16
I:Unable to mount '/data'
[OnePlus Nord N200 5G] Zwitterion:
This! Much easier:

1. flashboot boot [patchedbootfilename.bin]

2. Once booted, go to Magisk and do Direct Install.

3. Done.
[OnePlus Nord N200 5G] AiM2LeaRn:
i granted root access to both solid explorer and root explorer

HOWEVER...

i cant seem to edit , delete or replace files in the SYSTEM. anyone else having issues? i tried using both root explorer and solid explorer. Anyone have any idea why i cant make changes to system files?
[OnePlus Nord N200 5G] AiM2LeaRn:
so i figured out why i cant change system files even with root. So ive narrowed it down to dm-verity... has anyone successfully disabled dm-verity? if so care to post instructions? i see instructions for other devices, but im looking for someone that has successfully done it for this device, please dont post instructions to a different device

127|OnePlusN200TMO:/system/etc # rm apns-conf.xml
rm ro apns-conf.xml (y/N):y
rm: apns-conf.xml: Read-only file system

1|OnePlusN200TMO:/system/etc # remount
Please disable dm-verity
remount failed

10|OnePlusN200TMO:/system/etc #
[OnePlus Nord N200 5G] edale1:
I think this post has the info you're looking for.

https://xdaforums.com/t/disable-verity-which-vbmeta-image.4328673/post-85580099
[OnePlus Nord N200 5G] Lossyx:
If you're on stock you have to use something like this https://xdaforums.com/t/tool-win-li...ake-partitions-rw-in-super-partition.4120963/ .
[OnePlus Nord N200 5G] AiM2LeaRn:
thanks i found this as well

https://xdaforums.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
[OnePlus Nord N200 5G] cezar1:
Hi.

I want to root N200 according to your instructions. This is the safest method in my opinion. Some days ago my phone got an OTA-update to 11.0.1.7.DE18CB. I think the new version of the stock boot image is different from the old one that you published in the first post. How can I get or where can I find the stock boot image from the new build 11.0.1.7.DE18CB?

P.S. DE2118 model of the device. T-Mobile variant of the device. Bootloader unlocked.
[OnePlus Nord N200 5G] PopCaps1996:
11.0.1.7 magisk patched boot with or without twrp imgs

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com
[OnePlus Nord N200 5G] mingkee:
Can it revert recovery as well (flashed TWRP)?

In addition, may we have original (not patched) boot?
[OnePlus Nord N200 5G] Bob21lla:
Thank you for the help! 100% success on my end after getting my bootloader unlock key & such today...
[OnePlus Nord N200 5G] IdiotWithABox:
So here's my issue. I was able to figure out everything I needed to do for my slightly more updated device. I have the correct stock image and patched it using Magisk. I also made sure I had the name correct and that the patched image was in the correct directory. I get all the way to step six where I get this error:

I have tried searching for the answer on these forums and a variety of others. Any help would be greatly appreciated, I am extremely new to the android part of the technology scene. (If any more information would be useful please let me know what I can share)
[OnePlus Nord N200 5G] Link575:
I could be wrong but I don't believe they allow fastboot boot anymore if you are on A12, it has to be fastboot flash. The reason we were being told to use fastboot boot is so if there was an issue, it was only temporarily booting that image rather than flashing it.
[OnePlus Nord N200 5G] scanman0:
This guide is close to a year old and the N200 has been upgraded to Android 12 and ColorOS and this make the guide obsolete. The dialer codes have changed as well as the fastboot abilities.

I have the current root files/guide here for US OEM:

https://xdaforums.com/t/root-latest-a12-us-oem-c_18-ota-for-dummies-de2117.4484651/
[OnePlus Nord N200 5G] towardsdawn:
For T-Mobile DE2118 here is a full guide for rooting

If you don't have access to stock boot.img, this is how to get it. Otherwise skip to step 4 (I have uploaded DE2118_11_C.17 stock.img here. usually I try to upload to androidfilehost here but it's not working for me today, will try again later)

1) If magisk is installed, uninstall magisk

2) get active boot slot with [CODE}adb shell /bin/getprop ro.boot.slot_suffix[/CODE], the INACTIVE boot slot would be the opposite letter (so if active was _a then inactive is _b)

3) click "try again" and "resume" for system update. wait for "restart" button

If magisk was installed and still running:

a) before hitting "restart",

adb shell su

then copy the INACTIVE boot slot to downloads

dd if=/dev/block/bootdevice/by-name/boot_aORb of=/sdcard/Download/boot_stock.img

b) continue to step 4 below

If magisk was not installed previously or your device restarted automatically during update and magisk is no longer running

a) finish system update if necessary, restart device

b) load DSU Sideloader with phhusson GSI with root (I use arm64-ab-floss.img.xz)

c) restart device to load the DSU

d)

adb shell su

then copy the INACTIVE boot slot to downloads

dd if=/dev/block/bootdevice/by-name/boot_aORb of=/sdcard/Download/boot_stock.img

e) the file will be discarded when we restore original android so make sure to

adb pull /sdcard/Download/boot_stock.img

to your computer

f) restart to original android, push stock image back with

adb push /sdcard/Download/boot_stock.img

g) continue to step 4

4) finish system update if it is unfinished, restart device

5) run magisk, "select & patch a file", select boot_stock.img

5)

adb pull magisk_patched.img

pull patched img to your computer (it's easier to rename the file instead of trying to type in the default name magisk gives it)

6) reboot to fastboot

adb reboot fastboot

7)

fastboot flash boot magisk_patched.img

8) hit restart in fastboot
[OnePlus Nord N200 5G] scanman0:
I put the latest boot.img on Android File Host.

It seems to upload best for me if I choose the VA1 server.

boot_11_C.17_DE2118_tmobile_stock.img​

boot_11_C.17_DE2118_tmobile_MagiskV25.2 patched.img​

I also maintain the latest boot.img files for the US/OEM DE2117 version in this guide:

https://xdaforums.com/t/root-latest-a12-us-oem-c_18-ota-for-dummies-de2117.4484651/
[OnePlus Nord N200 5G] radford.will:
Thanks, worked well. I followed steps 1-10 and skipped step six. C16 firmware version
[Samsung Galaxy Note 9 Questions & Answers] pTeronaut:
Since when have we been able to uninstall the Facebook app?
[Samsung Galaxy Note 9 Questions & Answers] blackhawk:
I can't, it's factory load on my Note 10+.

Package Disabled, always.
[Samsung Galaxy Note 9 Questions & Answers] pTeronaut:
I was having issues with the app not loading posts in groups, so I went into settings on my Note 9 (snapdragon, so unrooted stock rom with August update) to reset it via clearing the data, and saw 'Uninstall' where 'Disable' usually was.
[Samsung Galaxy Note 9 Questions & Answers] blackhawk:
Cool. Take out the trash.

Just tried it on my OS version. Couldn't touch it.

Package disabled it... as usual.

FB is pure malware, destroyer of worlds.
[Samsung Galaxy S9  Questions & Answers] SiMkOo:
Hi there!

It's been a few years since my I flashed Firmwares on my S6 with Odin so please forgive me if I'm not quite up to date on that topic.

Background: For installing custom emojis on my S9 I wanted to use Zfont, however, this doesn't work. I did some research and it is said that zfont won't work on debloated Samsung firmwares. Next step would be temporarily re-bloating my debloated device. I tried, however, I couldn't manage to reinstall all the Samsung apps since I don't rebember all of the packages that I removed and the few that have been recovered were not enough to make Zfont work.

In the old days you just could flash the stock rom on a working device to get all the uninstalled factory apps back. Is this possible with Android 10 and OneUI 2.5? Will my data be wiped if I flash it with the current firmware? Do I need OEM unlock?
[Samsung Galaxy S9  Questions & Answers] spawnlives:
Download latest firmware. Unzip it, there will be 5 files to flash with Odin.

Home_csc - will keep your data

csc - will wipe your data
[Samsung Galaxy S9  Questions & Answers] SiMkOo:
Thank you for the info.

View attachment 5389245View attachment 5389247

This should be the correct firmware then, right?
[Samsung Galaxy S9  Questions & Answers] spawnlives:
Yes

When looking for firmware use your baseband version number in about phone-software info as a base to look for firmware on the net. Just bare in mind you can't downgrade (bootloader/binary) firmware ( 5th number/letter from right of firmware name).

You can also use frija pc tool to download lastest firmware. It will be quicker than sammobil. Your have to search here on xda as i can't post links at the moment.
[Samsung Galaxy S9  Questions & Answers] SiMkOo:
The flashing process went fine. Unfortunately, it didn't bring back the disabled apps. Probably because they have been disabled via adb for user 0, which means that they're still on that device but inactive for the current user.

At this point, I just don't want to spend any more investigating which missing apps causes zfont not to work.