yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] AndyC76:
Logcat is the output of putting the phone into a recording mode, which will record all the interactions and internal operations of the phone, this will be useful to OnePlus if you log a fault with customer service.

It may be worth finding out who your authorized repair center is in your region, it will be on the OnePlus site, I can't seem to access it from here in the UK.
[OnePlus 9 Pro] aztonyusa:
I feel it's not a problem with the phone., it's a problem with the network. I had been using the OP9P on the Visible legacy plan for over 2 years with no problem. The problem started when Visible upgraded their network to what they call the Visible+ network and forced everyone over to it. Now according to them, my phone is not compatible with the new network.
[Wear OS Q&A, Help & Troubleshooting] Log@n07:
Hi, i own Fossil gen 5, it runs on wear os 3, which is pretty outdated comparing what a wear os 4 watch can do, i bought it last year it was on sale without knowing much about verious of wear os it runs or it supports in the future, now i feel it's useless, can anyone help me with some mods and tricks to make it work somewhat equal to wear os 4 watch?

Thanks 😄
[Wear OS Q&A, Help & Troubleshooting] rodken:
Feel free to visit hacks and tricks for WearOS here.

{Mod edit: Broken hyperlink fixed. Oswald Boelcke, Senior Moderator}
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
First to note that I (KPBHacker1kk) am writing this thread specifically on Samsung Galaxy A30S (sm-a307fn). If you are another samsung user, first read this full thread before doing any action.

DISCLAIMER - TAKE YOUR OWN RISK BEFORE DOING ANY ACTION. IF YOU DO ANYTHING WRONG, I WON'T BE RESPOSIBLE FOR YOUR ACTION. THANK YOU..

Before staring, make sure you have downloaded or own these things..

i) SM-A307FN Boot_Corruption_Repairer. Download it from here.

[If you want to know how to make the Boot_Corruption_Repairer file for any samsung mobile, just comment me and I will be there.]

ii) ODIN Flasher. Download it from here.

iii) You need a Windows OS (Windows 7 or higher) to do this.

Let's start---->>

I) At first, you need to go to download mode by pressing power and vol. down together.

II) Connect your device to your PC, open ODIN, tap on 'AP' (2nd option) and then navigate to Boot_Corruption_Repairer file then tap on flash. It will be flashing 3 or 4 files in your phone and then it will reboot your phone to your favourite LOCK SCREEN.

IF I MISSED OR WROTE SOMETHING WRONG, PLEASE REPLY ON THIS POST..

AND IF YOU LIKE THIS POST, YOU CAN ALSO REPLY..

THANK YOU..
[Samsung Galaxy A30s Guides, News, & Discussion] ze7zez:
You have not successfully included Boot_Corruption_Repairer.
[Samsung Galaxy A30s Guides, News, & Discussion] GalaxyA325G:
See also...

How To Guide How to un-freeze an unresponsive Samsung Galaxy A32 5G with reboot, reset, factory reset, odin mode, download mode, android recovery mode & debug mode​
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
Sorry for that. I have attached a link at the top of this thread..
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
My Samsung Galaxy A32 5G (SM-A346E), stuck in a boot-loop,

How do I make a Boot_Corruption_Repairer for this model - it has FW - A34EXXS5BXA1
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
Give me some time for preparing the file and thank you for replying 🙂🙂
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
Thank you for looking into this for me below is the history

Phone is one of my kids phone, so I don't have the full story on how the phone got into a boot-loop.

Feb 2024 major update - I'm assuming it was TEL-A346EXXS5BXA1-20240215203521 Region - TEL (Australia) Android 14 update from 13. Installed all right no issues

After a few days it went a bit strange,

battery 65% then 1 min later it was 5%, so my kid quickly charged it. - I told her at the time, try re-booting the phone a few times this might help. - She didn't,

a week later few of the app crashed (message popped up close app)

Same day One UI app crashed she clicked closed - the phone re-booted - then boot-loop ever since.

Currently I can boot the phone in recovery mode

Android Recovery

Samsung A34xdxx/a334x

12/SP1A.210812.016/A34EXXS5BXA1

I have tried

Wipe cache partition, no change still boot-loop.

Apply update from ADB - can only go as far as ADB - sideload - so no luck (as usb debug is not turned on)

Mount system does nothing

Repair apps - nothing

etc..

I can also get into Download mode - I have used Odin3_v3.14.4, Odin3_v3.14.1, Odin3_v3.13.1 for windows to to flash FW - used AP, BL, CP and HOME_CSC - Odin successful but still boot-loop (in fact there is one strange thing it does....)

After the Flash from Odin reboots One UI comes up Animation icon - message says 'erasing' for about 3 seconds then re-boots into a boot-loop.

I have also tried booting a laptop into mAid Linux ISO and used the Linux version of Odin - JOdin, JOdin" Next"

and heimdall - I could not get any of these to work at all - my current guess is I don't have enough space ISO is been booted from USB stick or enough RAM.

Based on the files in your download I have used Freya loaded up the AP for my phone and only selected Boot.img, Recovery.img, vbmeta.img.lz4 and flashed - again message was successful, but still boots in a boot-loop.

I was going to do recovery mode and - Wipe data / factory reset yesterday, but I came across your post that might help me .

Let me know if you need more information on what I have ready tried -
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
Have you reflashed the whole ROM after wiping Data, Cache, System Section?? Sometimes after wiping data and system it might fixed..
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
I have flashed the whole ROM - a number of times - but only after wiping Cache.

I haven't wiped Data yet - (ie. I haven't done a factory reset)

I guess this is the point, I'm trying to get past the boot-loop, with keeping all internal data, ie photos on the internal memory
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
If in the end the Boot Corruption Repairer, only works after factory reset then happy to do that - a factory reset might fix the boot-loop - I haven't tried yet.

Seeing the above post - I assumed the Boot Corruption Repairer would allow me to boot the phone without losing any data.

I have started looking into SP Flash Tool Download as I believe the chip-set is a Mediatek - Dimensity 1080 (6 nm)
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
YOU CAN TRY FLASHING THE WHOLE ROM AFTER WIPING DATA AND SYSTEM SECTION USING TWRP OR ANY OTHER CUSTOM RECOVERY..
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
THIS TRICK SHOULD BE WORK..
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
Phone is still under warranty, don't really want to do down TWRP track - if I did TWRP I need to wipe the data anyway.

I thought he Boot Corruption Repairer (as far as I can tell, isn't just a few files from the AP FW) allow you to get the phone booting while still keeping your data - ?

If not then I'll just go into recovery mode and do a factory reset -
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
So question is - will Boot Corruption Repairer fix the boot-loop and allow me to get into the phone while still keeping your data - ? -
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
I HAVE SAMSUNG A30S WHICH ALSO CAUSED BOOT-LOOP FOR A UNKNOWN REASON. IT TOOK ABOUT 2 TO 3 DAYS TO FIND THIS SOLUTION. THIS FILE WORKED ON MY PHONE WITHOUT LOSSING ANY DATA..
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
I THOUGHT IF SOMEONE HAVE THIS ISSUE AND SUCKED IN IT, SO I PERSONALLY WROTE THIS THREAD FOR THEM..
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
Cool,

Are you able to make a Boot Corruption Repairer for this phone ? SM-A346E (Samsung Galaxy A34 5G) ?
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
CAN I HAVE THE EXACT INFORMATION OF THE ROM YOU CURRENTLY FLASHED USING ODIN??
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
yep -

https://samfw.com/firmware/SM-A346E/TEL/A346EXXS5BXA1

Files are

- AP_A346EXXS5BXA1_A346EXXS5BXA1_MQB75866951_REV00_user_low_ship_MULTI_CERT_meta_OS14.tar.md5 - 8.4G

- BL_A346EXXS5BXA1_A346EXXS5BXA1_MQB75866951_REV00_user_low_ship_MULTI_CERT.tar.md5 - 4.5MB

- CP_A346EXXS5BXA1_CP25713132_MQB75866951_REV00_user_low_ship_MULTI_CERT.tar.md5 - 39.6MB

HOME_CSC_OLM_A346EOLM5BXA1_MQB75866951_REV00_user_low_ship_MULTI_CERT.tar.md5 - 155.0MB
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
I'm assuming extract from the AP file (this is based on the downloaded file above)

boot.img.lz4

recovery.img.lz4

vbmeta.img.lz4

After that not sure if you a) modify the files and b) how create a new AP to load up into Odin
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
THANK YOU, I WON'T MODIFY ANY FILES. IF I MODIFY THOSE, YOU WILL HAVE A WARNING WHILE POWERING UP THE DEVICE..
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
There could be more then what I have posted - not sure how you created it
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
GIVE ME SOME TIME TO CREATE THE FILE..
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
JUST EXTRACT AND RECREATE THE MD5..
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
I WILL GIVE YOU THIS ON AROUND 10 PM (INDIAN TIMELINE)..
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
thank you -
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
Here is the file. Do with CAUTION..
[Samsung Galaxy A30s Guides, News, & Discussion] KPBHacker1kk:
THIS FILE SHOULD WORK WITH YOUR DEVICE IF YOU GAVE ME THE RIGHT OS LINK..
[Samsung Galaxy A30s Guides, News, & Discussion] braduv:
Thanks for the file - applied via odin - made no different - still in a boot-loop

I can still get into recovery mode and download mode - so I guess I'll just have to do wipe data / factory reset

Thanks for your help on this -
[G1 Android Development] jashsu:
I created a zeroed file with dd and attempted to mount it with:

mount -o loop /sdcard/test.img /data/test

and

losetup /dev/block/loop0 /sdcard/test.img

However, no loopback devices are displayed when I invoke mount. Can anyone clue me in? Feel like i'm missing something basic. By the way, I am running these commands from Saurik's busybox with the losetup /dev/block/loop fix.

p.s. I'd ask on the G1 hackers mailing list, but it's gone a bit bonkers in the past few days.
[G1 Android Development] JesusFreke:
I'm not sure, but doesn't the image file you're trying to mount have to contain an actual file system?
[G1 Android Development] jashsu:
Yea, I subsequently created a filesystem for it with mke2fs (which is mysteriously missing from busybox for android?). Still no go. Same when I tried to mount other partition-in-a-files like the module.cramfs or recovery.img :confused:

If I try to losetup the loop device then mount that, it returns error:

mount: mounting /dev/block/loop0 on /data/test failed: No such device

If I try to mount directly with -o loop, it returns:

mount: cannot setup loop device: No such file or directory

And yet Saurik seems to have been able to loop mount fine. Perhaps it is because I am testing on the qemu instead of hardware?
[G1 Android Development] JesusFreke:
That might be it. You might try busybox's mount also.

But yeah, It definitely does work on the phone at least.
[G1 Android Development] Koush:
I've been trying to figure out how to load debian on the emulator, but I can't get the ext2 image mounted. I had to recompile the kernel first so support loadable modules, but even after that, it would not work (can't remember the specific error). Has anyone gotten an ext2 file system mounted on the emulator successfully?

The reason I'm doing this is so I can do native compiles, without actually having to do it on the phone. It has advantages in that I can crank up the clock speed and the RAM.
[G1 Android Development] jashsu:
So I was able to mount loopback just fine on the actual hardware, but i'm having trouble getting it to run from the init.rc file. This is what i'm typing at the shell (it works):

(after insmod ext2.ko)

mount -o loop,noatime,nodiratime,nosuid,nodev -t ext2 /sdcard/loopy/app.img /data/app

It works fine and i'm able to install and run apks from the sdcard (/dev/block/loop2 on /data/app type ext2). Of course this is no good unless it can be mounted before the launcher starts (or it won't see any of our apks). The syntax for init mounting is different from sh, so I tried this (this is in /data/init.rc btw):

on userdata

#mount loopback file from sdcard

insmod /system/modules/2.6.25-01843-gfea26b0/kernel/fs/ext2/ext2.ko

mount ext2 /sdcard/loopy/app.img /data/app noatime nodiratime nosuid nodev loop

I know the script is being run since the ext2.ko module is getting installed. But the mount command isn't being executed. Can anyone shine a light on this? I'm not very familiar with the init daemon.
[G1 Android Development] JesusFreke:
Try

mount ext2 loop@/sdcard/loop/app.img /data/app noatime nodiratime nosuid nodev
[G1 Android Development] jashsu:
Tried that one earlier too. No love. :(
[G1 Android Development] JesusFreke:
I betcha the sdcard hasn't been mounted yet.

Is there anything in dmesg that looks relevant? Or maybe logcat?
[G1 Android Development] JesusFreke:
Try temporarily moving the image file to /data, and see if you can get it to mount. That should verify that it has something to do with it being on the sdcard
[G1 Android Development] jashsu:
Agh! You're right. The mount daemon runs at line 192, in the services section. Long after the /data/init.rc is parsed.

service mountd /system/bin/mountd

socket mountd stream 0660 root mount

Any way around this short of manually mounting the sdcard in the /data/init.rc?

Edit: dmesg bingo:

<3>[ 1.920368] init: unable to mount loop@/sdcard/loopy/app.img to /data/app

as ext2

<6>[ 1.921498] yaffs: dev is 32505860 name is "mtdblock4"

<6>[ 1.922016] yaffs: passed flags ""

<4>[ 1.922322] yaffs: Attempting MTD mount on 31.4, "mtdblock4"

<4>[ 1.927204] yaffs: restored from checkpoint

<4>[ 1.927845] yaffs_read_super: isCheckpointed 1

<3>[ 1.960002] init: unable to mount /system/xbin.cramfs to /system/xbin as c

ramfs

<3>[ 1.965221] init: service 'console' requires console

<4>[ 2.161895] mmc_sd_init_card: Delay 250 ms

<4>[ 2.522535] mmc1: host does not support reading read-only switch. assuming

write-enable.

<6>[ 2.523359] mmc1: new SDHC card at address cd4e

On a side note, it looks like the mount action for xbin.cramfs in the main init.rc is failing because it's redundant with an earlier mount in /system/init.rc. I'm guessing this is a vestige of development on cramfs loopback mounting (mentioned here by Saurik).
[G1 Android Development] JesusFreke:
Yeah, I had left in an extra mount for xbin.cramfs in the base init.rc. I believe that's fixed in v1.3. I'll check again and make sure :)
[G1 Android Development] dwang:
So I gather the reason for wanting to mount a loopback device is to be able to create an ext2 fs as a file on the sdcard fat fs instead of creating 2 separate parittions on the sdcard , one for fat and one for ext2?

If this can be done, this would be a much better solution for getting apps to run on the sdcard than the previous hack which requires creating an ext2 partition on the sdcard.
[G1 Android Development] jashsu:
Yeah that was what I was looking into. However as noted above, the I couldn't mount the image on the sdcard because the point at which /data/init.rc gets parsed occurs before the sdcard service starts up. The partition method doesn't have this problem because it creates a node for paritition #2 in the init.rc
[G1 Android Development] dwang:
so u can't mount the sdcard in /data/init.rc?
[G1 Android Development] jashsu:
Not sure, I didn't try mounting partition #1. You could give it a shot by using mknod in /data/init.rc like the parted sdcard method. The sdcard service might not like that the card has already been mounted though.

There are two major reasons I abandoned this concept. The first is I didn't want to figure out how to get permission to mount /sdcard (since / is ro). The second is that making the sdcard available as a usb mass storage device makes it exclusively unaccessible from Android. I suppose that might not be so bad if you are only offloading /data/app, as long as you don't try to execute any new apps while your mass storage connection is going. It's non-ideal.
[G1 Android Development] dwang:
I don't think the 2nd reason is that big of a deal. If google is planning on implementing the file based method for apps on the sdcard, they could just block access to apps when the sdcard is mounted to a pc. Its a lot better than the alternative of having to create a 2nd ext2 partition on the sdcard. Of course google should have really solved this issue before the g1 came out.

Anyways, I don't see /data/init.rc on my jf rc 1.2 g1. I only see /init.rc and /system/init.rc. Is /data/init.rc something that you created just for the purpose of mounting the file.
[G1 Android Development] jashsu:
Yeah it's referenced in /init.rc Easier to use since unlike /system/init.rc, it's not in a ro folder. You could use /system/init.rc too. Either way really.
[G1 Android Development] dwang:
Ok.. I'll probably just stick with partitioning the sdcard into fat and ext2. Its working well for me and there really isn't a whole lot of advantages having the ext2 as a file on the fat partition.

I have 41 apps installed on the sdcard now (including some huge games like bonzai blast and brain genius deluxe) and I still have 59 megs of free internal storage. I think everybody that has a rooted g1 should put apps to the sdcard.
[Verizon Samsung Galaxy S7 Edge Questions & Answers] alpitu21:
Hi, i have a SM-G935V on android 6.0.1 bootloader B1 and security patch of February 1st, 2016. Is this rare? Can i backup it and restore from it in any way? I want to rom this phone to unlock its carrier. Thanks!
[Verizon Samsung Galaxy S7 Edge Questions & Answers] dave678:
Where did you buy it? Yes that's rare. Unlock for what carrier?
[Samsung Galaxy A54 5G] nyddoT:
I need help on adding Camera 2 API Full and RAW compatibility on Exynos 1380, I can decompile the necessary blobs, but without a light or documentation on which path to follow, makes things tricky. Any help is appreciated.
[Samsung Galaxy S21 Ultra] tonyharr:
Hi There

I updated the firmware on my S21 ultra in Dec 2022.

But since then have not received any security updates. This worries me, but the phone has been rock solid.

Is there anyway to get just the updates rather than flashing the firmware again? I spent days on it... lol

AP G998USQS5DVL3

CP G998USQS5DVL3

CSC G998UOYN5DVL3

MODEL SM-G998U/DS

Also, I managed to flash the firmware with OEM unlocking. Is that a problem.?

Regards

Tony...
[Samsung Galaxy S21 Ultra] Ronnie McNutt:
change csc with samfw tool
[Samsung Galaxy S21 Ultra] tonyharr:
I’ve read that changing the csc to THL gives all the updates. Would you recommend using THL or another csv? Thanks for your help.
[Samsung Galaxy S21 Ultra] Ronnie McNutt:
I don't know as i dont have this device but the same issue happend to my s20 fe 5g and I solved it by changing csc I dont remember which you can experiment and find which csc gives you ota you will not lose your data by changing csc

Edit: Try CHA csc i checked it on samfw ,the latest patch is OneUI 5.1 August 2023
[Samsung Galaxy S21 Ultra] TacoNikky:
XID recommended because it has more features. For example auto call record, some extra quick setting toggles.
[Samsung Galaxy S21 Ultra] tonyharr:
Hi there. So I've downloaded Samfw Frp tool but every time I try to install my AV picks it up as a Malicious application. Is that normal?

Tony...
[Samsung Galaxy S21 Ultra] Ronnie McNutt:
It's most likely false positive
[Samsung Galaxy S21 Ultra] robot1000:
I have the same issue. The only way I've been able to update is through plugging my phone into my laptop and running the Samsung Switch application. This then gives the option of updating the firmware to the latest version.
[Samsung Galaxy S21 Ultra] tonyharr:
OK, so a Bit more information. So I bought this phone brand new in NZ. Turns out that it is a USA import and was originally locked to VZW (Verizon Wireless). Then I updated to One UI 5 with GCF as the country code. Esim doesn't work, call recorder doesn't work, and I get no updates.

Wondering what I should do next. I would like a reliable phone that gets updates on a regular basis.

I asked if Samsung themselves could do anything to help and they wont look at it. Screenshot attached.

Any help would be greatly appreciated.
[Google Pixel 7a] Shrek617:
Hello! Can I rollback my Pixel 7A from Android 14 to 13?
[Google Pixel 7a] Dayuser:
Why do you want rollback to older Android version?
[Google Pixel 7a] Shrek617:
I thought it was a little slow my Pixel with Android 14
[Google Pixel 7a] 306bobby:
You'll lose your data, but use the Android flash utility

Flash Tool
[General Questions and Answers] Phoenix3426:
On one hand, GrapheneOS' installation instructions strongly recommend locking the bootloader after install. On the other hand, I found ominous threads warning against locking the bootloader unless you're on 100% stock. I obviously don't want to brick my phone, but I do want the security advantages that come with verified boot.

What should I do? Suppose my GrapheneOS install refuses to boot. Can I still maneuver my way out of this if I lock the bootloader?
[General Questions and Answers] V0latyle:
As a general rule, never lock the bootloader unless you're on factory firmware.

The one caveat to this is when a custom root of trust key is set. GrapheneOS does this.

One of the functions of the bootloader is to authenticate the firmware on the device. Under normal conditions - factory firmware and bootloader locked - the bootloader is able to verify the authenticity of the boot image using the cryptographic keys set by the OEM. This prevents unauthorized software from running, such as a boot image that's been modified by an exploit with root access. This is Android Verified Boot.

Unlocking the bootloader does two things. One, it allows flashing of partitions from fastboot; normally, only authenticated packages may be installed from recovery. Two, it disables the authentication security, so unsigned images may now be flashed and run.

If the bootloader is locked with unsigned firmware installed, or if the firmware has not been signed with the cryptographic keys in the root of trust, the phone will fail to boot, and in some cases it may not be possible to unlock the bootloader again.

The reason GrapheneOS and a few others are able to run on a locked bootloader is because they set a new root of trust - they install new keys - that has been used to sign their firmware. Thus, when the bootloader is locked, it is able to authenticate their firmware with the custom keys, although the bootloader will warn about this: Yellow State

If you're concerned, you can leave it unlocked which will make things a lot easier if something goes wrong.

However since you want to have the protection of AVB, I would recommend this: Keep bootloader unlocked, install GrapheneOS, make sure it boots and runs correctly, then relock the bootloader. This should be safe since you've verified that it boots successfully.
[G1 Apps and Games] pdspatrick:
A very good vnc solution that is *actually* useable....It's beyond me as to why this isnt on the market (maybe its the $25?)

Play around with it...its quite fun...
[G1 Apps and Games] UnkzDomain:
Where's the link?

Is this it: http://code.google.com/p/android-vnc-viewer/ ?