yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] shabbypenguin:
I'll just go ahead and say this here, i hope no one sends this file on any phone at any time. nothing personal by any means, but your efs partition contains your devices IMEI. early on in android devices people would get ahold of someone elses efs partition and it would mess up both devices, nowadays on devices like the s4 it actually just corrupts the image when it reads the hardware values and compares to the image. but still having the image given freely is a fairly large security risk (with someones IMEI you can clone their device and report it lost/stolen blacklisting the device for the true owner and much more.)

if it truly is your efs partition there have been several tools which claim they can repair it, this is my second GSM device and ive made sure to backup EFS on both as soon as i got root so ive no idea if they work or not. seems kind of odd though that EFS would prevent you from booting, in all other cases i know about it just blanks out your cell signal stuff.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Yeah here's my problem I'm pretty sure. The nandroid doesn't backup the EFS but boot, recovery, cache, system and data. I quess the nandroid is the same as the CWM backup right? If not then I don't have nandroid but CWM backup. So maybe someone can help me with a EFS backup or I might even have to buy another used one, doh!

Partition table for SGH-T399

BOTA0 -> /dev/block/mmcblk0p1	4.0MB

BOTA1 -> /dev/block/mmcblk0p2	4.0MB

EFS -> /dev/block/mmcblk0p3	19.7MB	ext4

m9kefs1 -> /dev/block/mmcblk0p4	4.0MB

m9kefs2 -> /dev/block/mmcblk0p5	4.0MB

m9kefs3 -> /dev/block/mmcblk0p6	4.0MB

CARRIER -> /dev/block/mmcblk0p7	4.0MB

PARAM -> /dev/block/mmcblk0p8	8.0MB

BOOT -> /dev/block/mmcblk0p9	8.0MB

RECOVERY -> /dev/block/mmcblk0p10	8.0MB

OTA -> /dev/block/mmcblk0p11	8.0MB

CDMA -> /dev/block/mmcblk0p12	4.0MB

RADIO -> /dev/block/mmcblk0p13	32.0MB

TOMBSTONES -> /dev/block/mmcblk0p14	4.0MB

TDATA -> /dev/block/mmcblk0p15	4.0MB

HIDDEN -> /dev/block/mmcblk0p16	4.0MB

RESERVED1 -> /dev/block/mmcblk0p17	4.0MB

RESERVED2 -> /dev/block/mmcblk0p18	4.0MB

CACHE -> /dev/block/mmcblk0p19	492.1MB	ext4

SYSTEM -> /dev/block/mmcblk0p20	1378.0MB	ext4

USERDATA -> /dev/block/mmcblk0p21	5330.9MB	ext4
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] smartguy044:
Yea efs just makes you lose your baseband so phone still boots. It happened to me on my s3. Before you said your backup couldn't be flashed because of md5 mismatch that's why I said move the folder to try and see if it will flash. If you can flash system and boot.img I would do a full wipe meaning factory data reset, cache and system then restore. As shabby penguin said efs should just make you lose signal not cause a boot loop.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Hmm.... I still have corrupted data in CWM but everything else is OK.

c28e382964a0150a627254d9b3954821 boot.img god

d41d8cd98f00b204e9800998ecf8427e cache.ext4.tar good

7eb0e23aadf3bd475910b307aed80ef6 cache.ext4.tar.a good

d41d8cd98f00b204e9800998ecf8427e data.ext4.tar good

2ef2d279631e5fbe6ae9ba1af7981335 data.ext4.tar.a good

1fc42e24e93940bed5c0aa288baf2868 data.ext4.tar.b bad e89ad26275402f4308e637e7ead52278

dc8132337730574b7e8f2d144286880a data.ext4.tar.c bad 5117ad8977eaf88ddfef558a96ccd8e9

748e80dcb3fa05250efa0a8e39db48ed recovery.img good

d41d8cd98f00b204e9800998ecf8427e system.ext4.tar good

123a46a1b8d65cc42d37fd0b2d24185f system.ext4.tar.a good

621b8c942b833ac4c98270ee567b87a2 system.ext4.tar.b good

So could manipulate the nandroid.md5 and restore boot and system with CWM but data is corrupt. If the EFS is not the problem then whats your guess about this loop...

---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------

Say, let me know if you think I should start my own thread or something. I know this is primary CWM for SGH-T399 so my boot problem may not be best here...

---------- Post added at 10:51 PM ---------- Previous post was at 10:44 PM ----------

I still think it's EFS though because when in CWM I can mount /cache, /system, /data, /external_sd but when I try to mount /efs I get "Error mounting /efs!".
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] smartguy044:
Might need to see if someone will make you an Odin or cwm flashable stock Rom. This means you will have to start from scratch but it might be the only way to fix the problem
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Lol, I would be more than happy because my nandroid data files are corrupt and I already tried cwm factory reset. Hope someone make an efs backup and post so I can download, format efs partition, create cwm zip, and flash efs. If not I'll have to wait for rom or Odin. Thanks.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
If you use someone else's /efs, it will have their bt/wifi mac addresses, serial # and IMEI
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Bummer but we can change those with Odin? Maybe? Man I'm hosed? Doh!
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] tazmaniondvl:
[MENTION=2614663]shabbypenguin[/MENTION] or [MENTION=4525591]smartguy044[/MENTION] do either of you know how to make that happen? Stock Rom
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Ok somehow I missed important comments from smartguy and shabbypenguin but I understand now. Since using someone elses efs could cause problems and not having efs backup looks like I'm toast. The efs partition won't even mount so its worse than corrupt or incorrect. This is my first brick. I wish I could recreate own efs from data on the box or something.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] shabbypenguin:
efs wont mount on anyone's device, its not a file system. just one giant file. as i mentioned i dont think you overwrote your efs though, perhaps something more useless like param or hidden and its causing the bootloop. we know its not the bootloaders and we know its not system/data/boot/recovery/cache.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Wow, for me that's good news. It's also great that you devs are willing to share your time and knowledge. At least I can still access the device via adb, odin, etc... Never give up right... LOL

---------- Post added at 04:17 AM ---------- Previous post was at 04:05 AM ----------

If I open an ADB shell I see an efs directory with a wifi folder that is empty

..$ adb shell
root@android:/ # ls
acct
cache
config
d
data
default.prop
dev
[COLOR="DarkRed"]efs[/COLOR]
etc
fstab.universal_garda
init
init.carrier.rc
init.goldfish.rc
init.rc
init.trace.rc
init.universal_garda.rc
init.universal_garda.usb.rc
init.usb.rc
lib
lpm.rc
mnt
proc
root
sbin
sdcard
storage
sys
system
tmp
ueventd.goldfish.rc
ueventd.rc
ueventd.universal_garda.rc
vendor
root@android:/ # cd efs
root@android:/efs # ls
wifi
root@android:/efs # cd wifi
root@android:/efs/wifi # ls
root@android:/efs/wifi #

Ah never mind I keep getting stuck on efs and it's probably something else.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] shabbypenguin:
that the only file? if so then efs probably has been wiped. still wouldnt explain bootloops though :/
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
yeah, there isn't even a file just /efs and /efs/wifi folders? I've been looking at the loop errors and the run time seems to be having a problem. Wonder if it's the dalvik?

03-09 00:03:49.820: E/AndroidRuntime(4098): !@*** FATAL EXCEPTION IN SYSTEM PROCESS: main
03-09 00:03:49.820: E/AndroidRuntime(4098): java.lang.NullPointerException
03-09 00:03:49.820: E/AndroidRuntime(4098):	at com.android.server.pm.PackagePrefetcher.prefetchInner(PackagePrefetcher.java:166)
03-09 00:03:49.820: E/AndroidRuntime(4098):	at com.android.server.pm.PackagePrefetcher.prefetchPackages(PackagePrefetcher.java:160)
03-09 00:03:49.820: E/AndroidRuntime(4098):	at com.android.server.SystemServer.main(SystemServer.java:1908)
03-09 00:03:49.820: E/AndroidRuntime(4098):	at java.lang.reflect.Method.invokeNative(Native Method)
03-09 00:03:49.820: E/AndroidRuntime(4098):	at java.lang.reflect.Method.invoke(Method.java:511)
03-09 00:03:49.820: E/AndroidRuntime(4098):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1102)
03-09 00:03:49.820: E/AndroidRuntime(4098):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:869)
03-09 00:03:49.820: E/AndroidRuntime(4098):	at dalvik.system.NativeStart.main(Native Method)
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
My /efs
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Dang, I only have and empty wifi folder
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
There 5 hidden files a 1 hidden folder in /efs as well. You can edit the serial/imei/mac addresses, so copying someone else's partition could work. I'm not sure how much more editing would be needed, I'm not exactly sure what some of the files are for.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
I figured there would be some hidden stuff, thanks. Something tells me that it's not that easy to rebuild an efs though.

---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------

The worst part is the Light had the new smaller sim that doesn't fit any of my older t-mobiles, doh!
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] smartguy044:
I will try and get you a stock zip to flash to see if that will help you out
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
You can buy a sim adapter for $1 online or $5 at T mobile

How about a generous person doing a factory reset then donating a CWM backup of their reset device? (Assuming they did a backup beforehand to restore from, of course)

Edit: Still may may serial/imei/mac issue
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] smartguy044:
shouldnt have an issue with that. if someone supplies a back up just upload system and boot imgs. do not upload data etc
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
My CWM system, recovery, boot and cache were all ok with MD5. Only the data was corrupt in the nandroid. I already restored boot and system from CWM advanced and by manipulating nandroid.md5 but still boot looping.

---------- Post added at 04:02 PM ---------- Previous post was at 03:54 PM ----------

But I guess trying another boot and system cwm images would could help if something was wrong even if they passed the md5.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] smartguy044:
did you ever try putting them on your internal sd card and trying to do a restore like that
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Oh I guess you mean the whole clockworkmod folder on internal SD. I guess I could try but I have moved stuff around a bit. The MD5 on data fails on two copies of backups on 2 separate PC as well. I had the nandroids on PC's as I had just setup Bit Torrent Sync to keep music/photos/videos backed up locally across two machines and I did the same for backups like Titanium and CWM.

So when I experienced the initial boot loop the cwm backups were on the PC's as I had just re-partitioned the EXT SD. So now since the copies that are BT Synced fail MD5SUM check on data files I'm not sure would good it would do to put them on the internal sd and try to restore from cwm.

---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------

The part I don't get is that I did a factory reset and wiped the cache then restored boot and system cwm. The data and cache should be recreated on boot but I still boot loop. So it seems like something outside of what CWM can restore.

But I'm trying to restore CWM from internal SD right now.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] RaverX3X:
Just so they know you dont need someone elses efs file.. You can restore it from the nvdata and the nvdata backup.. you could completly wipe the efs folder it will remake it on boot and restore it from any backup of nvdata you had... Why people still ask for someone elses efs folder escapes me thanks for putting the warning out there.

also helpfull if theres a stock odin... Humm going to have to check my source on getting the stock odin image.. You can completly hose it 9 times out of 10 if u can get to a stock recovery from factory it will re provision your first boot might be 00000s but it will correct..

NEVER EVER EVER GIVE YOUR EFS OR NVDATA FILES TO ANYONE ASKING TO RECOVER THERE DEVICE... EVER.

Off chance that a developer asks for it make sure you know what your getting into.. Sometimes we do use them for hex editing unlockers. But we will a ask for your permission first second Tell you what were doing with it and thirdly. Give you the unlock code if successful. Thats only if we wanna test it on a device we dont own and or we already unlocked our device and want to say make sure it unlocks on someone elses.

Most the time we wont ask for it...
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
boot.img will probably fix smith's issue. Not a flashable zip, but workable. I'll try to post a /system folder later.

Good advice. /efs should be rebuildable, even if you end up manually creating some folders/files.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
[YOUTUBE]Y3wND2UKsnw[/YOUTUBE]

THANKS ALL!
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
Happy=Progress or Happy=Fixed?

Have you restored or repaired /data?

03-09 00:04:06.545: E/SecBandwidthController(5129): SecBandwidthController::enableBandwidthControl

03-09 00:04:06.545: E/SecBandwidthController(5129): information file open failed (No such file or directory)

03-09 00:04:06.545: E/SecBandwidthController(5129): backup file open failed (No such file or directory)

03-09 00:04:07.325: E/connfw(2784): connect error:2

03-09 00:04:07.380: E/DTT(2783): connect error:2

03-09 00:04:07.450: E/SMD(2781): connect error:2

03-09 00:04:07.765: E/cutils(5397): Failed to read /data/.layout_version: No such file or directory

03-09 00:04:07.765: E/installd(5397): Could not create directories; exiting.

03-09 00:04:07.765: E/keystore(5398): chdir: /data/misc/keystore: No such file or directory
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] RaverX3X:
The thing is with a official stock recovery will recreate the EFS folder properly which on a new device contains no user info sense that gets provisioned by the your carriers network with your info.. Phones dont contain any user info tell after activated for your account and or sim card is inserted. So a user created odin dump wont rebuild the afformentioned folder because it doesnt have a stock blank nvdata file to re create the /efs folder and its user contents. Hence why its a good idea to make a backup. Also the Nvdata files typically are not held n the /etfs folder if they are there is a backup thats also contained in encrypted parts of the rom that generally doesnt get wiped.

Nornally the only real way to completely brick your device would be to write garbage to the PBL and SBL of any given device. Primary boot loader and secondary bootloader.. Priimary bootloader isnt actually responsable for booting the device it contains things like the devices system parttion info for the NAD device. Booting gets handed off to the SBL then invokes the android kernel to start boot and init scripts and upstart.

The other way would be to completly scramble the devices Partition info to the point the device wouldn't know what to do with it.. if you can get to download mode try kies.. Im still working on the kies dump and makeing a workable odin/Hemidal counterpart that doesn't require aforementioned kies. i took my device and thew it in recovery mode and did an emergency recovery though kies to get the files.. They don't give a pit file so using Reparitioning wont be plauseable without a Pit file but stock recovery and 1 click to recovery will be ok.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] RaverX3X:
Have you tried using the fstab mount info for your CWR to see if you can mount it without having to do external sd then 0

Also internal sd typlically is just mounted as emmc I havent even played with recovery as i just been working out stock recovery options for people that will eventually need it...
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
xda really should give this device it's own page.

I'm off topic, but can we get usb otg working?
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
...Just happy that smart people like you are helping...

Nah, I think that's really the problem. I have a CWM backup but the data files where the only ones that failed the MD5. Manipulating nandroid.md5 and restoring data anyway still resulted in a boot loop. I also restored boot and system. No need to restore recovery or cache. Since efs won't stop the boot it must be corrupted /data creating the loop. I also have a Titanium Backup "all.zip" that include apps and data, I've never had success with TB zips and CWM. This zip is no exception.

---------- Post added at 09:05 AM ---------- Previous post was at 08:51 AM ----------

I can get to download mode and I have a yellow or blue com with Odin depending on the version. Kies is a bit different in that it just keeps displaying "Connecting..." while the device is in download mode. Oh and out of desperation I used CWM to format the internal SD, to try to make room for the large Titanium all.zip that did not work from extsd, so now if only shows as MTP. Doh!
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] inyork:
Anyone know of any custom roms being worked on for the T399?
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
I don't understand why Samsung doesn't have a recovery process or why the stock rom is not available. Is this a t-mobile proprietary thing?
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
adb no longer works?
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
No adb still works. On a linux box the device is reported as "47903095a11a307b device" while boot looping and "47903095a11a307b recovery" while in CMW. It's just the after formatting the SD with CWM the device no longer shows as an accessible file system under linux or windows. However, adb and adb shell are fine.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
Can't repair files if you can't access them. Maybe restoring the usable backup files you have will give access back.

Unfortunately, I think you're stuck til we have a flashable ROM.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
I can access files via adb and adb shell. But if someone could post adb shell "mounts" and "cat /proc/partitions" it would help me see if the problem is worse than I thought regarding partitioning.

Boy, I never wished of an Android OS update release from T-Mobile so bad in my life... LOL
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] RaverX3X:
shell@hammerhead:/ $ cat /proc/self/mountinfo better then using the standard cat /proc/mounts
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] RaverX3X:
umm kies emergency recovery mode should work with the device in just download mode... You should not need the kies driver just the standard recovery driver should work.
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
Partitions

root@android:/ # cat /proc/partitions

cat /proc/partitions

major minor #blocks name

179 0 7634944 mmcblk0

179 1 4096 mmcblk0p1

179 2 4096 mmcblk0p2

179 3 20480 mmcblk0p3

179 4 4096 mmcblk0p4

179 5 4096 mmcblk0p5

179 6 4096 mmcblk0p6

179 7 4096 mmcblk0p7

259 0 8192 mmcblk0p8

259 1 8192 mmcblk0p9

259 2 8192 mmcblk0p10

259 3 8192 mmcblk0p11

259 4 4096 mmcblk0p12

259 5 32768 mmcblk0p13

259 6 4096 mmcblk0p14

259 7 4096 mmcblk0p15

259 8 4096 mmcblk0p16

259 9 4096 mmcblk0p17

259 10 4096 mmcblk0p18

259 11 512000 mmcblk0p19

259 12 1433600 mmcblk0p20

259 13 5545984 mmcblk0p21

179 16 15351296 mmcblk1

179 17 15347200 mmcblk1p1

root@android:/ #

and

BOOT -> /dev/block/mmcblk0p9

BOTA0 -> /dev/block/mmcblk0p1

BOTA1 -> /dev/block/mmcblk0p2

CACHE -> /dev/block/mmcblk0p19

CARRIER -> /dev/block/mmcblk0p7

CDMA -> /dev/block/mmcblk0p12

EFS -> /dev/block/mmcblk0p3

HIDDEN -> /dev/block/mmcblk0p16

OTA -> /dev/block/mmcblk0p11

PARAM -> /dev/block/mmcblk0p8

RADIO -> /dev/block/mmcblk0p13

RECOVERY -> /dev/block/mmcblk0p10

RESERVED1 -> /dev/block/mmcblk0p17

RESERVED2 -> /dev/block/mmcblk0p18

SYSTEM -> /dev/block/mmcblk0p20

TDATA -> /dev/block/mmcblk0p15

TOMBSTONES -> /dev/block/mmcblk0p14

USERDATA -> /dev/block/mmcblk0p21

m9kefs1 -> /dev/block/mmcblk0p4

m9kefs2 -> /dev/block/mmcblk0p5

m9kefs3 -> /dev/block/mmcblk0p6
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Hmm, anyone know how to boot into Emergency Recovery Mode or did we wipe that with CWM? Doesn't work with the device in download mode. Well it actually says Odin mode. Maybe I'm in the wrong mode?

---------- Post added at 03:58 AM ---------- Previous post was at 03:55 AM ----------

What command produces this output?

BOOT -> /dev/block/mmcblk0p9

BOTA0 -> /dev/block/mmcblk0p1

BOTA1 -> /dev/block/mmcblk0p2

CACHE -> /dev/block/mmcblk0p19

CARRIER -> /dev/block/mmcblk0p7

CDMA -> /dev/block/mmcblk0p12

EFS -> /dev/block/mmcblk0p3

HIDDEN -> /dev/block/mmcblk0p16

OTA -> /dev/block/mmcblk0p11

PARAM -> /dev/block/mmcblk0p8

RADIO -> /dev/block/mmcblk0p13

RECOVERY -> /dev/block/mmcblk0p10

RESERVED1 -> /dev/block/mmcblk0p17

RESERVED2 -> /dev/block/mmcblk0p18

SYSTEM -> /dev/block/mmcblk0p20

TDATA -> /dev/block/mmcblk0p15

TOMBSTONES -> /dev/block/mmcblk0p14

USERDATA -> /dev/block/mmcblk0p21

m9kefs1 -> /dev/block/mmcblk0p4

m9kefs2 -> /dev/block/mmcblk0p5

m9kefs3 -> /dev/block/mmcblk0p6[/QUOTE]
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] tazmaniondvl:
[/QUOTE]

Lol odin, is download mode home key plus volume down plus power, then press volume up and your in download mode
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] GJSmith3rd:
Right just wanted to be sure. I just tried "Firmware Upgrade and Initialization with Kies Model and Serial number but Kies reports "SGH-T399 does not support initialising." Doh! :eek:
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
[/QUOTE]

Try running Kies as administrator while bootlooping. EFR is supposed to work if the ROM is borked, but since there's been no update, maybe it just won't. I haven't seen a way to manually force EFR other than to unplug a phone during a Kies update.

Cleaned up version of "ls -l /dev/block/platform/*/by-name"
[Samsung Galaxy Light ROMs, Kernels, Recoveries, & ] awd_fan:
I started a General Discussion thread for the SGH-T399 http://xdaforums.com/showthread.php?p=51146757#post51146757